Team structure and responsibilities¶

This page describes the team structure that we use in the Satyrn.ai community, as well as how you can get involved.

Expectations of all team members¶

We don't want team membership to be a big burden (many of us have one or more other jobs too!) but there are a few things that you should do as a new team member:

1. "Watch" the team compass repository so that you're notified when team conversations are happening.
2. Semi-regularly attend team meetings. You can find a calendar of upcoming meetings on the team meetings page.
3. Commit at least 6 months to team membership. Training and mentoring new team members is an investment by the existing team, hence team membership requires commitment from both sides. Beyond 6 months, if active team membership is no longer possible for you, you can always join the green team!
4. Let us know if you'll be unavailable or out of town for an extended period of time. It's no problem if you need to focus on other things for a bit, but it's helpful for the team to know who will be around. To do so, open an issue in the team-compass. If it's something you'd rather not mention to the public then send an email to one of the team members letting them know, and they can communicate it to the others.
5. Foster open and inclusive discussion. As a team member, you are responsible for ensuring that conversation in our communities is positive and inclusive. Open public issues to discuss things with the team. Try to do most communication in public spaces where others can join, or report back to team members if important conversations happened offline. When creating issues, provide enough context so that others can understand and provide their input. Encourage feedback and input from others often, and be patient when merging code - it is almost better to wait a bit for an approve than to self-merge.

Our teams¶

Satyrn.ai is organized into a few teams with varying levels of responsibility and expectations:

Satyrn.ai Contributors¶

Comprised of any individuals that have made significant contributions to the project.

Expectations and responsibilities¶

• Abide by the Satyrn.ai Code of Conduct.
• Generally do what they can to support the project.

How to join¶

Anybody that has made ongoing or significant contributions to the project is welcome to join the Satyrn.ai Contributors team.

Here are examples of things that may grant you Contributor status:

• Provide helpful responses in several Forum topics, GitHub Issues, or Pull Requests
• Provide Pull Request reviews that are productive and helpful
• Make several small improvements to any of our repositories.
• Make a significant improvement to any of our repositories.
• Be an advocate for the Satyrn.ai project to others.

Contributors are added by Organizers, who do so by adding a GitHub username to the satyrn-ai-team team on GitHub.

Team size¶

The Contributors team is very large and has no limit. Once you are a Contributor, you are always a Contributor. We encourage this group to be as large as possible.

Organizers¶

The organizerss are stewards and leaders of the Satyrn.ai community. They ensure that our repositories and collaborative spaces are healthy, inclusive, and productive.

Expectations and responsibilities¶

Organizers commit a larger part of their time stewarding our projects and doing the kinds of things that casual or infrequent contributors do not do. This may be focused on a subset of the Satyrn.ai organization (e.g., a specific repository or communication space).

For example:

• Watch issues. Monitor and provide helpful responses to issues in one or more repositories.
• Respond on the Discord. Monitor Discord and provide helpful responses.
• Guide the work of others. Provide helpful ideas and feedback so that others can make fast progress contributing to our projects.
• Triage issues. Identify what needs to happen, loop in relevant team members for discussion, get issues to an actionable state, and close completed issues.
• Mentor contributors. Share skills and knowledge, look for opportunities to let others earn and receive responsibility. Grow our tema.
• Review pull requests. Look over the changes others propose in repositories, provide feedback that improves them, and invite others to join you.
• Ensure healthy communication. Put extra effort into building a healthy, productive, friendly community dynamic amongst our community members.
• Attend our meetings. Try to attend our Team Meetings whenever you can.

Organizers generally have heightened privileges (e.g., "Moderator" privileges in a forum, or "Administrator" privileges on a repository). They also inherit all responsibilities Satyrn.ai Contributors team.

How to join¶

Organizers may be added by any other organizers. To add a new organizer a current organizer should recommend their addition via issues in our Team Compass, or via private communications channels. If there are no objections to adding a new organizer, add them to our list of organizers.

Team size¶

There is no limit to the number of maintainers that may exist in the Satyrn.ai Project. We hope to have a large and growing pool of regularly-engaged maintainers.

Our goal is to have at least two maintainers for any project within the Satyrn.ai community.

Web Team¶

Expectations and responsibilities¶

How to join¶

Team size¶

There is no limit to the number of Web team members.

Engine Team¶

Expectations and responsibilities¶

How to join¶

Team size¶

There is no limit to the number of Engine team members.

Models Team¶

Expectations and responsibilities¶

How to join¶

Team size¶

There is no limit to the number of Models team members.

Notebooks Team¶

Notebooks, whether Jupyter or Marimo, are a vehicle for spreading knowledge and uses. They are low friction to set up and the combination of prose, code, visualization, animation, and interaction give them a consistent way for people to share their knowledge and examples.

Expectations and responsibilities¶

How to join¶

Team size¶

There is no limit to the number of Notebooks team members.

Operations and Infrastructure Team¶

Expectations and responsibilities¶

How to join¶

Team size¶

Security Team¶

Expectations and responsibilities¶

How to join¶

Team size¶

Offboarding team members¶

Being a team member is not a life sentence. We expect team members to teach and grow other members so that they can pass their organizational responsibilities on to them. This encourages us to increase diversity, reduce burn-out and allow team members to shift their focus in reaction to changing life circumstances.

Declare yourself inactive¶

If at any time a team member feels that they would like to take a break from active team membership, they're can choose to be inactive by making a pull request to the team membership database.

Any team members that step down are considered "inactive". This means they no longer commit to the responsibilities of their previous team, but they retain their Satyrn.ai Team Membership status for life.

We keep a record of any inactive team members for the team in which they previously served. This is both to recognize their contribution, and to have a reference in case they wish to become active again.

Return from a break¶

Any Inactive team members may elect to re-join a team at any time. To do so, they should notify the other team members in our Team Compass, and add themselves to our team member list.

Removing team members¶

If a team member violates the Satyrn.ai Code of Conduct, they will be removed from team membership permanently (including from the Satyrn.ai org in general).