From: Drew P. V. <dv...@in...> - 2002-07-18 14:21:49
|
I can definitely understand not having enough time. No one does. I believe posting half as many bugs in the task list with twice the explanation would serve the project much better. Perhaps a better system would be to advertise important tasks on the mailing list or news items on the web site. Regards, Drew Vogel On Thu, 18 Jul 2002, Waba wrote: >On Wed, 17 Jul 2002 19:59:59 -0400 (EDT) >"Drew P. Vogel" <dv...@in...> wrote: > >> Since any project begins with many steps prior to an alpha release, won'= t >> the next release after a complete re-design be alpha #1, again? >No, hopefully it will be alpha 3 > >> Also, barrier to entry seems to be a bit high here. Higher than the Linu= x >> kernel. There I could just pick something off the kernel janitor's todo >> list and do it because the cause for most aspects of the project are 20 >> years old. Because the majority of the Arianne system is conceptually ne= w >> to most developers (there just haven't been enough MORPG to have enough >> experienced developers), the todo lists for newbies need to be much more >> detailed, explaining the cause behind the action. They also need to list >> the mandatory requirements of the product of the newbie's work. For >> example, "Create the script to help automate the creation of objects". >> Which type of objects? Where are they stored? 'the script' implies that = it >> is started, if so, where is it now? Who is working on it? Who started it= ? >> What are the prerequisites? What is the current process for creating >> objects? Now this might be a tad overdone, but while these may seem >> obvious to you, people new to the project haven't a clue. I'm sure the >> list would answer these questions and a half-skilled developer can figur= e >> these out. A newbie is probably saying "Oh god.. I'm not doing that one" >> and moves on down the list repeating this to himself until he finds a >> trivial task or gets to the bottom and goes to a different project >> figuring he will come back to us when get a little more organized. >Right, most bugs are very badly written. In fact, they are two kinds of >ones: Some are written the way everyone expect and can be achieved alone, >the others are "Remind me that we have to ..." and can't be done until you >have discussed the why and how with the bug author (or miguel, but they're >usually the same). >The second form is usually encountered when the writter has not enough >time to develop the subject, left alone putting it in the task tracker >instead. > >I personally try to write my bugs giving enough details, but I can >understand some have no time for it... Although it should change. > > >Waba > >-- >[www.ebb.org/ungeek] GCS/IT d-- a--- C++++ ULVB++++ P+++ L+++$>++++$ R+ >E---(-) W+(-) N+(++) w---(--) PE(--) PGP+ tv-- b+(+++) D++ h* r-- y? >___________________________________________________________ >Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran=E7ais ! >Yahoo! Mail : http://fr.mail.yahoo.comm > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Arianne-devel mailing list >Ari...@li... >https://lists.sourceforge.net/lists/listinfo/arianne-devel > |