Apologies if this is jumping the gun, but I would just like to express my
interest in picking up any of the discussions/sections that were jotted
down from the Dev room.
There were alot of good suggestions to be introduced. Is there a visible
overview of sections that require content?
Show replies by date
Apologies for the noise. Please ignore the earlier duplicate :)
Hi, you are definitely not jumping the starting line, and that is a great question to
which the answer is, yes and yes-sort-of.
The caveat is that things are messy process-wise right now and will be for a short while
yet. No questions are bad questions, and that is especially true curently.
My thinking is to have a very strong push over the next four weeks (is that a
"sprint"?) to have i) a clear status-of-content location, ii) processes tested
and in place for writing, review, editing, and merging (the "pull request
process"), and iii) the working schedule for 2.0 release (one of the items discussed
I know Shaun took notes by hand, I'll ask him to post the raw transcription of those
to this list and/or the git repo; however the git repo might be better served with a few
issues filed to track the individual items/ideas. For example, several new chapters and
sections were defined in the FOSDEM session, which could now have an issue-per.
That then is the way to get you--Ashley--started, is to create an issue for each of the
sections and/or chapters, and to get the notes/ideas so far organized into them, then to
let you get started writing/collating. I'll ask Shaun to start those up. Let us know
your GitHub account so the issues can be assigned to you (if I'm guessing the PR
Our OSPO team at Red Hat have a regular meeting on Thursday that partially covers this
project, and I've been thinking through how to begin to slice off that piece of the
meeting to have in a public forum for (at least) archive purposes; ideally it can be
interactive. Going for minimal viable something, I'll likely post a link to a Google
Hangout read-only to this mailing list & to Twitter for our meeting tomorrow. Or
failing that, I'll post the video of the meeting and write up all the necessary bits
into this mailing list so that we are making decisions _here_ and not in closed
discussions. Practice practice practice!