While there could be some technical aspects to it, the culture, behavior
and process one is certainly the first thing to deal with.
exactly to the point
Gruß
Christian
On 11/10/2015 06:32 PM, Tyler Jewell
wrote:
The
issue about GitHub Issues is not one of technology, but rather one of
culture & behavior.
That can be
discussed.
To me the culture and behavior at GitHub is the one of
open-source, Git and GitHub tools on top of it. I's not much more than what
SourceForge, Google Code, CodeHaus were some years ago. A free
Forge-as-a-Service for OSS projects. When one day, the trends change and a
GitHub competitor takes over, then the culture & behavior will remain and
evolve by adopting the new tools.
Anyway, testimonials such as the one
from Jetty claiming that they have more community investment in GitHub rather
than Bugzilla+Gerrit are very convincing about the need to be there for some
projects. But on the other hand, it also reveals that the Eclipse contribution
process is complicated. My idea on that is that a project GitHub page is
considered by many projects and contributors as the welcome page, and directly
shows code and all means to contribute, whereas most Eclipse projects show
instead a description page, then a link on How to Contribute and then users
can access the various tools. The code-centric approach of GitHub seems to be
more efficient.
-------------------------------------------------------------
compeople
AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18
0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand:
Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der
Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr.
DE207665352
-------------------------------------------------------------
_______________________________________________
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.