taskSavannah Administration - Tasks: task #16599, Submission of algol

 
 

task #16599: Submission of algol

Submitter:  Jose E. Marchesi <jemarch>
Submitted:  Tue 29 Oct 2024 08:29:22 AM UTC
   
 
Should Start On:  Tue 29 Oct 2024 12:00:00 AM UTC Should be Finished on:  Fri 08 Nov 2024 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  In Progress Privacy:  Public
Assigned to:  ineiev Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 06 Dec 2024 05:56:17 PM UTC, comment #12: 

comment #10:

> I have added notices to both README.md and css/jargon.css.


If a file is in the public domain, it should include a brief note at the beginning of the files recording the authors, and anything else relevant.

> As for the license notices in a68-jargon.texi, I appreciate the recommendation but I will keep them the way they are right now.


Well, the license notice in a68-mode.el looks a little strange: first, it says the file isn't a part of GNU Emacs, but then it says that a copy of the license should come with GCC, and refers to an absent COPYING3.

Is there a reason why the standard notice is wrong for those files?

 Ineiev <ineiev>
Site Administrator
Thu 14 Nov 2024 02:44:45 PM UTC, comment #11: 

I have just pushed an update for the jargon, adding the FDL part to the .texi files other than a68-jargon.texi.  They are all now explicitly dual-licensed.

Jose E. Marchesi <jemarch>
Wed 13 Nov 2024 04:48:12 PM UTC, comment #10: 

I have added notices to both README.md and css/jargon.css.  Thanks for pointing that out.

As for the license notices in a68-jargon.texi, I appreciate the recommendation but I will keep them the way they are right now.

Thanks!

Jose E. Marchesi <jemarch>
Wed 13 Nov 2024 03:19:51 PM UTC, comment #9: 

Thank you!

Please make sure that all copyrightable files in your tarball have valid copyright and license notices. Currently, files like README.md and css/jargon.css in a68-jargon lack them.

Also, please use the form of license notices recommended in the respective licenses (or in the HowTo documents for GPL and FDL).

 Ineiev <ineiev>
Site Administrator
Mon 11 Nov 2024 04:34:19 PM UTC, comment #8: 


comment #7:

> On Sun, Nov 10, 2024 at 01:31:03AM -0500, Jose E. Marchesi wrote:
> > >
> > > How about dual-licensing this documentation under "FDL or GPL"? Cf.
> > > https://www.akban.org/wiki/GNU_Free_Documentation_License#GPL_incompatible_in_both_directions
> >
> > I would be ok with that.
>
> Then let us proceed in that direction.
>


I just pushed a patch to a68-jargon.git that introduces the dual-licensing.

Jose E. Marchesi <jemarch>
Mon 11 Nov 2024 04:03:19 PM UTC, comment #7: 

On Sun, Nov 10, 2024 at 01:31:03AM -0500, Jose E. Marchesi wrote:

> >
> > How about dual-licensing this documentation under "FDL or GPL"? Cf.
> > https://www.akban.org/wiki/GNU_Free_Documentation_License#GPL_incompatible_in_both_directions
>
> I would be ok with that.


Then let us proceed in that direction.

 Ineiev <ineiev>
Site Administrator
Sun 10 Nov 2024 06:30:58 AM UTC, comment #6: 

comment #5:

> > Regarding the a68-jargon, I am well aware of the FDL incompatibility.  I have reasons for using GPLv3+ instead of the FDL.
>
> How about dual-licensing this documentation under "FDL or GPL"? Cf. https://www.akban.org/wiki/GNU_Free_Documentation_License#GPL_incompatible_in_both_directions


I would be ok with that.

Jose E. Marchesi <jemarch>
Sun 10 Nov 2024 01:56:19 AM UTC, comment #5: 


> Regarding the a68-jargon, I am well aware of the FDL incompatibility.  I have reasons for using GPLv3+ instead of the FDL.


How about dual-licensing this documentation under "FDL or GPL"? Cf. https://www.akban.org/wiki/GNU_Free_Documentation_License#GPL_incompatible_in_both_directions

 Bruno Haible <haible>
Site Administrator
Fri 08 Nov 2024 06:49:04 AM UTC, comment #4: 

Oh well, I will then look for some other place where to host my stuff.  Sorry for wasting your time.

comment #3:

> > Regarding the a68-jargon, I am well aware of the FDL incompatibility.  I have
> > reasons for using GPLv3+ instead of the FDL.
>
> I'm sorry, I missed that.  Current Savannah hosting requirements include FDL compatibility for documentation.
>

 Jose E. Marchesi <jemarch>
Fri 08 Nov 2024 04:32:41 AM UTC, comment #3: 


> Regarding the a68-jargon, I am well aware of the FDL incompatibility.  I have
> reasons for using GPLv3+ instead of the FDL.


I'm sorry, I missed that.  Current Savannah hosting requirements include FDL compatibility for documentation.

 Ineiev <ineiev>
Site Administrator
Thu 07 Nov 2024 08:44:12 AM UTC, comment #2: 

Hi Ineiev.

Thank you very much for looking at this.
I updated the copyright notice so it doesn't use a postal address.

Regarding the a68-jargon, I am well aware of the FDL incompatibility.  I have reasons for using GPLv3+ instead of the FDL.

The gcc front-end is not ready yet for publication.

Jose E. Marchesi <jemarch>
Thu 07 Nov 2024 03:54:52 AM UTC, comment #1: 

Please make sure that all copyrightable files in your tarball have valid copyright and license notices.  While at it: currently, your license notices refer to an obsolete FSF postal address; please update to the form GNU Maintainer guidelines recommend.

The a68-jargon part is essentially documentation, however, it's released under GPLv3+ which is incompatible with the FDL.

> There is a GCC front-end for Algol 68 in the works as well, whose sources I have not published yet.


Please attach the missing sources.

 Ineiev <ineiev>
Site Administrator
Tue 29 Oct 2024 08:29:22 AM UTC, original submission:  

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


Registration Administration


Approving or discarding the registration must be done using the specific
Group administration page, accessible only to site
administrators logged in as superusers.

Registration Details


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




Description:

Repository of programs and documentation related to algorithmic languages in general and to the Algol 68 programming language in particular.

a68-mode is an Emacs mode to edit Algol 68 programs.  It supports automatic indentation, pretty printing of bold tags and auto-stropping.

The Algol 68 Jargon File provides definitions for many terms used in the context of the Algol 68 programming language and associated technologies.



Other Software Required:

No dependencies atm.


Other Comments:

a68-mode currently lives in https://git.sr.ht/~jemarch/a68-mode.

The sources for a68-jargon currently lives in https://git.sr.ht/~jemarch/a68-jargon.  The file itself is published in both html and pdf formats at https://jemarch.net/a68-jargon

There is a GCC front-end for Algol 68 in the works as well, whose sources I have not published yet.

I want to get out of sourcehut ASAP.


Tarball URL:

https://git.sr.ht/~jemarch


 Jose E. Marchesi <jemarch>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by haible (Posted a comment)
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by carlc (Updated the item)
  • -email is unavailable- added by jemarch (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-11-07 ineiev StatusNone In Progress
        Assigned tocarlc ineiev
    2024-10-29 carlc Assigned toNone carlc

    Back to the top

    Copyright © 2025 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.14-04e1.
    Corresponding source code