[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

There are countless Open Source projects from JBoss/Red Hat to Spring/Pivotal/Dell, even .NET all hosted on GitHub. A few others use Bitbucket (probably more proprietary or open-source hostile now that Atlassian cut its ties with Eclipse when it comes to IDE support;-) and some e.g. SourceForge, etc. 
 
Big names like Google Code where EclipseLabs was also hosted gave up and provide free export into GitHub. It may be driven by a single hosting company (on top of Amazon and similar Cloud backbone) but it won't discriminate a project as long as it's either run open-source or paid in a private repo.
 
Many projects especially if they contain e.g. Java standards like JSRs also take care of IP or who contributes what. Of course that's up to the individual project, so unlike Eclipse GitHub won't enforce it for every single project based on a single license;-)
 
Regards,
Werner
 
Gesendet: Dienstag, 10. November 2015 um 15:35 Uhr
Von: "Alexandre Montplaisir" <alexmonthy@xxxxxxxxxxxx>
An: "Mailing list for all people involved in Eclipse project management" <eclipse.org-project-leadership@xxxxxxxxxxx>, ed@xxxxxxxxxxxxx
Betreff: Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects
Hi,

Migrating to GitHub means becoming dependant on a proprietary platform.
This was not the case in the CVS -> Git migration.

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. I would
much prefer if we could have an open-source ALM management platform
hosted at Eclipse.

Regards,
Alexandre


On 2015-11-10 09:22 AM, Ed Willink wrote:
> Hi
>
> GIven that those using GitHub Issues are very enthusiastic about it,
> is it time that we all move on? similar to the CVS to GIT migration.
>
> If we all move then we could retain the benefit of an
> all-Eclipse-scoped search and it could be worth an investment in
> migrating Bugzilla history.
>
> Regards
>
> Ed Willink
>
> On 10/11/2015 14:09, Jesse McConnell wrote:
>> FWIW we have Jetty mirrored out on github and we have more commits
>> trying to be contributed and discussions on specific commits out
>> there then we have had at eclipse or through gerrit.
>>
>> This is a very positive step forward for the eclipse community in my
>> opinion, much needed and very welcome. It may not work for projects
>> that are heavily tied into the release train or eclipse tooling but
>> for independent projects like Jetty it is a major breath of fresh air!
>>
>> Jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx <mailto:jesse.mcconnell@xxxxxxxxx>
>>
>> On Tue, Nov 10, 2015 at 7:56 AM, John Arthorne
>> <John_Arthorne@xxxxxxxxxx <mailto:John_Arthorne@xxxxxxxxxx>> wrote:
>>
>> > Maybe I am completely blind, but this comes a bolt out of the blue to me. Surely some discussion
>> was merited?
>> Just to give a bit of background context, there have been many
>> discussions about this in the past, both in public and private.
>> As a committer rep it is the single biggest thing I have been
>> lobbied to support in the past 3 years. I have the same
>> fragmentation concerns, but I believe the benefits for those
>> projects outweigh the downside. The reality for most developers
>> is that they already deal with libraries developed on GitHub and
>> we will never have a completely "closed system" where the entire
>> software dependency chain lives at eclipse.org
>> <http://eclipse.org>. Being forced to use bugzilla has also
>> been a significant barrier to attracting and keeping projects at
>> the Eclipse Foundation.
>> For even more background, here is a thread and bugzilla where
>> these requests have surfaced in the past:
>> https://dev.eclipse.org/mhonarc/lists/iot-pmc/msg00447.html
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=442828#c11
>> John
>>
>> ----- Original message -----
>> From: Ed Willink <ed@xxxxxxxxxxxxx <mailto:ed@xxxxxxxxxxxxx>>
>> Sent by: eclipse.org-project-leadership-bounces@xxxxxxxxxxx
>> <mailto:eclipse.org-project-leadership-bounces@xxxxxxxxxxx>
>> To: eclipse.org-project-leadership@xxxxxxxxxxx
>> <mailto:eclipse.org-project-leadership@xxxxxxxxxxx>
>> Cc:
>> Subject: Re: [eclipse.org-project-leadership] Use of GitHub
>> Issues by Eclipse Projects
>> Date: Tue, Nov 10, 2015 4:54 AM
>>
>> Hi
>>
>> "I am pleased to announce that at last week's Board meeting,"
>>
>> Maybe I am completely blind, but this comes a bolt out of the
>> blue to me. Surely some discussion was merited?
>>
>> If compatibility tooling is provided, I see a repeat of our
>> longstanding ongoing NNTP/Forum synchronization disaster.
>>
>> If tooling isn't provided we do a major disservice to all our
>> committers and users, seemingly just to accommodate some
>> projects who do not seem to be properly committed to Eclipse.
>> Eclipse is a community that IMHO endeavors to provide a
>> unified capability. We do not need fragmentation. (Unless of
>> course we are all to move to GitHub.)
>>
>> IIRC there was originally enthusiasm for using GitHub as a
>> mirror for Eclipse GIT repos. Unfortunately this did not
>> work. I suggest that efforts at GitHub support would be
>> better spent on solving the GitHub mirroring rather than a
>> flaky Bugzilla customization.
>>
>> Regards
>>
>> Ed Willink
>>
>>
>> On 10/11/2015 03:24, Mike Milinkovich wrote:
>>> All,
>>>
>>> Several years ago the Eclipse Foundation started allowing
>>> its projects to host their day-to-day development at GitHub.
>>> As part of that, we implemented several processes to ensure
>>> that Eclipse projects could maintain their freedom of action
>>> should GitHub ever go away, or dramatically alter their
>>> terms of service. A number of the projects which host their
>>> development at GitHub subsequently asked if they could also
>>> start using GitHub Issues, rather than Bugzilla for tracking
>>> issues.
>>>
>>> I am pleased to announce that at last week's Board meeting,
>>> the Eclipse Foundation approved the following two resolutions:
>>>
>>> *Resolved*, that with PMC approval, the Board approves
>>> the use of GitHub Issues for Eclipse projects which are
>>> hosted at GitHub. The EMO is instructed to backup GitHub
>>> Issues data on eclipse.org <http://eclipse.org> server
>>> infrastructure to ensure the future freedom of action of
>>> these projects.
>>>
>>> *Resolved,* the EMO is instructed to provide
>>> instructions to Eclipse projects hosted on GitHub on how
>>> to properly utilize GitHub features (e.g. Release Pages)
>>> to remain compliant with the Eclipse project branding
>>> requirements, Eclipse Development Process, and the
>>> Eclipse IP Policy.
>>>
>>> This does /not/ mean that you can start using GitHub Issues
>>> for your project right away. It does mean that the EMO has
>>> started working on a plan to enable that, and we hope to do
>>> so soon. Please follow bug 481771
>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=481771> if
>>> you are interested in progress on this.
>>>
>>> Thanks,
>>> --
>>> Mike Milinkovich
>>> mike.milinkovich@xxxxxxxxxxx
>>> <mailto:mike.milinkovich@xxxxxxxxxxx>
>>> +1.613.220.3223 <tel:%2B1.613.220.3223> (mobile)
>>>
>>> _______________________________________________
>>> eclipse.org-project-leadership mailing list
>>> eclipse.org-project-leadership@xxxxxxxxxxx
>>> <mailto: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
>> <mailto: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
>> <mailto: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 contactemo@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.