Difference between revisions of "Development/Software Engineering Framework"

Jump to: navigation, search
(Many changes and updates)
Line 1: Line 1:
This page is intended to be a summary of the tools used by the KDE
+
This page is intended to be a summary of the tools and processes used by the KDE
 
project for Software Engineering tasks, i.e. everything around coding
 
project for Software Engineering tasks, i.e. everything around coding
 
work. This includes bugfixing, review, testing, documentation,
 
work. This includes bugfixing, review, testing, documentation,
Line 15: Line 15:
 
| people=
 
| people=
 
The kde sysadmin team:
 
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]  
+
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
 
* [http://www.kdab.net/~dfaure/ David Faure]
 
* [http://www.kdab.net/~dfaure/ David Faure]
 
| getInvolved=
 
| getInvolved=
 
* {{KDEML|kde-scm-interest}}
 
* {{KDEML|kde-scm-interest}}
 
| altTools=
 
| altTools=
* [http://git.or.cz/ git]  
+
* [http://git.or.cz/ git], repo
 
* [http://bazaar-vcs.org/ bazaar]
 
* [http://bazaar-vcs.org/ bazaar]
 
* [http://www.selenic.com/mercurial/ mercurial]
 
* [http://www.selenic.com/mercurial/ mercurial]
Line 32: Line 32:
 
There is interest in migrating to a distributed source control
 
There is interest in migrating to a distributed source control
 
management tool, such as GIT. Discussion of this is taking place on the
 
management tool, such as GIT. Discussion of this is taking place on the
[http://mail.kde.org/pipermail/kde-scm-interest kde-scm-interest]
+
{{KDEML|kde-scm-interest}}
mailing list.
+
mailing list. It is likely git will be used along with a tool such as repo.
 +
 
  
  
Line 39: Line 40:
 
| name=Build System
 
| name=Build System
 
| currentState=
 
| currentState=
* [http://www.cmake.org/ CMake]  
+
* [http://www.cmake.org/ CMake 2.6.0]
 
* [http://api.kde.org/cmake/modules.html Custom CMake module documentation]
 
* [http://api.kde.org/cmake/modules.html Custom CMake module documentation]
 
| getInvolved=
 
| getInvolved=
Line 52: Line 53:
  
 
This tool was chosen as the buildsystem for the KDE4 series, and there
 
This tool was chosen as the buildsystem for the KDE4 series, and there
are no plans currently to migrate away from it.
+
are no plans currently to migrate away from it. CMake version 2.6.2 will be required to build KDE 4.2 final.
  
  
Line 58: Line 59:
 
| name=Identifier search
 
| name=Identifier search
 
| currentState=
 
| currentState=
http://lxr.kde.org  
+
http://lxr.kde.org
 
| people=
 
| people=
 
The kde sysadmin team:
 
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]  
+
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
 
* [http://www.kdab.net/~dfaure/ David Faure]
 
* [http://www.kdab.net/~dfaure/ David Faure]
 
}}
 
}}
Line 72: Line 73:
 
| currentState=
 
| currentState=
 
* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project.
 
* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project.
* trunk/kdereview  
+
* trunk/kdereview
 
| people=
 
| people=
 
* David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
 
* David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
Line 90: Line 91:
 
this system is that not all reviewers report that they have reviewed the
 
this system is that not all reviewers report that they have reviewed the
 
new content. It may make sense to have a checklist for reviewers to use,
 
new content. It may make sense to have a checklist for reviewers to use,
eg,  
+
eg,
  
* All new classes documented [x]  
+
* All new classes documented [x]
 
* Private classes and d-pointers used where appropriate [x]
 
* Private classes and d-pointers used where appropriate [x]
 
* Passes all krazy checks [ ]
 
* Passes all krazy checks [ ]
Line 99: Line 100:
 
* etc...
 
* etc...
  
 +
This was discussed to some extent [http://thread.gmane.org/gmane.comp.kde.devel.core/54213 here], but has not yet been refined into a techbase page.
  
 
{{SEFBox
 
{{SEFBox
Line 107: Line 109:
 
* SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits.
 
* SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits.
 
* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.
 
* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.
 +
* SVN <tt>CCBUG:</tt> feature used to notify closed bugs of updates. Commonly used when porting fixes between branches. Also notifies all bug subscribers of the commit.
 
| getInvolved=
 
| getInvolved=
 
* {{KDEML|kde-commits}}
 
* {{KDEML|kde-commits}}
Line 119: Line 122:
 
| name=Design Review
 
| name=Design Review
 
| currentState=
 
| currentState=
Design review takes place on  
+
Design review takes place on
 
* mailing lists
 
* mailing lists
 
* project wikis
 
* project wikis
Line 160: Line 163:
 
}}
 
}}
  
KDE API doucmentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.
+
KDE API documentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.
 +
 
 +
It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.
  
  
Line 166: Line 171:
 
| name=User documentation
 
| name=User documentation
 
| currentState=
 
| currentState=
* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation
+
* http://userbase.kde.org
* {{KDEML|kde-docbook}} Records all SVN commits with the GUI magic word.
+
* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation.
 +
* {{KDEML|kde-docbook}} Records all SVN commits with the <tt>GUI</tt> magic word.
 
| getInvolved=
 
| getInvolved=
 +
* http://userbase.kde.org Create tutorials and tips.
 
* {{KDEML|kde-doc-english}} Used to coordinate user documentation.
 
* {{KDEML|kde-doc-english}} Used to coordinate user documentation.
 
* {{KDEML|kde-docbook}} Help update documentation after GUI changes.
 
* {{KDEML|kde-docbook}} Help update documentation after GUI changes.
Line 176: Line 183:
  
 
meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.
 
meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.
 +
 +
http://userbase.kde.org is intended to be the primary source of user documentation on the web. Content will possibly be packaged for offline use in the future.
  
 
== Testing and Quality ==
 
== Testing and Quality ==
Line 207: Line 216:
 
| name=Static code analysis
 
| name=Static code analysis
 
| currentState=
 
| currentState=
[http://www.englishbreakfastnetwork.org/krazy/ Krazy] hosted at EnglishBreakfastNetwork (EBN).
+
* [http://www.englishbreakfastnetwork.org/krazy/ Krazy] hosted at EnglishBreakfastNetwork (EBN).
 +
* [http://www.coverity.com/ Coverity] is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of [http://ktown.kde.org/~dirk/dashboard/ Dirks Dashboard builds].
 
| people=
 
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]  
+
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://www.kdedevelopers.org/blog/1451 Allen Winter]  
+
* [http://www.kdedevelopers.org/blog/1451 Allen Winter]
 
| getInvolved=
 
| getInvolved=
*  
+
*
 
}}
 
}}
  
Line 246: Line 256:
 
[[Development/Tutorials/Unittests|Unit tests]] may be written with the QTest framework. Tests can be run with the command '<tt>make test</tt>'.
 
[[Development/Tutorials/Unittests|Unit tests]] may be written with the QTest framework. Tests can be run with the command '<tt>make test</tt>'.
 
| getInvolved=
 
| getInvolved=
 +
* [[Development/Tutorials/Unittests|Techbase Unit tests tutorial]]
 
}}
 
}}
  
Line 254: Line 265:
 
| name=Quality testing
 
| name=Quality testing
 
| currentState=
 
| currentState=
* The early adopter/user community  
+
* The early adopter/user community
 
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
 
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
 
| people=
 
| people=
Line 270: Line 281:
 
| currentState=
 
| currentState=
 
* {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE.
 
* {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE.
* Krazy also includes some optimization checks.
+
* Krazy and Coverity tools also include some optimization checks.
 +
* KDE macros for optimization of common algorithms.
 
| getInvolved=
 
| getInvolved=
 
* {{KDEML|kde-optimize}}
 
* {{KDEML|kde-optimize}}
 +
* [http://ktown.kde.org/~dirk/dashboard/4.1/i386/kdelibs.html Coverity report for KDE libs].
 
}}
 
}}
  
Line 289: Line 302:
 
| getInvolved=
 
| getInvolved=
 
* {{KDEML|kde-usability}}
 
* {{KDEML|kde-usability}}
 +
* [[Projects/Usability/HIG KDE Human interaction Guidelines]].
 
}}
 
}}
  
Line 301: Line 315:
 
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
 
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
 
* [http://www.kdedevelopers.org/blog/2904 Sebastian Trueg] leads the kde-nepomuk project.
 
* [http://www.kdedevelopers.org/blog/2904 Sebastian Trueg] leads the kde-nepomuk project.
 +
| getInvolved=
 +
* [http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde Nepomuk KDE mailing list]
 
}}
 
}}
  
