Skip to Content.
Sympa Menu

pcplantdb - Re: [pcplantdb] [mini-synthesis][36][5.17.05]

pcplantdb@lists.ibiblio.org

Subject: pcplantdb

List archive

Chronological Thread  
  • From: John Schinnerer <john@eco-living.net>
  • To: Permaculture Plant Database <pcplantdb@lists.ibiblio.org>
  • Subject: Re: [pcplantdb] [mini-synthesis][36][5.17.05]
  • Date: Wed, 18 May 2005 22:59:24 +0000

Aloha,

-Johns wrote, "Re 2), until we know more precisely what we are building and how it is supposed to work, opening testing up to others is most likely to result in a lot of static and clutter in the tracker." Is this becoming clearer with the Wiki? Or is there some other process we should engage in, doc we should create? Or just meet up at Chad's ;)

I will momentarily post an example of what looks like a well-structured, well-organized and prioritized open source project launch announcement. Their primary first steps after general goals and ideas discussions such as we have already had are to design an architecture, write specs, and validate their specs...before even worrying about a single line of code.

I think perhaps I am simply too structure-oriented for the PIW project.

-Speaking of tasks, would you like me to send out a task list or do you feel comfortable with what you're currently working on? PLEASE RESPOND.

How about using the issue tracker to track tasks?
I specifically supplied an issue type of 'task' for this purpose, as requested.

And send me individual updates por favor.

I was planning to start doing some docs for testing and the issue tracker (actually made a small start on some flow diagrams Tuesday).

At this point I first want some group sorting-out of the disagreements between myself and Rich about user community/testing/tracker issues.

I personally want a well-structured testing and issue-tracking environment for this project, and I want user/project community input for QA and testing to make maximum use of same.

A web forum, wiki, blog or similar free-form text entry environment does not meet this criteria for me.

I am hearing Rich say that most likely few in our user/project community will use the tracker if they have to register, and that we should provide some anonymous way for any and all comers to submit 'bugs', and that this might be through a web forum, wiki, blog or similar.

As I have put a lot of effort into generating the issue tracker, I am frankly pissed to hear that we ought not require user/community members to use it for what I thought it was intended for.

-Johns, Bear, and others - just wanted to remind you to keep track of the hours you spend on this project!

Is that just for your project reporting stats?
Thus far I have not done any work that I would be paid for.
In any case I haven't been tracking my time thus far.

p.s. I like guacamole as the password.

Now that it's been sent around the world a few times in clear text, I guess we'll hvae to pick another...

John S.



--

John Schinnerer - MA, Whole Systems Design
------------------------------------------
- Eco-Living -
Whole Systems Design Services
People - Place - Learning - Integration
john@eco-living.net
http://eco-living.net




Archive powered by MHonArc 2.6.24.

Top of Page