This document contains very specific and unambiguous instructions for project managers that cover the bootstrapping & management of projects. Please read Project Management before if you haven't already done so.

This document is a work in progress. Some things are missing and it is not as polished as it should be. Revisit again soon.

#Bootstrapping

• Create a new Sourcehut project
• Create an issue tracker
• Create 3 mailing lists
• Create as many code repositories as necessary
• Create a wiki
• Put the links to the resources above to the wiki

#Client / Partner Onboarding

• Give client / partner access to the resources created on Sourcehut
• Share the wiki with the client / partner
• Share the link to the Client Onboarding document with the client

#Planning

• Go to the client / partner for gathering & discussing requirements

• Prepare a requirements specification document

• Put the requirements specification to the project's main repository

• Share the news in the project's discuss mailing list and let the developers know that you are waiting for a technical specification

• Gather all clients, partners and developers for a short time to agree on the acceptance criteria

• Gather all clients, partners and developers for a short time to agree on the milestones

• Work with the project's lead engineer to make estimations

• Create an offer for the client / partner for the compensation. (You should already have an idea about their budget and thoughts on compensation thanks to the hiring mail they should've been sent us in the beginning.)

• Agree on the compensation

• Ask the project's lead developer to start creating issues

#Reporting

• Agree on the reporting frequency

• Regularly produce reports with the project's lead developer and publish them according to the frequency agreed on

#Meetings

• Decide on the catchup / standup frequency (if at all)

• Send invitations to the calendars of everybody involved