Excerpts from Dmitri Zagidulin's message of 2015-04-03 18:28:01 +0200:
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.
nice ideas. though beginners may not have any favourite projects. are there any stats on which projects are popular so those can be chosen for testing?
* Write blog posts in general! Write tutorials and walkthroughs on how to use some of the new 4.0 features.
same problem here, being new to pharo, i would not even know what the new features are. this should be documented in release-notes probably. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/