This is intended to cover design, testing, deployment, and migration
for a Mailman 3 based successor to our current Mailman 2 services.
Specs can have multiple assignees, or none if they're destined for
the Help Wanted section. Get rid of the idea of a "primary" assignee
an just let all interested assignees be listed. Also drop the idea
that we should list Launchpad identifiers, since we don't even use
LP for task tracking anyway. IRC nicks are a more relevant short
form for us, after all.
Backups are important, and specs should address whether changes to
them will be needed. This also serves as an important reminder to us
that new services aren't truly implemented until they're backed up.
Our Cacti server is aging and needs to be replaced. Rather than go
through a difficult Cacti upgrade take the opportunity to replace that
system with a modern one that gives us more potential functionality.
The Zuul project has agreed that it would like to move from OFTC to
a native Matrix room. OpenDev can help facilitate that by providing
some services that keep our communities together. This spec is a
description of how we can proceed.
The beginnings of a specification for a central authentication
single sign-on identity broker service. This attempts to encapsulate
and combine many years of discussions and informal proposals from a
number of OpenDev contributors (listed as Co-Authors since much of
the text is theirs and not mine). The bulk of the plan is still
missing, and analyses of specific software options may now be
somewhat dated, so further updates are warranted.
Co-Authored-By: Monty Taylor <email@example.com>
Co-Authored-By: "James E. Blair" <firstname.lastname@example.org>
Co-Authored-By: Clark Boylan <email@example.com>
This spec describes evaluating Xwiki as a potential wiki farm setup
for Opendev communities at wiki.opendev.org, using an initial test
community and initially leveraging Xwiki.com "open source free hosting"
This was missing in the original spec. Additionally add ianw as
volunteer as most of the changes are pushed up and ready to go now that
we have agreement.
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
Our test images are constructed in a particular manner largely driven by
history of python focus in our CI system. This focus is no longer
present and we'd like to make our images a bit more predictable and
This spec outlines the plan for this.
The original plan to migrate all OpenStack projects may have been
overly-ambitious, but more importantly it's a policy decision
outside the Infrastructure team's immediate sphere of control. Most
identified gaps in the intervening years have been addressed, with
some final ones (like attachments) under review nearing completion
or well into a planning stage (like self-service team management).
There will always be new features some teams want, and indefinitely
delaying completion of this spec for such a treadmill is
Update the spec to only cover the original well-established first
phase, and remove the hand-wavy stubs for a second phase where
"everybody agrees to migrate." Also remove the dependency on central
identity management as there is no clear path forward on it
presently. Many teams are already relying on StoryBoard today, and
the handful of developers and maintainers for it hold fairly regular
meetings and can be reached readily with questions, concerns or
suggestions. Further improvement to StoryBoard remains a priority
for them, but it doesn't need to be a priority spec for the
Infrastructure team for that to be the case.
The oslosphinx package is no longer supported. Jobs should also be moved
to run with Python 3.
Signed-off-by: Sean McGinnis <firstname.lastname@example.org>
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
Add in the two topics being used by the update of configuration
manamgent effort. Also rewrite the url so that it doesn't end in a ) as
sphinx doesn't end up including this in the final url.
This is blocking a number of projects from migrating to StoryBoard.
In an effort to get more project teams to migrate, this spec plans
the implementation of how we are going to build & handle story
The README.rst file included some rough instructions which may not
be entirely clear to newcomers to the community. Add some details so
that they don't need to guess where some things are.
Switch the recommendation for Story commit footers to Task so that
the corresponding story task will get its status updated by our
automation accordingly (we hyperlink these since the SB webclient
has grown support for routing them to the correct story, so
including a Story footer as well is now unnecessary).
Drop the step of providing the review link in a story comment since
our automation will do this if a Task footer is included in the