taskSavannah Administration - Tasks: task #12788, Submission of GoldBug Android...


task #12788: Submission of GoldBug Android Secure Instant Messenger

Submitted by:  Eric Schmith <elysium>
Submitted on:  Sun 25 Aug 2013 04:41:24 PM UTC  
Should Start On:  Sun 25 Aug 2013 12:00:00 AM UTC Should be Finished on:  Wed 04 Sep 2013 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  100% Assigned to:  Joan Lledó <jllledo>
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.


Mon 02 Sep 2013 10:37:11 PM UTC, comment #2:

Hi Tom,

Since Joan is away for a few days, I'll try to answer some of the
questions. (Sorry if it gets garbled.)

> GB is as well prepared for Windows Compile, the subpathes contain the
> libs with original source code and some supathes for the windows Libs,
> so dll. We have the Source code fully provided. For the windows compile
> it porvides for the convenience pre-compiled libs. If you compile on
> windows, the given Source has all source files that are needed.

As long as you are providing all the sources for the precompiled files,
I guess that is ok.

> The project uses the BSD License, The libs have other licenses Like
> libgcrypt has LGPL. That is possible, as the libgcrypt is not
> modified. there is no derived code from that, it is used as is.

Whether it's modified or not makes no difference, it seems to me.
Fortunately, all the licenses are compatible, I believe.

> We have the BSD licsense, see header files. I think it is not a
> modified license.

You are in fact using what is known as the "modified BSD" license, which
is good. The "original BSD" license (circa 1980s-1993) had a
required-advertising clause which made it incompatible with the GNU GPL.
(That's why we don't accept it.)
See http://www.gnu.org/licenses/license-list.html#OriginalBSD for more
info, if you care.

> Yes. please send us the text, if the licensing is needing it, or is it
> only needed for your project approval?

I think your project is only using the LGPL and "modified BSD", right?
Then I believe no special exception for OpenSSL's unique license is
needed. (The extra exception is needed when GPL code is involved, since
the GPL and OpenSSL license are incompatible.)

> i forwarded that to the developer.
> Makefiles are generated automatically.

It's crucial that the original sources (from which the Makefiles are
derived) have a license header. It's highly desirable that the derived
files copy in the license header too (as, say, Automake does), but not
100% required.

> I think you are a little bit strong here, as e.g. the QT Ui files are XML
> files, which cannot have a header.

XML files can usually have comments. But anyway, the crucial point is
to be clear on the licensing of every nontrivial file. If it's
impractical or impossible for some files to have license information in
themselves (e.g., all your icons), the information can go in an
accompanying (same directory) README.

> What is the difference in BSD and Modified version and why do you
> exclude BSD?

See above.

> And why are you so strong on readme-files having a license? they are
> not beloning to the source, they are side-effects for help

As you say, they are help files (a.k.a. documentation) and thus part of
the package and thus need some license statement, since the legal
default is nonfree ("all rights reserved").

It's true that we are pickier about this at Savannah than other forges.
It's because we want to be sure that everything distributed at Savannah
is free software/free documentation/free whatever, so that anyone using
or working on anything at Savannah need not worry about it.

jll> To help us better keep track of your registration, please use the
jll> tracker's web interface by following the link below.

> ok

You answered in email :). Please submit replies in the web tracker.

Hope this helps. Thanks for your interest in Savannah.

Karl Berry <karl>
Site Administrator
Mon 26 Aug 2013 10:09:37 PM UTC, comment #1:


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

You've linked a tarball with several folders, I'm evaluating the project inside the GeopIP-1.5.1 folder. I assume that the other folders are libraries, am I right? Please, give us a tarball containing your project's files only.

I'm not sure what license are you using for your project, the description of the submission says "Other (BSD)", but the file '/GeoIp-1.5.1/COPYING' inside the tarball you've attached contains the text of the LGPL2+ . Please, clarify this issue. If you're using a BSD license, please tell us whether it's the Original or Modified BSD, since we don't approve projects licensed under the Original BSD license.

Moreover, your project depends on the libssl library. This is a particular case and you must add an standard openssl exception text in your sources. We can give you that text, but first we need to know what license are you using.

In addition, most of files in your tarball lack the license header, the rule is that every file more than 10 lines long must contain a license header. It includes man pages, README files, ChangeLog, Autotools files like Makefile.am or configure.ac, test code, examples...

For more information, take a look at this document:

If you are willing to make the changes mentioned above, please provide us with an URL to an updated tarball of your project. Upon review, we will reconsider your project for inclusion in Savannah.

To help us better keep track of your registration, please use the tracker's web interface by following the link below. Do not reply directly; the registration process is not driven by e-mail, and we will not receive such replies.


Joan Lledó <jllledo>In charge of this item.
Sun 25 Aug 2013 04:41:24 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: GoldBug Android Secure Instant Messenger
  • System Name: gb-android
  • Type: Official GNU software
  • License: Other (BSD.)


GoldBug is a Secure Instant Messenger.
More Information is found here: http://goldbug.sf.net

This project provides the mobile device and Android compile for the Messenger based on Qt 5.1.

Other Software Required:

The compile requires Qt 5.1.x,
libGeoIP 1.5.1,
libcrypto 0.9.8 or later,
libgcrypt 1.5.x,
and libssl 0.9.8 or later.

Tarball URL:


Eric Schmith <elysium>


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

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by jllledo (Posted a comment)
  • -email is unavailable- added by elysium (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
    2014-05-18 jllledo StatusIn Progress => Cancelled
        Percent Complete0% => 100%
        Open/ClosedOpen => Closed
    2013-08-26 jllledo Assigned toNone => jllledo
    2013-08-26 jllledo StatusNone => In Progress

    Back to the top

    Powered by Savane 3.3