taskSavannah Administration - Tasks: task #14832, Submission of Megatest

 
 

task #14832: Submission of Megatest

Submitted by:  Matthew Welland <kiatoa>
Submitted on:  Mon 29 Jan 2018 07:30:54 PM UTC  
 
Should Start On:  Mon 29 Jan 2018 12:00:00 AM UTC Should be Finished on:  Thu 08 Feb 2018 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  In Progress Privacy:  Public
Percent Complete:  0% Assigned to:  Ineiev <ineiev>
Open/Closed:  Open 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)

Wed 25 Apr 2018 05:09:32 PM UTC, comment #39:

I'm sorry, I made you misunderstand me. My point was: all files should have the notices, not just PDF files.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 23 Apr 2018 07:45:15 PM UTC, comment #38:

Ok, I will update PDF files and add explicit mention of images with notices to the README. It will be 1-2 weeks before I have time to complete this so should be done in the first or second week of May.

Matthew Welland <kiatoa>
Wed 11 Apr 2018 05:31:28 PM UTC, comment #37:

All files should have prominent notices, https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html; if the file is a text like a typical PDF, the readers should see them when they read the file; if the file is an image, the notices should be in the README file in the same directory as the image.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 04 Apr 2018 09:08:38 PM UTC, comment #36:

By "editable" I meant text based files editable by a text editor. Thus graphic files such as png, svg and pdf would be excluded.

Matthew Welland <kiatoa>
Wed 04 Apr 2018 03:51:05 PM UTC, comment #35:

What do you mean by "editable" file? All files should have notices, no matter text or non-text.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 02 Apr 2018 05:44:08 PM UTC, comment #34:

That was an oversight, the script I used to detect candidates for copyright and license notice addition used file to detect if it was an editable file. That particular file detected as non-text:

> file ./tests/unittests/cron.scm

./tests/unittests/cron.scm: Emacs v18 byte-compiled Lisp data

I fixed the script and updated all files found with copyright and license notices.

Matthew Welland <kiatoa>
Mon 02 Apr 2018 04:30:19 PM UTC, comment #33:

Please comment on tests/unittests/cron.scm: as far as I can see, it still lacks the notices.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 26 Mar 2018 05:49:07 PM UTC, comment #32:

Thank you for pointing out the correct terms to use. This cleared up my confusion and I have made the corrections needed. All relevant files now have a copyright notice and a license notice.

Matthew Welland <kiatoa>
Fri 23 Mar 2018 08:32:21 AM UTC, comment #31:

> I used the word header as a synonym for the notice as I have been putting the notice in the header.


I'm sorry, this confuses me a little bit. Let us stick to Savannah's terms: copyright notice and license notice (not "the notice," in singular, because they are different things). In particular, I was speaking about copyright notices.

> Those are the files


These sentence seems incomplete. Would you like to amend it?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 22 Mar 2018 09:37:28 PM UTC, comment #30:

1. The sxml files were removed. It no longer matters that I could not add notices to them. To answer your question, there was no way to add notices without corrupting the file so that the tools that used it would not crash.

2. I used the word header as a synonym for the notice as I have been putting the notice in the header.

3. There are currently only three files in the Megatest code bundle that do not have a notice/header. ALL other files have a notice header at this time. Those are the files

I am a fan of the GPL and I'd be proud to have Megatest be a part of the GNU tools even if only indirectly. That said, if you prefer to not have Megatest be hosted at savannah.gnu.org I will be disappointed but I understand.

So far as I can tell the Megatest code bundle meets the requirements for hosting.

Matthew Welland <kiatoa>
Thu 22 Mar 2018 04:53:38 PM UTC, comment #29:

> I explained below that the .sxml files are metadata machine generated files that are included in a provided example flow.


I understand that they are examples and that they are generated; still I don't see why they have no notices.

> I've removed the files that were included to help new users and now there are only three files which do not have the header...


But I didn't care about the header, I spoke about missing notices. I think this confirms that Savannah policies would be hard for you to follow.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 20 Mar 2018 06:40:22 PM UTC, comment #28:

I explained below that the .sxml files are metadata machine generated files that are included in a provided example flow.

I've removed the files that were included to help new users and now there are only three files which do not have the header:

.fossil-settings/crnl-glob
.fossil-settings/ignore-glob
COPYING

Matthew Welland <kiatoa>
Mon 19 Mar 2018 01:44:16 PM UTC, comment #27:

> The only files that do not have the license header are the sxml files.


Why don't they have them?

Anyway, this may be less important issue; as far as I can see, many files still lack copyright notices. Perhaps following Savannah policies would be hard for your package.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 05 Mar 2018 03:27:39 PM UTC, comment #26:

You are right, xfig files have a comment line and those are preserved even after editing the file with xfig itself. I have added license headers to the xfig and html files.

The only files that do not have the license header are the sxml files. These are machine generated data files used in examples on how to use Megatest itself.

