+1 If we do not decide of replacing Jira with Github or another BT, we must keep Jira for contribution tracking.
There might be a jira integration in github for that ? Gil On Mon, Feb 03, 2020 at 12:16:11PM +0100, Michael Brohl wrote: > I'm automatically informed about the pull requests, I think that all > committers get those emails. > > IMO, we should make the creation of a Jira mandatory independent of the > contribution channel (patch or PR). That would inform everyone about the > contribution and we have a valid starting point for questions, discussion > etc. regarding the contribution. > > I feel that solely handling this on Github does not increase transparency. > > Regards, > > Michael Brohl > > ecomify GmbH - www.ecomify.de > > > Am 03.02.20 um 12:07 schrieb Pierre Smits: > > Hi All, > > > > With the move to Git, we can expect more pull request from Github (see also > > other threads where postings regarding feature branches appeared). > > Unfortunately, currently no notifications appear in a mailing list when > > those PullRequests are initiated. > > > > It seems to me that, if we want to get more engagements (from github > > contributors), aspects such as PullRequests should sent a notification to > > the dev ml. Otherwise these PullRequests remain in limbo, and we risk of > > losing these contributors. > > > > > > Best regards, > > > > Pierre Smits > > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > *Apache Directory <https://directory.apache.org>, PMC Member* > > Apache Incubator <https://incubator.apache.org>, committer > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) > > since 2008* > > Apache Steve <https://steve.apache.org>, committer > > >
signature.asc
Description: PGP signature
