1 |
On Thu, Apr 05, 2012 at 08:41:57PM -0700, Brian Dolbec wrote: |
2 |
> It is getting rather late to be just starting research for a project |
3 |
> proposal when the deadline to submit is only 15 hours from now. |
4 |
> |
5 |
> The contact person for that is not online at the moment. So unless you |
6 |
> already know what you need to do, I am afraid that you probably will not |
7 |
> get the information needed to submit a successful proposal. |
8 |
|
9 |
The deadline is indeed quite soon. Nevertheless, some resources and |
10 |
information about the project suggestion... |
11 |
|
12 |
A while ago, work was done on a Django-based framework that could (would) |
13 |
provide a new interface, layout but also new features on the Gentoo website. |
14 |
This project was called Okupy [1]. Due to lack of resources and the |
15 |
necessary push in the organization, Okupy is left as a "in-development" |
16 |
project. |
17 |
|
18 |
[1] http://blogs.gentoo.org/tampakrap/tag/okupy/ |
19 |
|
20 |
In this project suggestion, the idea is to enhance Okupy to provide |
21 |
conversion of our internal documentation format (GuideXML and the related |
22 |
XML formats) into other formats (beyond XHTML, which it already supports). |
23 |
ePub has been asked a few times (especially for the Gentoo Handbook), PDF as |
24 |
well. |
25 |
|
26 |
To integrate this in Okupy also means to verify if these translations are |
27 |
fast and powerful enough to do on a dynamically generated site. If not, |
28 |
you'll need to look into caching (well, let's say you need to. period.) and |
29 |
perhaps even pregeneration of the documents (especially for PDF as most |
30 |
conversion methods are CPU intensive). |
31 |
|
32 |
If this looks too easy for a GSoC project, consider integrating other |
33 |
document formats as master (like wiki, docbook, ...) which will have more |
34 |
consequences, as Okupy currently uses the XML files as the only master. But |
35 |
accepting input from other formats allows us to find more documentation |
36 |
providers for our documentation repository. |
37 |
|
38 |
Wkr, |
39 |
Sven Vermeulen |