From: kilo a. G. K. <kg...@gm...> - 2010-11-29 09:03:46
|
Hi JP & team, all fine for me. Thanks for summing it up. kilo On Sun, Nov 28, 2010 at 5:47 PM, Jean-Philippe <jpm...@fr...> wrote: > Hi, everyone. > > Important, please take time to read up to the end :-) > (sorry for being that long, but you know, I can't ;-) > > After some discussions and feedback (Wolf-Dieter, Kristof, Mart, Kilo and I), > it appears that there's an important issue in the release schedule that we have > been more or less following til now : the D09 task, that is Simu v2.1 and > associated changes to car / car category / track physics related parameters. > > Because these changes imply some light to heavy rework of all : > - the car default setups (= human setups = robot baseline setups), > - the associated robot setups. > > It probably depends on the car sets (whether their category bounds and > parameter values are far or close to realistic ones) and the robots. > > But this has definitely to be examined and fixed (to whatever extent) > before 2.0, if we want 2.0 to be as close as possible to what users probably > expect from a 2.0 (I mean : when compared to 1.4). > > There's also some work around robots and their ability to support wet tracks, > after this nice feature has been added (the "weather" feature). > > So, you probably won't like it, but the date we propose now for the release > is as far as April 2011, given the remaining work and available spare time > of the critical developers/tuners here. > We'll probably also have to make a stricter selection on the list of tracks > for which we maintain a specific setup for each robot (keeping only a default > one for the other tracks). > Some robots might also don't have a specific setup for some (few) cars > if this helps saving time (to be discussed). > > I just updated the wiki page about our actual plan for 2.0 > (http://sourceforge.net/apps/trac/speed-dreams/wiki/ActualFeaturePlanFor20), > in order to add a first proposal about this "last straight to 2.0" plan > / schedule. > > There are still some few missing "planned release dates" > (TODO + ?-flagged ones) ... up to you who work on the tasks to complete ... > > But please note that : > - Kristof is the director about car category bounds / car baseline setups, > - Wolf-Dieter is the one for Simplix-related tasks, > - Kilo is the one for Kilo2008 and USR-related tasks. > > Not meaning they'll do all the work (from far, they need your help), > but that they organize all the work, and must be aware of everything > happening about it. > > So, before changing _anything_ in the plan for these, first ask them if OK. > But everything is open :-) (apart from refusing the facts ;-), > especially about who work on what. > > As for the car baseline setups, as already said, they'll have to be reviewed, > if not reworked : for this we have to follow a clear method that keeps us > from losing time in the future always asking the same questions; > the proposed method for this mainly consists in limiting the value settings > to the small list of "main" parameters having a major influence > on the car handling : > see https://sourceforge.net/apps/trac/speed-dreams/wiki/BaselineSetupMethod > for more details, based on Wolf-Dieter's proposal. Of course, it can be > followed up manually, before we have the (basic) car setup menu mentioned > in the Wiki page (and planned in the schedule if enough time). > > Eager to ear from you :-) > Any new idea is welcome. > Hope you'll carefully read it and realize it is mainly based on facts > we can't change, and be ready for going on this slightly more constrained > / directed way. > > Cheers, > > Jean-Philippe. > > PS: As far as the organization of the work in the project is concerned, I'd also > like to make a small change : define big SD development domains > (physics engine, graphics engine, car graphical design, robot development, > menu system, ... etc ...), and then assign each of these domains > to a dedicated sub-team, with a mandatory director ; a sub-team would > have to organize the reflexions, decisions and work on its domain, > in the name of the whole team, while its director would do the same > inside the sub-team and would be responsible of making its sub-team > communicate / work with the rest of the whole team, prepare technical > reflexions before submitting decisions to the whole team, ... etc. > In one (Wolf-Dieter's) word : adding "delegation" inside "democracy", > in order to be able to speed-up reflexions and decisions by avoiding > complicated and messy discussions on subjects that need a first in-depth > reflexion before discussing in a wider way ... > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Speed-dreams-devel mailing list > Spe...@li... > https://lists.sourceforge.net/lists/listinfo/speed-dreams-devel > -- http://three.sentenc.es |