The previous 'Help Most Needed' list was presenting information in a way
that focused on the desires of the community rather than the value that
sponsoring organisations can generate - for both themselves and the
commons. Replace the list with a new list of 'Upstream Investment
Opportunities', and a process to keep them current by removing them
after they have been on the list for between 6 months and a year, so
that the submitter is forced to reaffirm their interest and the TC is
forced to re-evaluate the relevancy.
Since the current 'Help Most Needed' entries are generally not written
in a style emphasising the value to a business of investing, the initial
list is empty and will be filled as the TC evaluates business cases
according to its new criteria and understanding of the needs of
potential contributing organisations.
To preserve the existing information, the contents of the current 'Help
Most Needed' list appear as the 2018 upstream investment opportunites.
Links to the old list will temporarily redirect here until such time as
the new entries are in place, at which point we can redirect to the main
page with the latest index.
Change-Id: I65fef701dc2e3d50aa84e7ee79b068c78346c846
The infrastructure team no longer runs a cloud, therefore, let's
update the documentation appropriately.
Change-Id: I74d0465f61277d03d9f95fcbf1446c407a7e4728
This has come up several times discussing community goals, but the
effort it going to require people to do the work. This commit attempts
to describe the benefit that a consistent RBAC implementation has for
the entire OpenStack platform and people who use it.
Change-Id: I3e5ef86df320f2fbe945926bff3cc8d76839d3fe
Recent threads on the openstack-discuss mailing list [0] suggest
revisting the idea of formatting the help-wanted list to represent job
requests that describe the value of an initiative to potential
sponsors. This was feedback the OpenStack Technical Committee received
from the Board of Directors during the Vancouver summit in 2018.
This is an attempt at doing that with an existing cross-project
initiative to consume unified limits.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: I0cb4a0b1c0366afaa6d451d6c498d5b45b1fe242
Recent threads on the openstack-discuss mailing list [0] suggest
revisiting the idea of formatting the help-wanted list to represent
the value each initiative provides a sponsor. This feedback was given
to the Technical Committee during the Vancouver summit in 2018.
This is an attempt at describing the value contributing to Designate
has on a business.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: Ida1f2334db892107051d093d013e937cdee5f709
Recent threads on the openstack-discuss mailing list [0] suggest
revisiting the idea of formatting the help-wanted list to represent
the value each initiative provides a sponsor. This feedback was given
to the Technical Committee during the Vancouver summit in 2018.
This is an attempt at describing the value well-documented software
has on a business.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: Id12e50f084025713fc3aefc9c9ddf50b3a9072db
Recent threads on the openstack-discuss mailing list [0] suggest
revisiting the idea of formatting the help-wanted list to represent
the value each initiative provides a sponsor. This feedback was given
to the Technical Committee during the Vancouver summit in 2018.
This is an attempt at describing the value contributing to Glance
has on a business.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: I49d36758c3a7a5044f2a46a5a869819e36c24cca
Recent threads on the openstack-discuss mailing list [0] suggest
revisiting the idea of formatting the help-wanted list to represent
the value each initiative provides a sponsor. This feedback was given
to the Technical Committee during the Vancouver summit in 2018.
This is an attempt at describing the value improving the OpenStack CI
system has on a business.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: Icb0560e74afe4a62193aed573634280be645524a
Recent threads on the openstack-discuss mailing list [0] suggest
revisiting the idea of formatting the help-wanted list to represent
the value each initiative provides a sponsor. This feedback was given
to the Technical Committee during the Vancouver summit in 2018.
This is an attempt at describing the value sponsoring a goal champion
has on a business.
This commit also amends the document introduction to include intended
audiences and which parts of the document they might find most useful.
[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html
Change-Id: Idfa593a12550f8cdc3a5f617b8271a30e1d7a3b9
In Sphinx, it seems not possible to map a named link to a :ref:
object, so just directly embed it into the prose instead. This fixes
a 404 in the rendered version of the site. Thanks to n00balert in
the #openstack IRC channel for pointing this out.
Change-Id: Ice4d8235209645ca5ad1bb62906edbc72f793861
We should not wait to have 5 areas needing help to publish the
list, nor always have 5 areas on the list.
Change-Id: I664cfc6faeaf15b8adcbc47ceb490e6435d164b1
Zane Bitter