-
-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "* added leadership princples to assets folder so we can build…
… that out as part of this" This reverts commit 5211781.
- Loading branch information
Showing
1 changed file
with
2 additions
and
10 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,10 @@ | ||
## Leadership | ||
NOTE: that whether or not 'leadership' is the right word to resonate across multiple FOSS communities is currently in debate. | ||
What we currently mean is: | ||
|
||
* Community assigned role i.e. Mozilla Reps, Fedora Ambassador, Rust mod team member | ||
* Advanced responsibility (informal or formal) i.e. advanced role permissions (to merge code) | ||
* Mentorship (formal or informal) | ||
* Project or Initiative Lead i.e. Drupal DB module owner | ||
* Regional community organizer/lead i.e. Openstack Vancouver | ||
|
||
Goal: Identify how healthy our community leadership is. | ||
|
||
Name | Question | ||
--- | --- | ||
Leadership Principles | How well do leadership roles reflect these [principles for inclusive leadership](/assets/leadership-principles.md)? | ||
Leadership Pathways | Are there visible, and active leadership opportunities? Is the language used to describe those roles inclusive? Accessible? | ||
Leadership Principles | Does our leadership follow leadership principles? | ||
Mentorship | Do we have active mentorships and related activities? | ||
|
||
Comments/Discussion |