taskSavannah Administration - Tasks: task #13649, Submission of Alignak


task #13649: Submission of Alignak

Submitted by:  Alignak <alignak>
Submitted on:  Tue 16 Jun 2015 05:27:57 PM UTC  
Should Start On:  Tue 16 Jun 2015 12:00:00 AM UTC Should be Finished on:  Fri 26 Jun 2015 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  0% Assigned to:  Assaf Gordon <agn>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Mon 11 Jan 2016 01:37:37 PM UTC, comment #11: 


We are not interested in registering Alignak. We only wanted to register to use mailing list but we found something fitting our needs in a better way.


Alignak <alignak>
Mon 11 Jan 2016 01:35:54 PM UTC, comment #10: 


We are not interested in registering Alignak. We only wanted to register to use mailing list but we found something fitting our needs in a better way.


Sun 10 Jan 2016 09:21:01 PM UTC, comment #9: 


Are you still interested in the submission of project 'Alignak' ?

If within two weeks there is no reply, this submission request
will be closed. You will still be able to register the project
again once you have the time to
deal with the registration issues.

- Assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Sun 30 Aug 2015 11:39:23 PM UTC, comment #8: 


As I explained before, to comply with GNU Savannah's hosting requirements,
EACH file must have a clear copyright statement and license information.

If you had created a new package all by yourself (i.e. wrote ALL files by yourself from scratch),
then adding mentioning the copyright and licenses for all files in a README file
would be been somewhat acceptable (though still highly discouraged).

But you are forking an existing package written by others.
So for example, the files I've listed before:

Contains a AGPLv3 license notice, and a mention that "this file is part of Shinken".
But who is the copyright owner of this file?
I would assume that perhaps it is the "shinkin" project authors - but there is no way to know.

That is why, especially with a project is written by multiple parties, it is required that each file is clearly licensed and copyrighted.

ensure all files have clear copyright statements and licensing information - either by your or by the upstream project.

Regarding the usage of "Linux":
In the files that I've listed (and perhaps in others), the term "Linux" is used in comments.
Those could and should be changed without affecting program execution.

Regarding excluding files:
If you intend to later add these files to Savannah (e.g. using git), then these files should not be excluded.

To continue with project evaluation,
please upload an updated archive (i.e. a tarball, containing all files, updated and not-updated) using the savannah web interface.

 - assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Fri 28 Aug 2015 07:29:16 PM UTC, comment #7: 

Any news about this?

Alignak <alignak>
Mon 13 Jul 2015 08:00:46 PM UTC, comment #6: 


As you mentionned before I added a note in the README to specify the licence in file without it. Is it not enough?

My note is :

"Alignak is licensed under the Gnu Affero General Public Licence version 3 (AGPLv3). Unless specified by another header, this licence apply to all files in this repository"

For the linux vs GNU/Linux,
As far as I can see those are "variables" in configuration files and or in tests files.

