mikemccand opened a new issue, #29: URL: https://github.com/apache/lucene-jira-archive/issues/29
I think it is crazy trappy to leave Jira as writable after "switching" to GitHub issues. New users, people seeing old emails in archives and clicking on Jira links, old links in our Wiki/blog posts that we fail/forget to update, will all entice new users to make changes in Jira. I think this is really quite dangerous, and would specifically impact new users (not us old timers) which is the worst possible impact since our community grows only at its periphery of new users/contributors/developers. In fact, I don't think we can even call it a switch/migration if we have two writable issue tracking systems. Second, it is apparently not hard (at least, I heard from @rmuir that people do this by accident sometimes! I have not researched much myself) to restrict the workflow of Jira so that nothing is writable. We should also [add a comment to every Jira pointing to the migrated GitHub issue](https://github.com/apache/lucene-jira-archive/issues/15), and perhaps ideally (lower priority) [automatically redirect Jira issues to the right GitHub issue](https://github.com/apache/lucene-jira-archive/issues/28). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
