Fwd: Re: [Kde-pim] Problems with infrastructure

[Luca Beltrame]

Sending this to k-c-d, probably has been sent to me only by mistake: it offers 
additional insights on software.

---------  Messaggio inoltrato  ---------

Oggetto: Re: [Kde-pim] Problems with infrastructure
Data: sabato 13 dicembre 2014, 08:21:15
Da: Helio Chissini de Castro <helio at kde.org>
A: Luca Beltrame <lbeltrame at kde.org>

On Fri, Dec 12, 2014 at 8:25 PM, Luca Beltrame <lbeltrame at kde.org> wrote:
>
> Albert Astals Cid wrote:
>
> > So what do you suggest, because we already tried gitlab and didn't work,
> > is there any more github clones out there that may work for us? I don't
>
> There are at least a couple:
>
> - Gitbucket (written in Scala, mimics the GitHub interface)
> - Gogs (written in Go, see my previous mail on the topic)
>
> I've used both, but not at the scale KDE needs, though. ;)
>
> Gitbucket:
>
> - Uses its own embedded SSH (!) on a non standard port (like Gerrit)
> - There are a few issues with documentation
> - Java / Scala (not everyone's cup of tea)
> - Supports LDAP like KDE needs
> - No information on performance
> - No information on large number of repositories
> - Probably no customization of appearance
>
> Gogs:
>
> - Fast and lean
> - Go (not everyone's cup of tea)
> - Uses the system's SSH
> - Does not support yet LDAP like KDE wants (I filed issues about it
> upstream)
> - Inconsistent UI (not yet finished)
> - No information on customization of appearance
> - Strange way of configuration (copy ini file elsewhere, modify)
> - Behind Gitbucket in terms of features
> - No information on performance
> - No information on large number of repositories
>
> Gitbucket: https://github.com/takezoe/gitbucket
> Gogs: https://gogs.io
>
> Hope this helps.
>
> --
> Luca Beltrame - KDE Forums team
> KDE Science supporter
> GPG key ID: 6E1A4E79
>
>
>
Let me enter on this discussion :-)

In my previous company we used mercurial and for same reason they started
to look some open source frameworks like github, discarding any paid
solution.

We had three ones on plate:

- Phabricator
http://phabricator.org/
https://github.com/phacility/phabricator

- Apache Allura
https://allura.apache.org/

- Rhodecode
http://rhodecode.com
This is the one we choosed, and is indeed very powerfull, the only part is
that company behind it closed the source, but a fully open source fork is
been done
https://kallithea-scm.org/

So i'm throwing this three for us and maybe if one of then fit, we can use
the same strategy we did years ago when we needed deal with svn, then git,
then anything we used, help providing some code.

Hope this helped in some way.

Helio
------------------------------------------
-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: 6E1A4E79
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20141215/e13245e0/attachment.sig>