I searched for other groupware servers in Footnotes, and at least OpenGroupware was subject of an article. No bias here.
But Planet Gnome marketing really seems to be a little overboard...
I am the one who is currently putting the most effort into the KDE Quality Team implementation, so I am qualified to speak for the project:
Let's start by making something clear:
The main idea is not to build a QA project inside KDE. The main idea is to support and embrace new contributors with any background, and help to organize their efforts. For instance: Any doubts about the docbook? We are glad to help. Do you want feedback on your work? We are happy to provide. Looking for guidance? Hop in!
We don't want to point what is good for you: we try to present you with a long list of things one can do to help, and organize these efforts.
The recommended approach for non programmers is different from other projects: it is more like the project manager in a company than of a task specialist. In other words think of acting upon the whole of Kontact instead of acting upon the
context help for the whole KDE project. We recognize that the main tool for helping an application is knowing it well. A quick look at the activities list, presenting the requirements for performing the tasks, is sufficient to prove that.
Yes, the activities include QA. But this is just one of the activities. Hope this helps to avoid confusion with GNOME's bugsquad (also nice, but not related: it is a different concept).
Slashdot Mirror
Is it possible / not too difficult to write a Outlook plugin implementing GroupDav? Does Kolab implements Groupdav?
I searched for other groupware servers in Footnotes, and at least OpenGroupware was subject of an article. No bias here. But Planet Gnome marketing really seems to be a little overboard...
I am the one who is currently putting the most effort into the KDE Quality Team implementation, so I am qualified to speak for the project:
Let's start by making something clear:
The main idea is not to build a QA project inside KDE. The main idea is to support and embrace new contributors with any background, and help to organize their efforts. For instance: Any doubts about the docbook? We are glad to help. Do you want feedback on your work? We are happy to provide. Looking for guidance? Hop in!
We don't want to point what is good for you: we try to present you with a long list of things one can do to help, and organize these efforts.
The recommended approach for non programmers is different from other projects: it is more like the project manager in a company than of a task specialist. In other words think of acting upon the whole of Kontact instead of acting upon the context help for the whole KDE project. We recognize that the main tool for helping an application is knowing it well. A quick look at the activities list, presenting the requirements for performing the tasks, is sufficient to prove that.
http://quality.kde.org/develop/modules/
Yes, the activities include QA. But this is just one of the activities. Hope this helps to avoid confusion with GNOME's bugsquad (also nice, but not related: it is a different concept).