Re: [AgileWiki] A comprehensive set of issues

[Bill la F. <bil...@su...>]

Niall,

There was previously a partial list of issues in the issue tracker on 
the java.net site.

I've also from time to time indicated areas that needed work.

This weekend finally I wrote the comprehensive list of things to be 
done, and only just finished it. I thought that it would be well worth 
the effort.

I don't want to be the bottleneck on this project, though it is 
unavoidable for now. But with AgileWiki3 finally working well enough to 
be self-hosting, my main focus for a while will be on documentation, and 
especially programmer documentation. This will finally open up the 
project to other developers to contribute.

As I progress, I do hope that you and others will continue to help me by 
contributing what you can, especially with questions about things that 
need clarifying. My long-range goal is to see hundreds, no, thousands of 
developers building on what we have done together. But that is a goal 
that can not be reached without your help.

Norm has been working on Rolonics for 20 years, while I have only spent 
the last 6 on prototypes for the AgileWiki. So yes, there's some 
catching up to do. But there is pleanty of room in the core development 
team. And I will do my best to make it possible for anyone who has the 
interest to participate.

Also, the so-called comprehensive list of open issues isn't really 
comprehensive. I left out change notifications for one. And it really 
only covers what's been prototyped. There are still other areas of 
Rolonic theory that I have not yet had a chance to apply, one of 
particular interest being agent theory. And AgileWiki3 is likely not the 
be the all and end all. I expect there will be an AgileWiki 4 in a 
couple of years, and more beyond that. This has become my life's work.

And like other projects, JBoss for example, I expect there will be a 
financial side of AgileWiki3. But for that we need to build a team of 
developers interested in providing support. It will take time and effort 
on all our parts. But we have something unique in the industry--a 
comprehensive theory on which to base our work. Contrast that to other, 
ad hoc efforts (like EJB, SOA, Portlets), which may be the best efforts 
to date, but which are only probing the greater dark. Truely the 
opportunity is ours to loose.

Bill

Niall Loughnane wrote:

> Hi,
>  
> Sorry but this was the first time that the link was published to the 
> net for the published open issues?
>  
> Me was wondering that there were no open issues to fix or to discover?
>  
> Niall