Skip to content

Latest commit

 

History

History
65 lines (42 loc) · 3.16 KB

File metadata and controls

65 lines (42 loc) · 3.16 KB

Contributing Guide

Welcome! We are glad that you want to contribute to the AI Alignment Working Group.

Please review the CHAOSS CONTRIBUTING.md for general ways to contribute to CHAOSS; this document provides context specific to the AI Alignment working group.

Join the AI Alignment Slack Channel #wg-ai-alignment channel or submit pull requests if you'd like to reach out to the community!

Ways to Contribute

We welcome many different types of contributions including:

  • Metrics definitions
  • Bring your ideas related to AI Alignment for OSS and invite others to work with you!
  • Issue Triage
  • Speaking about our work at conferences
  • Inviting others to join (especially perspectives not represented here) - building bridges between this work and other communities is critical!
  • Writing about our work (blogging, posting)
  • Sharing relevant news articles, posts, research (etc) anything that helps us in the context of open source, AI and alignment. This can be done in Slack or via the issue template for links.

Working Group Chairs

There are people you can count on to keep things moving, and to help unblock you or answer questions if you are unsure.

Your current co-chairs are:

Chair Primary Role Descriptions

Chairs in the context of CHAOSS are those responsible for the productivity of the group and success of its contributors.

  • Responding to newcomer questions in [chat channel] and on GitHub.
  • Helping select tasks for newcomers or other community members who are unsure of where to start.
  • Reviewing pull requests and tasks.
  • Providing useful feedback in issues.
  • Encouraging and participating in discussions
  • Modelling Code of Conduct expected behaviors and escalating concerns to the Code of Conduct Committee if need be
  • Bridging the group with broader CHAOSS governance efforts (for example promoting elections)

Working Group Meetings

  • Agendas
  • Facilitation

How to Become a Co-Chair

If you are interested in supporting this working group through contribution of the co-chair activities- please reach out to any of the current co-chairs. We hope to better define this process in future.

Review Periods

Once per year, we'll check in with our team members (both active and on break) to ensure they are feeling supported, and to check if they will remain active on our team for the coming months. If we do not hear back from members at check-in time, they will be transitioned to an emeritus role.

As of this writing, the next review period will be May 2027.

Developer Certificate of Origin (DCO)

All contributions require a DCO sign-off. Please visit the DCO Setup Knowledge Base article for details.

Sign off each commit with:

git commit -s -m "Your commit message"