taskSavannah Administration - Tasks: task #14778, Submission of TutoTerm

 
 

task #14778: Submission of TutoTerm

Submitted by:  Félicien PILLOT <felandral>
Submitted on:  Wed 20 Dec 2017 12:17:05 PM UTC  
 
Should Start On: Wed 20 Dec 2017 12:00:00 AM UTCShould be Finished on: Sat 30 Dec 2017 12:00:00 AM UTC
Category: Project ApprovalPriority: 5 - Normal
Status: In ProgressPrivacy: Public
Percent Complete: 0%Assigned to: Ineiev <ineiev>
Open/Closed: OpenEffort: 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 Jump to the original submission)

Sat 20 Jan 2018 01:04:42 PM UTC, comment #21:

Hi Ineiev, sorry for the delay...

I believe the file 'ABOUT-NLS' is a part of Gettext's documentation, and, accordingly to the 'COPYING' file I found in their package [0] :

"""
The gettext-runtime package is partially under the LGPL and partially under
the GPL.

The following parts are under the LGPL, see file intl/COPYING.LIB:
- the libintl and libasprintf libraries and their header files,
- the libintl.jar Java library,
- the GNU.Gettext.dll C# library,
- the gettext.sh shells script function library.

The following parts are under the GPL, see file COPYING in the toplevel
directory:
- the programs gettext, ngettext, envsubst,
- the documentation.
"""

As 'ABOUT-NLS' is generated from '${gettext-runtime package}/doc/nls.texi', I think we can affirm it is documentation, and then under the GPL.

So, I added their copyright holder for this file, in my main './README' file.

I also made little changes in the package, which is attached with this comment, such as adding an 'autogen.sh' file (correctly copyrighted).

[0] http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-runtime

