Re: advice for free software package named almost identically to non-free software

2017-06-13 Thread Nicholas D Steeves
Hi Paul, On Sun, Jun 11, 2017 at 10:19:16AM +0800, Paul Wise wrote: > On Sun, Jun 11, 2017 at 7:42 AM, Nicholas D Steeves wrote: > > > Do you think it's ok to internally provide backwards compatibility? > > eg, for a library, newname provides/fulfils oldname, for a long period > > of

Re: advice for free software package named almost identically to non-free software

2017-06-13 Thread Nicholas D Steeves
Hi Ian, On Mon, Jun 12, 2017 at 12:27:12PM +0100, Ian Jackson wrote: > Nicholas D Steeves writes ("advice for free software package named almost > identically to non-free software"): > > An upstream has named their GPL software almost identically to a > > propriet

Re: advice for free software package named almost identically to non-free software

2017-06-13 Thread Nicholas D Steeves
On Fri, Jun 09, 2017 at 09:52:35AM +0800, Paul Wise wrote: > On Fri, Jun 9, 2017 at 6:29 AM, Nicholas D Steeves wrote: > > > An upstream has named their GPL software almost identically to a > > proprietary piece of software. > > I think it would be best to pro-actively rename the software now >

Re: advice for free software package named almost identically to non-free software

2017-06-12 Thread Ian Jackson
Nicholas D Steeves writes ("advice for free software package named almost identically to non-free software"): > An upstream has named their GPL software almost identically to a > proprietary piece of software. Both the free and the proprietary > software are developed in the U

Re: advice for free software package named almost identically to non-free software

2017-06-10 Thread Paul Wise
On Sun, Jun 11, 2017 at 7:42 AM, Nicholas D Steeves wrote: > Do you think it's ok to internally provide backwards compatibility? > eg, for a library, newname provides/fulfils oldname, for a long period > of time...perhaps a year. I'm trying to think of all the non-Debian > users who would also

Re: advice for free software package named almost identically to non-free software

2017-06-10 Thread Nicholas D Steeves
On Fri, Jun 09, 2017 at 09:52:35AM +0800, Paul Wise wrote: > On Fri, Jun 9, 2017 at 6:29 AM, Nicholas D Steeves wrote: > > > An upstream has named their GPL software almost identically to a > > proprietary piece of software. > > I think it would be best to pro-actively rename the software now >

Re: advice for free software package named almost identically to non-free software

2017-06-08 Thread Paul Wise
On Fri, Jun 9, 2017 at 6:29 AM, Nicholas D Steeves wrote: > An upstream has named their GPL software almost identically to a > proprietary piece of software. I think it would be best to pro-actively rename the software now rather than wait until renaming the software would be more painful. Even

advice for free software package named almost identically to non-free software

2017-06-08 Thread Nicholas D Steeves
Dear Debian Legal, An upstream has named their GPL software almost identically to a proprietary piece of software. Both the free and the proprietary software are developed in the U.S.A. The upstream has confirmed that the name is not a registered trademark in the U.S.A, but the proprietary