Skip to content

Add team communication process to TEAM.md#26

Open
Ajay-Singh-Adhikari wants to merge 10 commits into
mainfrom
feat/contributing_guide
Open

Add team communication process to TEAM.md#26
Ajay-Singh-Adhikari wants to merge 10 commits into
mainfrom
feat/contributing_guide

Conversation

@Ajay-Singh-Adhikari

@Ajay-Singh-Adhikari Ajay-Singh-Adhikari commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Relates to #19

What changed

TEAM.md had no documentation on how the team communicates day-to-day. Without this, new contributors have no reference for what to post, when, or where — updates get missed and PRs go unnoticed.

This adds a "How Team Communication Will Be Done" section to the existing TEAM.md.

TEAM.md — communication process section added

Added a table defining what gets posted in #alumni-connect, by whom, and when:

  • PR opened and merged
  • Issue picked up and completed
  • Blocker hit
  • Key decision made
  • Saturday sync (agenda Friday, notes Saturday)

Two rules added: keep updates short, no skipping the Saturday sync.

Acceptance Criteria from #19

Covered by this PR:

  • Communication process table defined (what gets posted, when, by whom)

Still remaining before #19 can be closed:

  • GitHub↔channel connection set up (webhook or manual posting protocol)
  • Weekly Saturday sync established as a recurring calendar invite
  • Process documented and pinned in the #alumni-connect channel

Documents the team communication protocol for the alumni-connect
channel and the standard PR description format for the project.
Add standard format for PR descriptions
…rding guide

Moves communication process table to docs/communication-process.md.
Rewrites CONTRIBUTING.md as a full onboarding guide covering prerequisites,
project understanding, picking up work, branch/commit conventions, PR format,
and post-merge process.
Removes communication-process.md and consolidates content into team.md
under a dedicated section for how team communication will be done.
Removes docs/team.md and adds the communication process table to the
existing TEAM.md in root under a dedicated section.
@Ajay-Singh-Adhikari Ajay-Singh-Adhikari changed the title Add contributing guide and team communication process Add team communication process to TEAM.md Jun 13, 2026
Covers prerequisites, understanding the project, picking up work,
branch naming, commit conventions, PR format, and post-PR process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants