Difference between revisions of "Liblicense 03 release todo"
| Line 27: | Line 27: | ||
** freshmeat | ** freshmeat | ||
** sourceforge | ** sourceforge | ||
| − | ** cc frontpage blog ('''written''') | + | ** <del>cc frontpage blog ('''written''')</del> |
| − | ** press release | + | ** <del>press release</del> |
*** <del>packaged PRESS file</del> | *** <del>packaged PRESS file</del> | ||
** <del>cc techblog how to</del> ([[Liblicense_tutorial]]) | ** <del>cc techblog how to</del> ([[Liblicense_tutorial]]) | ||
Revision as of 18:57, 31 July 2007
- issues
Nautilus writes a license to every file whose property dialog is displayedlicense chooser returns devnations -- should we mark this as retired and then not return retired licenses?(added isReplacedBy by/3.0)Unicode filename issues? Licenses aren't loaded for some test files with Japanese filenames.(Um, seems to work fine, now) (0.4)Update gui_gtk.py to use license chooser API once the above is taken care ofconfigure --prefix=/usr/local dies trying to install the python bindings- libtool: install: error: cannot install `liblicense.la' to a directory not ending in /usr/lib/python2.4/site-packages/liblicense
- Update: works after a 'make distclean'
new license chooser API not wrapped in Ruby(0.4)nautilus emblems don't work for me(Needed to touch /usr/share/icons/hicolor on installation)No sampling licenses' RDF include the prohibits commericial use statement
package press release
tag svn
- package
sourcerpm- deb
ebuild(Exempi, nautilus-python, and Liblicense ebuilds, courtesy of jakin)
- publicity
- mailing lists
- cc-devel
- cc-community
- freshmeat
- sourceforge
cc frontpage blog (written)press releasepackaged PRESS file
cc techblog how to(Liblicense_tutorial)- digg (?)
- slashdot (?)
- Boing Boing (?)
- mailing lists
