Every quarter we hold a Community Event called an Issue bash. These events aim to promote collaboration within our Community and introduce new contributors to GitLab.
We try to make the event accessible to contributors of all levels by collaborating on a range of tasks.
There is no shortage of tasks that contributors can try their hand at. Whether this is writing their first merge request to contribute a bug fix or a feature proposal or collaborating with the core team to track down and close some duplicate issues and streamline the issue tracker.
Comment on issues about what you have found out and your suggestions for issues, whether to close or keep open and if you've found a duplicate, mention the issue ID. Mention a key contact so that the correct course of action can be taken.
Anyone and everyone! We aim to make the Issue Bash as accessible as possible and offer things to do for contributors with no experience or plenty of experience. We also hope that contributors of all technical abilities can find stuff to work on.
Write a comment on the issue mentioning a key contact and the labels suggested using the label syntax ~label
Fixing known bugs and pain points or shipping existing feature proposals
Submit a merge request with a potential fix for the issue and mention a key contact so that proper labels can be assigned. The normal review process for Community Contributions will then commence.
2016-12-03 to 2016-12-04
2017-03-04 to 2017-03-05
2017-06-03 to 2017-06-04
2017-09-02 to 2017-09-03