Now that we are on the new asciidoc/asciibinder system I was thinking
about the release notes RPM and the fact that the it was generated by
publican. Last I check the RPM is still a blocker for releases, and as
it stands now, we don't have a way to make this with the new source
My personal preference would be to remove this as a requirement for
releases, but this needs to be discussed with a larger group of people
as I don't think we can just say this is not longer a release criteria.
I am not sure who we need to talk with (FESCo? RelEng?), but before we
talk to them we need to have a discussion about it here and figure out
what the docs team would like to see done so that we are talking with
I've started an issue to track what needs to be done for the F27
Please add tasks or point me to our existing documentaiton for this
process. I'd like to get it updated for hte new docs process.
I was talking with Matthew Miller and we believe that we should change
the way our publishing process stages. Specifically, we should have the
new CI job that does publishing push updates to both docs.stg.fp.o and
docs.fp.o at the same time.
Fedora infrastructure republishes docs.stg.fp.o approximately every 5
minutes and they republish docs.fp.o once per hour. By pushing to both
we are creating a situation where accepted changes go live faster. In
general we have time to catch any staging errors with a new publish, and
in the case where we miss it, the site is republished an hour later
What do you all think?
as usual we have upcoming elections, but we won't have FAmSCo elections
Instead we will have elections for the new Fedora Mindshare Committee ,
which is not only for ambassadors but also for other outreach teams like
Mindshare has appointed and elected seats, similar to the Council, and
have one seat.
Each outreach team will make its own process to choose the representatives,
but we need them by the end of the election period.
Please keep in mind that the new Mindshare Committee needs to define many
processes in the first months, that means having experienced
representatives within Mindshare will be helpful to have success.
Once you have appointed your representative, please open an issue in the
Mindshare pagure  where you communicate who will be in charge for Docs.
For any questions or doubts please reply to this topic.
I'm at All Things Open¹ this week and saw a great talk yesterday by VM
Brasseur on maximizing drive-thru contributions in open source projects
(spoiler: the secret is effective and updated technical and
From the discussions in Flock and elsewhere, I wanted to share the link
to the recorded presentation and slide deck from her presentation. It
seemed relevant. I want to spend more time working on these ideas
throughout the rest of 2017 too. :)
Hope some of you find this useful or interesting!
Justin W. Flory