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
gt;
> Would committers to Geode and Geode-docs be the same after this proposed
> change?
>
> Joris Melchior
>
> From: Dave Barnes
> Date: Tuesday, June 14, 2022 at 3:14 PM
> To: dev@geode.apache.org
> Subject: [PROPOSAL] Relocate Geode Docs from code repo to seperate
14, 2022 at 3:14 PM
To: 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%2Fa
; > Ideally, I don’t see code and doc being separate or even fundamentally
> > different.
> >
> > This sounds more like a process problem and a workaround to a broken
> > process, to me.
> >
> > $0.02
> > -John
> >
> >
> > From: Dave Barnes
> &
don’t see code and doc being separate or even fundamentally
> different.
>
> This sounds more like a process problem and a workaround to a broken
> process, to me.
>
> $0.02
> -John
>
>
> From: Dave Barnes
> Date: Tuesday, June 14, 2022 at 12:15 PM
> To: dev@geode.ap
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
ifferent.
>
> This sounds more like a process problem and a workaround to a broken
> process, to me.
>
> $0.02
> -John
>
>
> From: Dave Barnes
> Date: Tuesday, June 14, 2022 at 12:15 PM
> To: dev@geode.apache.org
> Subject: [PROPOSAL] Relocate Geode Docs fr
@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&dat
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
I'd like to move the doc sources for the Geode User Guide from the code
repo (https://github.com/apache/geode) 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
relea
12 matches
Mail list logo
