Hi Michael, doesn't this again exclude all external developers from discussing issues > with other developers? >
The mailing lists were established as the place where these discussions should take place, and anyone can write there. The situation with the javafxports/openjfx repo was a problematic, at least for me. People would discuss issues there and submit a fix to them only for the mailing list to be notified when it was ready for review. Anyone who does not keep constant track of the GitHub issues would not have a chance to say anything until that point. I have, by chance, caught several discussions there on topics relevant to me that I would have have liked to know about. It could also easily cause two people to work on the same issue in two different channels because many who used GitHub were not even registered to the mailing lists until the official fix submission. To my opinion disabling the issue tracker defeats the whole purpose of > using GitHub at all > GitHub's main strengths for contributors are the ease of code reviewing (inline comments etc.) compared to discussions on JIRA (JBS), and the ease of submitting a fix - PR with automated tests - compared to the current Webrev with manual tests. Having another issue tracker was actually a disadvantage. - Nir On Mon, Sep 30, 2019 at 4:05 PM Michael Paus <m...@jugs.org> wrote: > Hi, > doesn't this again exclude all external developers from discussing > issues with other developers? > To my opinion disabling the issue tracker defeats the whole purpose of > using GitHub at all, or > did I misunderstand something here? > Michael > > > Am 30.09.19 um 14:45 schrieb Kevin Rushforth: > > The official GitHub repos in the openjdk organization will not have > > the issue tracker enabled, which should help avoid this confusion. > > > > -- Kevin > >
