KDE Community Working Group takes care of the community


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News KDE Community Working Group takes care of the community
# 1  
Old 09-04-2008
KDE Community Working Group takes care of the community

09-04-2008 01:00 PM
If the rocky reception of KDE 4 has done anything, it has forced the KDE project to realize it needs to listen to users more closely. One of the first results of this realization is the new Community Working Group (CWG). Announced at Akademy, the recently concluded annual KDE conference, the CWG was described as designed "to act as a central point of contact by being available to communicate user needs and concerns to developers, and developer intentions and plans to users." The CWG is still being organized; to find out more about its plans, we contacted Anne Wilson and Juan Carlos Torres, two of the group's five initial members.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. What is on Your Mind?

How Can We Increase the Size of Our Community?

Any suggestions on how to increase the number of posters and contributors? Please vote and write in your suggestions. Thank you! (72 Replies)
Discussion started by: Neo
72 Replies

2. IP Networking

SNMP Community String ???

Hi I want to know more about SNMP Community Strings. What are this SNMP Community String, & what do they signify? What is this "public" used in the field of Community String? Please also let me know what other values can be used in the Field of Cummunity String other than public.... (4 Replies)
Discussion started by: S.Vishwanath
4 Replies
Login or Register to Ask a Question
KDE-BUILD(1)						User Contributed Perl Documentation					      KDE-BUILD(1)

NAME
kde-build - Updates and recompiles a tree of KDE CVS modules SYNOPSIS
kde-build DESCRIPTION
kde-build has been designed to keep a local copy of several KDE CVS modules up to date and recompile them. Those modules have to be saved in a common directory, e.g. something like ~/kde-src/ | +-> kdelibs/ | +-> kdebase/ | -> kdenetwork/ In this case, the KDE source directory would be ~/kde-src/. The script will take care of compiling them in the correct order, checks for dependencies and resolves them as far as possible. Please not that, prior to first invokation of the script, the configuration file 'kde-buildrc' has to be modified to reflect the local environment, such as paths etc. RETURN VALUE
The following error codes are returned by the script. 0 - No error seems to have occured. 1 - The script could not change into the directory of a module. 2 - The script could not open the file 'Makefile.in' of a module. 3 - The configuration of a module failed. 4 - The compilation of a module failed. 5 - The installation of a module failed. 6 - An invalid source directory was specified. 7 - An invalid Qt directory was specified. 8 - An invalid CVS client was specified. 9 - No cvsup server was specified. 10 - The temporary CVSUP configuration file couldn't be created. 11 - The configuration file kde-buildrc couldn't be loaded. EXAMPLES
cd ~/scripts/; vi ./kde-buildrc; ./kde-build BUGS
Lots, mostly that the script wasn't written with portability in mind and therefore won't run very nice on platforms other than Linux. TODO
Add a DIAGNOSIS section to this man page. AUTHOR
Frerich Raabe <raabe@kde.org> 3rd Berkeley Distribution perl v5.6.1 KDE-BUILD(1)