Hi all, Today we are having a dematerialized Pharo sprint.
# What is this sprint thingy? We join. We fix bugs. We discuss about fixing bugs. We add documentation. We review issues and pull requests. We make Pharo better for us and for everybody else :). # How is this sprint thing going on? In discord we have a text and a voice channel dedicated to #sprint. http://pharo.org/community <http://pharo.org/community> Please feel free to join and ask questions # What can I do to help? ## Get some knowledge => Read a couple of issues We have > 500 open issues. Some of them are difficult to reproduce, or the instructions are not clear enough, or maybe were already fixed but the issue was never closed. If everybody takes 3 issues at random and makes a review, we will be in much better shape for the next sprint!! Reviewing an issue is as easy as asking yourself the questions: - are there reproduction instructions? - it is specified the version / commit? - can I reproduce it? If some of those check fails, put a comment :) ## Get some action => Fix an easy issue In this morning (europe time) I’ve taken some time doing a pass on issues, and I’ve identified a list of potentially easy ones. https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%3AEasy <https://github.com/pharo-project/pharo/issues?q=is:issue+is:open+label:Easy> I’ve also categorised several of them as bugs, enhancements, new features and cleanups. Within those, you’ll see - super-easy (like adding a comment), - medium-easy (like changing some code following the analysis on the issue) and - hard-easy like a cleanup refactoring So if somebody wants to do a contribution for the first time, this list of 26 issues is probably a good place to look at. The info of how to make a PR is in here https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> ## Get to know other people involved in Pharo => Discuss with us in discord And have fun :) Guille
