Dirk Reiners wrote: > Hi Allen, > > Good idea. Anybody want to take a stab at it? >> All small issues that need fixing (experimental code etc) needs to be >> documented. A number of wiki pages exists for this now >> (PotentialContributions, ProjectIdeas, OngoingProjects, >> FeaturesToPortFrom1to2). Shouldn't all these be centralized to one and >> filled with content, so one can see what needs to be done? :) >> > They do serve different purposes, but I think not all of them are > necessary or easy to fill. > > Potential Contributions is a bit of a misnomer, IMHO. I'd call it > Bazaar, Grabbag or PuzzlePieces, as it's a wild mix of little things > that could be useful but need to be integrated. > ProjectIdeas looks good and I would leave it as is. OngoingProjects is > empty and honestly I have no clue what kind of things should go on > there, I'd remove that.
I cleaned it up a bit now, into ProjectIdeas (new stuff) and PotentialContributions (stuff made or in progress). I left re-naming and organizing it until we get even more stuff in there. (I can't delete wiki pages, so there some completely empty pages in there now.) > FeaturesToPortFrom1to2 seems too big to be useful, honestly. There is a lot > of little changes that need to be ported, the best way to find them is to > look at the diff in CVS from HEAD to to_gv_merge_7 and see if the change is > in 2. It sounds nasty and it is, but I don't really see another way. :( Ok. Hm. It still sounds to me as if someone needs to do just that and make a list (so that the rest of us have a chance at knowing what will be in and not once we switch)? Or is it up to each core-dev to move 'their' part? >> Immediate fix: Update Changes1To2 with a list on what you core-dev-guys >> have in your head for that. (or put in the description of 2.0 >> beta/release milsetones) >> > I would put the stuff that's been agreed on in the milestone and the > rest in the Wiki. Ok. I just added some small stuff to Changes1To2 from what I've heard here, to make it look better. Feel free to move things to the milestones. >> Screenshots / movies of each example on the website? Or in doxygen at >> least. (A separate doxygen run for examples & high-level documentation >> would probably make sense, to split that from API, which is more >> difficult to keep nicely formatted.) >> > Examples infrastructure needs to be added first. We still haven't quite > decided where to put them. One central directory or in the Source? I'd > still prefer the source and collecting them for install. Ok, so we have (in order of complexity and closeness to code): - tests - examples - tutorials - demos Tests should go with the source, yes. I could live with examples in the source _if_ they were properly referenced in doxygen and on the website. Tutorials as they are now (move examples over to tutorials instead?) Demos - not in dailybuild (separate pack there), but include in the large point release packs? >> (Is it possible to record from OpenSG? I don't think so, but there may >> be experimental code for it. Ought to be fixed and perhaps even >> automatically generated? .. start examples with a '--record' arg?) >> > We have a FileGrabForeground that can save every rendered frame to a new > file. We also have some contributed code from Mathias Gumz in Contrib > (VideoGrab) that uses ffmpeg to directly grab to video but I've never > gotten around seriously testing it. Yeah. Hm. I ought to contribute my 'hiresscreenshot' code. I got it to work pretty good (although it needs some improvement to be fully general.) How about mentioned the Contrib-code on the wiki, as stuff that works but could use some 'serious testing' ? /Marcus ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
