Re: Hello
"Frédéric Becquier" <[email protected]> Wed, 15 Nov 2006 14:52:35 +0100
| Newsgroups | gmane.comp.kde.kplato |
|---|---|
| Message-ID | <[email protected]> |
--===============0342421162== Content-Type: multipart/alternative; boundary="----=_Part_55670_2842735.1163598755679" ------=_Part_55670_2842735.1163598755679 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello! We have decided to work on large tasks and as we don't know very well the application we need your help to find other essential tasks. The two tasks you have mentionned interest us (PERT, KSpread plugin). Best regards. Nicolas MICAS, Fr=E9d=E9ric BECQUIER, Florian PIQUEMAL, Alexis MENARD, Fr= =E9d=E9ric LAMBERT. 2006/11/15, Dag Andersen <[email protected]>: > > Mandag 13 november 2006 16:47 skrev Nicolas MICAS: > > Hello! > > > > We haven't see the question asked by Dag about our criteria for > selecting > > things to do. > > To answer this question it is easy! (or ISI as you wants :P) > > We have studied the TODO list of KPlato on SVN and after clear it from > all > > things which were done we have selected those which seems to be most > > important and easily realisable during our project. > Yes, it's nice to be able to finish something :) > I was also thinking of whether you preferred many small fixes, or one or > fewer > larger tasks, gui, non-gui... > I thought maybe something that is distinct which you can point your finge= r > at > and say "We Made That". Should make it easier for you to document what yo= u > have done, also (important, no?). > > The things mentioned by Jim in his other answer to you could be > canditates, I > think. In general, I have almost not touched functions needed for project > execution yet, I haven't gotten further than the planning stage. > > Another example; I would like to be able to get data from project(s) into > kspread for further processing. The method would be to make a plugin for > kspread that fetches data from kplato files. There exists such a plugin > for > kexi which uses SQL to extract data from a database. I was thinking of > something similar. > > > We are studiing a another items to do, relative to the PERT method, it > will > > consist to find a simple way to key PERT data and so to calculate > > particulary things of the PERT method without a graph. > The solution now (in the task dialog) is to enter three estimates: > Expected > (E), Optimistic (O) and Pessimistic (P) along with Risk. O and P is > entered > as a persentage of E. They are stored as durations though, so changing > that > is easy. Risk controlles the PERT distribution used to calculated the > estimates used during scheduling. > There is no help to analyze the results, I haven't gotten that far yet ;) > > > > Best regards. > > > > 2006/11/10, Ga=EBl de Chalendar <[email protected]>: > > > Hello, > > > > > > Le vendredi 10 novembre 2006 08:30, Dag Andersen a =E9crit: > > > > Torsdag 09 november 2006 18:34 skrev Kevin Ottens: > > > > > I'm wondering about this one. I'm not 100% about the semantic of > this > > > > > dependency. Could someone enlighten me? > > > > > > > > task1 <--- task2. > > > > means task2 has to start before task1 can finish, so I suppose task= 2 > > > > > > should > > > > > > > be calculated first. > > > > I don't think there are many use cases for it, I can't pull one fro= m > > > > the top of my head just now ;) > > > > > > Maybe some specifications (like a file format) of task2 (that could b= e > > > splitted in more detailed subtasks) should be finished to allow the > final > > > implementation of task1 ? > > > This allows to have some tasks not too much detailed. > > > > > > Regards, > > > > > > Ga=EBl > > > _______________________________________________ > > > kplato mailing list > > > [email protected] > > > https://mail.kde.org/mailman/listinfo/kplato > > -- > Mvh > Dag Andersen > _______________________________________________ > kplato mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kplato > ------=_Part_55670_2842735.1163598755679 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello!<br><br>We have decided to work on large tasks and as we don't know v= ery well the application <br>we need your help to find other essential task= s.<br><br>The two tasks you have mentionned interest us (PERT, KSpread plug= in). <br><br>Best regards.<br><br>Nicolas MICAS, Fr=E9d=E9ric BECQUIER, Florian = PIQUEMAL, Alexis MENARD, Fr=E9d=E9ric LAMBERT.<br><br><br><br><div><span cl= ass=3D"gmail_quote">2006/11/15, Dag Andersen <<a href=3D"mailto:danders@= get2net.dk"> [email protected]</a>>:</span><blockquote class=3D"gmail_quote" style= =3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p= adding-left: 1ex;">Mandag 13 november 2006 16:47 skrev Nicolas MICAS:<br>&g= t; Hello! <br>><br>> We haven't see the question asked by Dag about our criteri= a for selecting<br>> things to do.<br>> To answer this question it is= easy! (or ISI as you wants :P)<br>> We have studied the TODO list of KP= lato on SVN and after clear it from all <br>> things which were done we have selected those which seems to be mo= st<br>> important and easily realisable during our project.<br>Yes, it's= nice to be able to finish something :)<br>I was also thinking of whether y= ou preferred many small fixes, or one or fewer <br>larger tasks, gui, non-gui...<br>I thought maybe something that is dist= inct which you can point your finger at<br>and say "We Made That"= . Should make it easier for you to document what you<br>have done, also (im= portant, no?). <br><br>The things mentioned by Jim in his other answer to you could be can= ditates, I<br>think. In general, I have almost not touched functions needed= for project<br>execution yet, I haven't gotten further than the planning s= tage. <br><br>Another example; I would like to be able to get data from project(s= ) into<br>kspread for further processing. The method would be to make a plu= gin for<br>kspread that fetches data from kplato files. There exists such a= plugin for <br>kexi which uses SQL to extract data from a database. I was thinking of<= br>something similar.<br><br>> We are studiing a another items to do, re= lative to the PERT method, it will<br>> consist to find a simple way to = key PERT data and so to calculate <br>> particulary things of the PERT method without a graph.<br>The solu= tion now (in the task dialog) is to enter three estimates: Expected<br>(E),= Optimistic (O) and Pessimistic (P) along with Risk. O and P is = entered <br>as a persentage of E. They are stored as durations though, so changing = that<br>is easy. Risk controlles the PERT distribution used to calculated t= he<br>estimates used during scheduling.<br>There is no help to analyze the = results, I haven't gotten that far yet ;) <br>><br>> Best regards.<br>><br>> 2006/11/10, Ga=EBl de Chalen= dar <<a href=3D"mailto:[email protected]">[email protected]= r</a>>:<br>> > Hello,<br>> ><br>> > Le vendredi 10 nov= embre 2006 08:30, Dag Andersen a =E9crit: <br>> > > Torsdag 09 november 2006 18:34 skrev Kevin Ottens:<br>&g= t; > > > I'm wondering about this one. I'm not 100% about the sema= ntic of this<br>> > > > dependency. Could someone enlighten me? <br>> > ><br>> > > task1 <--- task2.<br>> > >= means task2 has to start before task1 can finish, so I suppose task2<br>&g= t; ><br>> > should<br>> ><br>> > > be calculated fi= rst. <br>> > > I don't think there are many use cases for it, I can't p= ull one from<br>> > > the top of my head just now ;)<br>> ><= br>> > Maybe some specifications (like a file format) of task2 (that = could be <br>> > splitted in more detailed subtasks) should be finished to all= ow the final<br>> > implementation of task1 ?<br>> > This allow= s to have some tasks not too much detailed.<br>> ><br>> > Regar= ds, <br>> ><br>> > Ga=EBl<br>> > ____________________________= ___________________<br>> > kplato mailing list<br>> > <a href= =3D"mailto:[email protected]">[email protected]</a><br>> > <a href=3D"https= ://mail.kde.org/mailman/listinfo/kplato"> https://mail.kde.org/mailman/listinfo/kplato</a><br><br>--<br>Mvh<br>Dag An= dersen<br>_______________________________________________<br>kplato mailing= list<br><a href=3D"mailto:[email protected]">[email protected]</a><br><a href=3D= "https://mail.kde.org/mailman/listinfo/kplato"> https://mail.kde.org/mailman/listinfo/kplato</a><br></blockquote></div><br> ------=_Part_55670_2842735.1163598755679-- --===============0342421162== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kplato mailing list [email protected] https://mail.kde.org/mailman/listinfo/kplato --===============0342421162==--