-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating SIP Editors & Steering Committe list + removed 1 Tech CAB member + add 3 new members #124
Conversation
documenting all SIP Editors
adding a folder & md file for SIP editors list
for documentation and community awareness
Adding Steering Committee members list
one more entry to the list
Added Cyle.btc to Editor Committee
gentle push. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments, mainly small editorial stuff and feel free to push back.
For the file names, rather than create a folder for each one, you could use a descriptive file name and use the same directory:
sips
|- considerations
|-- (cab files)
|-- (template/readme)
|-- sip-editors.md
|-- steering-committee.md
If we need to separate things futher, we could put cab-
on the front of each cab document so they sort together, but for now I think using just the file name would be clearer.
Remove the word "Committee" Co-authored-by: Jason Schrader <[email protected]>
Remove break. Co-authored-by: Jason Schrader <[email protected]>
no line breaks Co-authored-by: Jason Schrader <[email protected]>
Removed duplication Co-authored-by: Jason Schrader <[email protected]>
Nice Co-authored-by: Jason Schrader <[email protected]>
Agree Co-authored-by: Jason Schrader <[email protected]>
Removed contact detail re Jenny since she left Foundation
If becoming...
Updated file name
Updated file name
Moving to a folder above
Moving to considerations folder
moving to considerations folder
Ready to merge into Stacksgov main? |
Daniel expressed that he can't keep up with these changes enough in general going forward to make a contribution to the group, therefore best course of is temporary removal from the CAB until he will be available in the future.
adding 3 new CAB members
Update technical.md - adding 3 new CAB members
@whoabuddy can you review this too along with others, just to tidy the paperwork up to reflect the latest CAB members? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - but we should open an issue or make sure to track/schedule getting the "To be updated." bits finished in both files.
Thanks to @dantrevino for teaching me how to do all the tasks!