You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,11 +78,11 @@ Here is a non-exhaustive list of ways you can help out:
78
78
79
79
1. Help out others in the [community slack channel][slack-channel], or in some [discussions][discussions]. :sos:
80
80
81
-
1. Chime in on [bugs](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fbug+), [feature requests](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Ffeature) and asks for [help][discussions]. :thought_balloon:
81
+
1. Chime in on [bugs](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fbug+), [feature requests](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Ffeature) and asks for [help][discussions]. :thought_balloon:
82
82
83
-
1. Dig into some [`needs-investigation`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/labels/needs-investigation) or [`help wanted`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/labels/help-wanted):detective:
83
+
1. Dig into some [`needs-investigation`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/labels/needs-investigation) or [`help wanted`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/labels/help-wanted):detective:
84
84
85
-
1. Get involved in some [PR reviews](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/pulls). :nerd_face:
85
+
1. Get involved in some [PR reviews](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/pulls). :nerd_face:
86
86
87
87
# Opening Issues
88
88
@@ -218,7 +218,7 @@ If you are not here to report a bug, ask for help or request some new behaviour,
218
218
is the section for you. We have curated a set of issues for anyone who simply
219
219
wants to build up their open-source cred :muscle:.
220
220
221
-
- Issues labelled [`good first issue`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/labels/good%20first%20issue)
221
+
- Issues labelled [`good first issue`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/labels/good%20first%20issue)
222
222
should be accessible to folks new to the repo, as well as to open source in general.
223
223
224
224
These issues should present a low/non-existent barrier to entry with a thorough description,
@@ -234,7 +234,7 @@ wants to build up their open-source cred :muscle:.
234
234
235
235
See more on [asking for help](#asking-for-help) below!
are for those a little more familiar with the code base, but should still be accessible enough
239
239
to newcomers.
240
240
@@ -441,7 +441,7 @@ the body of the commit should describe the _why_ and _how_.
441
441
If you encountered any weirdness along the way, this is a good place
442
442
to note what you discovered and how you solved it.
443
443
444
-
An example of a stellar commit message can be found [here](https://github.com/weaveworks-liquidmetal/flintlock/commit/7a30dd99dc7c05827ba11050505c476799bb2932).
444
+
An example of a stellar commit message can be found [here](https://github.com/liquidmetal-dev/flintlock/commit/7a30dd99dc7c05827ba11050505c476799bb2932).
445
445
446
446
The format can be described more formally as follows:
447
447
@@ -468,7 +468,7 @@ The core team regularly processes incoming issues. There may be some delay over
468
468
469
469
Every issue will be assigned a `priority/<x>` label. The levels of priorities are:
470
470
471
-
-[`critical-urgent`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/labels/priority%2Fcritical-urgent): These are time sensitive issues which should be picked up immediately.
471
+
-[`critical-urgent`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm/labels/priority%2Fcritical-urgent): These are time sensitive issues which should be picked up immediately.
472
472
If an issue labelled `critical` is not assigned or being actively worked on,
473
473
someone is expected to drop what they're doing immediately to work on it.
474
474
This usually means the core team, but community members are welcome to claim
@@ -477,13 +477,13 @@ Every issue will be assigned a `priority/<x>` label. The levels of priorities ar
477
477
they will be paired with a core team-member to manage the tracking, communication and release of any fix
478
478
as well as to assume responsibility of all progess._
479
479
480
-
-[`important-soon`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm//labels/priority%2Fimportant-soon): Must be assigned as soon as capacity becomes available.
480
+
-[`important-soon`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm//labels/priority%2Fimportant-soon): Must be assigned as soon as capacity becomes available.
481
481
Ideally something should be delivered in time for the next release.
482
482
483
-
-[`important-longterm`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm//labels/priority%2Fimportant-longterm): Important over the long term, but may not be currently
483
+
-[`important-longterm`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm//labels/priority%2Fimportant-longterm): Important over the long term, but may not be currently
484
484
staffed and/or may require multiple releases to complete.
485
485
486
-
-[`backlog`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm//labels/priority%2Fbacklog): There appears to be general agreement that this would be good to have,
486
+
-[`backlog`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm//labels/priority%2Fbacklog): There appears to be general agreement that this would be good to have,
487
487
but we may not have anyone available to work on it right now or in the immediate future.
488
488
PRs are still very welcome, although it might take a while to get them reviewed if
489
489
reviewers are fully occupied with higher priority issues, for example immediately before a release.
@@ -492,11 +492,11 @@ These priority categories have been inspired by [the Kubernetes contributing gui
Indicates that the issue or PR contains a decision that needs to be documented in a [ADR](#adrs-architectural-decision-records)_before_
497
497
it can be worked on.
498
498
499
-
-[`needs-investigation`](https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm//labels/needs-investigation): There is currently insufficient information to either categorize properly,
499
+
-[`needs-investigation`](https://github.com/liquidmetal-dev/cluster-api-provider-microvm//labels/needs-investigation): There is currently insufficient information to either categorize properly,
500
500
or to understand and implement a solution. This could be because the issue opener did
501
501
not provide enough relevant information, or because more in-depth research is required
502
502
before work can begin.
@@ -548,7 +548,7 @@ Contributors are also welcome to backfill ADRs if they are found to be missing.
548
548
# :rocket::tada: Thanks for reading! :tada::rocket:
0 commit comments