add issue labels

This commit is contained in:
Benjamin Elder
2020-12-03 13:07:04 -08:00
parent 6b2ccec129
commit 4cacec6f3f
2 changed files with 28 additions and 4 deletions

View File

@@ -370,6 +370,21 @@ blockquote p {
height: 100%;
}
/* mock github labels */
.gh-label {
/* mimic github */
display: inline-block;
padding: 0 7px;
font-size: 12px;
font-weight: 500;
line-height: 18px;
border: 1px solid transparent;
border-radius: 2em;
background: #bfd4f2;
/* additional styling to allow using on a tags */
text-decoration: none;
}
/* mobile */
@media (max-width: 50em) {
#content {

View File

@@ -92,21 +92,30 @@ philosphy and direction.
Issues are tracked on GitHub. Please check [the issue tracker][issues] to see
if there is any existing discussion or work related to your interests.
In particular, if you're just getting started, you may want to look for issues
labeled <a href="https://github.com/kubernetes-sigs/kind/labels/good%20first%20issue" class="gh-label" style="background: #7057ff; color: white">good first issue</a> or <a href="https://github.com/kubernetes-sigs/kind/labels/help%20wanted" class="gh-label" style="background: #006b75; color: white">help wanted</a> which are standard labels in the Kubernetes
project.
The <a href="https://github.com/kubernetes-sigs/kind/labels/help%20wanted" class="gh-label" style="background: #006b75; color: white">help wanted</a> label marks issues we're actively seeking help with while <a href="https://github.com/kubernetes-sigs/kind/labels/good%20first%20issue" class="gh-label" style="background: #7057ff; color: white">good first issue</a> is additionally applied to a subset of issues we think will be particularly good for newcomers.
If you're interested in working on any of these, leave a comment to let us know!
If you do not see anything, please [file a new issue][file an issue].
> **NOTE**: _Please_ file an enhancement / [feature request issue][fr-issue] to discuss features before filing a PR (ideally even before writing any code), we have a lot to consider with respect to our
> existing users and future support when accepting any new feature.
>
> To streamline the process, please reach out and discuss the concept and design
> / approach ASAP so the maintainers and community can get involved early.
Please reach out for bugs, feature requests, and other issues!
Also -- Please reach out in general for bugs, feature requests, and other issues!
The maintainers of this project are reachable via:
- [Kubernetes Slack] in the [#kind] channel (most active, along with the community)
- The issue tracker by [filing an issue][file an issue]
- The Kubernetes [SIG-Testing][SIG-Testing] [Mailing List][SIG-Testing Mailing List]
Current maintainers are [@BenTheElder] and [@munnerz] - feel free to
Current maintainers are [@BenTheElder] and [@munnerz] -- feel free to
reach out directly if you have any questions!
See also: the Kubernetes [community page].
@@ -118,8 +127,8 @@ contributor guides, signed the CLA ... now what?
If you're planning to contribute code changes, you'll want to read the [development guide] next.
If you plan to contribute documentation changes, you'll specifically want to see
the [documentation section] of the development guide.
If you're looking to contribute documentation improvements, first: Thank you! 🎉🤗
You'll specifically want to see the [documentation section] of the development guide.
[git]: https://git-scm.com/
[hugo]: https://gohugo.io