I believe all requirements for hosting are met.

Matthew Welland <kiatoa>
Thu 01 Mar 2018 03:42:36 PM UTC, comment #25:

> For convenience we bundle some generated html and sexpr files. These files cannot have headers added.


I believe notices can be added to HTML files, for example, https://savannah.gnu.org/register/requirements.php is HTML and contains them.

> There are also xfig files for drawings in the documentation and these also cannot have license headers added.


Why not?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 28 Feb 2018 08:07:39 PM UTC, comment #24:

For convenience we bundle some generated html and sexpr files. These files cannot have headers added. There are also xfig files for drawings in the documentation and these also cannot have license headers added. I have read all the requirements and I believe I now have the Megatest project in compliance.

FYI, you can use the below script to find files without a license header to confirm my assertion that Megatest meets the requirements.

Thanks.

===script to find files needing license header==
#!/bin/bash
project=Megatest
for f in $(
for x in $(find . -type f);do
if [[ $(file $x|grep text) ]];then
echo -n "$x ";
fi;
done);do
if [[ $(wc -l $f | awk '{print $1}') -gt 10 ]];then
if ! $(grep -q ${project}' is free software' $f);then
echo "$f ";
fi;
fi
done

Matthew Welland <kiatoa>
Wed 28 Feb 2018 05:52:03 PM UTC, comment #23:

> I have done yet another pass through all text files in the Megatest v1.65 release candidate bundle and added the license header in all files that are not machine generated or more than 10 lines long.


Thank you! What about the machine-generated files?

> Are there any other requirements?


They are documented on https://savannah.gnu.org/register/requirements.php

Other guidelines are provided in FAQs.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 27 Feb 2018 08:19:19 PM UTC, comment #22:

I have done yet another pass through all text files in the Megatest v1.65 release candidate bundle and added the license header in all files that are not machine generated or more than 10 lines long.

I believe the hosting requirements regarding licensing are met. Are there any other requirements?

Matthew Welland <kiatoa>
Sat 24 Feb 2018 10:26:54 AM UTC, comment #21:

Thank you, URLs like http://www.kiatoa.com/fossils/megatest/tarball?r=v1.65 will do.

Now, please make sure your tarball complies with Savannah hosting requirements; in particular, all files should have valid copyright and license notices.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 23 Feb 2018 07:59:33 PM UTC, comment #20:

Included are all the core files needed for compilation. I removed the testsuite, examples and documentation as I couldn't get it to upload, presumably because it was too big.

From the provided file, megatest.tar.gz, you have the core files needed to compile to the executable.

You can get the entire tar.gz for the current release using curl or wget:

curl 'http://www.kiatoa.com/fossils/megatest/tarball?r=v1.65' > megatest-v1.65.tar.gz

Or, from the URL https://kiatoa.com/cgi-bin/fossils/megatest/tree?ci=v1.65, you can browse all the files for the release.

Matthew Welland <kiatoa>
Fri 23 Feb 2018 06:28:37 PM UTC, comment #19:

Is this really what you are going to distribute? What are "extraneous files"?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 23 Feb 2018 04:43:38 PM UTC, comment #18:

I trimmed out extraneous files and was able to get a .tar.gz to load. Please take a look. Thanks.

Matthew Welland <kiatoa>
Thu 22 Feb 2018 03:05:09 PM UTC, comment #17:

Thank you, there are too many files. Please provide a tarball.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 22 Feb 2018 04:50:12 AM UTC, comment #16:

Cannot get tar to upload. Size is 2.5M. Please browse the files directly at https://kiatoa.com/cgi-bin/fossils/megatest/tree?ci=v1.65

Thanks.

Matthew Welland <kiatoa>
Thu 22 Feb 2018 04:41:56 AM UTC, comment #15:

Added new tar file.

Matthew Welland <kiatoa>
Thu 22 Feb 2018 04:33:26 AM UTC, comment #14:

Headers fixed.

Matthew Welland <kiatoa>
Wed 21 Feb 2018 05:17:35 PM UTC, comment #13:

Sorry, in the latest tarball, the COPYING seems correct; some license headers weren't.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 21 Feb 2018 05:16:02 PM UTC, comment #12:

I'm sorry, in the latest attached file I can see, in comment #5, the issue hasn't been addressed.

Did you attach the right file?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 21 Feb 2018 05:06:19 PM UTC, comment #11:

Thank you for re-opening the task. I believe the policy page provided for nanomsg addresses any concerns about the use of trademarks for nanomsg. I attached the .tar.gz below with the license headers done correctly. These changes will be a part of the next release of Megatest anticipated this week. Is there anything else needed to gain approval for Megatest?

Matthew Welland <kiatoa>
Wed 21 Feb 2018 03:36:25 PM UTC, comment #10:

> Does this policy address the concerns?


What do you think about it?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 21 Feb 2018 04:16:09 AM UTC, comment #9:

The author/maintainer of nanomsg posted this policy regarding the trademark on nanomsg: http://nanomsg.org/trademarks.html

Does this policy address the concerns? If so, then I think the requirements for registering Megatest have been met.

Thanks.

Matthew Welland <kiatoa>
Mon 19 Feb 2018 07:45:47 PM UTC, comment #8:

The current author/maintainer of nanomsg, gdamore, made the following comment:
========
I can see that the problem is that the "trademark" statement is in the actual license text, and that may be what is upsetting. (Martin did that with nanomsg. I never place trademark information in license files -- that information belongs on printed matter where the name is actually used. So, if you look at nng, I think you will find that it does not include the trademark notice on anything except some of the documentation files.)

I would be amenable to ripping off the trademark statement from the license statements. At present I own the trademark, so I think it would be ok for me to make that decision, even for files that Martin originally authored.

If the savannah people have more questions about this, or advice on how to proceed, please let me know. My main goal in the licensing is to make sure that there are as few barriers to use of nanomsg and nng as possible, and if this trademark statement is creating a barrier, that was assuredly never the intent.
==========
Please let me know what I can pass back to gdamore regarding addressing your concerns about the trademark of nanomsg.

Thanks.

Matthew Welland <kiatoa>
Mon 19 Feb 2018 06:43:35 PM UTC, comment #7:

Hi Ineiev,

I posted a request to the nanomsg team requesting that they clarify the use of the trademark. The author of the code has requested clarification. You can see the discussion here: https://github.com/nanomsg/nng/issues/239

I will cross-post the URLs to these two discussion threads in the hope of converging on a good solution.

Thanks for your patience in this.

Matthew Welland <kiatoa>
Mon 19 Feb 2018 05:23:33 PM UTC, comment #6:

Unfortunately, I've never programmed any low-level networking, so I hardly can suggest a replacement for nanomsg.

I see no point in re-opening this submission until all issues are resolved.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 19 Feb 2018 04:13:33 PM UTC, comment #5:

Adding tar of Megatest code with licence headers fixed and updated COPYING file.

(file #43361)

Matthew Welland <kiatoa>
Mon 19 Feb 2018 04:45:36 AM UTC, comment #4:

Sorry, I have made most of the changes (still a little more cleanup to do). Please consider reopening this, I'll be ready in a few days (very busy with the day job!). Can you suggest an alternative to nanomsg? It does seem that the nanomsg project has had some troubles.

Matthew Welland <kiatoa>
Mon 12 Feb 2018 08:54:31 AM UTC, comment #3:

No response; cancelling

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sun 04 Feb 2018 03:08:28 PM UTC, comment #2:

If there is no further interest, I'll cancel your submission.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 30 Jan 2018 10:24:40 AM UTC, comment #1:

Hello, Matthew!

There is some concern about nanomsg: its license text says its name is trademarked, without stating a trademark policy. Trademarks may render software proprietary.

Then, your license messages are not quite unambiguous, please use the form recommended in the GPL HowTo; also, please make sure that all copyrightable files in your tarball have valid copyright and license notice.

By the way, if you actually submit a tarball rather than an URL of a web interface to your VCS, it will make evaluation much easier.

Thank you!

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 29 Jan 2018 07:30:54 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: Megatest
  • System Name: megatest
  • Type: non-GNU software and documentation
  • License: GNU General Public License v2 or later

Description:

Megatest is a command-line, gui and web system for running and controlling large regression, functional testsuites and or general automation.

Megatest is written in Chicken Scheme and is actively in use inside a large computer hardware company to run 1000's of tests, 1000's of runs in a large compute farm. Megatest does not need a central database and can be considered to be distributed. All configuration is done in plain text files.

Other Software Required:

Chicken Scheme, BSD: https://www.call-cc.org/
IUP, MIT: http://webserver2.tecgraf.puc-rio.br/iup/
nanomsg, MIT: http://nanomsg.org/
sqlite3, public domain: https://www.sqlite.org

Tarball URL:

http://www.kiatoa.com/fossils/megatest?r=v1.65

Matthew Welland <kiatoa>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #43386:  megatest.tar.gz added by kiatoa (415KiB - application/gzip - Removed all extraneous files trying to get the tar small enough to upload. License headers are fixed.)
file #43361:  megatest.tar.gz added by kiatoa (1MiB - application/gzip - Megatest submission with requested fixes to license headers fixed.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by kiatoa (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.

     

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

     

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-02-23 kiatoa Attached File- => Added megatest.tar.gz, #43386
    2018-02-21 ineiev StatusCancelled => In Progress
        Open/ClosedClosed => Open
    2018-02-19 kiatoa Attached File- => Added megatest.tar.gz, #43361
    2018-02-12 ineiev StatusIn Progress => Cancelled
        Open/ClosedOpen => Closed
    2018-01-30 ineiev StatusNone => In Progress
        Assigned toNone => ineiev

    Back to the top


    Powered by Savane 3.3