Add community processes 2.0: - #43
Conversation
Sorry, something went wrong.
…ction, roles. Fixes #42
|
+1 from me. I left one comment which can probably be addressed in a future version. |
Sorry, something went wrong.
jaredmorgs
left a comment
There was a problem hiding this comment.
I'm on the fence a bit about the level of reference back to the GSoD processes in what appears to be a more generic Proposal Selection document.
Maybe we talk more about this together on the next Wednesday evening call or hash it out in Slack.
Sorry, something went wrong.
|
In today's weekly meeting, I discussed the intent of this MR with @camerons and @Loquacity . The intent of this MR is to just get us started with "some" guidelines, with the short to medium term motivation to decouple ourselves from the GSoD phases/links. With this intent clear, this MR has my 👍 given the scope. |
Sorry, something went wrong.
jaredmorgs
left a comment
There was a problem hiding this comment.
I approve of this MR:
- with the changes applied from Lana,
- with all other comments rolled into a GitHub issue tracking the suggestions.
Sorry, something went wrong.
|
I added a few comments for improvements, but I don't see any showstoppers. +1 vote to move forward with this. |
Sorry, something went wrong.
archaeogeek
left a comment
There was a problem hiding this comment.
With the exception of preferring to keep the +1/+0/0/-0/-1 voting scale I agree with the comments other reviewers have made
Sorry, something went wrong.
Summary
Pages/Sections AddedInside of the Community Page there is a list of links that serve as a table of contents -- several pages were added and some existing were renamed and organized under a section Decisions. Pages Added
Community Current Preview
There are changes to the Discussions page which is longer linked here, wasn't sure if that was on purpose or accident. I can confirm though all the links in the Community page link to where they need to go and no 404s. I have an animated gif I'll drop into slack as github won't let me post anything over 10megs :( -- and I'm not re-recording |
Sorry, something went wrong.
mgan59
left a comment
There was a problem hiding this comment.
Further review with comments on the content, found some broken links, etc..
@camerons if you want I can help tackle some of these changes / updates for the broken-links if we want to drive this forward and get it merged.
Sorry, something went wrong.
Co-authored-by: Lana Brindley <lbrindley@suse.de>
Co-authored-by: Lana Brindley <lbrindley@suse.de>
Co-authored-by: Lana Brindley <lbrindley@suse.de>
Co-authored-by: Lana Brindley <lbrindley@suse.de>
Co-authored-by: Lana Brindley <lbrindley@suse.de>
camerons
left a comment
There was a problem hiding this comment.
Thanks for all the feedback. I've either:
- Made updates as per your suggestion.
- Raised a bug #45, #46, #47, #48 (so the comment is addressed in a future release)
- Suggested the comment be raised in our forum
- Closed no action with my reasoning
I suggest we wait 24 hours for people to read my comments. If there are no objections (new word is lazy consensus) then someone else from the PSC approves this pull request.
Sorry, something went wrong.
|
I built the latest version and checked all the links fixed one outstanding link with #d7b86e1. We look g2m 👍 |
Sorry, something went wrong.
Updates processes for: decisions, prioritization, proposal-selection, roles.
Fixes #42
As this is a significant update to processes, we should endevour to get +1 votes from all PSC members.
Review and comments from other community members are welcomed.
Note 1: I'm hoping most feedback will be captured as a separate issue, and applied to a future version of these docs. That way we can get working processes in place, and start promoting community members into roles.
Note 2: We don't yet have a Code of Conduct Committee role. That is something which was postponed to a future version so we can get these processes in place without being blocked.
Note 3: I'm ashamed to admit that I haven't managed to get a working local environment stood up, and hence have only visually checked links in this update. It would be great if someone could check that for me.