Difference between revisions of "TODO list"
From WPKG | Open Source Software Deployment and Distribution
m |
m (→WPKG Client) |
||
| Line 26: | Line 26: | ||
** start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background | ** start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background | ||
* testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though. | * testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though. | ||
| − | + | * parse output of wpkg.js (STDOUT) and display programs which are being installed | |
== Developers == | == Developers == | ||
Revision as of 12:03, 22 January 2008
WPKG roadmap for 2008
If you have new ideas - please discuss it on the mailing list first.
Fixing existing bugs or feature requests
Fix bugs listed in Bugzilla: http://bugzilla.wpkg.org. Some of the bugs are ideas really, so please feel free to comment on them (or vote for them etc.).
Documentation
Write a proper documentation manual. Right now, documentation is in tiny little bits (different functionalities described on different pages). It isn't necessarily bad - but it isn't very friendly to new users.
New documentation should be an A to Z WPKG manual, with chapters, subchapters etc.
WPKG Client
- add support for 64 bit Windows systems - see http://bugzilla.wpkg.org/show_bug.cgi?id=93
- make WPKG Client window fit on 640x480 screen resolution - see http://bugzilla.wpkg.org/show_bug.cgi?id=90
- restarting the service locally from within the wpkginst.exe
- restarting the service on remote machines from within the wpkginst.exe
- possibility to enable more debugging:
- how long each part executed (-pre, -post, wpkg.js etc.)
- exit code of each part
- possibility to log into a file
- some more integration with wpkg.js: wpkg.js should be able to pass information to WPKG Client:
- start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background
- testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though.
- parse output of wpkg.js (STDOUT) and display programs which are being installed
Developers
- use SVN for commits
- all regular contributors should have a SVN account
- write a short SVN usage for contributors