+1 On Thu, May 18, 2017 at 2:23 PM, Joan Touzet <woh...@apache.org> wrote:
> Hi Anthony, > > Unfortunately, having a JIRA account is not the same as having an > Apache account. > > You have to be elected an official CouchDB Committer to obtain an > Apache account. New committers are elected by the PMC according to the > rules set out in the CouchDB bylaws: > > https://couchdb.apache.org/bylaws.html > > You'll know if you are a committer because you will have been contacted > by the PMC and gone through a process so submit a signed individual > contributor license agreement (ICLA). Your name will then appear on this > list: > > https://people.apache.org/committer-index.html > > or this list if the process is still ongoing: > > https://people.apache.org/unlistedclas.html > > If you are a committer, visit https://gitbox.apache.org/setup/ and > follow the instructions to link your accounts. > > For non-committers like yourself, you're still able to submit GitHub > issues and pull requests, and comment on others' issues and pull > requests. You just won't be able to assign labels/milestones/etc, > close issues, or merge pull requests. Just create a GitHub account > in the usual way and you're good to go. As always, if you don't > want to agree to the GitHub Terms of Service, these mailing lists > exist as an alternative. > > Hope this makes it clearer! > > -Joan > > > ----- Original Message ----- > From: "Anthony Ananich" <anthony.anan...@gmail.com> > To: u...@couchdb.apache.org > Cc: "CouchDB Developers" <dev@couchdb.apache.org> > Sent: Thursday, May 18, 2017 2:38:56 AM > Subject: Re: [Lazy Consensus] Move from JIRA to GitHub Issues > > Hi! > > I just tried to link my Apache and GitHub accounts and I've got an issue > that may be a problem for other contributors. Even if I'm able to login to > https://issues.apache.org/jira/, there is no way for me to login using > the same account to https://id.apache.org/ > > Have I missed something or it is by design? > > Regards, > Anthony Ananich > http://ananich.pro > > > > On May 18, 2017, at 9:04 AM, Nick North <nort...@gmail.com> wrote: > > > > +1 > > > > Nick > > > >> On 18 May 2017, at 07:01, Elisiano Petrini <elisi...@gmail.com> wrote: > >> > >> +1 👍🍻 > >> > >> Best Regards, > >> Elisiano Petrini > >> > >>> On May 17, 2017, at 9:38 PM, 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 >
