Excerpts from Rochelle Grober's message of 2018-03-22 01:05:42 +:
> It could be *really* useful if you could include the date (month/year
> would be good enough)of the last significant patch (not including
> the reformat to Openstackdocstheme). That could give folks a great
> stick in the mud
It could be *really* useful if you could include the date (month/year would be
good enough)of the last significant patch (not including the reformat to
Openstackdocstheme). That could give folks a great stick in the mud for what
"past" is for the spec. It might even incent some to see if there
>
> We want them all to use the openstackdocstheme so you could look
> into creating a "subclass" of that one with the extra content in
> the header, then ensure all of the specs repos use it. We would
> have to land a small patch to trigger a rebuild, but the patch
> switching them from oslosphin
Excerpts from Jeremy Stanley's message of 2018-03-19 20:17:37 +:
> On 2018-03-19 16:09:14 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > We want them all to use the openstackdocstheme so you could look
> > into creating a "subclass" of that one with the extra content in
> > the header, then en
On 2018-03-19 16:09:14 -0400 (-0400), Doug Hellmann wrote:
[...]
> We want them all to use the openstackdocstheme so you could look
> into creating a "subclass" of that one with the extra content in
> the header, then ensure all of the specs repos use it. We would
> have to land a small patch to t
Excerpts from Jim Rollenhagen's message of 2018-03-19 19:06:38 +:
> On Mon, Mar 19, 2018 at 3:46 PM, Jeremy Stanley wrote:
>
> > On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote:
> > [...]
> > > What do folks think about a banner at the top of the specs website
> > > (or each indiv
Agree this is a good idea.
Let me know what we can do to help.
Jay
On Mon, Mar 19, 2018, 9:58 AM Jim Rollenhagen
wrote:
> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discussion, and not completed
> documentation. It's obviously t
On 2018-03-19 19:06:38 + (+), Jim Rollenhagen wrote:
[...]
> Huh, I had totally thought there was a theme for the specs site
> that most/all projects use. I may try to accomplish this anyway,
> but will likely be more work that I thought. I'll poke around at
> options (small sphinx plugin,
On Mon, Mar 19, 2018 at 3:46 PM, Jeremy Stanley wrote:
> On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote:
> [...]
> > What do folks think about a banner at the top of the specs website
> > (or each individual spec) that points this out? I'm happy to do
> > the work if we agree it's a
On 2018-03-19 14:57:58 + (+), Jim Rollenhagen wrote:
[...]
> What do folks think about a banner at the top of the specs website
> (or each individual spec) that points this out? I'm happy to do
> the work if we agree it's a good thing to do.
[...]
Sounds good in principle, but the executio
On Mon, 19 Mar 2018 14:57:58 +
Jim Rollenhagen wrote:
> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discussion, and not completed
> documentation. It's obviously too much work to go back and update specs
> constantly.
>
> What d
I'm all for the idea, although that may be because I've been been one
of the people in the past attempting to assist people who have found
specs, and who are are confused or frustrated. I believe it is because
some people latch on to the highly technical design documents when
they can't find $compl
On Mon, Mar 19, 2018 at 02:57:58PM +, Jim Rollenhagen wrote:
> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discussion, and not completed
> documentation. It's obviously too much work to go back and update specs
> constantly.
>
> W
I think it's a good idea especially as some times a spec is never completed
or not in the same release.
Thanks,
Amy(spotz)
On Mon, Mar 19, 2018 at 9:57 AM, Jim Rollenhagen
wrote:
> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discu
14 matches
Mail list logo