nice +1 :)
> On 17 May 2017, at 22:32, Eli Stevens (Gmail) <wickedg...@gmail.com> wrote:
>
> As a user and occasional bug reporter, I welcome the change.
>
> Searching for existing issues in JIRA was painful, mostly due to
> feeling like I had to repeat myself in saying that I wasn't interested
> in any of the other projects on the instance.
>
> On Wed, May 17, 2017 at 1:59 PM, Jan Lehnardt <m...@jan.io> wrote:
>> \o\ /o/ \o/ <3
>>
>>> On 17. May 2017, at 21:38, Joan Touzet <woh...@apache.org> wrote:
>>>
>>> Hi everyone.
>>>
>>> As most of you know, a few months ago we moved many of our primary
>>> repositories from primary Apache hosting to primary GitHub hosting. A
>>> major reason we did so was to leverage the better user experience of
>>> GitHub, especially for community interaction.
>>>
>>> It's now time for us to move from JIRA to GitHub Issues. Here's how:
>>>
>>> 0. The community reviews and approves this change. As a non-technical
>>> decision, our bylaws say that no formal vote is required, only a
>>> lazy majority from committers with 72 hours notice. That said,
>>> I'd like to ensure broad support for this change, so even if
>>> you're not a committer, please reply to this email with any
>>> comments.
>>>
>>> 1. Approve pull requests to update our issue and pull request templates
>>> and add a CONTRIBUTING.md file to our primary repositories:
>>>
>>> https://github.com/apache/couchdb/pull/527
>>> https://github.com/apache/couchdb-docker/pull/15
>>> https://github.com/apache/couchdb-documentation/pull/132
>>> https://github.com/apache/couchdb-fauxton/pull/925
>>> https://github.com/apache/couchdb-nano/pull/44
>>> https://github.com/apache/couchdb-pkg/pull/5
>>>
>>> 2. Approve pull requests to update our webpage and documentation to
>>> point to GitHub apache/couchdb for issue reporting:
>>>
>>> https://github.com/apache/couchdb-documentation/pull/133
>>> https://github.com/apache/couchdb-www/pull/23
>>>
>>> 3. Start using GH Issues for all new issues. At the same time, any
>>> committers who have completed the account integration process
>>> (see the new CONTRIBUTING.md file for details) should start
>>> labeling their issues and pull requests with the new scheme.
>>> The label scheme is here:
>>>
>>> https://github.com/apache/couchdb/issues/499
>>>
>>> A reminder to committers - this means PRs don't need a JIRA ticket!
>>> And because PRs are just a special kind of GH Issue, there's no need
>>> to create a separate issue unless you want to. (Don't forget the
>>> labels!)
>>>
>>> 4. Start moving selected issues over from JIRA. At this point, only
>>> actively worked issues should be moved over. When developers pick
>>> up a new task from JIRA, they should create a companion GH Issue
>>> for the ticket and reference it in JIRA, then close the JIRA issue.
>>>
>>> 5. In the future, we will work to migrate more issues as desired.
>>> However, we won't be moving any 1.x-specific issues over to GitHub.
>>>
>>> At some point in the future, we will also consider:
>>>
>>> * A script to de-assign idle issues (and de-tag them if necessary)
>>> * A script to auto-repost new issues from JIRA into GH Issues. (We
>>> can't disable new issue creation in JIRA without shutting down
>>> the entire instance, and we don't want to do that.)
>>>
>>> This is perhaps the happiest email I've sent to any CouchDB mailing list
>>> ever. I'm really excited about this change, and I bet you are too!
>>>
>>> Thanks to everyone who's helped us get this far, especially Apache
>>> Infrastructure for the Gitbox integration workflow.
>>>
>>> -Joan
