Hi Team, Thanks to Tomoko's amazing hard work ( https://github.com/apache/lucene-jira-archive), we are getting close to having strong tooling and a solid plan to migrate all past Jira issues to GItHub issues!
But one contentious point is whether to leave Jira read-only or read-write after the migration. So let's DISCUSS and maybe VOTE to reach concensus? My opinion: I think it'd be crazy to leave Jira read/write. We would effectively have two issue trackers. New users who find Jira through Google, or through links we have in old blog posts, etc., might accidentally open new Jira issues or comment on old ones and we may not even notice. I think that would harm our community. I would prefer that we make a nearly atomic switch -- up until time X we use Jira, then it goes read-only and at time X + t (t being how long the migration takes, likely a day or two?), GitHub issues opens for business. This way we clarly have only one issue tracker at (nearly) all times. This would make a clean migration, and reduce risk of trapping users. Other opinions? Thanks, Mike -- Mike McCandless http://blog.mikemccandless.com