I can just reupload the tarball without the /test directory, which is basically useless for Savannah (as I won't run tests from this source)

Is this good for you?

I'll reupload the file without test and small fixes if so. (https://github.com/Alignak-monitoring/alignak/compare/Enh_linuxvsgnulinux?expand=1)

Thanks !

Alignak <alignak>
Mon 13 Jul 2015 02:55:01 AM UTC, comment #5: 


Thank you for the update.

There are still some source code files without a clear copyright statement or license notice (or both). Few examples are:

There could be others. Please ensure ALL source code files have a clear copyright and license information.

Regarding "linux" vs GNU/Linux:
All instances that refer to running under the GNU/Linux operating system should say "GNU/Linux". Instances that refer to kernel-specific function (e.g. a system-call) should say "Linux".

Few examples:

In 'etc/sample/hosts/srv-postgresql.cfg', the comment is "# This is a sample host for a postgresql server running under linux," - when the intention is that it runs under GNU/Linux operating system (unless it's a non-gnu but still linux-based system).
This repeats in many other CFG files.

In 'test/test_service_tpl_on_host_tpl.py', the comment says "The linux and http service should exist on the linux host" - since other comments near that line refer to "windows", I assume that "linux" here refer to the entire operating system which should be GNU/Linux, and not to the "Linux" kernel.

 - assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Thu 09 Jul 2015 05:48:02 PM UTC, comment #4: 

Hi there,

Since I did not have any feedback I'm uploading a new tarball

(file #34403)

Alignak <alignak>
Mon 29 Jun 2015 02:29:40 PM UTC, comment #3: 


Thanks for your feedback. I attached a draft of file to specify the Licence in the whole project.

Tell me if this is fine for you so that I can integrate it upstream.

Moreover, can you point me some file with linux in it?
My grep mostly give me test files or etc files.
I've found only one or two occurences of linux that are worth correcting IMO (logging event and comments in python file)
Do we agree that there are not many occurences of Linux that need to be replaced by gnu/Linux ?

For multisite.mk I removed a lot of file in contrib because this directory is mostly a trash / draft place. It's on the Roadmap to clean this properly.

Let me know if you are OK with the file so that I can merge it in the develop branch (the one you looked at it)


PS : There is no official release of this project for now. I was planning to update tarball at every release on Savannah.

(file #34343)

Alignak <alignak>
Mon 29 Jun 2015 03:59:13 AM UTC, comment #2: 


Thank you for submitting a new project to host on GNU Savannah.

The project type "non-gnu" is correct: using GPL/AGPL license does not make an official GNU package.

project hosted on savannah must comply with the hosting requirements:

Please add copyright statement and license notice to all files.
There are several python files and many cfg files which do not have one or the other (or both).
For non-source code files - if you can not embed a copyright and license information in the files, please add a README file with explicit information about the files.

Several files mention "Linux".
Linux is a Kernel, not a whole operating system. Please update the files and use the correct term GNU/Linux if the context is operating system and not Kernel-specific topic.
See http://www.gnu.org/gnu/linux-and-gnu.html and https://www.gnu.org/philosophy/words-to-avoid.html .

The file 'contrib/install.d/multisite.mk' mentions "Open Source Components".
Please use "Free Software" to refer to software which respects Your Freedom.
For more information, see http://www.gnu.org/philosophy/open-source-misses-the-point.html and https://www.gnu.org/philosophy/words-to-avoid.html .

Please upload an updated archive to continue the submission process.

- assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Thu 18 Jun 2015 03:43:09 PM UTC, comment #1: 

I think I made a mistake in the Type of project : it's a Gnu software as it is AGPL Licence.


Je pense avoir fait une erreur sur le type de projet : c'est un logiciel GNU comme c'est une licence AGPL

Alignak <alignak>
Tue 16 Jun 2015 05:27:57 PM UTC, original submission:  

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 Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):

Registration Details

  • Name: Alignak
  • System Name:  alignak
  • Type: non-GNU software and documentation
  • License: Affero General Public License v1 or later (AGPLv3)


Alignak is a monitoring project written in Python. It's a Shinken's fork

Other Software Required:

CherryPy - BSD - https://pypi.python.org/
pycurl  - MIT - https://pypi.python.org/
importlib - PSFL - https://pypi.python.org/
pbr - Apache - https://pypi.python.org/
termcolor==1.1.0 - MIT - https://pypi.python.org/
setproctitle - BSD - https://pypi.python.org/

Tarball URL:


Alignak <alignak>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #34440:  alignak-develop.tar.gz added by alignak (406KiB - application/x-tar-gz - Minimal version of tarball)
file #34403:  alignak-develop.tar.gz added by alignak (717KiB - application/x-tar-gz - New tarball)
file #34343:  copyright added by alignak (35KiB - application/octet-stream - Draft of README/copyright based on Debian one)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by agn (Posted a comment)
  • -email is unavailable- added by alignak (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-01-16 agn StatusWait reply => Cancelled
        Open/ClosedOpen => Closed
    2015-07-13 alignak Attached File- => Added alignak-develop.tar.gz, #34440
    2015-07-09 alignak Attached File- => Added alignak-develop.tar.gz, #34403
    2015-06-29 alignak Attached File- => Added copyright, #34343
    2015-06-29 agn StatusNone => Wait reply
        Assigned toNone => agn

    Back to the top

    Powered by Savane 3.5