Handbook page on how to use and structure the handbook #101
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
Signed-off-by: Georg J.P. Link <linkgeorg@gmail.com>
|
@bproffitt and @BenLloydPearson this was on the CHAOSS board action items that you had both expressed interest in :) |
|
I just spoke with @bproffitt on the Common Metrics Call. @bproffitt suggested to create issues for the different pages that should exist in the handbook and work from there. - I agree with this approach. We agreed that focusing on processes is sufficient. No need to add an extra layer for functions, since CHAOSS is a small project. |
|
@GeorgLink this is ok from my side. Please merge if you feel it is too. |
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.
In starting off the handbook, it would be great to agree on a structure of the handbook up-front.
This pull request is the first implementation of using a pull request to discuss changes to the handbook.
Please comment on specifics and let's figure out together how we want the CHAOSS Community Handbook to be structured. To start, I copied the GitLab handbook and made some changes. I don't know whether a
function/processoriented structure will work well for CHAOSS. Maybe we go straight to the processes, since we don't have many different functions. -- Thoughts?