-
Notifications
You must be signed in to change notification settings - Fork 303
Blog report of 27 Feb Governance meeting #538
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
Merged
Merged
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
layout: post | ||
title: "Governance Working Group Update: Meeting 27 February 2020" | ||
author: Val Grimm | ||
team: The Governance WG <https://github.com/rust-lang/wg-governance | ||
--- | ||
|
||
Hello everyone! | ||
|
||
This was the first governance working group meeting on Zulip. | ||
The following meeting will take place on 12 March. | ||
Reminder that EST & PST have changed to DST (summer time) as of 8 March, and CET will not change to DST until 29 March. These are most active timezones at present in governance wg so other timezones not evaluated. | ||
|
||
The agenda included | ||
1. Access policy RFC draft from Nell | ||
2. Pre-RFC process - determine right place to talk about this | ||
3. Follow-up on moving (community, devtools, nursery) to rust-lang | ||
|
||
You can find the [detailed minutes] on the [wg-governance] repository, but here is a quick summary: | ||
* Access policy RFC draft | ||
* Approved to submit as RFC | ||
* Pre-RFC process | ||
* Discussing on 12 March | ||
* Follow-up on moving (community, devtools, nursery) to rust-lang | ||
* Not complete, but some items discussed, list in official minutes | ||
|
||
There was additional off-agenda discussion after meeting about | ||
* Meeting Length | ||
* Outcome: 45-60 minutes | ||
|
||
* Handling Alumni | ||
* Need to define what info is needed | ||
* How talk about team Alumni who are not project alumni | ||
* Further discussion between XAMPPRocky and PietroAlbini, needs to be reported | ||
|
||
* Intro to contributing | ||
* Need a general intro as current info focused on main groups | ||
* Needs followup | ||
|
||
* Followup items not addressed on 12 March can be addressed in later meetings or async on Zulip, outcomes will be reported. [Zulip thread] links will be included in meeting summary blog posts in future. | ||
|
||
## Next meeting | ||
* Our next meeting will be 12 March 2020 via Zulip 18-19 CET / 1pm-2pm EST / 10-11am PST. | ||
* In 2020 the agenda is always at https://hackmd.io/ATj1rZJaRimaIfIWfAOYfQ | ||
* Current plan is: | ||
1. Pre-RFC process | ||
2. How to manage RFC discussion | ||
3. Plan agenda for next time, see Action Items in minutes from Feb 27 | ||
|
||
[wg-governance]: https://github.com/rust-lang/wg-governance/ | ||
[detailed minutes]: https://github.com/rust-lang/wg-governance/blob/master/minutes/2020.02.27 | ||
[Zulip thread]: https://rust-lang.zulipchat.com/#narrow/stream/223182-wg-governance/topic/meeting.202020-02-27 |
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.
Uh oh!
There was an error while loading. Please reload this page.