[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #14082] Submission of anise

From: Josef Hahn
Subject: [Savannah-register-public] [task #14082] Submission of anise
Date: Sun, 10 Jul 2016 23:23:10 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0


                 Summary: Submission of anise
                 Project: Savannah Administration
            Submitted by: parsley2015
            Submitted on: Sun 10 Jul 2016 11:23:07 PM GMT
         Should Start On: Sun 10 Jul 2016 12:00:00 AM GMT
   Should be Finished on: Wed 20 Jul 2016 12:00:00 AM GMT
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00



A new project has been registered at Savannah 
This project account will remain inactive until a site admin approves or
discards the registration.

= Registration Administration =

While this item will be useful to track the registration process, *approving
or discarding the registration must be done using the specific Group
<> page*,
accessible only to site administrators, effectively *logged as site
administrators* (superuser):

* Group Administration

= Registration Details =

* Name: *anise*
* System Name:  *anise*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later


==== Description: ====
Many software developers need to cope with a bunch of different large and tiny
tools for completing their day-to-day business. Developers working on
different projects, living in different software development ecosystems,
building on different software frameworks are even more confronted with that
issue. Typical tasks can be:

    generating documentation
    creating packages
    handling version information
        e.g. print it in the manual
    creating a homepage automatically built from the available version
information, the packages, the documentation and so on
    deploying this homepage to a web server

The anise framework allows you to implement all those tasks in a structured
but generic way in a combination of XML and Python code. Once you have created
this stuff at a defined place in your project, anise lets you easily execute
your tasks from command line (or from any editor if you embed it somehow).

The anise engine executes arbitrary Python source code and provides some
additional services like logging, parameter passing from command line, basic
graphical user interface support, a plugin interface, a flexible event system,
injecting code and data from other place, and more.

On top of this engine, anise comes with a bunch of implementations which
fulfill tasks (or parts of them) of software development. There is a testing
module, a documentation- and homepage-generator, some package building methods
and a lot more. The implementations use the event system in many places in
order to allow customization in a somewhat technical but very flexible way.

Your part as a project developer is to create a project description file,
which contains all project metadata and custom implementations of some tasks,
and add this file to your project. This is an xml file which assembles and
configures a 'program plan' from the stock of available features. A user may
choose a task from that program plan for execution afterwards.

Since your project's processes probably use tools which are not natively
supported by anise, you will also have to use the (really simple, I promise!)
plug-in system or hack some Python code directly into the xml (Ugh!) for
writing an adaptor.

==== Other Software Required: ====
Python 3.4, Python Software Foundation License,

==== Tarball URL: ====


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]