Re: Debian Med Homepage - maybe all blends as "blendname".debian.net ?

2019-03-14 Thread Paul Wise
On Thu, Mar 14, 2019 at 10:56 PM Andreas Tille wrote: > On Thu, Mar 14, 2019 at 02:42:18PM +0100, Steffen Möller wrote: > > I propose to give all blends a blendname.debian.net address. Would that > > be reasonable? med.debian.net for us, I mean. debian.net domains are a bit problematic if the dom

Re: Biological data being used by an unpublished research paper is considered proprietary

2013-09-16 Thread Paul Wise
I am not a lawyer but I don't think facts are copyrightable. In some jurisdictions there are "database rights" and copyright on collections of facts (like phone books) that could apply here. I suggest you consult the lawyers for your research institute for the legal situation in your jurisdiction.

Re: Question about a licensing problem

2014-03-17 Thread Paul Wise
My approach would be to ask upstream to revert back to the GPL. If they refuse then look for an alternative free implementation. If none exists revert back to using and packaging the GPL version. Also work on some patches to improve the GPL version and send them upstream. If upstream refuses to

Re: Status of uw-prism packaging for Debian

2014-08-01 Thread Paul Wise
On Fri, Aug 1, 2014 at 4:56 PM, Andreas Tille wrote: > I'm forwarding a part of a discussion to you legal experts for > clarification: I'm afraid debian-legal is mostly armchair lawyers. If you want to consult actual lawyers, it would be best to get legal advice from the SFLC, who we have gotten

Re: Team uploads.

2010-03-10 Thread Paul Wise
On Sun, Mar 7, 2010 at 1:47 PM, Charles Plessy wrote: > It was proposed in 2009 to formalise "Team uploads" in analogy to the "QA > uploads", as a special case of NMU, where most conventions are relaxed. As the initiator of the previous thread, I'd like to thank you for pushing this. As far as

Re: Bug#630977: ITP: raccoon -- preparation for ligand screening projects

2011-06-19 Thread Paul Wise
On Sun, Jun 19, 2011 at 8:02 PM, Steffen Moeller wrote: > * Package name    : raccoon That is one letter away from racoon, the IPsec IKE keying daemon. I wonder if that would be too confusing of a name? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-med-requ.

Re: use of json.org in biojava3-ws

2012-05-29 Thread Paul Wise
On Tue, May 29, 2012 at 8:17 PM, Andreas Tille wrote: > I'd call this an "over-picky" interpretation of something that rather > qualifies as a joke rather than a license which can be dealt with in > court (disclaimer: I'm not a lawyer, just try to apply common sense.) > > I'd like to answer this k

Re: use of json.org in biojava3-ws

2012-05-29 Thread Paul Wise
On Tue, May 29, 2012 at 9:28 PM, Andreas Tille wrote: > On Tue, May 29, 2012 at 08:31:46PM +0800, Paul Wise wrote: >> >> The definition of "evil" is subjective and could refer to anything, >> including the production of Debian itself. > > Sure and a statement

Re: Debian quotes? (Was: sponsor upload 1.1.13-1)

2012-08-02 Thread Paul Wise
On Thursday, August 2, 2012, Andreas Tille wrote: > I do not know whether we do collect some quotes IIRC there is a fortunes-debian (or similar) package for those. -- bye, pabs http://wiki.debian.org/PaulWise http://bonedaddy.net/pabs3/

Re: FreeMedForms projet

2020-01-09 Thread Paul Wise
On Thu, Jan 9, 2020 at 8:00 PM Eric Maeker wrote: > Free Source code is provided to any demander approved by the NPO, code > licence is still the same. I don't like this, people seeking source code should not have to get approval first. That said, I note that the source code is available directl

Re: FreeMedForms projet

2020-01-09 Thread Paul Wise
On Fri, Jan 10, 2020 at 2:02 AM Paul Wise wrote: > I don't like this, people seeking source code should not have to get > approval first. That said, I note that the source code is available > directly from the site without approval. I missed seeing that the git repository contain

Re: FreeMedForms projet

2020-01-10 Thread Paul Wise
On Fri, 2020-01-10 at 13:01 +0100, Eric Maeker wrote: > Sounds like we are travelling to "contrib" or "non-free" package ? Or > may be "non-debian" ? The section of Debian a package is added to depends solely on the DFSG compliance of the software (freely licensed and released source code). Wheth

Re: FreeMedForms projet

2020-01-10 Thread Paul Wise
On Fri, 2020-01-10 at 17:34 +0100, Eric Maeker wrote: > We know that at least two forks exists (this is what our private data > server's log tells us). We do not receive any patch, invitation to > git repos, or any kind of official informations or queries. Having multiple forks and having folks n

Re: FreeMedForms projet

2020-01-11 Thread Paul Wise
On Sat, 2020-01-11 at 17:08 +0100, Eric Maeker wrote: > I'm really sorry, but I can not answer to everyone and all your > questions. I feel a bit flooded. Sorry about that, I hope one final email is not too much. > About the website and the DFSG compliance, please consider that the > website tra

Re: Is there any way to refuse Janitor changes in team git?

2020-04-20 Thread Paul Wise
On Mon, Apr 20, 2020 at 6:21 AM Andreas Tille wrote: > To be clear about this: The command line tools used by the janitor are > considered extremely helpful. Lintian-brush became a fixed part of our > workflow. But since we do it anyway automatically any extra merging or > checking for merge re

Re: Python louvain packages naming confusion.

2021-02-09 Thread Paul Wise
On Tue, Feb 9, 2021 at 10:21 PM Diane Trout wrote: > The fairly popular (in the world of bioinformatics) ScanPy package uses > a Python version of the louvain clustering algorithm implemented by: ... > However currently in the Debian archive there's a different louvain > package I think this is s

Re: neon: armhf baseline for next release ?

2023-02-10 Thread Paul Wise
On Fri, 2023-02-10 at 10:23 -0800, Vagrant Cascadian wrote: > For an individual package that wants to make use of neon, the correct > thing to do is to make the neon support detected at run-time rather than > rely on it at build-time and enabling or disabling codepaths, features, > etc. as appropr