f8c1dd508e
A common request is better insight to how our hosted sites are accessed. This allows people to find 404s and fix them, invest in popular pages to ensure they are accurate and up to date, as well as measure if changes are effective over time. "Traditional" tools in this space often expose far more user information than we are comfortable with. Thankfully there exists a GPL tool, goaccess, that allows us to remove sensitive data from its reports. This will allow us to publish the data without concern over what is in the reports. Change-Id: I3e6673def7edcb2f31f9be88e1831f716f6e8c9d
Infra Specs Repository
This is a git repository for doing design review on enhancements to the OpenStack Project Infrastructure. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.
Expected Work Flow
- Create a story in StoryBoard with a task affecting the opendev/infra-specs project
- Propose a change to this repository and make sure
Task: #<taskid>for the corresponding story's initial task is included as a footer in the commit message (seeCONTRIBUTING.rstfor relevant documentation links). This change should also add an entry for the proposed spec document in theApproved Design Specificationssection of thedoc/source/index.rstfile. - Once proposed, members of the community provide feedback through code review, and the specification should be revised until there seems to be some reasonable consensus as to its fitness.
- When ready for final approval, request addition of a call for votes to the weekly infra meeting agenda.
- If agreed by the meeting attendees, the chair will announce an approval deadline before which members of the Infrastructure Council are asked to cast their roll call votes on the proposal under review.
Once a specification is approved...
- Update the story, copying summary text of specification to there.
- Leave a comment linking to the published URL of the specification on the specs site.
Revisiting Specifications
We don't always get everything right the first time. If we realize we need to revisit a specification because something changed, either we now know more, or a new idea came in which we should embrace, we'll manage this by proposing an update to the specification in question.