summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorRichard Hughes <richard@hughsie.com>2007-12-12 18:05:39 +0000
committerRichard Hughes <richard@hughsie.com>2007-12-12 18:05:39 +0000
commitd2189ff748cd6eaf6c4b1ba9b9e17d4f6f7096fa (patch)
treeb14aade392edc4bbd23126ccb05d9814b368fa08 /TODO
parent94aa4e8ab32e5feae959b23dc6fed382abc968fc (diff)
add some more items to the TODO
Diffstat (limited to 'TODO')
-rw-r--r--TODO38
1 files changed, 38 insertions, 0 deletions
diff --git a/TODO b/TODO
index 6275c0c8..91c19a4c 100644
--- a/TODO
+++ b/TODO
@@ -1,5 +1,43 @@
Order of no particular importance:
+* Lots of the functions are not well commented with gtk-doc. Most
+important is to get the libpackagekit/*.c annotated as it's used in
+other projects. This is probably quite a boring job but is a good way to
+work out how PackageKit is put together.
+
+* We need to make sure the html documentation is still correct and easy
+to read - does any of it sound like technobabble? Is it easy enough for
+developers to get detailed information about how to contribute?
+
+* We need to audit all the strings in gnome-packagekit so that they are
+easily localisable and don't contain markup. This is one for you if you
+are also a translator.
+
+* We need some yelp documentation for the gnome-packagekit tools. This
+will mean getting screenshots and generally explaining how to use the
+tools.
+
+* We need a proper security audit of the packagekitd daemon. We are
+running as root, so we need to make sure we are not doing anything
+insane that would mean we could crash and do bad things.
+
+* We need more unit tests where we can actually simulate _using_
+packagekit, probably using an enhanced dummy backend and libpackagekit.
+This is a tricky one as we can't assume we have the
+org.freedesktop.PackageKit.conf file installed in the system prefix -
+maybe we can #ifdef the daemon to run in the session bus for some
+testing.
+
+* The gnome-packagekit tools don't exactly conform the the GNOME Human
+Interface Guidelines (HIG). Someone needs to evaluate the GUI tools and
+suggest changing some control types, adding key-shortcuts and tooltips
+and changing the spacing between widgets where needed.
+
+* Maybe we need to have on the website who is responsible for what, i.e.
+that Ken and Elliot are the conary dudes, and Luke and Tim are the yum
+dudes, etc. Maybe photos and a short two sentence profile might be a
+good idea too.
+
*** write to the database for config stuff
- Probably should move the job number too