Re: [cowiki-dev] Why aren't we making progress?

I think the solution is to better-define a roadmap and specific
project goals.. and then to be so confident as to make that plan
public.

We already have a good philosophy designed.  Why don't I take that
work, the milestone and priority concepts.. and wrap it all together
to make it public.  I can do this.

Then, as we discuss things on the mailing list.. I will commit notes
into that huge roadmap.  We should not be afraid to do this.. if our
audience looks at this roadmap, they will see that the project is
young and we are driven to improving it.

If anyone in the public wants to, they can join us in discussion on
the mailing list.

We have already learned our lesson and we know that it's better to "do
the work" than to keep chatting about certain things.. but if our
audience has good ideas we can still be open to listening and such.

I would like to revisit the website anyway, and redesign some of it to
make it easier to navigate.



On 4/15/05, PAUL HANCHETT <[email protected]> wrote:
>  I think things broke down a bit when there was so much dissent over what
> coWiki should become.  I backed off to see if some consensus about what we
> should do would emerge.  It didn't.  Without agreement to all move in the
> same direction it is difficult to make progress.
>  
>  Personally, I was working on an installer and some diagnostic routines--
> but you told me to stop that until you finished the installer.  So, I've
> looked at the parser but there's not much point in doing that until we are
> agreed what the language should look like for the future.  (I don't think
> the idea of a fast parser I was pursuing will work so well anyway...  Too
> complex for my tastes.)
>  
>  I've thought about doing the file uploads and content management, but I
> really don't want to argue about whether or not html or graphics have a
> place in coWiki.  I know that what I want to do would make changes in the
> database, and what I'd most like to do (I think) is relatively intrusive.  
>  
>  Fundamentally, the question for the team is will we continue to do
> haphazard development, or will we do it professionally as a team, and part
> of a development plan?  (Doesn't mean it can't be fun!)  
>  
>  Are we ready to get back on track?  There are things that coWiki can be
> *absolute best* at.  Others where we can only be like other wiki's.  In
> every case were coWiki is selected, users are using the things that we _are_
> best at.  That is what we need to focus on for the future.
>  
>  Paul (direction setter) Hanchett
>  
>  
>  Daniel T. Gorski wrote: 
>  Folks,
> 
> whats going on? I need to push you. Where are your ideas for coWiki? Go, go
> and go. If you are working on something that needs time, please report it,
> tell us the status - if you don't you should#t be on the dev- list.
> 
> I complained once or twice that I do not see what you are doing, the ony
> visible output is the output of Syeed Ali (respect). What about the others?
> Are you sleeping? Is this project not satisfactory for you?
>  
>  
>