[FM Discuss] Versioning for entire collections

[Luke Faraone]

On Fri, Oct 17, 2008 at 16:52, adam hyde <adam at flossmanuals.net> wrote:

> A deb would be fantastic...were you thinking of doing it in html or
> using pdf? I was actually pondering the possibility of a simple GTK
> reader...too fancy? We could (for example) export to docbook if we could
> find a nice reading app...



GNOME uses Yelp <http://live.gnome.org/Yelp> to read their manuals, I'm sure
we could use that too if we'd rather. (Although I've been partial to
Browsers, we can do both!)

DocBook works the best, as it can be easilly converted from there to a
multitude of formats.

Here's my idea of the workflow:

   1. Upstream (FLOSSManuals) provides export functionality (to DocBook) and
   a generic make-me-a-manual script (pulls in the latest DocBook, converts to
   whatever format, I can write this)
   2. Downstream (Debian, Fedora, Ubuntu) works out the making it a package
   (I'll do this for sugar + debian/ubuntu)



On Fri, Oct 17, 2008 at 17:19, Seth Woodworth <seth at laptop.org> wrote:

> Hrrm... I would be very interested in upstreaming a sugar-manual package
> into Sugar-for-other-distro's.
>

That's the idea. I'm hoping to be able to package


> *shrug*  have high numbers.  Or name a release by day/time.  Having *any*
> > release info is better than none.
> >
> > Actually, I think that a timestamp wouldn't be awful, use the exact
> moment
> > that someone hits the publish button.  Easy.
>


>
> I agree. I think that even without any info it would still be good to
> have a DEB package of all of the manuals. Once the process is created,
> it can help bring focus to upstream/QA type work/issues.


I assume here that it'll be a separate DEB per manual... (or group)

-lf (ffm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20081017/1c3c0db3/attachment.htm>