Weekly Sync

[bobdingAI]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[bobdingAI]

Right now

1. Accept your Triage collaborator invitation. Check your email from GitHub or go to https://github.com/dora-rs//invitations. Without this you can't be assigned issues.
2. Review the 12 starter issues on your repo. They were auto-extracted from your accepted proposal — flag any that misquote or miscount your weekly plan. Comment on the issue or bring it up in the first meeting.
3. Star and Watch the upstream repo so you get notifications for PR reviews, mentor comments, and Discussion replies. (Top-right of the repo page → Watch → All Activity.)
4. Wire your fork to upstream:

git clone https://github.com//gsoc2026-dora-{topic}.git
cd gsoc2026-dora-
git remote add upstream https://github.com/dora-rs/gsoc2026-dora-{topic}.git
git fetch upstream
4. Periodically git fetch upstream && git rebase upstream/main so your fork stays in sync.
5. Set up local dev env — install Dora (pip install dora-rs or the Rust toolchain depending on project), run any "hello world" the project README points to. This is the bulk of Community Bonding work.
6. Introduce yourself in dora-rs's existing chat (Discord/Slack/etc. — check the dora-rs org README) AND optionally open a "Hi, I'm " post in the Show and tell Discussions category of your repo.
7. Read your proposal again and prepare 3 questions to ask the mentor in meeting #1.

Each week — the operating loop

1. Mon–Sat: Code on your fork.
   - Create a feature branch per task: git checkout -b week-03/control-api-list-endpoint.
   - Commit early and often; readable messages.
   - Push to your fork: git push origin week-03/control-api-list-endpoint.
2. Open a PR to upstream when ready. PR description must include:
   - Closes #N (the issue this PR addresses — auto-closes it on merge).
   - Brief description of what + why.
   - Test plan (how you verified it works).
   - Screenshots/recordings if it's UI work.
3. Move your issue on the project board. Drag from Todo → In Progress when you start, → Done when merged. (Board: github.com/orgs/dora-rs/projects/.)
4. Before your weekly meeting, post a status comment in the Weekly Sync Discussion thread: what you finished, what's open, what's blocking. This makes the live meeting about discussion, not status reading.
5. Attend the meeting (Sundays, your assigned slot). Show up with a screen-share-ready dev env.
6. After the meeting, mark up any action items in the Discussion thread or as new issues.

[bobdingAI]

Each week — the operating loop

1. Mon–Sat: Code on your fork.
   - Create a feature branch per task: git checkout -b week-03/control-api-list-endpoint.
   - Commit early and often; readable messages.
   - Push to your fork: git push origin week-03/control-api-list-endpoint.
2. Open a PR to upstream when ready. PR description must include:
   - Closes #N (the issue this PR addresses — auto-closes it on merge).
   - Brief description of what + why.
   - Test plan (how you verified it works).
   - Screenshots/recordings if it's UI work.
3. Move your issue on the project board. Drag from Todo → In Progress when you start, → Done when merged. (Board: github.com/orgs/dora-rs/projects/.)
4. Before your weekly meeting, post a status comment in the Weekly Sync Discussion thread: what you finished, what's open, what's blocking. This makes the live meeting
   about discussion, not status reading.
5. Attend the meeting (Sundays, your assigned slot). Show up with a screen-share-ready dev env.
6. After the meeting, mark up any action items in the Discussion thread or as new issues.

When you're stuck (any time)

• Technical question → open a thread in Q&A discussion category, @ when it's blocking your week.
• Blocking issue / not making progress → add the blocker label on an existing issue and comment what's holding you up. Don't wait for the meeting.
• Demo or milestone progress to share → Show and tell Discussion category.

Milestone gates (the GSoC dates)

Date (2026): May 24
Your action: End of Community Bonding — local dev setup must work; you should have started Week 1 tasks.
────────────────────────────────────────
Date (2026): Jul 10
Your action: Midterm evaluation deadline — submit your midterm form on the GSoC portal (Google sends the link). Mentor evaluates separately on the same portal. Failing
midterm = stipend stopped.
────────────────────────────────────────
Date (2026): Aug 24
Your action: Final submission deadline — your final work product (code + docs + a final report linked from your repo's README) submitted via the GSoC portal.
────────────────────────────────────────
Date (2026): Sep (TBD)
Your action: Final evaluation — Google sends both you and mentor an evaluation form.

Conventions to follow

• PR titles: short imperative, e.g. feat(control-api): add /dataflows list endpoint.
• Issue/PR cross-references: always use Closes #N or Refs #N.
• Branch naming: week-NN/.
• Commits: small, focused. Reviewable in <5 minutes. Multiple small PRs > one big PR.
• Don't force-push to PR branches once review has started — pushes appended commits are easier for the mentor to re-review.