[Savannah-register-public] [task #14832] Submission of Megatest

Update of task #14832 (project administration): Status: In Progress => Cancelled Open/Closed:Open => Closed ___ Follow-up Comment #41:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #40, task #14832 (project administration): If there is no further interest, I'll cancel this submission. ___ Reply to this item at: ___

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #39, task #14832 (project administration): I'm sorry, I made you misunderstand me. My point was: all files should have the notices, not just PDF files. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #38, task #14832 (project administration): 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.

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #37, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #36, task #14832 (project administration): By "editable" I meant text based files editable by a text editor. Thus graphic files such as png, svg and pdf would be excluded. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #35, task #14832 (project administration): What do you mean by "editable" file? All files should have notices, no matter text or non-text. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #34, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #33, task #14832 (project administration): Please comment on tests/unittests/cron.scm: as far as I can see, it still lacks the notices. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #32, task #14832 (project administration): 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.

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #31, task #14832 (project administration): > 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #30, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #29, task #14832 (project administration): > 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. >

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #28, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #27, task #14832 (project administration): > 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #26, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #24, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #23, task #14832 (project administration): > 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #22, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #21, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #20, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #19, task #14832 (project administration): Is this really what you are going to distribute? What are "extraneous files"? ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #18, task #14832 (project administration): I trimmed out extraneous files and was able to get a .tar.gz to load. Please take a look. Thanks. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Additional Item Attachment, task #14832 (project administration): File name: megatest.tar.gzSize:415 KB ___ Reply to this item at: ___

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #17, task #14832 (project administration): Thank you, there are too many files. Please provide a tarball. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #16, task #14832 (project administration): 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. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #15, task #14832 (project administration): Added new tar file. ___ Reply to this item at: ___ Message sent via/by Savannah

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #14, task #14832 (project administration): Headers fixed. ___ Reply to this item at: ___ Message sent via/by Savannah

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #13, task #14832 (project administration): Sorry, in the latest tarball, the COPYING seems correct; some license headers weren't. ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #12, task #14832 (project administration): 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? ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #11, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Update of task #14832 (project administration): Status: Cancelled => In Progress Open/Closed: Closed => Open ___ Follow-up Comment #10: > Does

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #9, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #8, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #7, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #6, task #14832 (project administration): 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.

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #5, task #14832 (project administration): Adding tar of Megatest code with licence headers fixed and updated COPYING file. (file #43361) ___ Additional Item Attachment: File name: megatest.tar.gzSize:1516

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #4, task #14832 (project administration): 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

[Savannah-register-public] [task #14832] Submission of Megatest

Update of task #14832 (project administration): Status: In Progress => Cancelled Open/Closed:Open => Closed ___ Follow-up Comment #3: No

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #2, task #14832 (project administration): If there is no further interest, I'll cancel your submission. ___ Reply to this item at: ___

[Savannah-register-public] [task #14832] Submission of Megatest

Update of task #14832 (project administration): Status:None => In Progress Assigned to:None => ineiev ___ Reply to this item at:

[Savannah-register-public] [task #14832] Submission of Megatest

Follow-up Comment #1, task #14832 (project administration): 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,

[Savannah-register-public] [task #14832] Submission of Megatest

URL: Summary: Submission of Megatest Project: Savannah Administration Submitted by: kiatoa Submitted on: Mon 29 Jan 2018 07:30:54 PM UTC Should Start On: Mon 29 Jan 2018 12:00:00 AM UTC