[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: GSOC [Continuous Integration for all biological applications inside Debian]

Hi again, 

I have to give you a little update i'm reading policy, join alioth page and have no problem in that subject but i  have a problem on packaging  PhyloPythiaS program. 
Program have no source code in its github repository, in article they said it's an GPL 3  licensed program but in license file they mentioned it is not a free software with another license in attachment and i confused about it . Can you suggest me another package i can work on it. Thanks for your help.

Regards

2016-03-22 15:14 GMT+02:00 Andreas Tille <andreas@an3as.eu>:
Hi Canberk,

On Tue, Mar 22, 2016 at 02:59:50PM +0200, Canberk Koç wrote:
> My name is Canberk i am  3. grade computer engineering student from
> Çanakkale Onsekiz Mart University/Türkiye.
> I interested in your project in GSOC.

Thanks for your introduction and your interest in the Debian Med project
and its GSoC.

> Nowadays i am working on a bionformatic project which may help Anvio Project
> <http://merenlab.org/projects/anvio/index.html> program and studying on
> making debian packages . I'm familiar with some bionformatic tools like
> PhyloPythiaS <https://peerj.com/articles/1603/> but also a newbie in this
> subject and open source community.
> I want to ask you what should i do and where to start to work with you and
> help you in this project.

>From my perspective the best way to start would be to package
PhyloPythiaS since you are familiar with it and also add a test suite
to it.  The main rules how to create Debian packages in the Debian
Med team are explained in our team policy[1].  I hope you might have
realised the Mentoring of the Month[2] effort which is discussed here
on the list currently in connection with the GSoC project.

This should provide you with all technical skills you need to cope
with the GsoC project.

> Already forgive my silly questions thanks to all :)

I do not remember any silly question here on this list and yours is
perfectly fine. ;-)

Feel free to keep on asking if this information was not helpful enough
to bring you on track.

Kind regards

    Andreas.


[1] http://debian-med.alioth.debian.org/docs/policy.html
[2] https://wiki.debian.org/DebianMed/MoM

--
http://fam-tille.de




-- 
PhyloPythiaS End-User License Agreement
---------------------------------------------------


This is a legal agreement ("Agreement") between you ("Licensee", either an individual or a single entity) and

Max Planck Institute for Informatics
Campus E1.4
66123 Saarbruecken
Germany,

("MPII" for short) about using the PhyloPythiaS software ("Software") that provides tools for DNA sequence classification. 

Please read the following Agreement carefully.

PhyloPythiaS is not open source and the program remains property of the MPII. The software must not be further distributed without prior permission of the MPII. If you use the Software in your scientific work, please cite as [reference]. We would also appreciate it if you send (a link to) your papers, so that we can learn about your research. 

By clicking on "I accept the License Agreement" or by downloading or installing the software you indicate that you have read and accepted the provisions of the Agreement and that you agree to be bound by all terms and conditions set forth herein. If you do not agree to any of the terms of this Agreement, do not submit a request for the Software and destroy any copies of the Software in your possession immediately.


1. Copyright

PhyloPythiaS, including but not limited to the program code, sample programs, any associated files and documentations (the "Software"), is owned by MPII and is protected by copyright laws. The copyright does not apply to the binary files (in the bin directory) and the Ruby libraries (in the lib/rubygems directory). The copyright for these files are owned by the corresponding authors. 


2. License

The Software is licensed free of charge to non-profit organizations for use in non-profit projects. Any commercial use of the software, including modified versions not developed in collaboration with MPII, is strictly forbidden (please contact MPII for a commercial license). Any copies of the Software should be complete copies including any copyright notices. The Licensee is granted a single, non-transferable license.



3. Limited Warranty and Liability

The Software is licensed to the Licensee on an "AS IS" basis without warranty of any kind. MPII is not liable to the damage caused by modified versions. The Licensee acknowledges that Software furnished hereunder is under test and may be defective.

The Licensee is solely responsible for determining the suitability of the Software and accepts full responsibility and risks associated with the use of the Software. In no event will MPII be liable for any damages, including but not limited to any loss of revenue, profit, or data, however caused, directly or indirectly, by the Software or by this Agreement.


4. Maintenance and Support

MPII is not obliged to provide maintenance or support to you.


5. Distribution

No distribution is to be made of the Software, or of modified versions of the Software, by you.


6. Delivery

The Software is obtained via Internet and/or E-Mail.


7. Privacy

MPII is committed to respecting the privacy and data security of the users of the software. In general, any uploaded data or conducted analyses are exclusively available under the same account data from where they were generated. MPI staff will access and / or view your data only when this is necessary for debugging purposes.
However, due to the software being in test state it may happen that private data becomes erroneously accessible to third persons. MPII cannot take responsibility for any damages caused by such an event.


8. Termination

If the Licensee fails to comply with any term of this Agreement, this Agreement is terminated and the Licensee has no further right to use the Software. On termination, the Licensee shall have no claim on or arising from the Software. The Software and any copies shall be destroyed.


9. Applicable Law and Court of Jurisdiction

This Agreement is made and shall be construed in accordance with the laws of Germany. Court of Jurisdiction is Saarbruecken, Germany.


10. Construction Clause

If for any reason a court of competent jurisdiction finds any provision of this Agreement, or portion thereof, to be unenforceable, that provision of the Agreement will be enforced to the maximum extent permissible so as to affect the intent of the parties, and the remainder of this Agreement will continue in full force and effect.

11. Citations
If you publish results obtained using the software, then we require that you cite the software as follows (references). 

12. Entire Agreement

This Agreement constitutes the entire agreement between the Licensee and MPII. It replaces all other representations.

All modifications or extensions of this Agreement need to be put down in writing.
Reply to: