On Tue, Nov 28, 2017 at 11:21 AM, David Chisnall <[email protected]> wrote:
> On 27 Nov 2017, at 22:58, Sergii Stoian <[email protected]> wrote: > > > > Hi David, > > > > On Mon, Nov 27, 2017 at 7:57 PM, David Chisnall <[email protected]> > wrote: > > Hi, > > > > This looks very nice, but a few comments: > > > > - Apple still owns the NeXT trademark, so be careful about using NEXT in > the name. > > > > I think it is exactly the "NeXT" right? Not "Next" or "NEXT”. > > I am not a lawyer, this is not legal advice: > > Trademark law depends a lot on the notion of ‘passing off’, i.e. using a > variation of a trademark in such a way that it may cause confusion. For > example, Mr MacDonald’s Restaurant may or may not infringe the McDonald’s > trademark, but if it uses a big yellow M as its logo (even in a different > typeface) then it probably will. > > Apple is generally quite aggressive about defending trademarks, so it’s > probably better not to risk it - even if you’re right, the cost of > defending an infringement suit in the US may run to millions of dollars. > > Agree. But I want the name that has connection to NeXT platform. Something that will be rememebered as "The space where NeXT applications rebirth". There is a site http://www.nextcomputers.org. I found former NeXT users/developers there. They miss modern NeXTSTEP environment. I guess It's good target audience. That's why I need a good message for this kind of people. Any idea? > - NeXT used the NX prefix (NS = NeXT + Sun, NX = NeXT), so using it as > your prefix is confusing. > > > > Yes I know that. Do you think it's a copyright issue? > > It’s not a copyright issue (Google vs Oracle notwithstanding), it’s a > confusion issue. I saw the headers and thought they were implementations > of pre-OpenStep NeXT classes, but then I looked more closely and they don’t > appear to be. > > You're right. I heed to think about it. > - Please don’t put big RPMs in the repo! It adds overhead to anyone who > clones it, and GitHub has a perfectly adequate Downloads facility for > hosting these. > > > > - It would be easier to package (and to collaborate) if these were > separate GitHub repos. > > I've switched to the github a couple of weeks ago and don't know all of > the github features. Can you help me to place RPMs outside of code on > github? > > Sure. If you click on the ‘0 releases’ line at the top of the page, > you’ll got to a page that has a ‘draft a new release’ button. From here, > you can generate a release associated with a tag and upload any binary > versions (e.g. the RPMs). > > That's it! Done. I've removed Packages directory from master branch. Thank you. Note that this will work better if you split the repo into different > projects, because then it’s easy to do the releases independently. > > This also helps packagers for other systems. For example, on FreeBSD if I > am the maintainer of a a port then portscout will send me an email if > there’s a new release automatically. > > Good idea. Gone in TODO list. David > > -- Sergii Stoian, ProjectCenter maintainer
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
