Loading...
 
Features / Usability

Features / Usability


Re: Tiki and Webdav

posts: 4656 Japan
I'm fine with you balancing work, family, hobbies, and Tiki development. However, the project as a whole cannot let individuals with your mindset control what it delivers. This is a management problem: how do you herd cats to get predictable results?


The situation, for all volunteer projects, is that "that mindset" is a given that must be accepted and worked with. These aren't corporations in which management can dictate how tasks are completed and goals achieved.

Even more than other open-source software projects, Tiki is all about "the wiki way," and encourages participation to the extent that each contributor can provide. This sometimes results in work that needs to be removed, it also gets some great things that probably wouldn't have happened with a more restrictive development model.

The fact remains that if you expect anyone to use this system, it has to be predictably useful, and leaving the documentation or reliability up to people who don't make it their first priority won't achieve that.


Well, it's their first priority when they're doing it, but they're busy people who also have other things to do. wink

To get a balance between organic contribution on the developer side and a predictable, usable experience on the user side, one thing we do is mark features as "experimental" and so on, so the code can get into the project and be tested and improved, while providing the disclaimer to users to use it with caution or expect some glitches for the time being.

My advice to you is that you don't confuse your hobbies and things that people depend on you for. Everyone will be happier.


Many talented people are available to contribute their worthwhile efforts only as a "hobby", and this is something that should be encouraged, not discouraged. There are a lot of happy Tiki users that are enjoying software created in large part by volunteers outside of their regular work. The Tiki model has been pretty successful so far (just hit the eight-year mark).

As a user - which is clearly what I am - I complain when something isn't usable. Telling me to write documentation when I don't know what I'm doing is the same mistake as you writing code when you don't have the time to support it.


I don't think you were asked to write documentation other than to report your error messages, etc. And about the idea that the code isn't supported, these forums aren't the only (or necessarily the best, for some issues) place for that. There's also the IRC channel and developer mailing list.

-- Gary

There are no comments at this time.