Project Elegance: Difference between revisions

From KDE Community Wiki
m (moved Elegance to Project Elegance: want redirection from elegance, this sounds more nifty and is what Aaron S described it as)
(This page is archived)
Tag: Replaced
 
(14 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= Project Elegance =
{{Note|This page is archived. See page history.}}
Place for team collaboration, especially when reimplementing functionality or forking code from another project.  
 
 
== Targeted Opportunities ==
''Senior KDE developers have placed emphasis on reaching goals for release.''
 
== Opportunities ==
''List specific feature where code has been forked, or functionality has been duplicated''
 
== Mature Practices ==
''Examples of libraries that are reused and provide robust features -- Look here before forking, move an item out of here if you are experimenting with a fork or reimplementation of this code, and put it back here when done''
 
*[[PE/Notifications]]
 
== Proposed Opportunities ==
''These pages have some notes and ideas -- if in doubt add your item here''
 
*[[PE/Tooltips]]
*[[PE/Icon Actions]]
 
== Out of scope Opportunities ==
''A design decision has been made to duplicate functionality, or functionality has branched at lower level for overriding reasons''
 
*[[PE/Plasmoid As XWindow]]
*[[PE/Panel and Desktop Activity]]
 
 
== References ==
 
Reaching for Greatness, Aaron Seigo, keynote 2010 [[Akademy]] 
http://dot.kde.org/2010/07/05/akademy-day-2
http://akademy.kde.org/sites/akademy.kde.org/files/video.png
 
== blah ==
A template for these projects
[[PE/Template]]
 
Orchestrate or avoid individual enhancement forks, and provide consistent  operation and powerful functionality to all KDE programs.
KDE, qt, C++, and our Community.

Latest revision as of 04:31, 1 October 2022

Note

This page is archived. See page history.