At the Train PTG, we discussed[1] what we could do to continue to
participate in open source internship programs like Outreachy while
keeping the high volume of applicants manageable. Outreachy requires
applicants to submit a contribution to the project they are applying
for, but we rarely have sufficient numbers of low-hanging-fruit tasks to
assign to all of them to allow all of them to make useful contributions.
Instead, we propose to give them exercises that most likely will not be
merged into keystone itself. These exercises are much more difficult
than typo fix tasks, and can be assigned to multiple people without
concern for applicants stepping on each others' toes. They can also help
new contributors get familiar with the architecture of keystone and the
development workflow, and encourages them to interact with the team.
[1] https://etherpad.openstack.org/p/keystone-train-ptg-outreachy-brainstorm
Change-Id: I615b1c029db59a1f9d8548dc0a80faa5c4150f2a
The current external-dev.rst page only contains 3
links that are semi-hidden in the current docs layout
unless someone specifically clicks on the
"External Developer" link.
This change removes the external-dev page, which only
contained 3 links, and now those 3 links are available
on the contributor index. These links also now show
up on the main keystone documentation page as well for
easy access to readers.
Change-Id: Ib0106ade10f1760a91bbac8e3c8e43b1aeda0884
We have a specification template and a keystone-specs repository, but
we don't offer any documentation or guidance on the specification
process we have.
This commit aims to clarify the difference between specifications and
RFE bug reports, and why we use both. It also describes the process
someone should follow if they want to file a feature request against
the project.
Change-Id: I5dbf6f81058de3f2a64a95e4cf34a1279a49c5dd
We see a lot of very small patches from new contributors to do things
like fix typos, correct grammar, switch to HTTPS URLs, and similar
trivial changes. Many of these changes are technically correct, but the
value they provide to the project is very low. Assuming the best of
intentions, the obvious conclusion is that these contributors very much
want to help, but don't know where to start and haven't been given
proper guidance.
This patch introduces a new guide that lists some ongoing tasks that we
always want help with. These should be tasks that someone with no
historical context in the keystone project should be able to pick up,
but by starting a few steps above typo fixes will be able to learn
enough to eventually make more significant contributions. When typo fix
patches come in, we can use this guide to gently encourage new people to
make more valuable contributions.
Change-Id: I2a003bbef3ffbde1818fddcb840905eac6f0618c
The specification detailing the great documentation migration
requires a doc/source/contributor/ directory for all contributor
documentation. Keystone had a directory specifically for this type
of content but it was in doc/source/devref/.
This commit renames devref/ to contributor/ because the term
`contributor` is more inclusive of other community members that
aren't necessarily developers. The specification also requires this
convention for consistency with other projects.
Change-Id: Id6363213dc6ba6946bd272ca5ee67b4604afc5ac
Partial-Bug: 1694460
Takashi Kajinami