Follow-up Comment #2, sr #485 (project savane):
Thanks for the quick reply...
I think an example use case would be helpful to better illustrate what I need
(which appears to be a strange hybrid of wiki and software development
management).
For example, someone at some university is working on Project A. The user
would log in, look for an appropriate category for the project, and if one
doesn't exist, creates a category that fits well. The person notes the to
do's for the project and posts files and documentation as he or she
progresses. The project is noticed by peers, who suggest other features or
point out some potential flaws, and suddenly the project is too big for one
person. The person then notes to other people that they are looking for help
in certain areas, and then you have people from all over collaborating to get
it done. Sounds utopic, but that would be the ideal.
Is that something you think would be best for wiki-like systems? The main
difference is that this would be more along the lines of project or research
development the the individual may eventually publish or present at
conferences and what-not rather than actual software.
by the way, it also appears versioning is possible with some wiki types (like
twiki) can do versioning. But I am vague as to whether wiki's could do
everything else that we would like.
_______________________________________________________
Reply to this item at:
<http://gna.org/support/?func=detailitem&item_id=485>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
