taskSavannah Administration - Tasks: task #14444, Submission of Memcopy

 
 

task #14444: Submission of Memcopy

Submitter:  Jared (Yerida) Ryan Bills <jbills>
Submitted:  Tue 04 Apr 2017 10:33:21 PM UTC
   
 
Should Start On:  Tue 04 Apr 2017 07:00:00 AM UTC Should be Finished on:  Fri 14 Apr 2017 07:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  ineiev Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 14 Apr 2017 06:31:37 AM UTC, comment #15: 

You can use CVS or enable other version control systems in group settings.

For further info, please see Savannah documentation,
https://savannah.nongnu.org/userguide/
https://savannah.gnu.org/maintenance/FrontPage/

Ineiev <ineiev>
Site Administrator
Thu 13 Apr 2017 10:22:00 PM UTC, comment #14: 

Hello Pavel. I see that the project is added to the list of projects, but I can not see any source code for it. I am unsure of how to upload patches to the source code as well, in case I have to re-upload the source on the project page.

Jared (Yerida) Ryan Bills <jbills>
Wed 12 Apr 2017 01:17:53 PM UTC, comment #13: 

Thank you, approving.

Ineiev <ineiev>
Site Administrator
Tue 11 Apr 2017 02:36:16 PM UTC, comment #12: 

Right, well the GNU website mentioned that you only have to put the notices in files longer than 10 lines. But anyways I'll still put notices on files such as these if asked because I just want the project hosted. Is it good enough to be hosted on savannah now?

Jared (Yerida) Ryan Bills <jbills>
Tue 11 Apr 2017 07:51:43 AM UTC, comment #11: 

In order to correctly license the program, you should put valid notices in every file of its distribution. This is not my liking, this is a policy of the GNU project and Savannah.

We generally rely on the maintainers following our policies, we have no dedicated volunteers to regularly check the compliance; on the other hand, once the package is registered on Savannah, it's hard to remove it.

So, if you don't feel like being committed to maintain such things as correct notices or having no GPL-incompatible dependencies, we'd better not register your package at all.

Ineiev <ineiev>
Site Administrator
Mon 10 Apr 2017 12:05:02 PM UTC, comment #10: 

Okay I also put a notice inside the README. But I figured as long as the program itself was correctly licensed and notice provided I wouldn't have to do that to the README. Now I hope everything is to your liking and I can finally submit the library.

(file #40347)

Jared (Yerida) Ryan Bills <jbills>
Mon 10 Apr 2017 06:58:50 AM UTC, comment #9: 

Thank you; all files should have valid copyright and license notices; README doesn't. Also, README should mention that the package may be distributed under LGPLv3 and later licenses.

Ineiev <ineiev>
Site Administrator
Sun 09 Apr 2017 09:23:09 AM UTC, comment #8: 

All right I made the significant changes. Just let me know if something doesn't look right.

(file #40337)

Jared (Yerida) Ryan Bills <jbills>
Sun 09 Apr 2017 05:38:22 AM UTC, comment #7: 

The LGPLv3 is designed as a set of additional permissions on top of the GPLv3, and it requires that redistributors provide both texts of the LGPL and the GPL with the package in question.

There is another issue: nothing in your sources explicitly says that the user may use them under later versions of the LGPL (if she can't, the package doesn't comply with Savannah requirements); please use statements from https://www.gnu.org/licenses/gpl-howto.html

Also, I strongly recommend using unmodified texts from https://www.gnu.org/licenses/lgpl-3.0.txt and https://www.gnu.org/licenses/gpl-3.0.txt

Thank you!

Ineiev <ineiev>
Site Administrator
Sat 08 Apr 2017 01:23:56 PM UTC, comment #6: 

I don't disagree. What's your point?

Jared (Yerida) Ryan Bills <jbills>
Sat 08 Apr 2017 08:02:19 AM UTC, comment #5: 

Please excuse me.

I think that when somebody provides a free program subject to certain terms and conditions, that person should be aware of what those conditions are, and follow them when distributing it.

Do you disagree?

Ineiev <ineiev>
Site Administrator
Fri 07 Apr 2017 09:46:11 PM UTC, comment #4: 

Okay. Attached should be the modified files which have license notices in the header. Removed the BSD license from the file altogether.

(file #40325)

Jared (Yerida) Ryan Bills <jbills>
Fri 07 Apr 2017 11:46:33 AM UTC, comment #3: 

So, I assume it's LGPL-licensed; then please make sure your tarball has all necessary authentic license texts as well as copyright and license notices.

Ineiev <ineiev>
Site Administrator
Fri 07 Apr 2017 07:08:28 AM UTC, comment #2: 

Well it was released in BSD before LGPL. I figure I might as well switch the license to pure LGPL for any future improvements.

Jared (Yerida) Ryan Bills <jbills>
Thu 06 Apr 2017 04:49:04 PM UTC, comment #1: 

But what is the point in releasing it under the LGPL if it's available under a lax permissive license?

Ineiev <ineiev>
Site Administrator
Tue 04 Apr 2017 10:33:21 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: Memcopy
  • System Name:  memcopy
  • Type: non-GNU software and documentation
  • License: GNU Lesser General Public License (Copyright (c) 2015-2017, Jared Ryan Bills

All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this

  list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice,

  this list of conditions and the following disclaimer in the documentation
  and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.)




Description:

An alternative to memcpy. I was experimenting and with some improvement I think it could be useful.


Other Software Required:

GNU standard C Library
LGPL v2.1+
https://www.gnu.org/software/libc/


Other Comments:

Is alternatively licensed with BSD 2-clause license for the time being. Future revisions may only use one if strategy permits. I'm hoping for the code to influence development of the GNU standard C library.


Tarball URL:

https://savannah.gnu.org/submissions_uploads/memcopy.tar.gz


Jared (Yerida) Ryan Bills <jbills>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #40347:  memcopy.tar.gz added by jbills (16KiB - application/gzip - Put copyright and license notice within the README file.)
file #40337:  memcopy.tar.gz added by jbills (16KiB - application/gzip - Updated files with actual proper copyright and license notices and an included README.)
file #40325:  memcopy.tar.gz added by jbills (4KiB - application/gzip - Updated files to be adequately licensed with correct notices.)

 

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 jbills (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 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-04-12 ineiev StatusIn Progress Done
        Open/ClosedOpen Closed
    2017-04-10 jbills Attached File- Added memcopy.tar.gz, #40347
    2017-04-09 jbills Attached File- Added memcopy.tar.gz, #40337
    2017-04-07 jbills Attached File- Added memcopy.tar.gz, #40325
    2017-04-06 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code