(file #42985)

Félicien PILLOT <felandral>
Tue 16 Jan 2018 10:40:04 AM UTC, comment #20:

I see two possibilities:

  • removing the file;
  • finding out its copyright and license notices and adding them.
Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sun 14 Jan 2018 01:23:13 PM UTC, comment #19:

> Oh, I beg your pardon, but I'm sure ABOUT-NLS isn't copyrighted by Félicien Pillot.


I don't know what to do with this file.

Félicien PILLOT <felandral>
Sun 14 Jan 2018 11:25:10 AM UTC, comment #18:

Oh, I beg your pardon, but I'm sure ABOUT-NLS isn't copyrighted by Félicien Pillot.

Copyright notices should be valid.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sat 13 Jan 2018 01:12:19 PM UTC, comment #17:

Hi Ineiev,

> I'm not quite sure what 'own' means. I perceive it as
> a bug of Gettext that affects your package.
>
> It's you who release a tarball, so you are fully responsible for every
> file in it: what if you use a tool that adds proprietary files to your
> tarball? Who else is in the position to make sure that such things
> can't happen?
>
> When a tarball contains files without proper copyright and license
> notices, it is technically undistributable; then, Savannah download
> area is automatically mirrored, so those who release undistributable
> files impose legal risks on mirror maintainers.


Oh, I didn't know..

./config.h.in ./Makevars and ./po/fr.po have now valid copyright & license notices

> Will these notices persist after you add something to your package
> and run autoreconf?


I checked multiple times, and normally it doesn't get overwritten when any runs "autoreconf", "intltoolize", etc.

> Agreed; what about ./data/icon/tutoterm.png?


./data/icon/README file wasn't listed in the EXTRA_DIST variable, so it had been removed by "make distcheck". It should be good now.

The new revision is attached.

(file #42900)

Félicien PILLOT <felandral>
Sat 06 Jan 2018 04:41:34 PM UTC, comment #16:

> I checked each single manually created file in my archive, I used the
> "gnueval" program to double check [0] and I reread the files listed by
> Svetlana (thank you for your help).


Thank you both!

> This led to these observations/modifications:
>
> ./ABOUT-NLS comes from Gettext, it have been automatically
> generated,


Some parts of it were hand-written, and they are copyrightable.

> I see no reason for me to own it.


I'm not quite sure what 'own' means. I perceive it as
a bug of Gettext that affects your package.

It's you who release a tarball, so you are fully responsible for every
file in it: what if you use a tool that adds proprietary files to your
tarball? Who else is in the position to make sure that such things
can't happen?

When a tarball contains files without proper copyright and license
notices, it is technically undistributable; then, Savannah download
area is automatically mirrored, so those who release undistributable
files impose legal risks on mirror maintainers.

> ./po/Makevars also comes from Gettext


Another bug: bug #52227.

> ./po/fr.po comes from xgettext, I see no reason to modify its header
> (it is left as is in most packages which use Gettext).


We are not discussing what most packages do, we are discussing what
Savannah policies require. I admit I may misunderstand something,
though, so I'm willing to listen to your interpretation.

> I just added my email address.


Could you point out the advantages of not including a full license
notice and referring to it instead?

I can think of two ones:

  • it reduces the comments in the header (this doesn't seem essential to me);
  • it makes it easier to relicense the package: the translations are automatically preserved, and only the consent of other authors are needed; I'm not sure if it's really good or bad.

> ./config.h.in comes from autoheader, again, nobody never modify this
> kind of files.


It is generated by autoheader, and it says so. I think it may be
actually uncopyrightable.

> ./TAGS was useless, I deleted it.


Good idea.

> ./data/README did contain a valid notice.


Yes, it did; although it was redundant for the files it listed,
and in fact, ./data/README itself is unneeded.

> ./po/ChangeLog was automatically generated, but I still added a
> notice to it
>
> ./po/POTFILES.in seems trivial to me, but I still added a notice.


Will these notices persist after you add something to your package
and run autoreconf?

> ./po/LINGUAS is trivial.


Agreed; what about ./data/icon/tutoterm.png?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 04 Jan 2018 11:31:33 AM UTC, comment #15:

Hi Ineiev, I wish you an happy, and free, new year!

I checked each single manually created file in my archive, I used the "gnueval" program to double check [0] and I reread the files listed by Svetlana (thank you for your help). This led to these observations/modifications:

./ABOUT-NLS comes from Gettext, it have been automatically generated, I see no reason for me to own it.
./po/Makevars also comes from Gettext
./po/fr.po comes from xgettext, I see no reason to modify its header (it is left as is in most packages which use Gettext). I just added my email address.
./config.h.in comes from autoheader, again, nobody never modify this kind of files.

./TAGS was useless, I deleted it.
./data/README did contain a valid notice.

./po/ChangeLog was automatically generated, but I still added a notice to it
./po/POTFILES.in seems trivial to me, but I still added a notice.
./po/LINGUAS is trivial.

My new version is attached to this comment.

[0] https://gnueval.housegordon.org/show/261

(file #42820)

Félicien PILLOT <felandral>
Thu 04 Jan 2018 12:10:52 AM UTC, comment #14:

If it helps, I see no licence in these files: ./ABOUT-NLS, ./config.h.in, ./TAGS, ./po/Makevars, ./po/LINGUAS, ./po/fr.po (says same licence as tutoterm,needs to name the licence clearly instead), ./po/ChangeLog, ./data/README, ./po/POTFILES.in

Svetlana Tkachenko <svetlana>
Wed 03 Jan 2018 06:00:34 PM UTC, comment #13:

Could you open all files in your tarball, one by one, and check for those notices?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sun 31 Dec 2017 08:17:25 PM UTC, comment #12:

You are right, there is no reason to not include a notice in this file :)
I hope it was my last mistake !

(file #42775)

Félicien PILLOT <felandral>
Sun 31 Dec 2017 06:01:11 AM UTC, comment #11:

Have you checked all files? configure.ac still has no notices; why did you miss it?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 29 Dec 2017 10:54:55 PM UTC, comment #10:

You are right, I changed every concerned files.
Again, the new package is attached.

(file #42758)

Félicien PILLOT <felandral>
Thu 28 Dec 2017 04:41:04 PM UTC, comment #9:

Hello, Félicien!

Files like ChangeLog have no valid license notice.

Please check GNU maintainers' documentation.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 27 Dec 2017 01:45:34 PM UTC, comment #8:

Hi Ineiev, and happy christmas ;) !

I attached with this comment a new version of my package, with valid copyright and license notices in data/command-descriptions.{en,fr}.txt
I also updated the source so the program can skip these lines while parsing the files (you were right, it wasn't difficult).

(file #42736)

Félicien PILLOT <felandral>
Sun 24 Dec 2017 07:06:47 AM UTC, comment #7:

> My program, for the moment, does not allow to insert comments in these files


I don't really think it's hard to make it allow comments (which could be generally useful, by the way).

> (which are, from my point of view, trivial anyway: they have very few lines


I believe they are not trivial from copyright point of view.

> and may not stay in this form in the package for a long time).


Then we could wait and see how they'll change.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 22 Dec 2017 11:12:28 AM UTC, comment #6:

My program, for the moment, does not allow to insert comments in these files (which are, from my point of view, trivial anyway: they have very few lines and may not stay in this form in the package for a long time).
I will embed the notices in these files when they have been correctly integrated into my program and I have found out how to ignore the comments.
Would you like me to deal with it immediately, so that everything is as clear as possible, or could it wait until development has progressed a little?

Félicien PILLOT <felandral>
Fri 22 Dec 2017 08:34:08 AM UTC, comment #5:

Thank you!

Files like data/command-descriptions.en.txt have a text format, the notices should be embedded in them. README is only for those that don't allow such comments internally.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 22 Dec 2017 08:22:42 AM UTC, comment #4:

That is because I put together these files in the same README, at the root of data/, because each of these files are (for me) data.

First, I didn't find in GNU documentation that this (putting all notices in the same README) was discouraged. But after some research I see that I didn't look properly:

"""
Even image files and sound files should contain copyright notices and license notices, if their format permits. Some formats do not have room for textual annotations; for these files, state the copyright and copying permissions in a README file in the same directory.
"""

I updated the package, both data/README and data/icon/README was corrected.
I'm sincerely sorry for that mistake, because I know how much time you're wasting processing all these tasks.

The new package is attached.

(file #42701)

Félicien PILLOT <felandral>
Thu 21 Dec 2017 12:57:08 PM UTC, comment #3:

Then I wonder how it came out that data/icon/ has tutoterm.png, but no README at all, and data/command-descriptions.en.txt has no notices?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 20 Dec 2017 06:39:39 PM UTC, comment #2:

Hi Ineiev!

I think all my files have valid notices, either inside themselves or in separated READMEs (in topdir and data).
I triple-checked it :)

Félicien PILLOT <felandral>
Wed 20 Dec 2017 06:02:52 PM UTC, comment #1:

Hello, Félicien!

Please make sure that all files in your tarball have valid copyright and license notices; this includes image and sound files, their notices should be written in a README in the same directory.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 20 Dec 2017 12:17:05 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: TutoTerm
  • System Name: tutoterm
  • Type: non-GNU software and documentation
  • License: GNU General Public License v3 or later

Description:

TutoTerm is a simple terminal emulator that includes interactive documentation for the novice user. It is a tutorial that seeks to help you discover and appropriate the command line, and thus to take a step forward towards expert computing.
While the user is typing commands, the program displays information on it, examples, then it explains what happens after the command is run.
It seeks to follow up on the user's learning, go at their own pace and propose exercises of increasing complexity, and even evaluations to validate skills.

« Learning by doing », John Dewey.

Other Software Required:

GTK3 GPLv3 https://www.gtk.org/

Tarball URL:

https://savannah.nongnu.org/submissions_uploads/tutoterm-0.5.tar.gz

Félicien PILLOT <felandral>

 

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

Attach File(s):
   
   
Comment:
   

Attached Files
file #42985:  tutoterm-0.5-7.tar.gz added by felandral (443KiB - application/gzip - New revision, ./autogen.sh added and copyright holder for ./ABOUT-NLS added in ./README)
file #42900:  tutoterm-0.5-6.tar.gz added by felandral (453KiB - application/gzip - New revision)
file #42820:  tutoterm-0.5-5.tar.gz added by felandral (452KiB - application/gzip - New revision, entirely checked.)
file #42775:  tutoterm-0.5-4.tar.gz added by felandral (453KiB - application/gzip - New revision with one more (and last?) valid license notice)
file #42758:  tutoterm-0.5-3.tar.gz added by felandral (440KiB - application/gzip - New revision with valid license notices)
file #42736:  tutoterm-0.5-2.tar.gz added by felandral (447KiB - application/gzip)
file #42701:  tutoterm-0.5-1.tar.gz added by felandral (443KiB - application/gzip - New revision with correct README files)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by svetlana (Posted a comment)
  • -unavailable- added by ineiev (Posted a comment)
  • -unavailable- added by felandral (Submitted the item)
  •  

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

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 9 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 20 Jan 2018 01:04:41 PM UTCfelandralAttached File-=>Added tutoterm-0.5-7.tar.gz, #42985
    Sat 13 Jan 2018 01:12:19 PM UTCfelandralAttached File-=>Added tutoterm-0.5-6.tar.gz, #42900
    Thu 04 Jan 2018 11:31:33 AM UTCfelandralAttached File-=>Added tutoterm-0.5-5.tar.gz, #42820
    Sun 31 Dec 2017 08:17:25 PM UTCfelandralAttached File-=>Added tutoterm-0.5-4.tar.gz, #42775
    Fri 29 Dec 2017 10:54:55 PM UTCfelandralAttached File-=>Added tutoterm-0.5-3.tar.gz, #42758
    Wed 27 Dec 2017 01:45:34 PM UTCfelandralAttached File-=>Added tutoterm-0.5-2.tar.gz, #42736
    Fri 22 Dec 2017 08:22:42 AM UTCfelandralAttached File-=>Added tutoterm-0.5-1.tar.gz, #42701
    Wed 20 Dec 2017 06:02:52 PM UTCineievStatusNone=>In Progress
      Assigned toNone=>ineiev

    Back to the top


    Powered by Savane 3.1-cleanup1