taskSavannah Administration - Tasks: task #15939, Submission of...

 
 

task #15939: Submission of Perl::PrereqScanner::Scanner::DistZilla::PluginBundle

Submitted by:  Asher Gordon <asdago>
Submitted on:  Sat 10 Apr 2021 05:53:49 PM UTC  
 
Should Start On:  Sat 10 Apr 2021 04:00:00 AM UTC Should be Finished on:  Tue 20 Apr 2021 04:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Ineiev <ineiev>
Open/Closed:  Closed 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)

Mon 26 Apr 2021 08:27:42 AM UTC, comment #6: 

Thank you, approving.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 22 Apr 2021 05:47:19 PM UTC, comment #5: 

comment #4:

> comment #1:
> > However, if anyone else makes a release, it will have the wrong identifier "GPL-3.0-only".
>
> This is confusing. Probably you would be better off if you didn't use this feature.


Well, I'm not sure if it's actually possible to disable this feature (at least not without some hacks). If it's really necessary, I can ask on #distzilla. The only case where anyone else would be making a release is probably just for their own testing purposes. The tarballs that I will release on CPAN will all have the correct identifier.

> Manuals should be licensed in a way compatible with the GFDL.  Whether the inline documentation qualifies as a manual---it depends on the contents of that documentation. For this case, I think the documentation is short enough, so it's OK to release it just under the GPL.


Ok, great.

> > (Incidentally, the license notices for BoBot claim that it is part of the GNU project, but the Savannah project page states otherwise.)
>
> This should be fixed. Please contact the developers.


I reported that here.

> Do your other packages registered on Savannah have these issues?


No, this is the first project I'm releasing that uses Dist::Zilla. I am planning on releasing a few more, though, so I'll fix these issues with them before submitting.

Asher Gordon <asdago>
Thu 22 Apr 2021 09:59:06 AM UTC, comment #4: 

comment #1:

> However, if anyone else makes a release, it will have the wrong identifier "GPL-3.0-only".


This is confusing. Probably you would be better off if you didn't use this feature.

comment #3:

>
> Also, another thing I just thought of: The documentation is under the same license as the rest of the project (GPLv3+), which is incompatible with the GFDL. But the documentation is inline with the code (POD), so does this matter? It would be kind of a pain to specify different licensing terms for different things in the same file.
>
> I found [https://savannah.nongnu.org/projects/bobot another

...

>line 131).


Manuals should be licensed in a way compatible with the GFDL.  Whether the inline documentation qualifies as a manual---it depends on the contents of that documentation. For this case, I think the documentation is short enough, so it's OK to release it just under the GPL.

> (Incidentally, the license notices for BoBot claim that it is part of the GNU project, but the Savannah project page states otherwise.)


This should be fixed. Please contact the developers.

Do your other packages registered on Savannah have these issues?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 19 Apr 2021 10:03:41 PM UTC, comment #3: 

Hi. Not to rush, but any chance this could be accepted soon? I believe it follows all hosting requirements, and please let me know if it doesn't so I can fix it. Thanks!

Also, another thing I just thought of: The documentation is under the same license as the rest of the project (GPLv3+), which is incompatible with the GFDL. But the documentation is inline with the code (POD), so does this matter? It would be kind of a pain to specify different licensing terms for different things in the same file.

I found another project on Savannah, BoBot, that is licensed under GPLv2+ and that has POD documentation. For example, see this file (beginning of POD at line 131). So it would seem that GPL licensed POD is not an issue then? (Incidentally, the license notices for BoBot claim that it is part of the GNU project, but the Savannah project page states otherwise.)

Asher Gordon <asdago>
Sat 17 Apr 2021 05:14:53 PM UTC, comment #2: 

Hello. It seems that I forgot to add a license notice to .gitignore. I guess GNU All-Permissive is good for this file too, since it's so small?

Please see the attached tarball (contains only the development directory).

