**Please read this first** if you are interested in submitting a GSoC proposal for Canasta

[jeffw16]

Thanks for your interest in the Canasta Project! We always welcome new contributors and we're so glad you're interested in contributing to Canasta.

In 2023, our goal is to add multi-wiki support to Canasta (also known as wiki farm support). #57

The best way to be considered for becoming a GSoC contributor is by working on smaller existing items in the backlog, which can be found on our GitHub issues.

Here's a few that we would appreciate your assistance with completing:

• Switch to using PHP-FPM and mpm_event #54
• Use GitHub mirrors instead of Gerrit #35
• Move asynchronous tasks from web app container to dedicated MediaWiki maintenance container #33
• Add option to choose version to install Canasta-CLI#34 (don't plagiarize the first attempt by the other open source contributor)
• Add "canasta elasticsearch index" command Canasta-CLI#41
• "which docker-compose" check in install.sh is not always reliable Canasta-CLI#59
• Have --verbose also pass verbose to subcommands Canasta-CLI#61

If you are interested in completing one of these issues, please comment on the issues themselves to claim it. That way, nobody is working on the same task as someone else. Once you've done that, you will have two weeks to complete it. (Extensions are available as long as you are making progress on it.)

Here's how to improve your chances of being selected:

• Show us what you've got by proving your coding skills.
• The quality of code contributions and conceptual sophistication of the code you write is much more important than the lines of code you contribute or the number of commits you make. (This doesn't mean the code you contribute should be made overly complex; it means we are looking for impact.)
• It's not enough to write code for the PR that looks complete. Contributors must also demonstrate in the PR that their code works as expected and they have tested it out.
• If there are any ambiguities, it's important for the contributor to ask the questions they need answered so they can complete the job. The ability to properly communicate with your mentors in technical English is important to the success of a GSoC project and is therefore of paramount importance in being selected as a GSoC contributor for Canasta.

If you excel in completing one or more of the issues above, we will consider endorsing your GSoC proposal when you submit it to Wikimedia Phabricator. Anyone can create a GSoC proposal, but it is strongly advised you do not make a proposal unless we have notified you that we will be endorsing your proposal.

Please let us know if you have any questions.

[jeffw16]

We added some new microtasks:

• Add option to choose version to install Canasta-CLI#34 (don't plagiarize the first attempt by the other open source contributor)
• Add "canasta elasticsearch index" command Canasta-CLI#41
• "which docker-compose" check in install.sh is not always reliable Canasta-CLI#59
• Have --verbose also pass verbose to subcommands Canasta-CLI#61

[jeffw16]

Thanks for everyone's interest in becoming a GSoC contributor for Canasta!

To anyone new seeing this page for the first time: we've gotten several great candidates at this point and we'll now be proceeding with our next stage of candidate selection.

To the existing contributors: we will reach out to you with next steps if applicable.

[jeffw16]

Please keep in mind that proposals need to be submitted to Phabricator and the GSoC website by the deadline.

Also, I cannot reach out to you if you don't have an email showing publicly on GitHub. I'll assume you're not interested if there's no way for me to reach out to you privately.

[jeffw16]

Applications are now closed. Best of luck to the applicants. The results will be announced in the coming weeks.