Agreed, and I think some of the conversations on issues have gone better (more smoothly) because of the ready availability of related GitHub features.
A good move, thanks to Andy for making it for us! Adam On Wed, Jun 29, 2022, 2:30 PM Bruno Kinoshita <brunodepau...@gmail.com> wrote: > The reply looks really good. That's the same way I feel. It looks like it > has brought more users, and that users do not mind being asked to create > issues in GH for pull requests. > > Thanks Andy! > -Bruno > > On Thu, 30 Jun 2022, 4:35 am Andy Seaborne, <a...@apache.org> wrote: > > > In the last board report, we got a request to hear about the addition of > > github issues. We also reorganised the emailing lists as well to have > > separate list for issues and JIRA, not using the dev@ list. > > > > Comments etc? > > > > ---------------- > > > > As a project, Jena communications fluctuate so it isn't possible in 3 > > months to be completely conclusive on all points but the switch from > > JIRA to github issues has been remarkably complete and swift. > > > > Github issues were enabled at the beginning of May. > > > > * The use of github issues has quickly taken over from JIRA as the > > preferred route. (Jena still gets a few JIRA tickets.) > > > > * The dev@ mailing list has had much less traffic because of emails > > routed to other lists. > > > > * The project also enabled the github discussions area. This has seen > > some activity but not a lot. The users@ list has been relatively quiet. > > (Nowadays a significant number of Jena questions are on StackOverflow > > anyway.) > > > > * We have had more external contributors. > > > > * There has been several large, significant contributions on github. We > > can't conclusively say that it is related to the change but some of them > > are filed early - being worked publicly on the contributor's PR branch, > > rather than being finished work when the PR is opened. > > > > * We have put in github workflow templates for issues and pull requests. > > For PR's this includes a statement that the contributions are understood > > as being made under the Apache Contributors agreement. > > > > * The issues templates refer to the Code of Conduct. > > > > Andy > > >
