Decision making for Apache projects is described here: https://community.apache.org/committers/decisionMaking.html
So to make it official: I hereby declare that I will start implementing the stuff from my initial email if nobody objects in the next 72 hours (meaning: before next Monday). After that I will create the INFRA issue. The other, preliminary taks can already be started - I did by creating 2 cordova-docs issues that I already linked. For the rest of b) I will probably start another mailing list thread. 2018-08-02 15:35 GMT+02:00 Chris Brody <chris.br...@gmail.com>: > What will it take to take care of a) Enable GitHub issues on all > repositories via INFRA ticket? > > I think this is needed really badly. There are way too many cases of > questions and issues being raised in the wrong place, lost in diverse > discussion forums, or not even asked at all. > On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <ellis.br...@gmail.com> wrote: >> >> +1 >> >> Not sure if (f) was a task, as in to find a way to integrate GH and Slack, >> but it does exist. >> >> https://slack.github.com/ <https://slack.github.com/> >> >> It covers a lot including new commits, pr, new issues, code reviews, and >> more. >> >> >> > On Aug 1, 2018, at 22:22, Jan Piotrowski <piotrow...@gmail.com> wrote: >> > >> > Another one: >> > >> > f) Find and activate way for Github issue (and PR) updates to be >> > posted so Slack #issues >> > >> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <piotrow...@gmail.com>: >> >> The npm forum solves a very different problem for npm - they had too >> >> much noise in Github issues because of the project's popularity. Too >> >> much popularity is not one of Cordova's problems ;) >> >> >> >> Many uses of cordova-discuss will be able to move to the individual >> >> project repositories issues, maybe we can even think about getting rid >> >> of it. Good thing to keep in mind after everything is migrated. >> >> The mailing list can be used much more to just point people to a >> >> specific issue (as I also did in my original mail here) where the >> >> actual discussion will happen. >> >> >> >> -J >> >> >> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <chris.br...@gmail.com>: >> >>> +1 (+100) for migrating away from JIRA issues >> >>> >> >>> npm took a different approach that I am starting to really like: using >> >>> npm.community (Discourse) with GitHub login for issues and discussions >> >>> >> >>> solves another major problem since I don't like mail list for >> >>> discussing issues and cordova-discuss has proven to be such an >> >>> unpopular repo >> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <piotrow...@gmail.com> >> >>> wrote: >> >>>> >> >>>> While our repositories are already fully on GitHub [1], our issues >> >>>> mainly still live in JIRA. We previously decided this should be >> >>>> changed [2] so issues live with code. >> >>>> >> >>>> We also did some first switches that were pretty successful: >> >>>> >> >>>> https://github.com/apache/cordova-docs/issues >> >>>> https://github.com/apache/cordova-windows/issues >> >>>> >> >>>> So I suggest we move forward with the rest. Here is a list of stuff to >> >>>> do: >> >>>> >> >>>> >> >>>> a) Enable GitHub issues on all repositories via INFRA ticket >> >>>> >> >>>> b) Define and update Contributor documentation: >> >>>> * Contributor guidelines >> >>>> - https://cordova.apache.org/contribute/contribute_guidelines.html >> >>>> - https://cordova.apache.org/contribute/ >> >>>> - https://cordova.apache.org/contribute/issues.html >> >>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA >> >>>> => https://github.com/apache/cordova-docs/issues/861 >> >>>> * Issue template(s) >> >>>> * Pull Request template(s) >> >>>> * Github labels / issue triaging documentation >> >>>> * Usage of GitHub merge functionality >> >>>> * READMEs of all repositories >> >>>> * Prepare all these changes as PRs that can merged when a) is taken >> >>>> care of. >> >>>> >> >>>> c) Define and document handling of security issues >> >>>> => https://github.com/apache/cordova-docs/issues/860 >> >>>> >> >>>> d) Define and execute issue migration from JIRA to GitHub >> >>>> e) Define and execute "disabling" of JIRA (if applies) >> >>>> >> >>>> Related: >> >>>> - Check if ICLA documentation is correct and fix if necessary >> >>>> >> >>>> >> >>>> Any input or objections? >> >>>> >> >>>> I expect d) and e) to require some more discussion and planning, but >> >>>> think it is ok to just leave this to be done later after everything >> >>>> else was taken care of. Agree? >> >>>> >> >>>> Did I miss any documents for b) that will have to be updated? >> >>>> >> >>>> >> >>>> Best regards, >> >>>> Jan >> >>>> >> >>>> >> >>>> PS: >> >>>> >> >>>> For future reference, the links I collected while researching the >> >>>> previous work done and current state: >> >>>> >> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova: >> >>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E >> >>>> https://issues.apache.org/jira/browse/INFRA-14347 >> >>>> https://issues.apache.org/jira/browse/INFRA-14398 >> >>>> https://issues.apache.org/jira/browse/INFRA-14399 >> >>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E >> >>>> https://issues.apache.org/jira/browse/INFRA-14994 >> >>>> https://issues.apache.org/jira/browse/INFRA-14815 >> >>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E >> >>>> >> >>>> [2] Migrate Jira issues over to Github: >> >>>> https://issues.apache.org/jira/browse/CB-13157 >> >>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md >> >>>> https://github.com/apache/cordova-discuss/pull/75 >> >>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E >> >>>> https://issues.apache.org/jira/browse/INFRA-16503 >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> >>>> For additional commands, e-mail: dev-h...@cordova.apache.org >> >>>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> >>> For additional commands, e-mail: dev-h...@cordova.apache.org >> >>> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> > For additional commands, e-mail: dev-h...@cordova.apache.org >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
