On 10/16/05, Christoph Thiel
We had that kind of openness from day 0 - just go ahead, file a bugreport, attach a patch and discuss it with the developers. But be aware of the fact that we might not accept your patch - which has nothing to do with openness, but with the fact that the responsible developer / project manager will have the final say.
Christoph, I do think that this is the problem with communication in many open source projects is that we think that signing up for a users mailing list will give us some insight and say in future releases, whereas it seems to be more of a first level support situation. Some of what this thread is talking about goes beyond offering patches and bug reports and more into the general direction of the project. For example "please don't make OpenSuse yet-another-gtk-centric distribution" isn't exactly a bug report/patch situation. How does someone who's not a developer or Novell employee get involved in the openness you discuss, and find out what's being planned for upcoming releases? Sander P.S. I'm glad to hear about the in improvements YaST you mentioned, as that is the one weakness I've found in so far.