From kde-promo Sat May 17 09:01:02 2003 From: Eva Brucherseifer Date: Sat, 17 May 2003 09:01:02 +0000 To: kde-promo Subject: Re: [kde-promo] Re: KDE 3.2 release cycle X-MARC-Message: https://marc.info/?l=kde-promo&m=105316558023591 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Philippe, cool stuff! We are getting many emails to the kde-ev@kde.org where people ask how to help and a page summerizing all possible contribution would of course ease things. One addition to the "money" section: You should also mention the adopt-a-geek program there, see http://devel-home.kde.org/~wheeler/adopt-a-geek/ And in the "code" section you can add a link to developer.kde.org and kdevelop.org. Also a link to apps.kde.com fits in here. Greetings, eva On Friday 16 May 2003 11:33, Philippe Fremy wrote: > Hi, > > > So if there's a lack of people we > > need to promote them as well (I'm in progress rewriting the "support KDE" > > page on kde.org to reflect all the possibilities how to contribute for > > exactly this purpose). > > I think we should list every action that could be make to help KDE and then > put an article on the dot to call for help. > > This page is a start: > http://www.kde.org/helping/ > > I am thinking about: > > Task: reporting bugs > Requirement: KDE user. It is better if you compile KDE with debugging > information. > Job: user KDE daily and report every bug you find. You can improve by > exploring many applications and unused aspects of the desktop. If you can, > try strange settings to see if everything works. > > Task: sorting bugs out > Requirement: KDE user > Job: working as a first filter between bug reporters and developers, to > alleviate the bug managing tasks of developers > -> removing bug duplicates > -> asking more information when bug can not be reproduced > -> adding informaiton to the bug when it can be done. > How about creating a bug squadron that would officially dedicate to this > task ? > > Task: summerising lists: > Requirement: read a KDE mailing list and summerise it every week. > Job: join the KDE traffic team, follow a list a every week, include the > most interesting thread in KDE traffic. > > Task: summerising cvs commits: > Requirement: read a KDE CVS mailing list and summerise it every week. > Job: join the KDE CVS digest person and help him to summerise what has been > checked in into CVS every week. > > Task : application reviewer > Requirement: use KDE, write english > Job: when you can grab a KDE application and make an extensive review of > all the capabilities of the application. Talk to the developers about the > future development, compare it with other applications, etc. This helps to > promote the KDE desktop. > > Task: interview > Requirement: curiosity, write english > Job: pick-up an application or an area or a guy you like, and make up a > full intervie of him. One possiblity is to ask first to the community the > questions that people wish to ask. > > Task: helping release writing > Requirement: time > Job: for each release, dig out all the features that have been added for > any KDE application since the latest release, so that more detailed > information can be added into the press release. > > Task: developer articles > Requirement: small development skill > Job: write a tutorial or an example of how to use one KDE feature, to > promote and ease the entry of new KDE applications developers. > > Task: local promotion > Requirement: time, communication > Job: promote KDE in your local area. Talk to journalists, political, LUGs, > talk about KDE in conferences, talk about KDE in your school, ... > > Task: maintain a KDE application > Requirement: coder > Job: take an unmaintained KDE application [ link ] and maintain it so that > it can live up to the standards of KDE. > > Task: usablity reports > Requirement: usability understanding, or access to user base. > Job: join the KDE usability team and help them target area of KDE where the > usability can be improved, by writing a usabilty report. The report can be > based on your personal experience but it is better if you can provide some > real user testing. > > There are probably more but that the most important one I think. I am sorry > I don't have more time for this. The next thing to do is to take this list, > propose it to kde-core or whatever so that people add more tasks or > describe each task better, put it somewhere on the kde.org and write an dot > article calling for people to fill in these positions. Can somebody take > care of that ? > > The important thing is for people to realise that you don't need to be a > coder to contribute to KDE. I think many people are still not aware of > that. > > regards, > > Philippe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+xfpOTaAgihPikKQRAuyKAJ9sxSuCleaLPM1XG0q5+ZbHV4facQCfTX1u nW8L/gwd5w+0CrWq4fcJfKM= =CSPy -----END PGP SIGNATURE----- _______________________________________________ This message is from the kde-promo mailing list. Visit http://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.