Re: wyona feature list / roadmap

Michael Wechner <[email protected]>
Newsgroups gmane.comp.cms.wyona.user
Message-ID <[email protected]>

Oliver Malang wrote:

> Hi there,
> 
>  
> 
> I'm thinking of trying wyona for one of my next projects as it looks 
> very interesting to me.


Thanks

 But I would be interested if there's anything 
> like a (unofficial) feature list, a todo list and kind of a roadmap. 


Here you will find kind of a feature list

http://www.wyona.org/docs/xdocs/architecture.html

Concerning the roadmap:

We are currently working on the publication "unipublic",
because the goal is to be live on October first.

Another step will be the integration of Slide.

Another step will be throwing out stuff we don't really
need (there's a lot we can actually throw out), because Wyona
is just getting too big.

Working on the docu (Any help appreciated).

Consolidate and refactor stuff which can be used for all
publications.

Well, this is not a real roadmap actually, but stuff
I think are important to do.

But you are right, we have to do a roadmap.

But the most important thing I actually think is to make
people use Wyona. We have to produce something which is
usable, because else the whole thing will die in the end,
even if it was great.


> Obviously the documentation should be completed asap;)


any help appreciated


> 
> I'm currently looking for a open source cms and I prefer something that 
> is written in Java and uses xml, hence choises are rare. It would be 
> quite usefull for interested users to have a feature list and a roadmap 
> to get a more detailed first impression of the project.


What features does your project require? What are your deadlines?

All the best

Michael





> 
>  
> 
> thanks
> 
> oliver
> 
>  
> 
>  
> 


-- 
OSCOM - Open Source Content Management Conference
September 25th - 27th 2002, Berkeley, California
http://www.oscom.org/conferences/berkeley2002/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.