[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

IBM has launched an effort a few years ago called OSLC which tries to address this issue of scattered information sources. Maybe this technology can be reused to provide some central ticket repo. Also Mylyn has a great track record when it comes to unyfing tasks from different sources.


Met vriendelijke groet - Best Regards - Mit besten GrÃÃen -  Cordialement - Saludos cordiales - Serdeczne pozdrowienia - ÏÎÏ ÎÎÎÏÏÎÏÎÏ ÎÏÏÎÏ - Yoroshiku

Wim Jongman




From:        Mickael Istria <mistria@xxxxxxxxxx>
To:        eclipse.org-project-leadership@xxxxxxxxxxx
Date:        10-11-2015 08:36
Subject:        Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects
Sent by:        eclipse.org-project-leadership-bounces@xxxxxxxxxxx





Hi,

I believe this is a good thing for the projects that want to be on GitHub, but I have similar concerns as Ed about multiplying the media.
Users will just get even more lost because of this. Currently we can say "open a bugzilla request and in worst case we'll re-route it to the right project"; now some projects will say "open a ticket on Bugzilla", others will say "open a GitHub issue". It really scatters the contribution process that is already so difficult to teach...

Mind the hype!

Cheers,

--
Mickael Istria
Eclipse developer at
JBoss, by Red Hat
My blog - My Tweets_______________________________________________
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.