----- "Christopher Curran" ccurran@redhat.com wrote:
a) add @books to the Development category, (fits the 3 current opensource devel books there)
There is no point breaking string freeze if the books are already deprecated.
I don't think any are deprecated.
For reference the current books are:
- diveintopython - javanotes - ldd-pdf (linux device drivers)
so yeah developer-oriented. I went ahead and put @books into the Development category for F12.
I am still wondering about a "Content" category for F13. Should we go with that even it only were to contain @books for now? Anyway probably more important would be getting gnome-packagekit to list books when we have more.
Jens
On Tue, Sep 22, 2009 at 02:13:11AM -0400, Jens Petersen wrote:
I am still wondering about a "Content" category for F13. Should we go with that even it only were to contain @books for now? Anyway probably more important would be getting gnome-packagekit to list books when we have more.
I like that; there could be lots of content that fits, e.g. screencasts. Better to be a bit wider in our solution.
- Karsten
Karsten Wade wrote:
On Tue, Sep 22, 2009 at 02:13:11AM -0400, Jens Petersen wrote:
I am still wondering about a "Content" category for F13. Should we go with that even it only were to contain @books for now? Anyway probably more important would be getting gnome-packagekit to list books when we have more.
I like that; there could be lots of content that fits, e.g. screencasts. Better to be a bit wider in our solution.
- Karsten
I think, even considering, delivering screencasts by RPM or yum is completely the wrong approach. Documentation has a space on the desktop, videos do not.