Project Lockdown
Search…
⌃K
Links
🚧

How to participate

ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.

About

​

Introduction

Project Lockdown is an initiative that highly encourages participation from the broader community. To this end, we crowdsource as many tasks as possible, in observance of our 3 values: Community + Accountability + Impact.
Please note that, as a result, the list of Issues you will find in this repository cover a wide range of needs, such as:
  • Technical Issues (Features, bugs and the like)
  • Member positions
  • Infrastructure needs (from setting up
  • General needs (identifying necessary tools or platforms, documenting and the like)
  • Enabling and growing our partners network
  • Seeking advise from experts in some
  • Looking for community feedback
**This document will help you understand how to proceed with this repository's Issues for a better experience for you and the whole community. Please read it before proceeding with **

Participating in Project Lockdown

How can I contribute?

Contributing in Project Lockdown is easy! There are 2 ways to proceed:

Becoming a Project Member

Project Members join a Team are an active part of the initiative and must be able to commit according to the responsibilities acquired. As a Project Member you'll participate in organized tasks and you'll have access to tools and other resources as well as training.

External Collaborators

It is not necessary to be a Project Member to participate and make a meaningful contribution to the initiative. There are plenty of Issues that can be solved without requiring to dive into the complexities of the project.

Issues

Structure of an Issue

Title

[PROD] [ADM] [NOTICE]

Contents

  • Templates - DO NOT POST WITHOUT A TEMPLATE.
  • Review the instructions on top & remove when ready to publish
  • Follow each of the segments of the Template
  • If your Issue is ready, please make sure to label it as Stage: Ready

Labels

Project Lockdown adopts a sane label approach to provide more structure and clarity to the different project tasks that are published.
The more important Labels types are:
  • Need: Illustrates the nature of the need described in the Issue. Issues are primarily organized by Need.
  • Stage: Determines the implementation phase in which the Issue is at present time.
  • Module: Indicates which module is the Issue related to.
Other relevant Labels are:
  • Priority: Sets the corresponding degree of urgency to solve the Issue.
  • Keyword: Lists specific technologies that the Issue requires.
A complete list of Labels and their usage can be found on the wiki:  How to participate > Labels​

Assignees

Teams

Project Meetings

Recordings of Project Lockdown meetings are publicly available here: https://drive.google.com/drive/folders/1byWldhm6uuernfmHD12jOXT1tM4E43-6?usp=sharing
Note: We are slowly implementing this element of Accountability in our processes. Please be patient until we have it fully operational.

Tasks flow

  • For code-related issues If you are not already, please familiarize yourself with GitHub's flow https://guides.github.com/introduction/flow/ Check the list of code-related issues: [Need: Code + Stage: Ready]​
  • For other type of needs All Issues have instructions on how to proceed to implement them. Should you have any doubts, please open a  Q&A Discussion. Check the list of code-related issues: [Need: Code + Stage: Ready]​

Other resources

You can find all necessary information to learn about Project Lockdown, its technical documentation and all you may need to collaborate in the initiative in our wiki:  Project Lockdown:
We strive to provide all the information you may need. If there is anything you feel is incomplete or not sufficiently explained please reach out to us by opening an  Ideas Discussion.