[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian github organization ?



On Thu, 2015-04-16 at 19:37 +0200, Sven Bartscher wrote:
> On Thu, 16 Apr 2015 09:04:07 -0600
> Dimitri John Ledkov <xnox@debian.org> wrote:
> 
> > I'd rather see gitlab.debian.net :)
> 
> I don't  a reason to have gitlab/github/someother git stuff for debian,
> since we already have alioth.
> Maybe someone can enlighten me.

Probably not.  UI's are a personal thing and if you've looked at the
others and still the UI provided by FusionForge, that's unlikely to
change.

But do acknowledge that makes you unusual.  Github has all but
annihilated SourceForge in the hosting market place, and the stand out
change is it's UI.  That is in spite of SourceForge's impressive mirror
network and SourceForge being VCS agnostic.  So it's not surprising some
DD's want to move away from the FusionForge UI.

I'm on SourceForge now.  [0]  I'd prefer to be on Debian's
infrastructure of course, but Alioth is so poorly maintained it was
unusable for me [1].

Of the suggestions so far only Kallithea is VCS agnostic, but Kallithea
only supports source code hosting - no Ticketing (eg bug tracking), no
web project web page, no release hosting (binaries).  Maybe that's an
advantage for Debian projects because it forces you to use Debian's
existing infrastructure for everything else, but for me it makes it a
no-go.

Gogs looks to be similar, but is unstable.  Gitlab is git only and
doesn't support releases.

SourceForge's Apollo is an open source project supporting all those
features plus a heap more, but the UI is not "code centric" like the
others - it feels more like FusionForge.  That said, unlike FusionForge
modern work flows (forking, pull requests and the like) - it's just they
aren't a prominent in the UI.



[0]  http://sourceforge.net/u/rstuart/

[1]  https://lists.debian.org/debian-devel/2014/05/msg00463.html

     That triggered this response, but it read like someone in denial
     rather than acknowledging the problem:

     https://lists.debian.org/debian-devel/2014/06/msg00435.html

     Acknowledging the problem is always the first step in fixing it,
     and I think it's significant the number of open bugs has gone up by
     20% since then.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: