Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects 
I really like Pagure [1] it takes project hosting to another decentralization level by applying same git techniques not only to code but to docs, issues and so on [2].
This is just for giving more options to people not advertisement to migrate/integrate/etc and being fully open source is nice benefit in my eyes.


[1] https://pagure.io/pagure
[2] http://blog.pingoured.fr/index.php?post/2015/03/25/Progit-is-dead%2C-long-live-pagure

Alexander Kurtakov
Red Hat Eclipse team

----- Original Message -----
> From: "Simon Bernard" <sbernard@xxxxxxxxxxxxxxxxxx>
> To: "Mailing list for all people involved in Eclipse project management" <eclipse.org-project-leadership@xxxxxxxxxxx>
> Sent: Tuesday, 10 November, 2015 6:02:57 PM
> Subject: Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects
> 
> I thought using the the Community Edition.
> Which features are missing in this one ? =>
> https://about.gitlab.com/features/
> 
> Le 10/11/2015 16:44, Werner Keil a écrit :
> 
> 
> 
> Looks like a self-hosted variant of GitHub;-)
> Or if you want like Jenkins does to Hudson or vice versa.
> If you look at https://about.gitlab.com/features/
> The Community Edition seems very restricted compared to the Enterprise
> Edition, so do you suggest Eclipse Foundation should buy or subscribe the
> Enterprise one?
> Gesendet: Dienstag, 10. November 2015 um 16:36 Uhr
> Von: "Simon Bernard" <sbernard@xxxxxxxxxxxxxxxxxx>
> An: "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx> , "Mailing
> list for all people involved in Eclipse project management"
> <eclipse.org-project-leadership@xxxxxxxxxxx>
> Betreff: Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse
> Projects
> Le 10/11/2015 16:15, Mike Milinkovich a écrit :
> > On 10/11/2015 9:35 AM, Alexandre Montplaisir wrote:
> >> Migrating to GitHub means becoming dependant on a proprietary
> >> platform. This was not the case in the CVS -> Git migration.
> > This is true. And that is why we have added a requirement for "freedom
> > of action" for all infrastructure. If GitHub was to go away tomorrow, we
> > will need to be able for all affected Eclipse projects to be able to
> > continue unabated.
> > 
> >> There is imo no question that the user experience on GitHub is miles
> >> better than on Bugzilla. However I think we have to be very careful
> >> before deciding to become entirely dependant on a third-party.
> > Agree 100%. Much careful thinking went into this.
> > 
> >> I would much prefer if we could have an open-source ALM management
> >> platform hosted at Eclipse.
> > So would we all. But since an industrial-grade ALM management project
> > has not yet appeared, we have to deal with the facts as they are.
> 
> This solution exist, this is gitlab. This is open source and could be
> hosted by the eclipse foundation.
> Gitlab seems to resolve all the issues raised here. I think this
> solution should be really considered.
> _______________________________________________
> eclipse.org-project-leadership mailing list
> eclipse.org-project-leadership@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership
> 
> IMPORTANT: Membership in this list is generated by processes internal to the
> Eclipse Foundation. To be permanently removed from this list, you must
> contact emo@xxxxxxxxxxx to request removal.
> 
> 
> _______________________________________________
> eclipse.org-project-leadership mailing list
> eclipse.org-project-leadership@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership
> 
> IMPORTANT: Membership in this list is generated by processes internal to the
> Eclipse Foundation.  To be permanently removed from this list, you must
> contact emo@xxxxxxxxxxx to request removal.

Back to the top