| 1 |
Theo Chatzimichos wrote: |
| 2 |
> > > Another option that looks nice is GitLab. |
| 3 |
> > |
| 4 |
> > How does it work? The screenshots look exactly like github. |
| 5 |
> |
| 6 |
> Don't ask, just go for it! |
| 7 |
|
| 8 |
That's not very helpful? |
| 9 |
|
| 10 |
I'm happy to expand on my experience with Gerrit, and I'll gladly |
| 11 |
answer specific questions if I can. |
| 12 |
|
| 13 |
|
| 14 |
> It's a few steps to set up, but it's not too bad. |
| 15 |
|
| 16 |
Great! Have you run it in production or in a lab? Did you encounter |
| 17 |
any non-obvious issues? |
| 18 |
|
| 19 |
|
| 20 |
> I agree that github is sucky, but I don't think rejecting GitLab |
| 21 |
> just because it looks exactly like Github makes sense. |
| 22 |
|
| 23 |
Where did you get the idea that anyone is rejecting GitLab? |
| 24 |
|
| 25 |
Especially surprising that you think that *I* would reject GitLab, |
| 26 |
since I'm not even a developer. |
| 27 |
|
| 28 |
(Comparing github with Java doesn't make much sense.) |
| 29 |
|
| 30 |
|
| 31 |
> Look at what the application does and how it works first. |
| 32 |
|
| 33 |
Yes indeed, obviously I tried that, but the gitlab.org webpage |
| 34 |
doesn't have a lot of information beyond the github-like screenshots. |
| 35 |
|
| 36 |
Hence my question to the list, where perhaps someone can talk about |
| 37 |
gitlab based on their experience. |
| 38 |
|
| 39 |
All pointers to better resources are surely appreciated not only by me. |
| 40 |
|
| 41 |
|
| 42 |
//Peter |
Archives