[openstack-dev] [infra] Wiki signups (was: Re: [ironic] third party CI systems - vendor requirement milestones status)

Jeremy Stanley fungi at yuggoth.org
Thu May 26 21:49:28 UTC 2016


On 2016-05-26 21:18:06 +0000 (+0000), Jay Faulkner wrote:
[...]
> This is a recurring issue though, and it affects new contributors
> disproportionately to those of us who have been in the community
> longer. Are there any plans in place to make it so wiki signups
> can occur in a more normal manner, or should projects move data
> that needs to be widely modifyable off the wiki?

I'll quote from my summit session summary:

    Consensus within the room was that we want to continue the
    current years-long effort of moving important content off the
    wiki, deprecating it for specific use cases when there are more
    suitable publication and information management mechanisms
    available. Some current uses will still need new solutions
    engineered of course, but over the coming year we'd like to get
    to a point where sufficient content is moved off so that we can
    better determine whether its continued existence is warranted.

    I'll be starting a thread on the openstack at
    lists.openstack.org mailing list in the next few days to cover
    the situation in greater detail and get the community-facing
    discussion going for this. Thierry Carrez volunteered to work on
    identifying remaining wiki use cases, and on handling
    discussion/collecting feedback throughout the wider community.
    Elizabeth K. Joseph volunteered to research alternative
    solutions for the current under-served use cases as they're
    identified, and determine feasibility of implementation.

    That said, we still need to have the wiki in sufficient shape to
    be able to continue serving its current purpose, to enable us to
    better identify its remaining stakeholders, and to provide them
    with an opportunity to comfortably transition to other platforms
    as we make them available. Paul Belanger volunteered (with
    Spencer Krum and James Blair assisting as backups) to get the
    current deployment into configuration management, and upgraded
    into a usable and reasonably spam-resistant state again.

    http://lists.openstack.org/pipermail/openstack-dev/2016-May/094540.html

I'll let the volunteers above chime in with additional details, but
know that we're aware this is a painful situation and we're trying
to balance keeping things sane for all consumers of the wiki against
the challenges of allowing new users to create/update content there.
-- 
Jeremy Stanley



More information about the OpenStack-dev mailing list