Marcus Lindblom wrote: > This is one big e-mail. I'm not sure how to begin answering it. From the > top of my head: > > * The roadmap needs to be there. At least something that we can look at > and comment on. Direction for effort is also a good point in this. > > * A 1.8 end-game list needs to be made, so we know what needs to be done > to get it released. Then work like mad on that. (There is work being > done on 2.0 everyday, I'd prefer finishing 1.8 first.) What is left?
I don't know. But I did create a page to start listing the things here: http://opensg.vrsource.org/trac/wiki/Planning1_8release I don't want this page to be a place to put things instead of tickets, but it could act as a nice central location to plan what needs to be done and point to the detailed tickets that should be completed. Almost an index to the tickets combined with a discussion area. What do people think, is this a good idea, can we try it for the 1.8 release? > * As said, we will use 1.8 for the current project (until march next > year), then probably switch to 2.0 if it is stable enough. We need to > know the status of 2.0 to know when to make the switch (and thus, if we > need/can contribute to make things happen faster). It is good to hear that you are planning to switch. I think we are going to switch within the next couple of months. There are many things that need ported over to 2.0, but the code itself seems pretty stable to me. > * I agree with Dirk's comment that OpenSG is really in a sort of 'middle > ground' with many users and too few contributing developers. Again, > fixing the roadmap for 2.0 & setting tickets for everything 1.8 would > help greatly. I think a planning page for 2.0 similar to the one I just created for 1.8 would help this out. > * I think IRC or anything text-based is better for conferences. That > way, we also have a log of the discussions. But that's just me. (We seem > to do pretty well here on the mail list, we just need faster iterations.) Any discussion would be good. IRC, skype, whatever. Let's just start discussing. :) > * Examples/Tutorials for new features are good. I think it would be easy > to do since you at least need to test something that builds only within > OpenSG that works with your new feature. Might as well put that up, > extend and document it. Agreed. > * Leadership: > > Dirk-as-benevolent-dictator is ok. However, it seems as he does not have > sufficient time to comment on all parts. > > Could we make a list of various parts of OpenSG where we have ppl with > sufficient time & knowledge to provide leadership (or at least be the > current 'point of contact' for communication), so that we have a clear > map over which parts are covered and not. Each person would then be > responsible to at least keep track of current status for her/his module > and coordinate development. > > It need not be a single person, and could be the "mail-list forum" for > some issues until we get more ppl commited. At least, the list of > modules/areas, current leadership and current status should be > summarized. (The PEOPLE file in trunk is a base for this.) I like this idea, but I don't know who would go where. Are you willing to take a first crack at making a wiki page like this to outline the leadership? > This overlaps the roadmap work in some sense. > > I think the most important thing is establish where we are on the map > and try to point out a heading to everyone. I agree 100% with you on this on. Without a roadmap we have no plan or direction and that is a bad place to be in a software project. -Allen ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
