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
The issue about GitHub Issues is not one of technology, but rather one of culture & behavior.  To get a full picture of this, I could try and write some notes, but I would never author it as articulately as Stephen O'Grady in Developers are the New Kingmakers.  It's a short 2 hour read and is a wonderful articulation of the evolution of choices within developer communities.  I would encourage everyone to read this to have an appreciation of the context.

Tyler

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55


On Tue, Nov 10, 2015 at 9:29 AM, Simon Bernard <sbernard@xxxxxxxxxxxxxxxxxx> wrote:
Of course you could approve pull request in Community Edition... The feature you point is just to configure rules which force to have several comitter approval before to merge. AFAIK, this is not available in github too...
"The CE has nothing to offer, Eclipse Git or other infra doesn't already do", you could say that too for github ... The reality is something is missing a better user experience, that's why so many people want to use github.
GitLab offer the same kind of use experience than github, with the benefits to be open source and so could be self-hosted or hacked.

Did you already test it or you make your opinion in 2 seconds just by look at the pictures ...

I'm not sure if gitlab could fit perfectly the needs of eclipse foundation, but I thought this should be at least considered.



Le 10/11/2015 17:46, Werner Keil a écrit :
The CE has nothing to offer, Eclipse Git or other infra doesn't already do. I mean
"Ability to fork a repository" is free, but for "Approve Merge Requests" one has to pay.
Sorry but Eclipse already got Gerrit and does not need to pay for that to another vendor;-)
 
Gesendet: Dienstag, 10. November 2015 um 17:42 Uhr
Von: "Simon Bernard" <sbernard@xxxxxxxxxxxxxxxxxx>
An: "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
I'm not sure to see which kind of missing integration with jenkins/hudson/ is mandatory for you ?
And about JIRA hooks... if we don't need it we don't use it ... what is your point ? ...
 
Le 10/11/2015 17:15, Werner Keil a écrit :
It's totally crippled compared to Enterprise. No Jenkins (which of course had to be Hudson for Eclipse, they are similar but not identical;-) support and who needs external JIRA hooks unless Eclipse also migrated from Bugzilla to the paid/closed-source/proprietary JIRA system...
 
Gesendet: Dienstag, 10. November 2015 um 17:02 Uhr
Von: "Simon Bernard" <sbernard@xxxxxxxxxxxxxxxxxx>
An: "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
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. 
 
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.

_______________________________________________ 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