Line 323: Line 339:
 
* http://www.kde.org/announcements is the official source of promotional announcements regarding KDE.
 
* http://www.kde.org/announcements is the official source of promotional announcements regarding KDE.
 
* Design and maintenance of KDE websites is organised on the [https://mail.kde.org/mailman/listinfo/kde-www kde-www mailing list]
 
* Design and maintenance of KDE websites is organised on the [https://mail.kde.org/mailman/listinfo/kde-www kde-www mailing list]
 +
* The [http://ev.kde.org/workinggroups/mwg.php Marketing working group] coordinates several marketing efforts such as promoting planning and branding.
 +
* KDE e.v provides a booth box for conference booths containing posters, leaftlets and other information needed at a conference stand.
 
| people=
 
| people=
 
* [http://wadejolson.wordpress.com/ Wade Olsen]
 
* [http://wadejolson.wordpress.com/ Wade Olsen]
Line 336: Line 354:
 
| name=Community management
 
| name=Community management
 
| currentState=
 
| currentState=
* helping the KDE community with community advice when needed
+
* The Community Working Group helps with community advice when needed
 +
* [http://www.kde.org/code-of-conduct/ Code of Conduct] Based on the Ubuntu Code of Conduct, documents guidelines for acceptable behaviour within the community. Can be summarized as 'Be Excellent to Eachother'.
 
| people=
 
| people=
 
* Anne Willson
 
* Anne Willson
Line 352: Line 371:
 
| currentState=
 
| currentState=
 
Developers communicate with each other through
 
Developers communicate with each other through
* [http://lists.kde.org/ mailing lists]  
+
* [http://lists.kde.org/ mailing lists]
 
* [http://searchirc.com/irc-kde-1 IRC]
 
* [http://searchirc.com/irc-kde-1 IRC]
 
* [http://planetkde.org Blogs]
 
* [http://planetkde.org Blogs]
Line 358: Line 377:
 
Developers communicate with users though
 
Developers communicate with users though
 
* [http://planetkde.org Blogs] to some extent (mainly early adopting users).
 
* [http://planetkde.org Blogs] to some extent (mainly early adopting users).
* [http://kde-forums.net Forums] to some extent where the developer chooses to.
+
* [http://forum.kde.org Forums] to some extent where the developer chooses to.
 
* [http://dot.kde.org News announcements]
 
* [http://dot.kde.org News announcements]
 +
Users communicate with each other and developers through
 +
* [http://forum.kde.org Forums]
 +
* {{KDEML|kde}} mailing list
 +
* #kde irc channel.
 
| people=
 
| people=
 
* [http://c133.org/blog/ Chris Lee] administers planetkde.org
 
* [http://c133.org/blog/ Chris Lee] administers planetkde.org
 
| getInvolved=
 
| getInvolved=
 +
* Add your blog to planet kde if you contribute to KDE in some way, including development, testing, advocacy, translation, documentation etc.
 
}}
 
}}
  
Line 372: Line 396:
 
* Maintained at [[Schedules]].
 
* Maintained at [[Schedules]].
 
| people=
 
| people=
*  
+
*
 
* [http://cyrilleberger.blogspot.com/ Cyrill Berger] - KOffice release coordinator.
 
* [http://cyrilleberger.blogspot.com/ Cyrill Berger] - KOffice release coordinator.
 
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM release coordinator.
 
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM release coordinator.
Line 383: Line 407:
 
| name=Feature planning
 
| name=Feature planning
 
| currentState=
 
| currentState=
* [[Schedules/KDE4/4.1_Feature_Plan]]  
+
* [[Schedules/KDE4/4.1_Feature_Plan]]
* [[Schedules/KDE4/4.2_Feature_Plan]]  
+
* [[Schedules/KDE4/4.2_Feature_Plan]]
 
| people=
 
| people=
 
[https://mail.kde.org/mailman/listinfo/release-team The KDE release team]
 
[https://mail.kde.org/mailman/listinfo/release-team The KDE release team]
Line 395: Line 419:
  
 
Currently techbase is used for feature planning but there may be better alternatives.
 
Currently techbase is used for feature planning but there may be better alternatives.
 +
 +
{{SEFBox
 +
| name=Downstream packagers and contributions
 +
| currentState=
 +
* Many distributions package KDE3 & KDE4.
 +
| getInvolved=
 +
* {{KDEML|kde-packagers}} - Private mailing list for packagers. Includes information relating to security releases.
 +
}}
  
  
Line 402: Line 434:
 
| name=Artwork
 
| name=Artwork
 
| currentState=
 
| currentState=
The {{KDEML|kde-artists|kde-artists team}} creates offical artwork for KDE.
+
* The {{KDEML|kde-artists|kde-artists team}} creates offical artwork for KDE.
 +
* kde-look.org for non-offical artwork.
 
| people=
 
| people=
 
* [http://pinheiro-kde.blogspot.com/ Nuno Pinheiro]
 
* [http://pinheiro-kde.blogspot.com/ Nuno Pinheiro]
Line 422: Line 455:
 
* Krazy includes sanity checks/plurals checking for translation.
 
* Krazy includes sanity checks/plurals checking for translation.
 
| altTools=
 
| altTools=
launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations.
+
launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. This is considered not to be useful as fly-by translators often do not follow guidelines or consistency rules when translating.
 
| getInvolved=
 
| getInvolved=
 
* {{KDEML|kde-i18n-doc}}
 
* {{KDEML|kde-i18n-doc}}
 +
}}
 +
 +
== Legal And Support ==
 +
{{SEFBox
 +
| name=KDE e.v. - Representative Legal Entity
 +
| currentState=
 +
* [http://ev.kde.org KDE e.v] is a registered non-profit organization that represents the KDE Project in legal and financial matters.
 +
| altTools= N/A
 +
| getInvolved=
 +
* [http://ev.kde.org/getinvolved/ KDE e.v. membership]
 +
}}
 +
 +
{{SEFBox
 +
| name=Resolving licencing issues.
 +
| currentState=
 +
* A [http://ev.kde.org/announcements/2008-08-22-fsfe-welcomes-fla.php Fiduicary Licence Agreement] is available, which will allow KDE developers to optionally assign copyright of their contributions to KDE e.v. This would allow easier relicencing of contributors content in the event that KDE needs to move to another licence. It also allows the e.v. to more easily represent the work in the unlikely event of a court dispute involving KDE code.
 +
* [[Policies/Licensing_Policy|KDE licencing policy]] allows commercial and non-commercial development and proprietry and non-proprietry development.
 +
* [[Projects/KDE_Relicensing|Projects/KDE_Relicensing]] Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.
 +
| altTools= N/A
 +
}}
 +
 +
{{SEFBox
 +
| name=Sponsorship and Patronship
 +
| currentState=
 +
* [http://ev.kde.org/supporting-members.php Supporters of KDE] contribute sponsorship money to KDE e.v.
 +
* http://ev.kde.org/getinvolved/supporting-members.php
 +
| altTools= N/A
 
}}
 
}}

Revision as of 21:34, 29 October 2008

This page is intended to be a summary of the tools and processes used by the KDE project for Software Engineering tasks, i.e. everything around coding work. This includes bugfixing, review, testing, documentation, requirements etc.

The current tool used by KDE should be listed along with the extent of its use, known alternatives, and advantages/disadvantages.


Contents

Development Tools

Source Control

Source Control
Current State   People  

The kde sysadmin team:

Get Involved   Alternative Tools  


Subversion 1.4 is currently used for source control management in KDE on a server hosted in Frankfurt. A separate server is used for access to the read-only mirror anonsvn.kde.org.

There is interest in migrating to a distributed source control management tool, such as GIT. Discussion of this is taking place on the Action mail generic.svg kde-scm-interest mailing list. It is likely git will be used along with a tool such as repo.


Build System

Build System
Current State   People  
Get Involved   Alternative Tools  

n/a


CMake is the build tool currently used by KDE. It is Free Software developed by kitware inc and available on multiple platforms supported by KDE.

This tool was chosen as the buildsystem for the KDE4 series, and there are no plans currently to migrate away from it. CMake version 2.6.2 will be required to build KDE 4.2 final.


Identifier search

Identifier search
Current State   People  

http://lxr.kde.org

The kde sysadmin team:

Get Involved   Alternative Tools  

n/a

n/a


LXR indexes classes and methods used in KDE. This can be useful for finding examples of how to use a class, and finding all uses of a class while refactoring or updating API.

Review

Patch review (pre commit)

Patch review (pre commit)
Current State   People  
  • David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
Get Involved   Alternative Tools  
  • Launchpad.net offers merge review/approval pre-merge [1] [2] [3]


In general KDE does not have a formal patch review policy for individual patches. Some patches do get reviewed prior to committing to svn by the relevant mailing lists. This is the case for particularly large patches or patches by new developers.

As an official policy kdereview is used to review new applications and new classes for kdelibs prior to inclusion in KDE trunk. A drawback of this system is that not all reviewers report that they have reviewed the new content. It may make sense to have a checklist for reviewers to use, eg,

  • All new classes documented [x]
  • Private classes and d-pointers used where appropriate [x]
  • Passes all krazy checks [ ]
  • No obvious security concerns [ ]
  • Designed well/maintainable [ ]
  • etc...

This was discussed to some extent here, but has not yet been refined into a techbase page.

Commit review (after commit)

Commit review (after commit)
Current State   People  
  • Action mail generic.svg kde-commits mailing list records all commits to KDE svn.
  • The commit filter is used to filter relevant commits based on path of the commit.
  • SVN CCMAIL: feature used to notify relevant mailing lists or individuals of specific commits.
  • SVN BUG: feature used to close bugs, and also notifies all bug subscribers of the commit.
  • SVN CCBUG: feature used to notify closed bugs of updates. Commonly used when porting fixes between branches. Also notifies all bug subscribers of the commit.

Unknown

Get Involved   Alternative Tools  
  • Unknown


The commit filter is used by several projects to forward all commits to the relevant mailing list.


Design Review

Design Review
Current State   People  

Design review takes place on

  • mailing lists
  • project wikis
  • face-to-face/BOF sessions and sprints
  • kdereview

Unknown

Get Involved   Alternative Tools  

n/a


KDE does not have an offical design review process. Some design review takes place as part of the kdereview process. It may be possible to further formalise this or encourage design documentation.

Documentation

Technical documentation

Technical documentation
Current State   People  
  • Danimo is the MediaWiki admin for techbase.kde.org.
Get Involved   Alternative Tools  

n/a


techbase.kde.org is a MediaWiki powered site used for collaborating on technical tasks such as tutorials, schedules, and project information. wiki.kde.org is a tiki-wiki site with the same function. Both are actively used. It might make sense to merge the two sites.


API documentation

API documentation
Current State   People  
  • Doxygen is used to generate api documentation from documentation strings in code.
Get Involved   Alternative Tools  


KDE API documentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.

It is possible to create man pages and qthelp documentation from kde sources.


User documentation

User documentation
Current State   People  

Unknown

Get Involved   Alternative Tools  

n/a


User documentation is generated from module doc/ folders and hosted on http://docs.kde.org.

meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.

http://userbase.kde.org is intended to be the primary source of user documentation on the web. Content will possibly be packaged for offline use in the future.

Testing and Quality

Bug tracking

Bug tracking
Current State   People  
  • Matt Rogers and the KDE sysadmin team maintain the KDE bugzilla installation.
Get Involved   Alternative Tools  


Bug tracking in KDE currently is managed using Bugzilla 3.0. Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. There is still cleanup work going on but most features of the previous Bugzilla installation already work.

Bugzilla can be difficult to use and daunting to newbies.


Static code analysis

Static code analysis
Current State   People  
  • Krazy hosted at EnglishBreakfastNetwork (EBN).
  • Coverity is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of Dirks Dashboard builds.
Get Involved   Alternative Tools  

n/a


Additional checks are always welcome for adding to Krazy. See http://websvn.kde.org/trunk/quality/.

Build testing

Build testing
Current State   People  
Get Involved   Alternative Tools  

n/a


There is interest in more build testing for KDE especially on non-linux platforms. Improvements include some standard ctest scripts that can be used to build and submit a dashboard result for kdelibs to CDash. This would be run on a cronjob for simplicity.

Builds are planned for the following platforms:

  • Windows
  • MacOS
  • FreeBSD 6 (gcc)
  • FreeBSD 7 (gcc)
  • Solaris (S10, S11) on SPARC and amd64


Unit testing

Unit testing
Current State   People  

Unit tests may be written with the QTest framework. Tests can be run with the command 'make test'.

Unknown

Get Involved   Alternative Tools  

n/a


It may be possible run run these tests automatically possibly on EBN or on Dirks dashboard.


Quality testing

Quality testing
Current State   People  
  • The early adopter/user community
  • SQO-OSS
Get Involved   Alternative Tools  

n/a



It may be possible to obtain metrics such as bugs per kloc, defect injection rate etc.


Profiling and Optimizations

Profiling and Optimizations
Current State   People  
  • Action mail generic.svg kde-optimize mailing list coordinates optimizations in KDE.
  • Krazy and Coverity tools also include some optimization checks.
  • KDE macros for optimization of common algorithms.

Unknown

Get Involved   Alternative Tools  

n/a


Tutorials may be provided in the future to help developers optimize their code.


Accessibility and Usability

Accessibility and Usability



Research

Research
Current State   People  
Get Involved   Alternative Tools  

n/a


Marketing and Expectations

Requirements Gathering

Requirements Gathering
Current State   People  
  • Requirements come from user feedback on http://bugs.kde.org and from commercial interests.
  • Developers may do some research into requirements for applications based on User Research Profiles.

Unknown

Get Involved   Alternative Tools  

n/a



Promotion

Promotion
Current State   People  
  • The Action mail generic.svg KDE marketing team manage marketing and promotion from official kde sources.
  • http://dot.kde.org is the community forum around promotional announcements.
  • http://www.kde.org/announcements is the official source of promotional announcements regarding KDE.
  • Design and maintenance of KDE websites is organised on the kde-www mailing list
  • The Marketing working group coordinates several marketing efforts such as promoting planning and branding.
  • KDE e.v provides a booth box for conference booths containing posters, leaftlets and other information needed at a conference stand.
Get Involved   Alternative Tools  

n/a



Community management

Community management
Current State   People  
  • The Community Working Group helps with community advice when needed
  • Code of Conduct Based on the Ubuntu Code of Conduct, documents guidelines for acceptable behaviour within the community. Can be summarized as 'Be Excellent to Eachother'.
Get Involved   Alternative Tools  
  • Send an e-mail to community-wg@kde.org

n/a



Communication

Communication
Current State   People  

Developers communicate with each other through

Developers communicate with users though

Users communicate with each other and developers through

Get Involved   Alternative Tools  
  • Add your blog to planet kde if you contribute to KDE in some way, including development, testing, advocacy, translation, documentation etc.

n/a


Release

Release Scheduling

Release Scheduling
Current State   People  
Get Involved   Alternative Tools  

n/a



Feature planning

Feature planning
Current State   People  

The KDE release team

Get Involved   Alternative Tools  


Currently techbase is used for feature planning but there may be better alternatives.

Downstream packagers and contributions

Downstream packagers and contributions
Current State   People  
  • Many distributions package KDE3 & KDE4.

Unknown

Get Involved   Alternative Tools  
  • Action mail generic.svg kde-packagers - Private mailing list for packagers. Includes information relating to security releases.

n/a



Theming and Translations

Artwork

Artwork
Current State   People  
  • The Action mail generic.svg kde-artists team creates offical artwork for KDE.
  • kde-look.org for non-offical artwork.
Get Involved   Alternative Tools  

n/a


Additional contributed artwork is available on http://kde-look.org.

There may be a need to create tutorials on how to create artwork for kde.

Translation

Translation
Current State   People  
  • http://i18n.kde.org/ is used for level of completion of translations in KDE.
  • GNU gettext is used for translation in KDE.
  • .po files are edited directly in KDE svn to update translations.
  • A kde4 based translation client (lokalize) is being developed in kdesdk/.
  • Krazy includes sanity checks/plurals checking for translation.

Unknown

Get Involved   Alternative Tools  

launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. This is considered not to be useful as fly-by translators often do not follow guidelines or consistency rules when translating.


Legal And Support

KDE e.v. - Representative Legal Entity

KDE e.v. - Representative Legal Entity
Current State   People  
  • KDE e.v is a registered non-profit organization that represents the KDE Project in legal and financial matters.

Unknown

Get Involved   Alternative Tools  

N/A


Resolving licencing issues.

Resolving licencing issues.
Current State   People  
  • A Fiduicary Licence Agreement is available, which will allow KDE developers to optionally assign copyright of their contributions to KDE e.v. This would allow easier relicencing of contributors content in the event that KDE needs to move to another licence. It also allows the e.v. to more easily represent the work in the unlikely event of a court dispute involving KDE code.
  • KDE licencing policy allows commercial and non-commercial development and proprietry and non-proprietry development.
  • Projects/KDE_Relicensing Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.

Unknown

Get Involved   Alternative Tools  

n/a

N/A


Sponsorship and Patronship

Sponsorship and Patronship
Current State   People  

Unknown

Get Involved   Alternative Tools  

n/a

N/A



KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal