Hi Nguyen, *, this is starting to get off-topic, but well...
On Fri, Oct 31, 2008 at 4:14 AM, Nguyen Vu Hung <[EMAIL PROTECTED]> wrote: > > In my very humble opinion, OpenOffice.org is not a truly open. It is. It is big and thus hard to get your hands on, but that doesn't depend on the "openness" of OOo. > Main coders is a team working in German and they work locally. > Language is not the problem but IMO this is what they want to do. This is not my experience (anymore, definitely was that way in the past, but not anymore). Developers hang out in IRC regularily (or if not, can be asked to join) and answer devel-related questions. They answer on the mailinglists as well. Of course if you don't ask at all, you don't get an answer. Of course if you ask on IRC where everyone in Europe is supposed to be sleeping, you'll probably not recieve any reply from one of the german developers. But that is again nothing related to the "openness" of the project, just people living in different parts of the world. > OOo is a very big project( 9.8 MLOC) and it is quite hard to add a new > feature, > or fix a bug. If a local team( or a contributor) shows a bug and tags > it WORK_FOR_ME( a stopper), "Works for me" means: Works fine, doesn't need a fix at all. So if you're waiting for a fix for an issue that was closed as "works for me", then you're waiting in vain. It will not be fixed unless you either make the ones who closed it change their mind (usually by discussing the problem on the appropriate mailinglist of the affected project) or provide a fix yourself (but if it is a bigger change, you should get in contact with the project first, to avoid conflicting and in the end wasted work) Again not related to the "openness" of the project, just a matter of common sense and restricted ressources. You just cannot fix anything. And of course it doesn't make sense at all to follow every request. (again common sense) > chances are they get fixed with very low probability. Due to the big size, > new comers will find it very hard to get started with OOo. This is nothing to blame on the "openness" of the project. >The main reason, IMO( again) is that, core coders of the OOo project is not >willing to share the knowledge. No, that's not the case. Plese give some *recent* examples. > In my case, I am trying to submit some bugs to OOo qa. Most of them > are still there, marked as "NEW" > and a questions pops up in in mind: How OOo treats contributors? How > QA works in OOo? Again: How is that related to the "openness" of the project? *Because* OOo is an open project and *everyone* can submit issues, the number of issues is very high. And compared to the number of issues the number of people who could fix things is rather low. Again common sense: If there are more issues that you (the developers) can handle, there must be issues that will remain unfixed/unhandled. But *because* OOo is an open project, *you* (the individual) can make a difference: You can reduce the number of issues by reviewing them, by consolidating related ones and maybe write a spec/proposal that combines multiple issues to save some work. Of if you have programming experience, you can fix a problem yourself and attach a patch. Patch handling has been much improved (despite the wrong facts that are spread in blogs or articles which are all based on the situation back in 2000/2002). If you have a patch and it wasn't touched/processed/evaluated within two weeks, make noise on IRC or on the mailinglists to have someone have a look at it. > The openness is heart of the Open Source developement model, an open > file format and an open source csv are not enough. Please state what of your points is related to OOo not being open. Your points are all based on the fact that OOo is big, has a big userbase and rather few active developers for the amount of requests made by those users. This is much different than saying: OOo is not open. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
