IF we are making changes ... what's the preferred email routing?
GH issues -> issues@jena (new list)
GH pull requests -> pr@jena
GH discussions -> not practical today?
No stable GH API - not INFRA provided
Or one "github@" list?
JIRA:
Today - goes to dev@jena
We may have a jira@ list - if so, it's not active.
Options:
leave as-is
route to issues@jena, same a GH issues
route to a separate jira@jena
I mildly prefer to split the lists out and allow people to file to same
or different folders as the choose.
(I use GH notifications across all my watched repos)
As most of the traffic on dev@ is JIRA related, I wouldn't mind routing
it to jira@ - it allows people to have all in one place or to split it.
A dev@ for project discussions and VOTEs will make dev@ significantly
quieter and maybe encourage discussions as they are a little easier to
see and track. (And have to be explain in the board report!)
Andy
On 17/02/2022 20:08, Bruno Kinoshita wrote:
I think this would be a good experiment, but definitely not the place for
project decisions to be recorded (if a discussion there generates some
decision, then we'd still have to move it & document in the mailing list I
think).
We can also ourselves treat GH-issues as a more convenient route for
external issue raising, many of which are specific problems, and keep
JIRA for significant fixes and change of functionality.
Also - we do have an upturn in JIRA that are questions. Once, that never
happened; now it is happening. Not many but some.
But that might increase the user interaction and contribution. Will wait
for the vote thread :-)
Thanks
Bruno
On Fri, 18 Feb 2022 at 07:28, Andy Seaborne <a...@apache.org> wrote:
...
== GH issues
...>> == GH Discussions
