Maybe the confusion here is between "committee" (as in PMC) and "committers", who are so-called because they have commit rights to the code (normally earned by being personally committed to the project). Here is some documentation about what an Apache PMC is and does as opposed to committer-ship:
https://apache.org/foundation/how-it-works.html#roles and all of https://apache.org/foundation/how-it-works.html is pretty useful. https://www.apache.org/foundation/governance/pmcs is about PMCs specifically and: https://www.apache.org/foundation/governance/pmcs#merit is particularly relevant. ajs6f > On Dec 6, 2019, at 11:53 AM, Marco Neumann <marco.neum...@gmail.com> wrote: > > OK I see, I have inferred that from the Apache site [1] where it says that > the Apache Jena Committee is also called PMC . > > I have seen a number of changes over the years, even predating the move to > Apache, so yes migrating to a new system might be an option. possibly a > wiki type system. But it's not urgent from my point of view at the moment. > > Thanks for the explanation attempt. > > [1] https://projects.apache.org/committee.html?jena > > > > > > > On Fri, Dec 6, 2019 at 4:31 PM ajs6f <aj...@apache.org> wrote: > >> No, I didn't mention the PMC at all. >> >> Perhaps we're getting confused here because like other Apache projects, >> Jena has both a roster of committers, who have privileges to work on the >> codebase and docbase, but also a Project Management Committee or PMC (of >> which Andy is now the chair), which is ultimately responsible for the >> conduct of the Jena project to the Apache Foundation. The PMC, amongst a >> few other duties, elects new committers. Like many Apache projects, those >> lists for Jena are substantially the same (with a few small differences), >> but the only one that is relevant here is the committer roster. >> >> As for other kinds of roles, I'm not sure how much flexibility is >> available from the Apache bylaws, but I know of no other project that >> features other "official" roles-- that is, roles other than committer or >> PMC member that would be recognized by the Foundation. We've discussed >> this question before and come to the conclusion that the Jena project is >> small enough that we don't need any new roles-- that if someone is making >> contributions that should be recognized with a greater level of >> responsibility (whether or not those contributions are in the form of code >> or something else like work answering questions on the mailing lists, >> etc.), we can simply make them a committer immediately. >> >> Does that help explain? >> >> In any event, several threads over the past months (years now, I think!) >> have arisen on this list to the effect that our documentation in Apache >> INFRA's old-line CMS isn't easy to maintain or publish, so that >> alternatives are attractive. I suspect that real improvement for our >> documentation process would be better achieved by migrating to a new system. >> >> ajs6f >> >>> On Dec 6, 2019, at 11:17 AM, Marco Neumann <marco.neum...@gmail.com> >> wrote: >>> >>> in short yes, I would think for documentation purposes and the like a >> more >>> relaxed form of participation should be available. So you say currently >>> only members with role PMC can commit edits to the documentation on the >>> apache cms? Can roles be dynamically generated here or does each Apache >>> project has only one type of role membership on the Apache cms? >>> >>> >>> >>> On Fri, Dec 6, 2019 at 3:58 PM ajs6f <aj...@apache.org> wrote: >>> >>>> It is not tied into that build process, except for the Javadocs, since >>>> Javadocs are extracted from the codebase. There is no need to build the >>>> codebase to publish the site as a whole. >>>> >>>> As for assigning an account to individual users, I'm not quite sure what >>>> that would do. Currently accounts are for committers because only >>>> committers can make changes to the documentation. Are you suggesting >> that >>>> we allow any user with an account to make changes there and allow any >> Jena >>>> user who asks to have an account? Or something else? >>>> >>>> ajs6f >>>> >>>>> On Dec 6, 2019, at 10:52 AM, Marco Neumann <marco.neum...@gmail.com> >>>> wrote: >>>>> >>>>> assign user name and password to individual users? I'd say it doesn't >>>> need >>>>> to be tied into the build process of the Apache Jena project IIUC >>>>> >>>>> On Fri, Dec 6, 2019 at 3:41 PM ajs6f <aj...@apache.org> wrote: >>>>> >>>>>> Did you have suggestions for a different process? >>>>>> >>>>>> ajs6f >>>>>> >>>>>>> On Dec 6, 2019, at 8:38 AM, Marco Neumann <marco.neum...@gmail.com> >>>>>> wrote: >>>>>>> >>>>>>> Thanks Adam, >>>>>>> >>>>>>> the process sounds a bit cumbersome, but in any event the page I have >>>>>>> already edited is here >>>>>>> >>>>>>> >>>>>> >>>> >> https://cms.apache.org/jena/wc/edit/anonymous-n3xU7Y/trunk/content/documentation/javadoc/index.mdtext >>>>>>> >>>>>>> >>>>>>> the idea was to update the bread crumb navigation items since >> currently >>>>>> to >>>>>>> spatial search links to a 404 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Dec 5, 2019 at 7:49 PM ajs6f <aj...@apache.org> wrote: >>>>>>> >>>>>>>> Yes, a committer needs to push the change through to be committed to >>>> the >>>>>>>> documentation base, and then the site must be published. We always >>>>>> publish >>>>>>>> for a release, but we can publish at other times, too, if needed. >>>>>>>> >>>>>>>> I do not recall seeing the actual change come across dev@ (which it >>>>>>>> normally would). Do you have a link to the patch in the Apache CMS >>>>>> handy? I >>>>>>>> am happy to review and commit it. >>>>>>>> >>>>>>>> ajs6f >>>>>>>> >>>>>>>>> On Dec 4, 2019, at 2:58 PM, Marco Neumann <marco.neum...@gmail.com >>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> I have made some changes to the documentation on the >> jena.apache.org >>>>>>>> site >>>>>>>>> with the anonymous username and can indeed see these changes now in >>>> the >>>>>>>>> edit view but not in the live view. Is this correct behavior, does >>>> this >>>>>>>>> change wait for some admin approval? >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> >>>>>>>>> --- >>>>>>>>> Marco Neumann >>>>>>>>> KONA >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> --- >>>>>>> Marco Neumann >>>>>>> KONA >>>>>> >>>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> --- >>>>> Marco Neumann >>>>> KONA >>>> >>>> >>> >>> -- >>> >>> >>> --- >>> Marco Neumann >>> KONA >> >> > > -- > > > --- > Marco Neumann > KONA
