taskSavannah Administration - Tasks: task #4612, Submission of Project Gutenberg...

 
 

task #4612: Submission of Project Gutenberg Distributed Proofreade

Submitter:  Sébastien Blondeel <sbi>
Submitted:  Mon 05 Sep 2005 05:45:14 PM UTC
   
 
Should Start On:  Mon 05 Sep 2005 12:00:00 AM UTC Should be Finished on:  Thu 15 Sep 2005 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 24 Oct 2005 05:44:20 PM UTC, comment #12: 

Hello.

I reviewed your project today and I couldn't found any further problems. So we can close this tracker item.

Have fun with Savannah. :-)
Regards,

Sebastian Wieseler <kickino>
Thu 22 Sep 2005 03:12:53 PM UTC, comment #11: 

Answer to Question 1
--------------------

Greek: personal Perl module, not yet cleaned up and committed to the
CVS.

Roman: the standard Perl module. (not very important though)

Answer to Question 2
--------------------

I use many different Unix tools (X11 options, xterm, display, xzgv,
xmessage, Perl, libpng...) many of which may not work exactly the same
way in Windows, so I guess it won't be very easy to port to Windows. I
have no Windows and no experience with it.

Right now I guess the priority is to debug (I am debugging the
second-round mode now. It worked for me bug the CVS version is a merge
and a cleaned-up version of different programs so new bugs appeared) and
find other users :) And maybe collect comments, feature requests, etc.

Then, if one is fluent enough in Windows, maybe he can help me port it
to that system. That would be great.

Sébastien Blondeel <sbi>
Thu 22 Sep 2005 02:57:43 PM UTC, comment #10: 

Question 1:  When you say 'Greek' and 'Roman' in the Other Software Required List, are you speaking of Language Packs or are you speaking of Type Face Fonts? 

Question 2:  Are you planning to port to Windows?  I am asking out of professional curiosity.  Although I am a total SuSe Linux devotee, I realize that many professionals are still locked in to the Windows XP mode [ie-> The ITS people here at the institution where I work ordered me to take NOVELL SuSe Linux 9.x off of my office box, as it was "making the network vulnerable to viruses."  So, I work in XP with only one desktop and a lot of artifact clutter to deal with while I am at the office.] 

Have a great day.

Sincerely,

MG Stough


MG Stough <mgstough>
Tue 13 Sep 2005 05:20:19 PM UTC, comment #9: 

Hello.

Further mail is available on our mailing list (just for record).


I have approved your project for inclusion in Savannah.

We will be reviewing the cvs code in a month (or better at your request) to check if the source files contain appropriate copyright notice and permission-to-copy statements at the beginning of every file of source code.
Our review would help catch potential legal issues early.

You should get an automated email with more information shortly.

Regards and thanks for using Savannah ;)


Sebastian Wieseler <kickino>
Mon 12 Sep 2005 07:52:35 PM UTC, comment #8: 

Sébastien Blondeel <sbi> wrote per PM:
I must have misunderstood something about Savannah. Is it only for
finished and polished projects? There is a bootstrap problem then.

I am not planning to publish the project right away, just clean up my
private mess (developed at home over the years) and put it on a public
place with regular backups so I don't have to take care of the hosting +
bandwidth + etc. myself.

I found a beta-tester to help me comment the installation procedures:
http://www.pgdp.net/phpBB2/viewtopic.php?p=154856#154856
Another Distributed Proofreader is interested in my tools too.

Until the software is not officially "publicly released" it has no
status with respect to free or proprietary software: it is private
software.

Do you write a copyright statement first thing of all every time you
create a new file?

Sanity check: I am requesting the Savannah team for CVS write permission
on some place on their disks. If/when I have it, you will have to trust
me to not remove that legalese (I guess you don't keep looking all CVS
changes in order to catch that). If you trust me that much, you can
trust me to be able to include those things in the now-existing files.
If/when new files exist, I will have to think about it anyway.

The tarball I sent you will not be committed to the CVS as is. I will
need to remove the hardcoded paths in there, make it easier to install
for others, document things and algorithms used, explain what I did to
custom VIM behaviour for others to adapt it to their pet editor, etc.

You wrote in your first mail:
Please include a (perhaps temporary) URL pointing to the source code.
We wish to review your source code, even if it is not functional, [...]

