From Fedora Project Wiki
< Changes
m (→Scope) |
(Move back to Incomplete - update if F21 is target) |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
= Qtile window manager = | |||
= | |||
== Summary == | == Summary == | ||
Line 27: | Line 5: | ||
== Owner == | == Owner == | ||
* Name: [[User:tdabasin|Tomas Dabašinskas]] | * Name: [[User:tdabasin|Tomas Dabašinskas]] | ||
* Email: tomas | * Email: tomas AT redhat.com | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
Line 37: | Line 14: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/20 | Fedora 20 ]] | * Targeted release: [[Releases/20 | Fedora 20 ]] | ||
* Last updated: | * Last updated: 22/07/2013 | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
Line 60: | Line 37: | ||
== Scope == | == Scope == | ||
* Package python-xpyb (complete) | * Package python-xpyb (complete){{result|pass}} | ||
* Enable xcb for cairo | * Enable xcb for cairo{{result|inprogress}} | ||
* Enable xcb and xpyb for pycairo | * Enable xcb and xpyb for pycairo{{result|inprogress}} | ||
* Package qtile | * Package qtile{{result|inprogress}} | ||
Line 69: | Line 46: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: | * Other developers: [[User:Cicku|Christopher Meng]](package review/testing)<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
Latest revision as of 12:58, 29 April 2014
Qtile window manager
Summary
Self contained change to provide qtile window manger.
Owner
- Name: Tomas Dabašinskas
- Email: tomas AT redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 20
- Last updated: 22/07/2013
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
- Qtile is simple, small, and extensible. It's easy to write your own layouts, widgets, and built-in commands.
- Qtile is written and configured entirely in Python, which means you can leverage the full power and flexibility of the language to make it fit your needs.
- The Qtile community is active and growing, so there's always someone to lend a hand when you need help.
- Qtile is free and open-source software, distributed under the permissive MIT license.
Benefit to Fedora
- Qtile is configuration files are written in python
- Qtile is packaged for every other major distro.
Scope
- Package python-xpyb (complete)
- Enable xcb for cairo
- Enable xcb and xpyb for pycairo
- Package qtile
- Proposal owners: tdabasin
- Other developers: Christopher Meng(package review/testing)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)