t go hand by
> hand, how will we know?
>
> Alberto
>
> From: Dave Barnes
> Sent: Wednesday, June 15, 2022 11:06 PM
> To: dev@geode.apache.org
> Subject: Re: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo
>
> Adopting
question a
no-brainer. But if code and documentation do not go hand by hand, how will we
know?
Alberto
From: Dave Barnes
Sent: Wednesday, June 15, 2022 11:06 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo
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 mirr
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
Date: Tuesday, June 14
Whenever necessary, anyone should feel free to file blocker tickets for
> missing/incorrect docs to ensure the release does not ship prematurely
> without meeting Geode’s standard of documentation.
> [1] https://geode.apache.org/docs/
>
> From: Dave Barnes
> Date: Tuesday, June 14, 202
Geode Docs from code repo to seperate repo
⚠ External Email
John,
Thanks for acknowledging that docs are just as important as code! As a
career tech-writer, the "docs=code" model appeals to me.
I get what you're saying, and have worked in environments where release
managers have enfo
de is frozen.
Alberto
From: Udo Kohlmeyer
Sent: Wednesday, June 15, 2022 5:05 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo
Hi there Dave,
I can understand the frustration that you face. I think the freezing o
of
sequence with the deliverable)
--Udo
From: Dave Barnes
Date: Wednesday, June 15, 2022 at 8:11 AM
To: jb...@vmware.com.invalid
Cc: dev@geode.apache.org
Subject: Re: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo
⚠ External Email
John,
Thanks for acknowledging that docs are
John,
Thanks for acknowledging that docs are just as important as code! As a
career tech-writer, the "docs=code" model appeals to me.
I get what you're saying, and have worked in environments where release
managers have enforced such constraints.
In this vein, the Geode code is well-supplied with
Personally, I believe doc is a critical component to any software project,
especially a project like Apache Geode, and so, is the project really “complete
“(or should thee codebase really be frozen during a release) if the doc is not
done or consistent yet?
Having the doc be part of the source
I don’t see any downsides to this approach. We already do this for other assets
like examples, native, site, and benchmarks.
> On Jun 14, 2022, at 12:03 PM, Dave Barnes wrote:
>
> ⚠ External Email
>
> I'd like to move the doc sources for the Geode User Guide from the code
> repo
> (https://na
11 matches
Mail list logo