(file #51281)

Asher Gordon <asdago>
Sat 10 Apr 2021 06:03:15 PM UTC, comment #1: 

Oh, also, another thing I forgot to mention: Software::License::GPL_3::or_later has a bug where it returns, for the SPDX identifier, "GPL-3.0-only" (inherited from Software::License::GPL_3) rather than the correct "GPL-3.0-or-later". I fixed this bug and reported it here (with a patch), but it hasn't been accepted yet. My installation of Software::License::OrLaterPack has my fix applied, so any releases I make will have the correct SPDX identifier in META.json and META.yml. However, if anyone else makes a release, it will have the wrong identifier "GPL-3.0-only".

Not sure if that's relevant, but I thought I'd mention it.

Asher Gordon <asdago>
Sat 10 Apr 2021 05:53:49 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: Perl::PrereqScanner::Scanner::DistZilla::PluginBundle
  • System Name:  bundle-scanner
  • Type: non-GNU software and documentation
  • License: GNU General Public License v3 or later (I've licensed supporting files (Changes, dist.ini) under the GNU All-Permissive license. Does that make sense for these files, or would it be better to license them under GPLv3+ like the whole?)

Description:

This is a prerequisite scanner plugin for Perl::PrereqScanner. It is designed to scan plugin bundles for Dist::Zilla and Pod::Weaver, and detect any required plugins or plugin bundles (or Pod::Weaver sections).

Other Software Required:

Configure (build) dependencies:

    Name: ExtUtils::MakeMaker
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/ExtUtils::MakeMaker

Development dependencies:

    Name: Test::Pod
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Test::Pod

    Name: Dist::Zilla::PluginBundle::Author::ASDAGO
    License: GPLv3+
    Not released yet, but I will submit it to Savannah after this project gets accepted.

Runtime dependencies:

    Name: Moose
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Moose

    Name: Perl::PrereqScanner::Scanner
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Perl::PrereqScanner::Scanner

    Name: Pod::Weaver::Config::Assembler
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Pod::Weaver::Config::Assembler

    Name: namespace::autoclean
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/namespace::autoclean

    Name: perl
    License: GPLv1+ or the Artistic License
    Website: https://dev.perl.org/perl5/

Testing dependencies:

    Name: Perl::PrereqScanner
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Perl::PrereqScanner

    Name: Test::More
    License: GPLv1+ or the Artistic License
    Website: https://metacpan.org/pod/Test::More

See also Perl-PrereqScanner-Scanner-DistZilla-PluginBundle/release/META.{json,yml}.

Other Comments:

The attached tarball contains two directories under the root directory: development and release. The development directory contains what will go in the git repository, whereas the release directory contains what will go in the release tarball (built by 'dzil build', and what I will release on CPAN.

Also, the LICENSE file in the release is automatically built using Software::License::GPL_3::or_later. However, a LICENSE (or COPYING) file is also required even in the git repository, correct? So I also added a LICENSE in the development directory. Note that this LICENSE does not include a copyright and license notice, whereas the release version does (because this is how Dist::Zilla and Software::License::GPL_3::or_later do it by default).

I'm also going to release two more similar projects, but they will likely have similar issues to this one (if any), so I will wait until this project is accepted to submit my other ones. Should I also include the release directory in the other two like I did for this one?

Finally, for the system name I was going to do the full name with "::" replaced by "-", but the system didn't like that (presumably because it was too long). Then I was going to use "plugin-bundle-scanner", but that didn't work either. So instead, I went with "bundle-scanner". Is that an acceptable system name for this project? It's not that descriptive (doesn't even mention Perl or Dist::Zilla or even plugins or prerequisites), but the full name is descriptive, of course.

Tarball URL:

https://savannah.nongnu.org/submissions_uploads/Perl-PrereqScanner-Scanner-DistZilla-PluginBundle.tar.gz

Asher Gordon <asdago>

 

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

Attach Files:
   
   
Comment:
   

Attached Files

 

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 asdago (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.

     

     

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-04-26 ineiev StatusIn Progress => Done
        Open/ClosedOpen => Closed
    2021-04-22 ineiev StatusNone => In Progress
        Assigned toNone => ineiev
    2021-04-17 asdago Attached File- => Added Perl-PrereqScanner-Scanner-DistZilla-PluginBundle.tar.gz, #51281

    Back to the top


    Powered by Savane 3.6