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.
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 ? 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. Not just Blender but many open source projects work similarly. On Tue, Aug 5, 2014 at 1:13 AM, Nicolai Hess <nicolaih...@web.de> wrote: > 2014-08-04 22:37 GMT+02:00 kilon alios <kilon.al...@gmail.com>: > > I can tell you why. Because its rarely is simple for people not familiar >> with Pharo like me. >> >> I once tried to help Damien with PharoLauncher. I added the progress bars >> you get when you download a new image it was simple as pie. Then Damien >> recommended for me to try to add support to PharoLauncher for CLI . I >> understand how Pharo does CLI stuff but was not able to understand anything >> about how PharoLauncher downloads and handles images. I literally spent >> hours trying to understand the internal architecture and gave up after 2 >> hours or so cause I had no clue how things worked. >> >> Also finding a bug to fix in Pharo is time consuming, you have to go >> through one bug after another till you find that you can figure out whats >> wrong and how to fix. Its not easy and its very annoying at times. >> >> Generally what kills me is lack of motivation, I don't like reading >> other's people code, I don't even like reading my code. I prefer >> documentation , If I am to fix a bug I want at least someone to show me how >> it works because figuring it by myself takes a lot of time and I am simply >> not willing to invest that time just because people find documentation >> something that should write one day when their software reaches version 1 >> meaning years later. >> >> So you want to motivate people to contribute to bug fixes ? Do not allow >> any code to enter pharo main distribution without full class comments. I >> really mean "full class comment" not 2 , or 3 lines. >> >> PBE has been left hanging years after the release of 1.4 , why ? you >> expect people to contribute to bug fixes even when the most basic of >> documentation is abandoned ? >> >> Sorry if I sound harsh but you wanted a honest answer . For me >> undocumented code is far more annoying than a bug or a missing feature. >> > > I find it a bit to harsh :) > +1 for more source code documentation, but keep in mind that there are > people that may not do proper documentation (even change code > or fix bugs and don't document their code) but doing A LOT for pharo > behind the scenes. > > > >> >> >> On Mon, Aug 4, 2014 at 10:51 PM, stepharo <steph...@free.fr> wrote: >> >>> Hi guys >>> >>> I'm sure that most of you did not realize it, but Pharo does not >>> magically improve. It improves because some of us are looking >>> at the tracker issues and looking at the code and improving it. >>> >>> Since Pharo is yours I wonder why you do not take the time to improve. >>> In fact, this is the key advantage of true open-source: being able to have >>> an impact. An example, I was fed up to have a stupid widget to move >>> method between protocol and classes between packages. I fixed it. >>> It took my 20 min without knowing anything about Nautilus. >>> >>> And it improved Pharo Right now, Right there. >>> Of course if more people would be improving Pharo we could also focus on >>> enabling technology and frameworks. But >>> apparently we have to choose either we improve Pharo now or we invent >>> cool stuff that takes time. >>> I wonder why I do not go for the fame of writing a cool stuff instead of >>> just improving systematically the system. >>> >>> I wrote some roadmaps for people willing also to help. >>> >>> https://github.com/pharo-project/pharo-workingRoadmaps >>> >>> Stef >>> >>> >>> >> >
