This retrospective week is designed to give us an idea of what it means to make an open-source contribution. We got to check out a lot of awesome projects!
Part of development is learning from other people's experiences, and so our contributions illuminate a third-person perspective and provide an external feedback system for their review.
What it does & How we built it
In our first PR (https://github.com/MLH-Fellowship/vscode-github-projects/pull/53), we integrated Webpack for proper bundling by directing the Webpack compiler to the correct ./dist/extension directory and specifying .js type. Rollup compiles our extension's Svelte files into the ./out/compiled directory.
In our second PR (https://github.com/MLH-Fellowship/SocioMark/pull/132/files), Shrill wrote detailed contribution steps for guiding contributors and visitors.
In our third PR (https://github.com/MLH-Fellowship/PoseRunner/pull/46), I am improving the contribution guidelines such that people know how to git rebase, add upstreams, and resolve merge conflicts so that they are more likely to contribute.
Challenges we ran into
There was a time constraint on both of us, the main challenge being to improve our apprehension of project structures and see things from the contributors' perspective.
Accomplishments that we're proud of
We are proud of contributing and of learning how important it is to provide detailed contribution guidelines, both in Issues and in the Contributing section of README.md.
What we learned
Team collaboration, how to navigate other people's projects and get a hint of it, how to ask the right questions, and how to motivate others to contribute to our projects through goodwill.