Hi Jason, now this looks a lot more like something we can help support :-)
And projects don’t necessarily have to be mono repos. Stuff like examples, project websites … that’s quite common to be in separate repositories. I guess the amount of additional work would not be that much … yeah … the reports have to be written, but most use templates for that and just fill in special things being noted. Writing the reports for a project usually doesn’t take much time. Regarding setting up of infra … I guess you would go a GitHub approach and not sign up for Jira and Confluence now that public user registrations are disabled. I would dare to say the amount of work to set this up for one project and multiple project would be identical. Chris From: Jason Porter <jpor...@ibm.com.INVALID> Date: Tuesday, 6. December 2022 at 17:27 To: general@incubator.apache.org <general@incubator.apache.org> Subject: Re: [DISCUSS] KIE Proposal > On Dec 6, 2022, at 01:43, Christofer Dutz <christofer.d...@c-ware.de> wrote: > > Hi Jason, > > Well, those numbers are a bit better than the initial ones. > Thing is: Mentors will not only have to help onboard people to Apache and > teach them how to do things, if they are doing their job correctly, they > should also really audit the releases being done and help get the codebase > into shape first. > > Even with 12 sub-projects, work-wise that would put a load on the mentors, as > if they signed up for mentoring 12 projects. > > So how about bringing in projects separately (where it makes sense)? There > each project could have their initial PPMC and committer lists and it would > spread out the load a bit. However I would expect staffing 12 projects with > enough work-willing mentors will still be challenging and I would assume not > all of them to find enough of them, but it could be one first step. > > Or is there an advantage of considering all projects as one unity? > > Chris > > [snip] That is part of a broader question. Some of those repos are things like examples for kogito, the website, etc. Things that are part of the projects themselves, but don’t have a life outside of the project to which they belong. I understand we’ll probably have to collapse the structures within Apache and have a single repo per project. What we’re really looking at as far as projects being donated: Kogito Drools jBPM Then there are the supporting repos for things like examples, docs, website, tooling, etc. Many of the people working on these projects work on all of them, so it would probably be the same group of people with very little deviation in the list of committers. Could they be different PPMCs, but they’d basically be the same group, just more work with the reports, setup, infra, etc. Jason Porter Software Engineer He/Him/His IBMB�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[ ��[�\�[ ][��X��ܚX�P[��X�]܋�\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[ ��[�\�[ Z[ [��X�]܋�\X�K�ܙ�B
