[Savannah-hackers] Re: submission of exselt : a XSLT-based web publishing eng - savannah.nongnu.org

[Mathieu Roy]

Hi,

I'm evaluating the project you submitted for approval in Savannah.

address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Stéphane Bonhomme <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: exselt : a XSLT-based web publishing eng
> System name: exselt
> Type: non-GNU
> 
> Description:
> exselt is a web publication engine based on XSLT and designed to use
> effeciently CSS2.
> With this Perl and XSLT kit for Apache, the structure of a website and the 
> global layout of pages (blocks) are described in an XML sitemap file. When a 
> page is requested, the XML sitemap is processed on the fly to build the HTML 
> document served to the browser.
> The strong point of the system is that blocks can be defined not only at page 
> level but also at a section level providing a convenient way to design menus 
> and other blocks for a subset of the site\'s pages.
> Another point is that a site designed with this tool has a coherent
> class attribute (of HTML div elements) naming convention for use with
> CSS. As a consequence, the system can generate CSS skeletons providing
> the selectors, so that the web designer just has to fill in the gaps with 
> style rules.
> Actual page content is not part of the site description file, it
> only references modules which can be either \"standards\" modules of the
> system (such as sitemap or page summary) generated by an XSLT process or 
> \"user\" modules adressed by keywords.
> The user modules are chuncks of HTML files, indexed by an XML catalog file 
> containing meta information (keywords, date, author...). In the process of 
> building a page, the modules matching at least one keyword are gathered to 
> produce the actual content of the page.
> \"As of today\", the composition of pages is efficient. I\'m currently
> working on a web-based interface for module management.
> Other small tricks are also included such as a cookie mechanism to recall the 
> CSS used (as on savannah site :). It is also possible to write CSS using 
> #IFDEF directives in order to manage the difference of implementation between 
> browsers (it uses the gcc preprocessor).
> 
> project source code : http://waloo.homelinux.net/webengine

To release your project under the GPL, you should put
copyright notices and copying permission statements
at the beginning of every source-code file, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt).
Put it in a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explain the reason behind these recommendations.  For
example, there is an entry explaining why the GPL requires including a
copy of the GPL with every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude



Please register your project once more with the changes mentioned
above.  The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times.  Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,


-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english