[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2019-06-16 Thread Ineiev
Update of task #14968 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #28:

Approving. Sorry for so long delay.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-11-12 Thread JoaquínCuéllar
Follow-up Comment #27, task #14968 (project administration):

Hi!

any news?

cheers,
Joa

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-20 Thread JoaquínCuéllar
Follow-up Comment #26, task #14968 (project administration):

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)
___

Additional Item Attachment:

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-20 Thread Ineiev
Follow-up Comment #25, task #14968 (project administration):

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?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-19 Thread JoaquínCuéllar
Follow-up Comment #24, task #14968 (project administration):

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)
___

Additional Item Attachment:

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-19 Thread Ineiev
Follow-up Comment #23, task #14968 (project administration):

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.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-16 Thread JoaquínCuéllar
Follow-up Comment #22, task #14968 (project administration):

Hello Ineiev!

As I already asked:

So what lacks this project to be registered? 

thanks!
happy Hacking
Joa

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-15 Thread Ineiev
Follow-up Comment #21, task #14968 (project administration):

Hello, Joaquín!

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-13 Thread JoaquínCuéllar
Follow-up Comment #20, task #14968 (project administration):

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! 

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-13 Thread Ineiev
Follow-up Comment #19, task #14968 (project administration):

This task depends on sr #109527.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-12 Thread JoaquínCuéllar
Follow-up Comment #18, task #14968 (project administration):

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-12 Thread Ineiev
Follow-up Comment #17, task #14968 (project administration):

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-11 Thread JoaquínCuéllar
Follow-up Comment #16, task #14968 (project administration):

> 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!


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-10 Thread Ineiev
Follow-up Comment #15, task #14968 (project administration):

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.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-10 Thread JoaquínCuéllar
Follow-up Comment #14, task #14968 (project administration):

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-10 Thread JoaquínCuéllar
Additional Item Attachment, task #14968 (project administration):

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-10 Thread Ineiev
Follow-up Comment #13, task #14968 (project administration):

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.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-03 Thread JoaquínCuéllar
Follow-up Comment #12, task #14968 (project administration):

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



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-02 Thread Ineiev
Follow-up Comment #11, task #14968 (project administration):

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-01 Thread JoaquínCuéllar
Follow-up Comment #10, task #14968 (project administration):

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)
___

Additional Item Attachment:

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-07-01 Thread Ineiev
Follow-up Comment #9, task #14968 (project administration):

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.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-30 Thread JoaquínCuéllar
Follow-up Comment #8, task #14968 (project administration):

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)
___

Additional Item Attachment:

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-27 Thread JoaquínCuéllar
Follow-up Comment #7, task #14968 (project administration):

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 




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-27 Thread Ineiev
Follow-up Comment #6, task #14968 (project administration):

> 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).

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-26 Thread JoaquínCuéllar
Follow-up Comment #5, task #14968 (project administration):

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? 

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-26 Thread JoaquínCuéllar
Additional Item Attachment, task #14968 (project administration):

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-26 Thread Ineiev
Follow-up Comment #4, task #14968 (project administration):

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.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-24 Thread anonymous
Additional Item Attachment, task #14968 (project administration):

File name: GSResolver.tar.gz  Size:20 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-23 Thread Ineiev
Follow-up Comment #3, task #14968 (project administration):

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-22 Thread JoaquínCuéllar
Follow-up Comment #2, task #14968 (project administration):

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

thanks!
Joa

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-22 Thread JoaquínCuéllar
Additional Item Attachment, task #14968 (project administration):

File name: GSResolver.tar.gz  Size:26 KB


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-20 Thread Ineiev
Update of task #14968 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

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

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

2018-06-19 Thread JoaquínCuéllar
URL:
  

 Summary: Submission of Gentooza's Sudokus Resolver
 Project: Savannah Administration
Submitted by: 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: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= 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






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/