taskSavannah Administration - Tasks: task #10305, Submission of Sila


task #10305: Submission of Sila

Submitted by:  Chi-kwan Chan <ckchan>
Submitted on:  Mon 29 Mar 2010 02:59:18 PM UTC  
Should Start On:  Mon 29 Mar 2010 04:00:00 AM UTC Should be Finished on:  Thu 08 Apr 2010 04:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Mario Castelán Castro <marioxcc>
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)

Sat 10 Apr 2010 06:46:41 PM UTC, comment #8: 

Hash: SHA256

April 5th 2010 in GNU Savannah task #10305: "Submission of Sila".

Hi Chi-Kwan.

The project was approved since
https://savannah.gnu.org/task/?10305#comment5.  Just I leave open this
task to do a final review.  All is ok, so I close the item :).

Good luck mantaining Sila at GNU Savannah.

Item status changes:

Status -> Done
Open/Closed -> Closed
Version: GnuPG v1.4.9 (GNU/Linux)


Mario Castelán Castro <marioxcc>
Project MemberIn charge of this item.
Wed 07 Apr 2010 12:44:23 AM UTC, comment #7: 

HI Mario,

Sorry for the delay.  I was waiting for the auto-generated email.  Apparently it's for Alex but not for me.

I went through a few more GNU projects.  I finally decided to follow coreutils and use the GNU Free Documentation License for my plain text documentations (i.e., CONVENTIONS, DESIGN, and README).  I attach a updated lzma file (due to the upload size limit).

The license texts are now standard, as described in <http://www.gnu.org/licenses/fdl-howto-opt.html>.  They are listed at the end of the documentations.  This style is consistent with coreutils, emacs, and some other GNU projects.

I hope Sila is now properly licensed.

Many thanks,

(file #20142)

Chi-kwan Chan <ckchan>
Tue 06 Apr 2010 01:38:47 AM UTC, comment #6: 

Hash: SHA256

April 5th 2010 in GNU Savannah task #10305: "Submission of Sila".


I am waiting you upload the code to GNU Savannah so I can check
whether it is properly licensed.

Please write a response in this tracker within one week, else I will
delete the submission, but you still will be able to resubmit the
project again once you have enought time to deal with the registration

If you are no longer planning use GNU Savannah please let us know.  We
won't bite, and it will make us gain time.


Item status changes:

Status -> Ping-ed
Version: GnuPG v1.4.9 (GNU/Linux)


Mario Castelán Castro <marioxcc>
Project MemberIn charge of this item.
Wed 31 Mar 2010 11:50:19 PM UTC, comment #5: 

Hash: SHA256

March 31th 2010 in GNU Savannah task #10305: "Submission of Sila".

Thanks Alex for your help.

I have approved this project.  You will receive an auto-generated
email containing detailed information about the approval.

Could you please use the standard GNU GPL header in all the files
(Including plain text documentation)?.

Assigned to -> marioxcc
Version: GnuPG v1.4.9 (GNU/Linux)


Mario Castelán Castro <marioxcc>
Project MemberIn charge of this item.
Tue 30 Mar 2010 08:06:26 AM UTC, comment #4: 

Hi Alex,

I uploaded a updated version.  All the configure.ac, Makefile.am, BASH scripts, and IDL scripts in sila/tests and sila/tools now contain license headers.  In the root, in addition to Makefile.am, bootstrap.sh, and configure.ac, the document files CONVENTIONS, DESIGN, README, and THANKS also include license headers, although they are much shorter and just refer to the COPYING file.


Chi-kwan Chan <ckchan>
Tue 30 Mar 2010 06:41:15 AM UTC, comment #3: 

Hi Chi-kwan,

Let us start at the end.

  • The hosting requirements explicitly list the GFDL "or a compatible license", so using it for your documents is perfectly fine.
  • As I said I am not an administrator yet, but real admins can at their discretion approve your submission while you make the required changes (and keep this task open to ensure compliance). This is usually the case when the remaining modifications are small and/or a lot of time has elapsed, but it is best if you make the changes and resubmit a tarball. This way the approval process can be closed and everyone can go on with their businesses.
  • I also use git and I love it! Well, this was not a question but I wanted to say it :)

