Ideas for beginners, for Sprints etc:

* Adding class comments/documentation, as mentioned, is a fantastic idea.
Maybe we can provide some code snippets, that will bring up a list of
classes with missing comments (or with too-short comments, less than X
characters). People can coordinate (on IRC, or via something like EtherPad)
on who's working on which classes.

* Not related to core Pharo code itself, but still very helpful: Test
various libraries for compatibility with Pharo 4.0. Pick your favorite
pharo-related project or library off of SmalltalkHub (or SqueakSource,
etc), try to load it into Pharo 4. Run the unit tests. Fix stuff until it
loads fine in 4.0.Try and use the library in a simple demo project. Best
yet, write a blog post about it. The success of Pharo largely depends on
the success of its ecosystem of libraries and projects.

* Benchmark things. Which JSON library (of the several available) is faster
at parsing large json objects in Pharo 4? That sort of thing.

* Write blog posts in general! Write tutorials and walkthroughs on how to
use some of the new 4.0 features. Do programming puzzles / interview
questions and post about em. Share tips on how you theme and customize your
Pharo images, which tools you use most, and so on.

* As mentioned before, at least browse the open 4.0 issues on the pharo
FogBugz. Try to think about how you'd go about discovering how to solve
them. You'll learn a lot about the system. Also, once the issues are fixed,
you can help test and confirm the fix (if you can figure out the 'how to
reproduce' steps). Follow the 'to reproduce' steps to make sure you
reproduce the error/issue. Then load the slice containing the fix from the
pharo inbox repo, and redo the steps again to make sure it was fixed.






On Fri, Apr 3, 2015 at 8:54 AM, Marcus Denker <marcus.den...@inria.fr>
wrote:

>
> > On 03 Apr 2015, at 14:36, Jigyasa Grover <grover.jigya...@gmail.com>
> wrote:
> >
> > Ohk.
> > No issues :)
> > Looking forward to other Pharo Sprints focusing on beginners :D
> >
>
> Yes… maybe other people have ideas?
>
>         Marcus
>
>
>

Reply via email to