Loading...
 
Skip to main content

Features / Usability


You are viewing a reply to TikiWiki - CSM and Groupware

Re: TikiWiki - CSM and Groupware

Yes. I'm an almost 50 year old man who has his normal billions of years experience in the development field with bla bla bla.

TikiWiki is an amazing piece of software and an excellent development effort of a large group of bright people.
Many features are usable, only a few are not 'finished' (i.e. the friends and user points).

Since I'm an old man, my development activities mainly consists out of running medium and large development project with hundreds, even thousands of people involved all over the world, from companies like Microsoft, HP, IBM, NASA, ESA and many others. Actual development is now quite a hobby with the nice and fancy software technologies out there and the newest methodologies. Quite exciting.

Development is a large process, where many people are involved with. But with good projects, there is a spearhead, a person who is in charge. A person who is working towards a certain goal, a goal, which must be clear for everyone involved.

If that is not the case, and the project has money and resources enough, then you might say that the goal is work therapy, a feeling of accomplishment when you finish your small part of the total. And there is nothing wrong with that. It's a pity that I can't come to Spain at the end of this month.

If I would take over a project like this, the first thing I would take care for is the increase of resources, so that the developers can continue to have a good time. Then the organization; project management, integration and monitoring, the strategical path, the final goal to get more resources and to increase the productivity. So, be happy that I won't be able to take over, huh? Well, at least everyone can freak with a large bag of money!


-

That said, a product, which is nice as it is, but is not finished (like the forums, the points and more details) is a product, which is scheduled to die, to be passed by something else, which is doing something similar or better.
To fragmentize your efforts by working on this, then that and then something else is not the way how a large product like TikiWiki must run and can survive. Everything needs to grow, but it needs to grow on a firm fundament, and that firmament becomes weaker by the day. Finish what you start before starting something new.


-

A good idea - a bit different subject - is to adopt the license and not make it free anymore. For personal usage FREE would be nice, but for commercial usage you make an agreement with the one who uses the software commercially, to share in their revenue.

This sounds maybe harsh, but it is the actual fact that nothing can survive for free.

If I would manage this project, my priority is getting (read here not hoping to get, but simply getting) the money, the resources to continue.
I would implement the following.

Banners and Advertisement

There is an excellent banner management module in TikiWiki. I would contact advertisers and make agreements with them. From TikiWiki central location it will feed banners for every TikiWiki installation, if the owner like it or not. The owner will not be able to disable the banners.

In case they don't want, they must pay for a license.

Licenses

Millions of hours of development went into the product. It is about time that you guys came up with a license model. Personal use is free (I assume), but commercial usage is not. They pay an amount per year for leasing, not buying. For personal use only one TikiWiki installation is allowed, but not more.

That means that you need to have a server, which monitors all TikiWiki installations out there and determine the licenses. If there is something wrong, disable to TikiWiki. I wrote many of those license servers and they are easy to implement and very hard to fool.

The license server is one of the central parts of the TikiWiki network, which can be used again to centralize all kind of things, like users, information, forums, blogs, and and much more and sell services.
The license server must be able to collect statistics of all TikiWiki installations out there, which can be used for advertisement and other form of income.

Changed development

At the moment you have several people working on the TikiWiki. Those are volunteers? Great. But if you want to have real nice stuff going, finished and all, make it interesting for the developers and companies! And that brings a very nice source of income and the growth of the TikiWiki is guaranteed for several years, making resources free to 'fool and freak around'.

Enable Module development

Allow companies and/or third parties develop modules/plugins. TikiWiki gets part of the sales; they must have a license to install a module and that is again very easy to track.

Focused development teams

Your own developers will work on specific parts of the system, which will lead to rewards (more resources, money, etc). You are going to work for specific projects, like for example, any institute, company, government, etc.

With other words, you must attract marketing and sales people, product development people, project management, the whole bunch.

Finally, I don't think that the TikiWiki must be a company or an endeavor. It can still be the same, but it demands in that case a focused leader, who is managing the whole thing from the top. It requires an open mind of everyone involved and an increase of people in the team/project, people like marketing and sales people, people involved in Product Management, and go on like this until the end of times.


Wim