Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document team structure and project roles #334

Merged
merged 10 commits into from
Sep 1, 2023

Conversation

pavithraes
Copy link
Member

@pavithraes pavithraes commented Jun 17, 2023

Reference Issues or PRs

Closes #332

What does this implement/fix?

Put a x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

Documentation

Access-centered content checklist

Text styling

  • The content is written with plain language (where relevant).
  • If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
  • All links describe where they link to (for example, check the Nebari website).
  • This content adheres to the Nebari style guides.

Non-text content

  • All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
  • If there are emojis, there are not more than three in a row.
  • Don't use flashing GIFs or videos.
  • If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

We need to agree on the structure, and then update the current Teams to match before merging this PR.

@netlify
Copy link

netlify bot commented Jun 17, 2023

Deploy Preview for nebari-docs ready!

Name Link
🔨 Latest commit e806808
🔍 Latest deploy log https://app.netlify.com/sites/nebari-docs/deploys/64ee131e775c180008dd8b92
😎 Deploy Preview https://deploy-preview-334--nebari-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@pavithraes pavithraes added status: in progress 🏗 This task is currently being worked on area: community 🪴 Nebari community matters labels Jun 17, 2023
@pavithraes pavithraes marked this pull request as draft June 17, 2023 17:33
@pavithraes pavithraes added the DO-NOT-MERGE This is not ready for merge label Jun 17, 2023
@pavithraes pavithraes added status: in review 👀 This PR is currently being reviewed by the team and removed status: in progress 🏗 This task is currently being worked on DO-NOT-MERGE This is not ready for merge labels Aug 15, 2023
@pavithraes pavithraes marked this pull request as ready for review August 15, 2023 10:54
@pavithraes pavithraes changed the title [WIP] Document team structure and project roles Document team structure and project roles Aug 15, 2023
Copy link
Contributor

@kcpevey kcpevey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! I just had a question about CoC "training". Pending some clarity there, I'll approve.

docs/docs/community/team-structure.md Outdated Show resolved Hide resolved
Copy link
Member

@trallard trallard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @pavithraes. This has been long overdue. 💜

I left a couple of notes - I think it is important to signal that life changes often and that we a) recognize this and b) take that into account within our structure, so the active/inactive status should be flexible.
That is the only blocking change; the rest are nits/edits.

docs/docs/community/team-structure.md Outdated Show resolved Hide resolved
docs/docs/community/team-structure.md Outdated Show resolved Hide resolved
docs/docs/community/team-structure.md Outdated Show resolved Hide resolved
docs/docs/community/team-structure.md Outdated Show resolved Hide resolved
@pavithraes
Copy link
Member Author

@kcpevey @trallard Thank you so much for reviewing! I've made the necessary updates, and this is ready for another look. :)

Copy link
Contributor

@kcpevey kcpevey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Copy link
Member

@trallard trallard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect 💜 - thank you so much @pavithraes

@trallard trallard merged commit b76d583 into nebari-dev:main Sep 1, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: community 🪴 Nebari community matters status: in review 👀 This PR is currently being reviewed by the team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[DOC] - Document the Nebari GitHub team structure
3 participants