On 2010-01-12 20:40, Dominik Rau wrote: > Hi. > > Am 12.01.2010 15:17, schrieb Marcus Lindblom: >> On 2010-01-12 13:14, Dominik Rau wrote: >> >> >>> If you need help (web space, web design, machines for daily builds, >>> documentation, domain registrations...) let us (the community) know - >>> I'm sure that there are more people out there willing to help. However, >>> you (the core team) have to coordinate that. >>> >> Or, failing that, announce that you need help with coordination and >> announce that the potato is in the air. :) > > Well, I guess it's easier if the guys with the big picture in mind > define some tasks, but this might be also a matter of taste (and > involvement in the project). But let me say it that way: Getting the > potato back in the air is exactely what I try to achieve with this > mailing list thread. :)
Oops. By "you" in my comment I meant the core devs. English is such an ambiguous language. (Swedish is way better, all the time ;-P) I'm just a user just as you (on Windows, at a company) that really would like to see OpenSG work out well. I suppose what OpenSG needs is some way to make contributions in code, documentation and other resources easier. But OpenSG is after all a rather complex product that might need a clear direction if not to fall apart. I've had the feeling that the core devs are rather strict on how things should be done. This is good if they have time to manage contributions etc etc. If not, it sort of hinders progress and usage. OTOH, there's probably more than enough code in there that it's pretty hard to change things fundamentally now. W.r.t. Windows-builds, there's nothing stopping anyone from publishing such builds themselves (but regular releases do help, as in-the-middle builds are seldom made externally). Tagged releases (i.e. 2.0rc1) is something that even I could build and release, and it would be worth the effort if as people are usully more inclined to more use, test & report bugs on "official" releases. Perhaps we should go to time-based releases, and do one every quarter. If we start now and declare that what we have now is OpenSG 2.0 10R1 (or something, the first offical 2.0 release anyway), I'd wager there will be at least some who shift and try it out. (After all, we've been using 2.0 for over a year, and others even longer, so it should be reasonably good, and the pieces that aren't ported over will be reported.) Cheers /Marcus ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
