Skip to content

Latest commit

 

History

History
99 lines (76 loc) · 3.77 KB

core-guidelines.md

File metadata and controls

99 lines (76 loc) · 3.77 KB
Raw

What is Core

Core members are maintainers first and foremost, with the added responsibility to manage the platform as a whole, for the betterment of the platform.

This can mean

  • final decisions on large topics via votes
  • handling the final decisions related to infrastructure (but not necessarily managing it, that can be anybody on the team)
  • handling any licensure items
  • being "legal owners" of assets and brand
  • owning any sensitive material (such as keys, passwords, payment information, etc)
  • manage any benefactor relationships
  • and any other necessary executive decisions

Core Expectations

Remain active

Stay up-to-date with changes that affect any one, but not necessarily all, of the various topics that comprise The Odin Project

  • TOP-meta contribution and tracking
  • Repositories under the TOP umbrella
  • Infrastructure that runs TOP
  • Relationships with benefactors/stakeholders (e.g. Thinkful)
  • Core and maintainer channels on the server
  • Major curriculum changes
  • Votes
  • Meetings
  • Initiatives (Fireside chat, TOPathons, gamejams)

Maintenance of the platform

  • Curriculum contributions, edits, changes, PR review, and helping drive contributors all fall under this umbrella
  • Core members should follow the maintainer guidelines for contributions, with relaxed requirements to spend time on initiatives
  • Some core members may have specializations that bend this guideline at times, though, contributing to top-meta is still a requirement
  • Maintenance can mean community events (TOPathons, game-jams, Fireside chats), design/UX, and other items like social media

Make informed decisions

  • Everybody is expected to vote
  • Some things may not have any guidelines
  • Use the voting system in place

Adhere to the social contract and communication guidelines

Found in the "staff-guidelines" document.

Be a leader

  • Continue to do everything in your ability within reason to improve and maintain the quality of the platform for the end-user with respect to the time and efforts of those maintaining the platform.

Voting levels

Small

No votes, but notification to team if necessary

Examples:

  • Renaming chat rooms
  • Archiving chat rooms
  • Moving chat rooms
  • Toggling dyno features
  • Bot command adds
  • Moderation action
  • Social media
  • Calls to action
  • Fireside chat organizing
  • Announcements

Medium

Fewer than 3 "no" votes in 1 hour, 24 hours if more time is requested for review

Examples:

  • Editing or changing chat rules
  • Adding a new bot
  • Adding or removing content from the website or curriculum (pending PR reviews)
  • Gamejam/TOPathon plan approval

Large

Simple majority vote, 24 hours

Examples:

  • Approving work on a new track,
  • Significant changes to the curriculum
  • Non reversible or difficult to reverse changes to the chat (deleting rooms)
  • Significant reworks of the chat rules system (i.e. the proposed ‘zaps’ matrix system)
  • Adding Chat-mods and/or Maintainers
  • Major site feature overhauls

Massive

Super majority vote (9 approvals if 12 core), ALL memmbers must vote

Examples:

  • Adding or Removing Core members
  • Removing maintainers or chat-mods
  • Decisions about the future of Odin

Etc.

Anything that is small to medium that is brought up during a monthly meeting can be decided upon. Anything large, must have an agenda item to have been decided in a meeting.

In general, disagreement at a lower level would escalate an item to the next level. So, if something is considered a small impact no-vote item, but concerns about it are brought up in chat.. Simply escalate it to medium and call a vote.

A core Member’s judgement should be used and considered when selecting a level. if a proposer calls something medium-impact, but someone else suggests that they would feel more comfortable escalating it.we should default to escalating.