I don't question people contribution to Pharo.
I do think however that we need to prioritize documentation. For example Blender development works in a way that a developers adding a feature to Blender main repo (not external code and external libraries) must add documentation to Blender wiki for the users.
+1
we do not like wikis (bah, I like them, but others don�t� and they have a point: a wiki must be maintained, otherwise is a waist of time and effort).
but� since Pharo4 we started a practice which is: we do not integrate any new stuff that is not correctly commented (in classes), with tests and (if possible), examples.
in the long way this is the best because Pharo relies a lot in �autodocumentation�.
now, we can improve this:
- even if new stuff has to come that way, most of the code inside image is poorly documented, tested and examples. We can improve that. We need to. I remember the comment per day Luc started a couple of years ago� is complicated to have them running in long way (until documentation is finished) because people get tired, but we could have a �two weeks comments� each three months or something like that. Not perfect, but better than what we have now.
- I dream with PetitParser integrated into Pharo, and then a markdown/pillar parser into class comments, allowing us to have better formating and references, etc. to improve navigation.
and of course, more can be done:
-tutorials for newbies (your work on the videos is great there, btw!)
-example projects in different areas (I think the laser game is a good one, but we need more �professional� examples: web apps, desktop apps, etc.)
-etc.
Also Blender has coding guidelines that need to be followed in order for code to added to main repo, does Pharo has something similar ? If yes where is such a document ?
Not really (at least that I know). We should.
Also Blender mailing list is very active with major bug fixes and features enhancement , in Pharo it looks to me that a lot of this discussion is located to fogbug . That means however than unless you frequent there its very difficult to track changes that affect your workflow.
we still need to find the best workflow, yes. I�m not happy with fogbugz in general, not because of the tool, which is great (and I�m very grateful that we have it), but because it does not seems to adapt correctly to an open source project, or at least to our own project. Anyway, maybe if we continue the "moving to github� effort, probably we will prefer to use the github tracker, eventually (even if not as powerful as fogbugz).
Esteban
Not just Blender but many open source projects work similarly.