I think the committer list, like the PMC membership, is shared across all the Geode-related sites. The geode-docs site would be added to this list. >From the "Committers" link on Geode "Community" page ( https://geode.apache.org/community/): Repositories managed by this Committee (from ASF Git mirrors <https://git.apache.org/>):
- geode: https://gitbox.apache.org/repos/asf/geode.git - geode-benchmarks: https://gitbox.apache.org/repos/asf/geode-benchmarks.git - geode-dotnet-core-client: https://gitbox.apache.org/repos/asf/geode-dotnet-core-client.git - geode-examples: https://gitbox.apache.org/repos/asf/geode-examples.git - geode-kafka-connector: https://gitbox.apache.org/repos/asf/geode-kafka-connector.git - geode-native: https://gitbox.apache.org/repos/asf/geode-native.git - geode-site: https://gitbox.apache.org/repos/asf/geode-site.git - geode-svn: https://svn.apache.org/repos/asf/geode/ On Thu, Jun 16, 2022 at 6:08 AM Joris Melchior <jmelch...@vmware.com.invalid> wrote: > I like this idea. I agree that changes to documentation are different from > changes to code, and documentation should be able to move in a different > cadence. > > Would committers to Geode and Geode-docs be the same after this proposed > change? > > Joris Melchior > > From: Dave Barnes <dbar...@apache.org> > Date: Tuesday, June 14, 2022 at 3:14 PM > To: dev@geode.apache.org <dev@geode.apache.org> > Subject: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo > ⚠ External Email > > I'd like to move the doc sources for the Geode User Guide from the code > repo ( > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode&data=05%7C01%7Cjmelchior%40vmware.com%7C54eb53d60ca94a1b157308da4e3a1593%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637908308627227614%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2JRX3rpAptf1Sa0EmEPJnDu%2B3mS%2FsEB83M2warTTni4%3D&reserved=0) > to a separate geode-docs repo. > > The primary reason is to allow docs to cycle at their own rate, rather than > in lock-step with the code. The present arrangement causes problems during > releases, when code is frozen (including doc sources) to prepare a release > candidate. This is exactly the time when critical last-minute doc changes > are needed, but such changes are forbidden due to the code freeze. > > I have participated in the Geode project since its inception, and can > confidently state that this conflict arises with nearly every Geode > release. Setting up the docs in a separate repo would alleviate this > regularly-recurring, counter-intuitive situation. > > Of note: The docs directories and toolset are almost entirely independent > of directories and tools needed for code development and release, so > removal of the doc sources from the Geode code repo should be painless for > developers. > > Observations and opinions welcome... > > Dave Barnes > > ________________________________ > > ⚠ External Email: This email originated from outside of the organization. > Do not click links or open attachments unless you recognize the sender. >