Now for your remaining questions:

  • The recommended style for documentation (anything beyond 10 lines) is with a license header, not a footer, just like any code file. Other projects have different styles, but they are not hosted in Savannah; we are just trying to ensure that your copyrights (or rather "copylefts") are clear for everyone and enforceable.
  • I understand then that you have joint copyright for the code, and that you should only use the name of your institute (not the division if it's not a legal entity). That should be fine.
  • Thanks for the clarification about libtool.

Please resubmit so the approval process can be closed as soon as possible and you can go back to hacking!

Alex Fernandez <alexfernandez>
Project Member
Tue 30 Mar 2010 03:05:16 AM UTC, comment #2: 

Hi Alex,

Thanks a lot for reviewing my submission!  Let me first respond to the issues you pointed out:

  • I try to make Sila follow the GNU coding standard.  I also read a few other packages (such as coreutils and fftw3) and try to follow their styles.  In fftw3, the files AUTHORS, README, NEWS, TODO, etc don't have license headers.  Nevertheless, in coreutils, I do find license "footers" in HACKING, README, etc.  I also notice the emacs README has another style...  Do you recommend me to follow the coreutils style?
  • Sure I will put the license headers back to the script files.
  • "Harvard-Smithsonian Center for Astrophysics" (CfA) is a joined institute of Harvard College Observatory and the Smithsonian Astrophysical Observatory.  (See <http://www.cfa.harvard.edu/about/>.)  I am in one of its division called the "Institute for Theory and Computation" (ITC).  I asked our director long time ago.  Because I'm paid by ITC, either CfA or ITC holds part of the copyright of my software.  Although they are totally fine to make the software open source.
  • I don't need to maintain a copy of libtool by myself.  Instead, I use libtoolize to add sila/libltdl automatically (see line 27 in sila/bootstrap.sh).  When I need to create a distribution, all I need is `sh bootstrap.sh; ./configure; make distcheck`.

However, before I start making change to the source code, let me also ask a few additional questions.

  • I notice that coreutils uses the GNU Free Documentation License v1.3 for README etc.  If I use the GNU Free Documentation License for my documents, will it complicate the copying of the project?
  • I use git.  Because the current and older versions of my code do not contain proper license headers, can I still upload the whole git repository to Savannah?


Chi-kwan Chan <ckchan>
Mon 29 Mar 2010 11:10:22 PM UTC, comment #1: 

Hi Chi-kwan,

I am trying to review your submission; I am an aspiring administrator so please excuse any mistakes in the process.

I have found a few issues with your submission:

  • A few files in the root directory (README, THANKS) don't have the license header, and they should have the same header as e.g. sila.hin -- just like code they are going to be licensed.
  • For files shorter than 10 lines (or images) this is not a requirement, but they have to be listed in the README or a similar file along with copyright information (year and holder).
  • Files like tools/budget.pro don't have copyright information at all. Are they autogenerated from other files? In this case they would not need the license header. Same goes for tests/grid.sh, */Makefile.am, etc.
  • Files have two copyright notices, one in your name and the other for "Harvard-Smithsonian Center for Astrophysics". Is this a valid copyright holder? (I would assume yes, but it has to be a legal entity, not an informal group.) Do you hold joint copyright with this institution?
  • About including the source code for libtool: I will have to ask admins if it's in the requirements, but practically speaking I don't think that the convenience of having this external library available with your code overcomes the burden of keeping and maintaining a copy yourself.

Please answer these questions to continue with the approval process; if you need to correct any files please upload a new tarball for review and we will continue from there. Thanks!

Alex Fernandez <alexfernandez>
Project Member
Mon 29 Mar 2010 02:59:18 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: Sila
  • System Name:  sila
  • Type: non-GNU software & documentation
  • License: GNU General Public License v3 or later


Sila is a collection of free software.  It provides a framework to
simulate hydrodynamic and magnetohydrodynamic flows in the rotating
shearing box approximation.  The goal of developing such a code is
two-folded: 1) to study/minimize the numeric artifacts in local
turbulence simulations; and 2) to study/measure the properties of
turbulence so one can construct sub-grid models for astrophysical
large eddy simulations.

Other Software Required:

fftw3 + GPLv2 or later + http://www.fftw.org/

Other Comments:

Sila uses libtool.  The source is in sila/libltdl so Sila should compile on a platform without libtool.
In sila/tools, we distribute some IDL scripts to visualize the simulation.  Sila runs perfectly fine without these scripts.

Tarball URL:


Chi-kwan Chan <ckchan>


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

Attach Files:

Attached Files
file #20142:  sila-1.0-alpha2.tar.lzma added by ckchan (289KiB - application/octet-stream - Both gz and bz2 are too big. Use lzma instead.)
file #20065:  sila-1.0-alpha2.tar.lzma added by ckchan (289KiB - application/octet-stream - Both gz and bz2 are too big. Try lzma...)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by marioxcc (Posted a comment)
  • -email is unavailable- added by alexfernandez (Posted a comment)
  • -email is unavailable- added by ckchan (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 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-04-10 marioxcc StatusPing-ed => Done
        Open/ClosedOpen => Closed
    2010-04-07 ckchan Attached File- => Added sila-1.0-alpha2.tar.lzma, #20142
    2010-04-06 marioxcc StatusIn Progress => Ping-ed
    2010-03-31 marioxcc Assigned toalexfernandez => marioxcc
    2010-03-30 ckchan Attached File- => Added sila-1.0-alpha2.tar.lzma, #20065
    2010-03-29 alexfernandez StatusNone => In Progress
        Assigned toNone => alexfernandez

    Back to the top

    Powered by Savane 3.5