A couple of questions: - Where should we get to work (1.8 or 2.0):
See: http://opensg.vrsource.org/trac/wiki/FutureOfOpenSg#Question:ShouldthisbedoneonOpenSG2.0orOpenSG1.8 I propose that we do pursue all the new documentation, examples, organization, etc with the 2.0 development. What does everyone else think? - What are we doing to do for user/developer guide documentation? Will it be wiki or dox files? Should we base it on the current guides? See: http://opensg.vrsource.org/trac/wiki/FutureOfOpenSg#Issue:Documentation I ask because starting tomorrow I am going to be spending the next month using some of the new features of OpenSG 2.0. If we can decided on the form for the documentation and get the old docs ported over, I am willing and interested in putting some time into documenting the new capabilities. -Allen Dirk Reiners wrote: > Hi Allen, > >On Mon, 2006-09-04 at 11:21 -0500, Allen Bierbaum wrote: > > >>> - What is the preffered format for discussing things on the wiki? >>>Starting a ticket (sort of like a forum thread) or opening a separate >>>page per issue where users could add comments (like the c2-wiki)? >>>(Or, in a larger sense, how should we manage this entire process?) >>> >>> >>> >>> >>This sounds like a good discussion to have to get things started. :) >> >>This is a question that should be answered by someone like Dirk, but I >>will throw a proposal out there for discussion. >> >> > >Let's see. ;) > > > >>- Mailing list: >>- User support >>- On-going threaded discussions. (such as this one) >>- Pointing to wiki and tickets for people to look at and comment on >> >>- Wiki: >>- For "putting it on paper" and documenting the decisions and plans that >>have been made. >>- The wiki pages will also serve as a source for new discussions and >>needs so this isn't really cut-and-dried. But from my experience I know >>that although wikis are great for collaboration they are not great for >>drawn out discussions with a large number of people. For example the >>"Future of OpenSG thread" would not work well there. >>- Discussing development alternatives. (for example the PluginPaths >>discussion happening right now) >> >>- Tickets: >>- Bugs >>- Once plans have been made on the mailing list and/or wiki, assign >>tasks that break the work down into chunks. >>- Link to tickets from the appropriate wiki page, but use the tickets to >>track work that needs done, milestones, and the detailed roadmap. >> >> > >Sounds good to me. use the list for the initial, free-flowing >discussion, once it gels a little put it on the Wiki, and after it >solidifies break it down into chunks that are tickets. > > Dirk > > > >------------------------------------------------------------------------- >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 > > > ------------------------------------------------------------------------- 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
