It seems to me that the huge problem here is the messed
documentation we have for WO+Maven. You are not complaining about
bugs yet. :)
Depends on how you look at it, I guess :)
We should have a concrete site for the WOProject tool set. Maven is
pretty good to generate this kind of documentation. The Wiki could
be reorganized to make general user lives easier. We need a better
structure for the wiki documentation. That is my thought about what
can help to solve the problem. But am I right?
I think just defining ANY structure for the WOProject/WOLips wiki
would be enough. At the moment it's all over the place and there's a
lot of old stuff. I like keeping it a Wiki because we DO have several
people contributing to it, and that format is just easier -- I think
it just needs an overarching outline to organize it.
I really miss a visible roadmap for WOLips. I know a lot of people
work hard to improve this tool (it's 22:46 here on Sunday and I
haven't eaten yet). But it is very difficult to know if I'm planning
to do something that other people is already doing. Or if what I
want to do is really a good idea for the entire community.
So, how could we solve this problem concretely? IMHO, we should keep
track of this ideas and issues. We should discuss the solution with
each other and start to split tasks between the people concerned to
improve the WOLips experience for general users (from the beginner
to the advanced).
Seems to me the easiest way is to just log Jiras for tasks and claim
ownership of the ones being worked on. I think that would go a long
way. I don't think we need much formal, just writing it down at all
would go a long way.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
