Sprint/Intersprint Calendar

	Wed	Thurs	Sat	Sun	Mon	Tues
Week 1i			Intersprint Planning Meeting
Week 2i	Announcement Survey Posted	Off-Boarding Planning 2		Proposal Voting	Hard Deadline Day
Week 1	Sprint Begins Weekly Report 1
Week 2	Weekly Report 2		Phone-A-Friend Day
Week 3	Weekly Report 3		Phone-A-Friend Day
Week 4	Weekly Report 4		Mid-Sprint Meeting
Week 5	Weekly Report 5		Phone-A-Friend Day
Week 6	Weekly Report 6		Phone-A-Friend Day
Week 7	Weekly Report 7		Phone-A-Friend Day
Week 8	Weekly Report 8		Phone-A-Friend Day			Soft Deadline Day

Schedule Overview

Intersprint Week 1 (Week 1i)

Intersprint Meeting occurs on Saturday, editors must join, open to public.
Due before the Intersprint Meeting on Saturday:
- Gather and document metrics for last sprint's information
- Write a blogpost summarizing the accomplishments of the last sprint in a format which is easily accessible to the general public, publish this blogpost to the site and share.
Due by Tuesday:
- All revisions to the announcement survey must be made and approved by the other editors.

Intersprint Week 2 (Week 2i)

Announcement Survey is posted on Wednesday.
On Thursday, anyone who is currently working on an extension of the last sprint must have and present a plan by which they can wrap up their work by the Hard Deadline Day.
Due before Proposal Voting on Sunday:
- Editors must have their three sample proposals completed and any changes to the proposal format must be completed before this day.
- Anyone else looking to submit a proposal must do so by this day.
Due before Hard Deadline Day on Monday:
- All Intersprint work mustbe completed by this time.
- All work on any extended Sprints must cease by the end of this day.

Week 1

Sprint begins on Wednesday.
- All members must have joined the Matrix room and filled out the survey by this day.
- Proposal voting ends on this day, Editors must announce the next project and post the first Weekly Report on this day.
- Editors must have a specified Phone-A-Friend Day time range and committed member to be there for that time.
Look at participating members' timezones, and depending on feasibility, pair people up in similar timezones.
Wednesday through Saturday is an Onboarding Period.
- Members should get to know each other by then, introductions and icebreakers should be completed.
- Editors should reach out to members throughout this period and get to know them.
- Each member should understand what part of the project they have elected to become a Subject Matter Expert in by Saturday.
- The Point of Contact should be reached/communicated with by Saturday, and project maintainers should be notified of our effort by then.
Wednesday through Saturday should be dedicated to getting feet wet with the work.
- Establish a Codeberg Wiki and each person should begin documenting their aspect.
Due Tuesday:
- Members should collectively decide to what milestones they plan to collectively accomplish by the end of Week 4.

Weeks 2-3

Weekly Report posted every Wednesday outlining what has been planned and what needs to be accomplished.
Due every Thursday:
- Members should notify both Editors and the other Members what tasks they promise to have done by the end of the week. If tasks are left uncommitted or people have not made promises by the end of the day, Editors need to start reaching out via DMs.
Each Saturday will be Phone-A-Friend Day, a dedicated, common period of time in which members can ask each other for help or advice on parts they are stuck at.
- On this day, people should commit to having the Matrix chat open and whether or not Jitsi calls are held can be decided in the moment.
- One Editor should make a commitment ahead of time as to being available to "seed" activity on these days, although we should still stress that this is for everyone to attend and get help from each other.

Week 4

Weekly Report posted on Wednesday.
- Discussions surrounding the time for the Mid-Sprint Meeting on Saturday to occur should begin.
On Saturday, the Mid-Sprint Meeting occurs.
- Editors must attend, open to the public. Discuss Sprint progress, talk about any corrections needed to be made in Editor conduct, likelihood of finishing, etc.

Weeks 5-7

Same as Weeks 2-3.
Offboarding Planning 1 begins on Thursday.
- Members must begin working on developing a plan to wrap up the work and hand it off to the maintainers by the Soft Deadline Day, in accordance with the Offboarding Checklist.
- Members can elect to form a subteam and extend the project through the Intersprint Period. This subteam will need to decide on a leader to manage the Intersprint Period, and state what they expect to accomplish with the given time.

Week 8

Weekly Report posted on Wednesday.
The Offboarding Plan must be finalized and presented to the editors by Thursday.
Soft Deadline Day is on Tuesday.
- Unless the project has been extended, work should be done at the end of this day.. Pull requests should be made, code should be cleaned up, the Sprint period is over and the Intersprint period begins.

Further Notes on Structure

About the Promise System

Any task that is discussed during the Intersprint Meeting, Mid-Sprint Meeting, or in-the-moment must have both an assignee and a promised (estimated) due date attached to it.

About Weekly Check-Ins

With the publication of each Weekly Report, Editors are to ask Members "What do you commit to getting done this week?" The member then selects a task from the Weekly Report's list they expect they can finish in that time and promises to complete it.
- In order to ensure tasks can be clearly understood, selected, and completed, Editors should be careful to break them down especially well during the Weekly Reports.
- Editors should note which skills correspond to which tasks to make the aspect of volunteering issues easier.
- The exception to this is Week 2, where tasks are discussed/assigned at the end of Week 1, before transitioning over to the promise system from there on out.
If a member fails to complete the task, the Editor asks them "Why were you unable to finish your task this week?" and then takes note of the reason.

About the Intersprint Period

During the Intersprint Meeting, alongside meeting notes should be kept a list of deliverables that are expected to be done by the end of the Intersprint period.
These deliverables are then fed into a Kanban board and explicitly decided upon by the Editors who is promising to complete what and by what date. Every single deliverable should be accounted for during the meeting.