On Sun, Apr 3, 2011 at 6:31 PM, Toon Verwaest <toon.verwa...@gmail.com>wrote:
> > The thing is that all things, even the smallest tiniest triviality, >> happens if someone *does* it. Nothing happens by itself. >> > I'm probably very naive here; and also a bit lazy and so on... So: could > you point me at a short text that describes exactly what I have to do to get > any line of code into a new Pharo? > It is explained in the Pharo FAQ http://www.pharo-project.org/documentation/faq How can I contribute to Pharo? Check out the wiki page HowToContribute<http://code.google.com/p/pharo/wiki/HowToContribute>for a detailed description of how to submit code. There is also a screencast<http://pharocasts.blogspot.com/2010/03/how-to-contribute-to-pharo.html>demonstrating the process. > > Like I figured out that these syntax coloring and compiling of traits > happens in a strange scope... how can I push this immediately back? I just > got used to always including these changes in my own repos since I didn't > know how to get access to such changes immediately; nor how to properly > publish them. > > My own main goal isn't Pharo, although I really like Pharo and would like > to contribute whatever I do back to Pharo. So knowing about the streamlined > process will help me push the small changes I do back. And yes, sorry, I'm > lazy ;-) > > cheers, > Toon > >