> And because of tools/*:


What about tools? I can see only one file there in my disk:
Catalog_Extract.pl
Maybe it got into the tarball I sent you too. It it something different,
independent, I once did to help somebody on the gutvol-d mailing-list.

<-----------< End of quotation <-------------<

Hello.

| Is it only for finished and polished projects

We can also approve project without source code, but if you upload something in planning phase it has to valid with our policy, too.

We host free software projects and provide developer tools for the project maintainers and members.

But it's all /public/, because the code has to be open everytime. So if you would like to program on your own something, don't use Savannah.

| no status with respect to free or proprietary software

We only host free software that can run on free operating systems.

| Do you write a copyright statement first thing of all every
| time you create a new file?

No because a file <10 lines doesn't need a copyright, or even cannot be copyrighted. ;-)
But if you would like to publish something on a world-readable-platform (like Savannah), you had to keep care of copyright and license issues.


So if you really care about privacy, how could be Savannah be useful for you? We don't host /private/ projects.

Clarify this point please.
Thanks.

Sebastian Wieseler <kickino>
Mon 12 Sep 2005 06:30:12 PM UTC, comment #7: 

Hello.

Sorry, watching to the false tarball. :(
We are now still in discussion-your-project status.

| Oh. I hadn't thought of that. You want that legalese as soon as
| the very first draft versions of a project?

We want it now.
In order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the beginning of every file of source code.

In addition, if you haven't already, please include a copy of the plain text version of the GPL,
available from http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.
To learn why a copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.


And because of tools/*:
Licensing under the "GNU GPL v2 only" is problematic.
 Would you agree to license your project under the "GNU GPL v2 or later"?

The reason for this is that when we publish GPL v3,
it will be important for all GPL-covered programs to advance to GPL v3.
If you don't put this in the files now, the only way to port your program to GPL v3 would be to ask each
and every copyright holder, and that may be very difficult.

We can explain the issue in more detail if you wish.
If you have concerns about "GNU GPL v2 or later", we'd be happy to address them too.


And at last, in order to release your project (the documentation of it) properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING' (http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.

Regards and look forward to your updated tarball.

P.S.: You can send the tarball to me per private mail, but reply to this tracker item nevertheless.

Sebastian Wieseler <kickino>
Mon 12 Sep 2005 06:18:26 PM UTC, comment #6: 

Hello.

Please notice for further work:
All included Perl modules must be available under a GPL compatible license (the Perl license is GPL compatible).


I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

Regards.


Sebastian Wieseler <kickino>
Thu 08 Sep 2005 07:22:39 PM UTC, comment #5: 

Hello.

-email is unavailable- bounces all mails. ;-)
If you would like to send Sebastian^Wme a mail, please send it to -email is unavailable- - thank you very much. :-)


Regards,
Sebastian Wieseler

Sebastian Wieseler <kickino>
Wed 07 Sep 2005 10:07:55 PM UTC, comment #4: 

I replied to Sebastian tonight again, at his Reply-To: address:
-email is unavailable-
Is this the right one? Is this the preferred way to communicate?

Sébastien Blondeel <sbi>
Wed 07 Sep 2005 06:20:17 PM UTC, comment #3: 

Me? When did you sent it? Don't received anything. :-/

Sebastian Wieseler <kickino>
Wed 07 Sep 2005 09:23:12 AM UTC, comment #2: 

I sent Sebastian a TAR archive by mail.
Is this enough or should I submit this TAR archive again in this form?

Sébastien Blondeel <sbi>
Mon 05 Sep 2005 08:33:43 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.


Please include a (perhaps temporary) URL pointing to the source code.
The description you gave when registering will not be read by the general public.
If you are still concerned with privacy, however, you can forward the code to me by email.

We wish to review your source code, even if it is not functional, to catch potential legal issues early.

For example, to release your program properly under the GPL you must include a copyright notice and
permission-to-copy statements at the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch potential omissions such as these.

Regards,

Sebastian Wieseler <kickino>
Mon 05 Sep 2005 05:45:14 PM UTC, original submission:  

A new project has been registered at Savannah
The project account will remain inactive until a site admin approve or discard 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):

  <https://savannah.gnu.org/admin/groupedit.php?group_id=7950>


######### REGISTRATION DETAILS #########

Full Name:
----------
  Project Gutenberg Distributed Proofreade

System Group Name:
-----------------
  pgdp

Type:
-----
  non-GNU software & documentation

License:
--------
  GNU General Public License V2 or later

Description:
------------
  Project Gutenberg Distributed Proofreaders (PGDP US, PGDP EU)
proofing and formatting (R1, R2, P1, P2, F1, F2) assistant
self-learning tool for scannos and OCR errors

References
www.pgdp.net
dp.rastko.net

Other Software Required:
------------------------
  Unix
Perl
modules (not all are necessary):
  Data::Dumper
  Greek
  HTTP::Cookies
  HTTP::Request::Common
  LWP::UserAgent
  Roman
  Term::ANSIColor
  Term::ReadKey
  Time::ParseDate
fvwm2 (or other easy to configure
programmable text editor is a good thing
  (I use VIM but others should work)


Sébastien Blondeel <sbi>

 

(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

 

CC list is empty

 

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 12 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-10-24 kickino CategoryApproved Projects to be Reviewed Project Approval
    StatusNone Done
    Open/ClosedOpen Closed
2005-09-13 kickino CategoryProject Approval Approved Projects to be Reviewed
    StatusNeed Info None
2005-09-12 kickino StatusWait reply Need Info
2005-09-12 kickino StatusDone Wait reply
    Open/ClosedClosed Open
2005-09-12 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2005-09-05 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-758e.
Corresponding source code