Update README.md #36
Merged
Update README.md #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15 tasks
9 tasks
gianarb
previously approved these changes
Sep 18, 2020
displague
added
the
kind/documentation
displague
reviewed
Sep 18, 2020
displague
previously approved these changes
Sep 18, 2020
mmlb
previously approved these changes
Sep 21, 2020
mmlb
dismissed stale reviews from displague, gianarb, and themself
via
46a0083
mmlb
force-pushed
the
rainleander-patch-2
branch
2 times, most recently
from
46a0083
to
0b67520
Compare
Signed-off-by: K Rain Leander <rainleander@users.noreply.github.com> Signed-off-by: Manuel Mendez <mmendez534@gmail.com>
mmlb
force-pushed
the
rainleander-patch-2
branch
from
0b67520
to
24f62b4
Compare
mmlb
approved these changes
Sep 21, 2020
|
Rebased on master and squashed the commits, as its really a fixup anyway. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: K Rain Leander rainleander@users.noreply.github.com
Description
Our repositories should be the example from which adjacent, competing, projects look for inspiration.
Each repository should not look entirely different from other repositories in the ecosystem, having a different layout, a different testing model, or a different logging model, for example, without reason or recommendation from the subject matter experts from the community.
We should share our improvements with each ecosystem while seeking and respecting the feedback of these communities.
Whether or not strict guidelines have been provided for the project type, our repositories should ensure that the same components are offered across the board. How these components are provided may vary, based on the conventions of the project type. GitHub provides general guidance on this which they have integrated into their user experience.
Why is this needed
Fixes: #38