[Savannah-register-public] [task #4784] Submission of Project PSIworld

[Sebastian Wieseler]

Update of task #4784 (project administration):

                  Status:                    None => Wait reply             
             Assigned to:                    None => kickino                

    _______________________________________________________

Follow-up Comment #1:

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


At first, "Linux" is just a kernel of a more complex system that we like to
refer to
as GNU/Linux, to emphasize the ideals of the Free Software movement.

Would you mind changing references to Linux as an OS to GNU/Linux?

For more information, see http://www.gnu.org/gnu/linux-and-gnu.html.


At second, note that Savannah supports projects of the Free Software
movement, not projects of the Open Source movement.

We are careful about ethical issues and insist on producing software that is
not dependent on proprietary software.

While Open Source as defined by its founders means something pretty close to
Free Software, it's frequently
misunderstood.
For more information, please see
http://www.gnu.org/philosophy/free-software-for-freedom.html.



At third, to use OpenSSL in a GPL released program is a little bit difficult
- it's better to use GNU TLS instead.

On the other hand you can include an exception to your license to allow
linking with the OpenSSL library - and doing so, you prevent yourself from
include GNU GPL'd code that you do not own to your project. But that's only
possible if you are the copyright holder of all the code (the code which you
are linking to, too) that is released under the license incompatible with
OpenSSL's (the GNU GPL).


At fourth, the license does not contain the last section, titled "How to
Apply
These Terms to Your New Programs".

Please use a complete verbatim copy of the license,
which may be found at http://www.gnu.org/licenses/gpl.txt,
http://www.gnu.org/licenses/lgpl.txt or http://www.gnu.org/licenses/fdl.txt.

The license must be copied verbatim and in its entirety.



At fith you might want to release your documentation under the GNU FDL:
In order to release your project 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.



And at last, the address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Please update your license notices.

Updates versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.

You can find some background and a possible migration script at
https://savannah.gnu.org/forum/forum.php?forum_id=3766

Regards,

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=4784>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/