[Savannah-register-public] [task #14528] Submission of relax

[Edward d'Auvergne]

Follow-up Comment #53, task #14528 (project administration):

Since the very start, the copyright has been waived for all data sets
deposited in the PDB database upon submission.  How could that "advisory
notice" text also cover copyright when all copyright has been waived - i.e.
all contents of the PDB database are public domain?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #6, task #15352 (project administration):

[comment #5 comment #5:]
> Files like .gitignore and src/exit.dat still have no notices; also, many
files in your tarball say they are GPLv2+ rather than GPLv3+, and have an
obsolete address of the FSF. I recommend using the form of the notice from the
GPL HowTo .

OK.  We will modify the notices accordingly and make a modified tar file later
today.

> 
> > Others have been excluded in the tar.gz file.
> 
> As far as I can see, you excluded files like 'configure'.  This is wrong,
because your package needs them.

This isn't "wrong" since the software currently builds by running the "build"
script which is included in the tar file.  This, as you can see, generates the
"configure" file.  Currently this is our preferred mode of building the
software.  I hope Savannah does not impose restrictions on how to build the
program from the source code.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

 Should Start On: Mon 05 Aug 2019 12:00:00 AM UTC => Tue 30 Jul 2019
12:00:00 AM UTC
   Should be Finished on: Mon 05 Aug 2019 12:00:00 AM UTC => Fri 09 Aug 2019
12:00:00 AM UTC

___

Follow-up Comment #7:

> This isn't "wrong" since the software currently builds by running the
"build" script which is included in the tar file.  This, as you can see,
generates the "configure" file.  Currently this is our preferred mode of
building the software.  I hope Savannah does not impose restrictions on how to
build the program from the source code.

Savannah has no requirements about building the package from the source code;
but you applied for inclusion in the GNU Project, so you still should comply
with GNU Standards.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #8, task #15352 (project administration):


[comment #7 comment #7:]
> 
> Savannah has no requirements about building the package from the source
code; but you applied for inclusion in the GNU Project, so you still should
comply with GNU Standards.

We are working separately to comply with GNU standards before it can be
accepted as a GNU Project.  There are other things in the code that need
change to comply with GNU standards.  Also we still don't know if it will even
be accepted as a GNU Project.  

Therefore we would like to start using Savannah as our git repos first and do
the development required on this repos to comply for acceptance as a GNU
Project. Hence the current effort to do whatever is needed to comply with
Savannah requirements.  

Let us know if this is OK. I.e. get the various legal notices etc. right to
make it a Savannah project first, without changing how we currently build the
project.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #9, task #15352 (project administration):

> We are working separately to comply with GNU standards before it can be
accepted as a GNU Project.
...
> Let us know if this is OK. I.e. get the various legal notices etc. right to
make it a Savannah project first, without changing how we currently build the
project.

It's up to you.  Let us to that separately.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15348] Submission of Free Molecular Dynamics

[Arham Amouei]

Follow-up Comment #7, task #15348 (project administration):

I see. I think within a week I can learn what I need to know about free
licenses.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14528] Submission of relax

[Edward d'Auvergne]

Follow-up Comment #51, task #14528 (project administration):

Yes, as all copyrights have been waived by the authors upon submission.  So
copyright law does not come into it.  The other "intellectual property"
categories - trade secrets, trademarks, design patents, etc. - are not
applicable.  The only thing left is patent law.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14528] Submission of relax

[Ineiev]

Follow-up Comment #50, task #14528 (project administration):

> But note that the advisory notice you quoted earlier specifically covers
patent issues:

That passage says about "intellectual property" in all cases but the last "a
patent involving the structure".  I conclude that it also covers copyright
issues.  Do you suggest the opposite?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15348] Submission of Free Molecular Dynamics

[Ineiev]

Update of task #15348 (project administration):

 Should Start On: Thu 01 Aug 2019 12:00:00 AM UTC => Mon 29 Jul 2019
12:00:00 AM UTC
   Should be Finished on: Thu 01 Aug 2019 12:00:00 AM UTC => Thu 08 Aug 2019
12:00:00 AM UTC

___

Follow-up Comment #6:

We have no resources to continually check all hosted packages for compliance.
The GNU project does provide a set of licensing-related pages like
https://www.gnu.org/licenses/license-list.html
https://www.gnu.org/licenses/gpl-faq.html
https://www.gnu.org/licenses/gpl-howto.html, but in general, we have to rely
on the ability of package maintainers to tell whether licenses are compatible
and whether they are free.


___

Reply to this item at:

  

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

[Savannah-register-public] [task #15356] Submission of PHP Hello

[Ineiev]

Follow-up Comment #3, task #15356 (project administration):

Any chances to include it in Guix?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14528] Submission of relax

[Edward d'Auvergne]

Follow-up Comment #49, task #14528 (project administration):

Of course!  But note that the advisory notice you quoted earlier specifically
covers patent issues:

"The user assumes all responsibility for insuring that intellectual property
claims associated with any data set deposited in the PDB archive are honored.
It should be understood that the PDB data files do not contain any information
on intellectual property claims with the exception in some cases of a
reference for a patent involving the structure."

This is basic knowledge for all practitioners in the structural biology field.
 So I've been talking about patents because you specifically brought up this
PDB patent text.

PDB file deposition into the database requires the authors to waiver their
copyright.  There are absolutely zero exceptions to this!  You see this in the
deposition forms  when you are going
through the deposition process.  That is why the Usage policy
 states:

"Data files contained in the PDB archive (ftp://ftp.wwpdb.org) are free of all
copyright restrictions and made fully and freely available for both
non-commercial and commercial use."

Data deposition to the PDB has required authors to waiver their copyright
since the start of the database in 1971.  The next sentence is basic advice on
how to be a good scientist - it has nothing to do with copyright law:

"Users of the data should attribute the original authors of that structural
data."

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14528] Submission of relax

[Ineiev]

Follow-up Comment #48, task #14528 (project administration):

I ask to postpone discussing patent issues until we are done with copyright.

Is this possible?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14694] Submission of Guile TD

[Ineiev]

Update of task #14694 (project administration):

Category:Project Approval => Approved Projects to be
Reviewed
  Status:Done => In Progress
 Open/Closed:  Closed => Open   

___

Follow-up Comment #4:

Currently, files like maps/rt-based/map0.png have no valid copyright and
license notices ; could
you check your package again and fix the issues?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #14528] Submission of relax

[Ineiev]

Follow-up Comment #52, task #14528 (project administration):

Indeed, since trade secrets etc. are not applicable, the only thing apart from
the patents left seems to be copyright.  If it were only patents, the notice
would say "patents" rather than "intellectual property".

___

Reply to this item at:

  

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