taskSavannah Administration - Tasks: task #14968, Submission of Gentooza's Sudokus...

 
 

task #14968: Submission of Gentooza's Sudokus Resolver

Submitted by:  Joaquín Cuéllar <gentooza>
Submitted on:  Tue 19 Jun 2018 08:44:41 AM UTC  
 
Should Start On:  Tue 19 Jun 2018 12:00:00 AM UTC Should be Finished on:  Fri 29 Jun 2018 12: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)

Sun 16 Jun 2019 05:00:21 PM UTC, comment #28: 

Approving. Sorry for so long delay.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 12 Nov 2018 12:59:00 PM UTC, comment #27: 

Hi!

any news?

cheers,
Joa

Joaquín Cuéllar <gentooza>
Fri 20 Jul 2018 08:46:56 AM UTC, comment #26: 

Hi Ineiev!

fixed! the license header was wrong so it had to be corrected in ALL files.

> All are many. (comment #6)


No they aren't. And this makes communication more difficult

http://www.wordreference.com/enru/many
https://www.wordreference.com/enru/all

But no homeworks, only explanations ;-)

happy hacking

(file #44601)

Joaquín Cuéllar <gentooza>
Fri 20 Jul 2018 08:30:24 AM UTC, comment #25: 

Hello, Joa!

Many files in your tarball say,

You should have received a copy of the GNU General Public License
along with Foobar.

What has Foobar to do with GSResolver?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 19 Jul 2018 12:51:27 PM UTC, comment #24: 

Hi Ineiev!

- ok, remade the copyright notice

- I didn't know the README should have a full license notice! I thought it had only to show the program license.
Added a full license notice.
(also it was bad redirecting to COPYING for license notice, when it's the license full text. Removed)

- Terrible mistake, and good point the Linux vs GNU/Linux text. fixed

is it done?

happy hacking!
Joa

(file #44593)

Joaquín Cuéllar <gentooza>
Thu 19 Jul 2018 12:36:00 PM UTC, comment #23: 

Hello, Joa;

Your README.md file still lacks a valid copyright notice; the "license notice" is also too vague, it confusingly says that COPYING contains the license notice rather than a copy of the license.

Then, your package refers to the GNU/Linux operating system as "Linux". Savannah is the forge of the GNU project, and we require that packages hosted here give due credit to us.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 16 Jul 2018 07:41:46 AM UTC, comment #22: 

Hello Ineiev!

As I already asked:

So what lacks this project to be registered?

thanks!
happy Hacking
Joa

Joaquín Cuéllar <gentooza>
Sun 15 Jul 2018 07:32:29 AM UTC, comment #21: 

Hello, Joaquín!

I have read the CoC; why do you point at it?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 13 Jul 2018 05:01:25 PM UTC, comment #20: 

Hi!

well

I don't know if you have ever read this:

http://savannah.gnu.org/maintenance/CodeOfConduct/

I don't think the submission of this project depends of a issue you've just created in other.

I think is a strange coercing way of doing things.

So what lacks this project to be registered?

happy hacking!

Joaquín Cuéllar <gentooza>
Fri 13 Jul 2018 04:49:33 PM UTC, comment #19: 

This task depends on sr #109527.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Thu 12 Jul 2018 06:13:00 PM UTC, comment #18: 

Cool, Perfect!

And I'll listen them carefully but in another task as I already said.

Could we focus in the submission this task was opened for?

Happy Hacking

Joaquín Cuéllar <gentooza>
Thu 12 Jul 2018 05:41:35 PM UTC, comment #17: 

Dear Joaquín,

I could submit patches, but I don't think you'd really like them; besides that, the objective is to teach the maintainers (that is, you) how to follow Savannah hosting requirements, and no patches from occasional contributors can help with that task.

I believe my words were exact. Please listen to them.

Yours truly,
  Ineiev

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 11 Jul 2018 06:19:14 PM UTC, comment #16: 

> So, let me be didactic. (...)


Hi!

thanks for your interest in the project!

Feel free to open a task in it's proper place or provide a patch to improve the project, it's free-libre software so my work is yours, and of the whole world.

Please, try not to be rude, and be exact in your words to be efficient in accomplishing the community objectives.

thanks again and happy hacking!

Joaquín Cuéllar <gentooza>
Tue 10 Jul 2018 05:25:52 PM UTC, comment #15: 

So, let me be didactic.

This is a homework for you:

Carefully read Savannah hosting requirements. Visit your first Savannah project and evaluate it against them. Summarize the work done and the results for each criterion.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 10 Jul 2018 08:32:15 AM UTC, comment #14: 

I forgot the file! sorry

> No, you won't. The maintainers have to keep the things right within their project themselves, they can't rely on Savannah admins to do that.


I prefer more than rely, share knowledge, ask for advice, receive a didactic focus ... What we FSF lovers want (opposite to Open Source for example) COMMUNITY.

> By the way, since you mentioned your earlier projects, I suggest that you should also check them and bring in compliance if needed.


Well, if you have proposals to improve (As I'm sure you have lot of knowledge) I'm open to adopt them, but please, no menaces here.

happy hacking

Joaquín Cuéllar <gentooza>
Tue 10 Jul 2018 07:37:45 AM UTC, comment #13: 

Hello,

Please attach the new file.

> If I'm not capable I won't be able to register my project?


No, you won't. The maintainers have to keep the things right within their project themselves, they can't rely on Savannah admins to do that.

By the way, since you mentioned your earlier projects, I suggest that you should also check them and bring in compliance if needed.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 03 Jul 2018 10:12:41 AM UTC, comment #12: 

Hi

so...

#1- In **README.md** I have redirected the user to see the full license in **COPYING**

#2- I have removed **ROADMAP** as it seems the only file without license header

#3- well after more than 5 revisions I think there should be no doubt about my will, and if I'm finally not capable... Well, I feel I've not received any help at all from a supposed to be a Free Software advocate.

If I'm not capable I won't be able to register my project? I think it's a very impolite, ANTI-FSF movement, ANTI-community... answer. Indeed.

cheers, and happy hacking

Joaquín Cuéllar <gentooza>
Mon 02 Jul 2018 04:41:12 PM UTC, comment #11: 

> What I don't understand is why the license notice should be longer... but I see noting more.


The full notice contains additionally

  • the disclaimer; and
  • the instructions on where to get the text of the license.

It's important that the user is aware of such things. You can't take them for granted.

> examples as GCC, https://gcc.gnu.org/viewcvs/gcc/trunk/README?view=markup, it has no license notice, it directs you to COPYING files.


GCC has multiple licenses (and some exemptions), probably they have to do that for good reasons.

Some files in your tarball still lack notices. If you are not willing or unable to follow Savannah policies, we'd better not register your package.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sun 01 Jul 2018 11:52:49 AM UTC, comment #10: 

Hi Ineiev!

Added copyright statement in readme file.

What I don't understand is why the license notice should be longer, in (https://www.gnu.org/licenses/gpl-howto.html) only say that if readme file contains “This program is released under license FOO,” helps with the realease licence comprehension. but I see noting more.
examples as GCC, https://gcc.gnu.org/viewcvs/gcc/trunk/README?view=markup, it has no license notice, it directs you to COPYING files.

also added license header in changelog.md

cheers

(file #44474)

Joaquín Cuéllar <gentooza>
Sun 01 Jul 2018 09:36:55 AM UTC, comment #9: 

Hello, Joa!

README.md still lacks any copyright notice, please check https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

The recommended form of the license notice is longer:
https://www.gnu.org/licenses/gpl-howto.html

By the way, did you read https://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly/ ? I could describe it, but it's written better than I can.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sat 30 Jun 2018 04:22:26 PM UTC, comment #8: 

ok,

small license notice added at the end of the readme file, is it correct?
(authors added too by the way)

cheers
Joa

(file #44466)

Joaquín Cuéllar <gentooza>
Wed 27 Jun 2018 07:36:02 PM UTC, comment #7: 

I don't think a readme file has to have a copyright notice :-/
or at least, please, be a little more pedagogic (and nice happy life lover) and tell me exactly what you think it lacks? a copyright notice as a source file?

it's gonna really save your time and mine

Joaquín Cuéllar <gentooza>
Wed 27 Jun 2018 05:56:42 PM UTC, comment #6: 

> some files in my tarball lacking copyright notices are....?
> because I see no one


README.md, for example.

> many files have a wrong form of copyright notice are..?
> because they all have the same copyright notices


All are many.

> I've remade them with, what I think is, the canonical way.
> is it okay finally?


Yes, the copyright notices are OK (where they are present).

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 27 Jun 2018 06:28:57 AM UTC, comment #5: 

some files in my tarball lacking copyright notices are....?
because I see no one

many files have a wrong form of copyright notice are..?
because they all have the same copyright notices

:-S

I've remade them with, what I think is, the canonical way.
is it okay finally?

Joaquín Cuéllar <gentooza>
Wed 27 Jun 2018 05:46:04 AM UTC, comment #4: 

Some files in your tarball lack copyright notices; many files have a wrong form of copyright notice; please check our documentation on how they should look like.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sat 23 Jun 2018 12:39:06 PM UTC, comment #3: 

Please remove backup files created by your editor from your tarball, this looks impolite.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Fri 22 Jun 2018 08:07:06 AM UTC, comment #2: 

I've remade headers and changed them also in makefiles
Please, could you be more specific if it's already something wrong?

thanks!
Joa

Joaquín Cuéllar <gentooza>
Wed 20 Jun 2018 04:51:11 PM UTC, comment #1: 

Please make sure all files in your tarball have valid copyright and license notices.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Tue 19 Jun 2018 08:44:41 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: Gentooza's Sudokus Resolver
  • System Name:  gsresolver
  • Type: non-GNU software and documentation
  • License: GNU General Public License v3 or later

Description:

A C++ program to solve sudokus using different algorithms.
It's designed for learning purposes and get fun:
- using plugins model, by adding further algorithms easily as dynamic plugins.
- using a pattern design approach.
- working with basic terminal GUIs and I/O

Other Software Required:

N/A all standard in a GNU/Linux environment.

Other Comments:

thanks team!

Tarball URL:

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

Joaquín Cuéllar <gentooza>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #44601:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip - corrected copy/paste error in license header)
file #44593:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip - fixed README.md)
file #44531:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip)
file #44474:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip - changed authors to copyright in readme, changelog.md with license header)
file #44466:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip - license notice added to readme file)
file #44441:  GSResolver.tar.gz added by gentooza (21KiB - application/gzip - remade license notices)
file #44426:  GSResolver.tar.gz added by None (21KiB - application/gzip - backup files removed)
file #44411:  GSResolver.tar.gz added by gentooza (27KiB - application/gzip - ok, I've reamed headers and improve them in makefiles.)

 

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

    Date Changed by Updated Field Previous Value => Replaced by
    2019-06-16 ineiev StatusIn Progress => Done
        Open/ClosedOpen => Closed
    2018-07-20 gentooza Attached File- => Added GSResolver.tar.gz, #44601
    2018-07-19 gentooza Attached File- => Added GSResolver.tar.gz, #44593
    2018-07-19 ineiev DependenciesRemoved dependency to support #109527 => -
    2018-07-13 ineiev Dependencies- => Depends on support #109527
    2018-07-10 gentooza Attached File- => Added GSResolver.tar.gz, #44531
    2018-07-01 gentooza Attached File- => Added GSResolver.tar.gz, #44474
    2018-06-30 gentooza Attached File- => Added GSResolver.tar.gz, #44466
    2018-06-27 gentooza Attached File- => Added GSResolver.tar.gz, #44441
    2018-06-24 None Attached File- => Added GSResolver.tar.gz, #44426
    2018-06-22 gentooza Attached File- => Added GSResolver.tar.gz, #44411
    2018-06-20 ineiev StatusNone => In Progress
        Assigned toNone => ineiev

    Back to the top


    Powered by Savane 3.5