Long term todos

See also

• Proposed Goals for the next coming release
• Missing patches.

Documentation

• In general, the document needs improvements. See this post for detailed account. (The gap between 1.3.0 and 1.5.0 pointed out there is already filled.)
  • needs update.
  • both in volume and in order.
  • both for users and developers.
  • the online and the distributed. (may be better to be united to one?)
• How sawfish is initialized.
  • How sawfish uses librep.
• How to test patches gracefully.
• What exactly is 'deprecated' feature? No doc at all now.
• Terminology; clarification, replacement to better ones, description.
• At least, complete GUI doc.
• Librep intro, at least Sep 2008 thread in the ML
• Sawfish event system: To aid in development and understanding, there needs to be documentation the X event model and how Sawfish interacts and deals with it.
• Crawl thru the web, find articles on sawfish, and compile them.

info

• Maybe keep only core lisp part in info, and others written in HTML.

coding

• Better to have heavy comments in the source.

Wish list

• Maybe wish items in bugzilla(s) should be collected here...

Merge good scripts into the trunk

Merge good scripts into the trunk.

In adoption, notice following points:

• Name (of feature, function, variable ...) is good?
• It should work & merge smoothly with already existing design and codes.
• User contributed codes are often slack. Make loose ends meet.

• Good one: Gimme.