> Just for a supplement, this is effective for all developers (committers, long-term or first-time contributors) and all pull requests, without any conditions.
I'm sorry for being verbose for it again, but I'd like to emphasize this point. I mean, if we absolve only first-time contributors from the requirement for JIRA issues, this can add unnecessary barriers between developers; this is not my intention. The contribution workflow should be the same for all developers. If any administrative issues pop up by exempting JIRA issues for all pull requests, I'll try to improve the workflow. Tomoko 2022年5月3日(火) 13:17 Tomoko Uchida <[email protected]>: > Thank you Adrien for confirming. > > Just for a supplement, this is effective for all developers (committers, > long-term or first-time contributors) and all pull requests, without any > conditions. > Every developer can skip opening a JIRA when contributing if he/she feels > it's an unnecessary extra ceremony. > > So - I hope this will also eases long-term committers' daily work. > > Thanks, > Tomoko > > > 2022年5月3日(火) 5:24 Adrien Grand <[email protected]>: > >> Thanks Tomoko! >> >> I'm +1 on no longer requiring external contributors to create JIRA >> issues, JIRA can be quite intimidating the first time you have to deal >> with it with its complex UI, specific markup language, etc. This will >> hopefully improve the experience of first-time contributors. >> >> On Mon, May 2, 2022 at 4:30 PM Tomoko Uchida >> <[email protected]> wrote: >> > >> > Assuming there are no strong objections, I merged the PR. This is >> effective from now on. >> > In brief, a CHANGES entry can refer Jira issues or GItHub pull >> requests. In the latter case, Jira issue is not required or is optional >> (it's up to the author). >> > >> > >> > >> > 2022年4月30日(土) 12:29 Tomoko Uchida <[email protected]>: >> >> >> >> The pull request receives one approval and a few comments. Feedback is >> welcome, thank you. >> >> >> >> There are no effects on the current contribution workflow though, this >> could slightly change the forms of communication (some people will continue >> to use both Jira and GitHub as before, some people might tend to use GitHub >> only). >> >> >> >> I am not familiar with how to proceed with such workflow changes; >> according to the "lazy consensus" concept that is well described on this >> page, I plan to merge it with an example CHANGES entry later next week if >> there are no objections. >> >> https://community.apache.org/committers/lazyConsensus.html >> >> >> >> Tomoko >> >> >> >> >> >> 2022年4月29日(金) 22:01 Tomoko Uchida <[email protected]>: >> >>> >> >>> Hello all. >> >>> >> >>> I guess this has been discussed before (several times). Once again, I >> would propose to relax the requirement for creating JIRA account/issue when >> contributing. >> >>> >> >>> LUCENE-10545 allows CHANGES.txt to directly mention to GitHub PR (to >> be exact, I just fixed the obsoleted link to the repository) so that >> developers can skip opening a JIRA if he/she is ready to start the >> conversation with a working PR. >> >>> To see how it will work, please see the associated PR on it - this >> includes a concrete example. >> >>> >> >>> Please note that this does not replace Jira with Github (we still >> absolutely need issues for discussion and migrating Jira issue to GitHub >> issue is out of the scope here), but provides an option for developers who >> already have working patches. >> >>> >> >>> Thank you, >> >>> Tomoko >> >> >> >> -- >> Adrien >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
