📝 docs(ROOT): Add charter area leads for F45–F46 term #17
Labels
No labels
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mindshare/docs!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add/committee-assignments"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The F45 housekeeping meeting (mindshare/tickets#130) assigned each committee member to a charter area, but this was only recorded in a ticket comment. Adding leads directly to the responsibilities section makes ownership visible to the community and to new contributors looking for the right person to contact.
And yes, I did intentionally use
[U+2013]symbols in this PR. 😉Three approvals? Merging this.
📝 docs(ROOT): Add charter area leads for F45–F46 termto ccto 📝 docs(ROOT): Add charter area leads for F45–F46 term