taskSavannah Administration - Tasks: task #15466, Submission of RCscope

 
 

task #15466: Submission of RCscope

Submitter:  Vladimir Sedach <vsedach>
Submitted:  Fri 15 Nov 2019 04:36:15 AM UTC
   
 
Should Start On:  Fri 15 Nov 2019 12:00:00 AM UTC Should be Finished on:  Mon 25 Nov 2019 12: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

Thu 05 Dec 2019 11:51:24 AM UTC, comment #11: 

Thank you, aproving.

Ineiev <ineiev>
Site Administrator
Wed 04 Dec 2019 04:12:19 AM UTC, comment #10: 

Alright. Is there anything else I need to do to make RCscope conform to Savannah guidelines? I think everything is in order now.

Vladimir Sedach <vsedach>
Tue 26 Nov 2019 10:54:40 AM UTC, comment #9: 

comment #8:

> I think so, because most project README files I see do not have copyright notices (including several projects I looked at that were hosted on Savannah, to see examples I could follow),


The actual practices don't override the requirements; on the contrary, the requirements are written to regulate the practices.

If you see that some copyrightable files miss copyright or license notices in a package hosted on Savannah, this is a bug in that package; please ask its admins fix that.

> When https://savannah.gnu.org/maintenance/ValidNotices/ states that "For copyright purpose, any file more than ten lines long is nontrivial, so it should have copyright and license notices," the literal interpretation would mean that the file COPYING would need a project copyright notice, which clearly does not make sense.


And in particular, the file COPYING does need a copyright notice. (I'm not quite sure what you mean by "project copyright notice". What the documentation discusses is valid copyright and license notices.)

Ineiev <ineiev>
Site Administrator
Mon 25 Nov 2019 07:11:09 PM UTC, comment #8: 

I think so, because most project README files I see do not have copyright notices (including several projects I looked at that were hosted on Savannah, to see examples I could follow), and I suspect many people have the misconception as I did. When https://savannah.gnu.org/maintenance/ValidNotices/ states that "For copyright purpose, any file more than ten lines long is nontrivial, so it should have copyright and license notices," the literal interpretation would mean that the file COPYING would need a project copyright notice, which clearly does not make sense. I think a lot of people think the same about README. That is what I thought.

Vladimir Sedach <vsedach>
Sun 24 Nov 2019 10:03:22 AM UTC, comment #7: 

It wouldn't be feasible to explicitly mention all possible file names; is 'README' a specific name that needs a note?

Ineiev <ineiev>
Site Administrator
Sat 23 Nov 2019 09:25:35 PM UTC, comment #6: 

Ok, I added the copyright and license notice to the README file. https://savannah.gnu.org/maintenance/ValidNotices/ only mentions README in the context of "If some of your files cannot carry such notices," and this is not something I see in the majority of project README files, so it is not something I thought of doing. https://savannah.gnu.org/maintenance/ValidNotices/ should be updated to explicitly point this out.

https://oneofus.la/files/rcscope.tar.gz

Vladimir Sedach <vsedach>
Sat 23 Nov 2019 01:03:48 PM UTC, comment #5: 

README still has no copyright and license notices.

We rely on package admins to maintain proper copyright status of their packages.  If you can't do that, we'd better not register your package on Savannah.

Ineiev <ineiev>
Site Administrator
Tue 19 Nov 2019 07:09:58 PM UTC, comment #4: 

Ok, I have corrected the copyright notices. The updates can be found at the same URL: https://oneofus.la/files/rcscope.tar.gz

Thank you for your diligent feedback. I find it easy to overlook these things.

Vladimir Sedach <vsedach>
Mon 18 Nov 2019 06:21:25 AM UTC, comment #3: 

The copyright notice in rcscope.el has a form that doesn't match the recommendations.

It doesn't matter if the file is "source" or not; all copyrightable files should have the notices.

Ineiev <ineiev>
Site Administrator
Fri 15 Nov 2019 09:27:12 PM UTC, comment #2: 

Ok, I corrected the issue (the file LICENSE containing the text of the GPL renamed to COPYING as per the guidelines). The only source file in the project, rcscope.el, has a dated copyright notice with author information, and a GPL license notice, in the comments at the top of the file, which I believe to be correct. Please let me know if there is anything else that needs to be fixed.

The updated archive file is available at the same URL:
https://oneofus.la/files/rcscope.tar.gz

Vladimir Sedach <vsedach>
Fri 15 Nov 2019 06:39:03 AM UTC, comment #1: 

Please be sure to add valid copyright and license notices to all copyrightable files in your tarball.

Ineiev <ineiev>
Site Administrator
Fri 15 Nov 2019 04:36:15 AM 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: RCscope
  • System Name:  rcscope
  • Type: non-GNU software and documentation
  • License: GNU General Public License v3 or later





Description:

RCscope is Cscope interface for the GNU Emacs 25 era.

RCscope follows GNU Emacs `compilation-mode' and `occur-mode'
conventions. Output is displayed in a format similar to
`multi-occur'. Query results can be navigated using
`next-error'/`previous-error', just like `grep' and `occur'
searches.

RCscope automatically manages Cscope index files and index updates
(using projectile.el and the -R Cscope option), and uses persistent
Cscope processes that also support working on remote projects with
TRAMP.

In addition to standard Cscope queries, RCscope also provides a
tree visualization of a function's callers in a format similar to
Steve Baker's Tree directory listing utility.


Other Software Required:

GNU Emacs GPLv3 or later https://www.gnu.org/software/emacs/

Cscope BSD http://cscope.sourceforge.net/

expand-region.el GPLv3 or later https://github.com/magnars/expand-region.el

projectile.el GPLv3 or later https://github.com/bbatsov/projectile




Other Comments:

Currently RCscope is available from https://github.com/vsedach/rcscope

I would like to delete that repository, and make the project available on Savannah.


Tarball URL:

https://oneofus.la/files/rcscope.tar.gz


Vladimir Sedach <vsedach>

 

(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 ineiev (Posted a comment)
  • -email is unavailable- added by vsedach (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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-12-05 ineiev StatusIn Progress Done
        Open/ClosedOpen Closed
    2019-11-15 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code