Latest revision as of 22:46, 4 June 2015

qtile

Summary

qtile is a tiling window manager written in python. More can be found at the project's website

Owner

Name: John Dulaney
Email: <jdulaney@fedoraproject.org>
Release notes owner:

Current status

Targeted release: Fedora 22
Last updated: 10-12-2014
Tracker bug: #1191544

Detailed Description

Simple, small and extensible. It's easy to write your own layouts, widgets and commands.
Configured in Python.
Command shell that allows all aspects of Qtile to be managed and inspected.
Complete remote scriptability - write scripts to set up workspaces, manipulate windows, update status bar widgets and more.
Qtile's remote scriptability makes it one of the most thoroughly unit-tested window mangers around.

Benefit to Fedora

Bring a really slick window manager with an active upstream to Fedora.

Scope

Proposal owners:

Completed.

Other developers: N/A (not a System Wide Change)

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

Install qtile (dnf install qtile)
In desktop/session manager, select qtile
log in
Hit meta(Windows key) - r to bring up launcher on task bar at bottom of screen
type firefox and hit enter
Firefox should come up
Use ctrl-meta-q to log out.

User Experience

Nice, highly configurable, python-y awesomeness!

Dependencies

All dependencies are packaged, upstream has released 0.9.1

Contingency Plan

Package is in repos, change is in place.

Documentation

Coming

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 <!-- Self Contained or System Wide Change Proposal?
 Use this guide to determine to which category your proposed change belongs to.
@@ Line 20: / Line 18: @@
 -->
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
+= qtile =
-= Change Proposal Name <!-- The name of your change proposal --> =
 == Summary ==
-<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
+qtile is a tiling window manager written in python.  More can be found at the project's [http://www.qtile.org/ website]
 == Owner ==
@@ Line 32: / Line 28: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:jdulaney| John Dulaney]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Email: <jdulaney@fedoraproject.org>
 * 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)
@@ Line 45: / Line 41: @@
 == Current status ==
-* Targeted release: [[Releases/<number> | Fedora <number> ]]
+* Targeted release: [[Releases/22 | Fedora 22 ]]
-* Last updated: (DATE)
+* Last updated: 10-12-2014
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 Bugzilla states meaning as usual:
@@ Line 55: / Line 51: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1191544 #1191544]
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+* Simple, small and extensible. It's easy to write your own layouts, widgets and commands.
+* Configured in Python.
+* Command shell that allows all aspects of Qtile to be managed and inspected.
+* Complete remote scriptability - write scripts to set up workspaces, manipulate windows, update status bar widgets and more.
+* Qtile's remote scriptability makes it one of the most thoroughly unit-tested window mangers around.
 == Benefit to Fedora ==
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+Bring a really slick window manager with an active upstream to Fedora.
 == Scope ==
 * Proposal owners:
-<!-- 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?-->
+Completed.
 * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 77: / Line 77: @@
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 97: / Line 96: @@
 -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Install qtile (dnf install qtile)
-N/A (not a System Wide Change)
+* In desktop/session manager, select qtile
+* log in
+* Hit meta(Windows key) - r to bring up launcher on task bar at bottom of screen
+* type firefox and hit enter
+* Firefox should come up
+* Use ctrl-meta-q to log out.
 == User Experience ==
-<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+Nice, highly configurable, python-y awesomeness!
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+All dependencies are packaged, upstream has released 0.9.1
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Contingency Plan ==
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+Package is in repos, change is in place.
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+Coming
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==
@@ Line 133: / Line 123: @@
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF22]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Search

Changes/qtile: Difference between revisions