openshift/openshift-origin-design

[Conventions] Reviewing conventions for places to add rationale and philosophy

rachael-phillips opened this issue · 4 comments

This issue should be a review of all places in the design conventions we want to add rationale and philosophy behind our conventions. An example is breadcrumbs. The second part of this issue will be writing and adding this rationale to the design conventions.

cc @andybraren @bmignano I added this issue based on our conversation last Friday: https://docs.google.com/document/d/1NoqsDRa28kwKZc1Fg3-tlOnn-C5lwKN9Vcidbh_DvKU/edit?usp=sharing

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.