Changes: Development

Latest revision as of 21:09, 15 June 2013

This page is the portal of sawfish developments.

Want to join?[]

It's hard to tell the current status in short.

Read mailing list, or its archive. That's our main communication method.
Use git repository. Summary may be tracked via Changelog or news.texi.

If you find an interesting item in Proposed Goals, then declare it in the mailing list, and send us a patch. (Unless it's marked as assigned to someone, it's likely that none is working on that item. We're short of developers. Items in Long term todos are left untouched.)

Todos[]

Proposed Goals - todos for the coming release.
Long term todos

Past todos is a partial list of what is accomplished.
Versioning scheme

If possible[]

(Dec 2008) No one seems to be working on the items listed under this category.

Enhancements suggestion in sawfish core

Composite Extension, OpenGL and friends[]

Ostensibly the future of sawfish is have access to the new protocols. One key to implementing is understanding what they do and how they are supposed to be interacted with. To start these pages can be nothing more than links to the specs and basic tutorials.

Current Docs:

Known difficulty[]

Some know difficulty in development can be found at Patches (suspended).

Bug reports[]

Since the 2011-06-19 Sawfish left GNOME and moved to Tuxfamily. Now all new bug reports can be found on the Flyspray bug tracker. Consequently the following procedure is obsolete.

List of open bugs on bugzilla.gnome.org, of
- sawfish
- librep
- rep-gtk

To report a bug at bugzilla.gnome.org, choose:

classification: Other
application: sawfish / librep / rep-gtk

If you're not sure of which the bug is, choose sawfish.

For search from browser (like Firefox smart keyword), use the following url:

https://bugzilla.gnome.org/buglist.cgi?bug_status=__open__&order=Bug+Number&product=Sawfish&content=%s

If you want to receive notices of new bug reports, then

Make bugzilla account.
Log in, and go to 'Email preferences'
Go to 'User Watching' section, in 'Add users to my watch list', add 'librep-maint@gnome.bugs, rep-gtk-maint@gnome.bugs, sawfish-maint@gnome.bugs'.

Librep & rep-gtk[]

Librep internals[]

How to write a librep C modules is not documented. The documentation would have the API, the conventions and an skeleton example with a tutorial of sorts. The example would have all the other helper code like Makefiles and directory structure laid out. The reason for this documentation is so that new X protocols (and OpenGL) modules can be created.

Current Docs:

Librep_Internals

Window manager specs[]

Window Manager Standards

Small window managers can be taken as tutorials for how to implement window managers. Examples are:

tinywm - this is the minimal. start here.
failsafewm - then read this.

Move to other hosts?[]

Update Jun 2011: We're almost done moving to Tuxfamily.

Migration to other development hosts were discussed several times. The latest one is here.

@@ Line 5: / Line 5: @@
 It's hard to tell the current status in short.
 * Read {{ML}}, or its archive. That's our main communication method.
-* Use [[Download#GIT|git]] repository. Summary may be tracked via [http://git.gnome.org/cgit/sawfish/tree/ChangeLog Changelog] or [http://git.gnome.org/cgit/sawfish/tree/man/news.texi news.texi].
+* Use [[Download#GIT|git]] repository. Summary may be tracked via [http://git.gnome.org/cgit/sawfish/tree/ChangeLog Changelog] or [http://git.tuxfamily.org/sawfish/main.git?p=gitroot/sawfish/main.git;a=blob;f=man/news.texi;h=774c50577bddf5e3f1896114ec99e697dadbd985;hb=HEAD news.texi].
 If you find an interesting item in [[Proposed Goals]], then declare it in the {{ML}}, and send us a patch. (Unless it's marked as assigned to someone, it's likely that none is working on that item. We're short of developers. Items in [[Long term todos]] are left untouched.)
@@ Line 21: / Line 21: @@
 ==== Composite Extension, OpenGL and friends ====
-Ostensibly the future of sawfish is have access to the new protocols.  One key to implementing is understanding what they do and how they are supposed to be interacted with. To start these pages can be nothing more than links to the specs and basic tutorials.
+Ostensibly the future of sawfish is have access to the new protocols. One key to implementing is understanding what they do and how they are supposed to be interacted with. To start these pages can be nothing more than links to the specs and basic tutorials.
 Current Docs:
@@ Line 32: / Line 32: @@
 == Bug reports ==
+Since the 2011-06-19 [http://sawfish.wikia.com/wiki/2011_06_19:_Sawfish_left_GNOME Sawfish left GNOME] and moved to Tuxfamily. Now all new bug reports can be found on the [http://sawfish.tuxfamily.org/flyspray/ Flyspray] bug tracker. Consequently the following procedure is obsolete.
-* Open bugs on bugzilla.gnome.org, of
-** [http://tinyurl.com/327j83 sawfish]
-** [https://bugzilla.gnome.org/buglist.cgi?query_format=advanced;short_desc_type=allwordssubstr;short_desc=;product=librep;long_desc_type=substring;long_desc=;status_whiteboard_type=allwordssubstr;status_whiteboard=;keywords_type=allwords;keywords=;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;emailassigned_to1=1;emailtype1=substring;email1=;emailassigned_to2=1;emailreporter2=1;emailqa_contact2=1;emailcc2=1;emailtype2=substring;email2=;bugidtype=include;bug_id=;chfieldfrom=;chfieldto=Now;chfieldvalue=;cmdtype=doit;order=Bug%20Number;field0-0-0=noop;type0-0-0=noop;value0-0-0= librep]
-** [https://bugzilla.gnome.org/buglist.cgi?query_format=advanced;short_desc_type=allwordssubstr;short_desc=;product=rep-gtk;long_desc_type=substring;long_desc=;status_whiteboard_type=allwordssubstr;status_whiteboard=;keywords_type=allwords;keywords=;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;emailassigned_to1=1;emailtype1=substring;email1=;emailassigned_to2=1;emailreporter2=1;emailqa_contact2=1;emailcc2=1;emailtype2=substring;email2=;bugidtype=include;bug_id=;chfieldfrom=;chfieldto=Now;chfieldvalue=;cmdtype=doit;order=Bug%20Number;field0-0-0=noop;type0-0-0=noop;value0-0-0= rep-gtk]
-* [http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&product=sawfish All Sawfish bugs on bugzilla.gnome.org]
-* [http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sawfish Bugs reported in bugs.debian.org]
-To report a bug at bugzilla.gnome.org, choose:
+* '''List of open bugs''' on bugzilla.gnome.org, of
+** [http://bugzilla.gnome.org/buglist.cgi?product=sawfish&bug_status=__open__&order=Bug+Number sawfish]
+** [http://bugzilla.gnome.org/buglist.cgi?product=librep&bug_status=__open__&order=Bug+Number librep]
+** [http://bugzilla.gnome.org/buglist.cgi?product=rep-gtk&bug_status=__open__&order=Bug+Number rep-gtk]
+* [http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sawfish Debian bug reports]
+* [https://bugs.launchpad.net/ubuntu/+source/sawfish Ubuntu bug reports]
+To '''report a bug''' at bugzilla.gnome.org, choose:
 * classification: Other
 * application: sawfish / librep / rep-gtk
 If you're not sure of which the bug is, choose sawfish.
-For search from browser (like Firefox ''smart keyword''), use the following url:
+For '''search from browser''' (like Firefox ''smart keyword''), use the following url:
+<pre>https://bugzilla.gnome.org/buglist.cgi?bug_status=__open__&order=Bug+Number&product=Sawfish&content=%s</pre>
-<pre>http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=sawfish&long_desc_type=substring&long_desc=%s&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=</pre>
+If you want to '''receive notices''' of new bug reports, then
+# Make bugzilla account.
+# Log in, and go to 'Email preferences'
+# Go to 'User Watching' section, in 'Add users to my watch list', add 'librep-maint@gnome.bugs, rep-gtk-maint@gnome.bugs, sawfish-maint@gnome.bugs'.
 == Librep & rep-gtk ==
@@ Line 53: / Line 61: @@
 === Librep internals ===
-How to write a librep C modules is not documented.  The documentation would have the API, the conventions and an skeleton example with a tutorial of sorts.  The example would have all the other helper code like Makefiles and directory structure laid out.  The reason for this documentation is so that new X protocols (and OpenGL) modules can be created.
+How to write a librep C modules is not documented. The documentation would have the API, the conventions and an skeleton example with a tutorial of sorts. The example would have all the other helper code like Makefiles and directory structure laid out. The reason for this documentation is so that new X protocols (and OpenGL) modules can be created.
 Current Docs:
@@ Line 66: / Line 74: @@
 == Move to other hosts? ==
+Update Jun 2011: We're almost done moving to Tuxfamily.
 Migration to other development hosts were discussed several times. The latest one is [http://old.nabble.com/The-get-rid-of-gnome.org-sf.net-thing-%28chapter-3%29-to27227913.html here].