News for hackers. Stuff that matters.
Re: Non Session Manager vs New Session Manager by mxmilkiib on Friday July 09, 2021 @08:56PM (#27790165)
A really one sided take.

The Non dev was being abusive in public threads and even nastier in private mails to various Linux Audio devs.

The full story is on the archives of the Linux Audio Development and Consortium mailing lists.

Folk should come visit #lad (Linux/Libre) on Libera.Chat.

Re: Non Session Manager vs New Session Manager by ww520 on Friday July 09, 2021 @09:37PM (#27790373)
If they had picked a different name for the forked project, none of the drama would exist. By picking a very similar and the same acronym, the gang is doing something underhanded.

In the business world, this is a clear case of trademark infringement and they would be sued out of existence.

Re: Non Session Manager vs New Session Manager by geofft on Friday July 09, 2021 @10:29PM (#27790658)
I have no context here, but from reading the post, it sounds like they did in fact pick a different name, but they picked one that let them reuse the same executable name for API compatibility.

In the business world, picking a different name for marketing and using functional elements for compatibility is a good way to get sued but win. See, for instance, Sega v. Accolade - Accolade sold software for the Sega Genesis without Sega's approval. Sega added something to the Genesis game loader which checked for the string "SEGA" and displayed the message "Produced by or under license from Sega Enterprises LTD." Accolade's games caused that message to appear, even though there was no license. The courts ruled that Accolade was entitled to do this, because the point was compatibility.

Re: Non Session Manager vs New Session Manager by FeepingCreature on Friday July 09, 2021 @10:51PM (#27790741)
Using the same binary name for a daemon is not necessary for compatibility.
Re: Non Session Manager vs New Session Manager by mxmilkiib on Saturday July 10, 2021 @07:40AM (#27792693)
As it happens, the first time this came up in #lad I was like "another name is sensible!" ("how about osm? like, One Session Manager!" (that being, at least, British humour)), but, by the second time, I was resigned to the fact that renaming what would be the same (but more robust protocol) to another acronym would be pointlessly confusing to users (and devs). NSM was a hopelessly overloaded term already.

It's interesting to see the instance of HN groupthink speculation (and lack of google fu) there has been in this comment section. Folk should come idle/chat in #lad. It's available via Matrix.

Re: Non Session Manager vs New Session Manager by ww520 on Saturday July 10, 2021 @01:45PM (#27795111)
Because people here look dimly on those taking other's hard work with underhanded tactics. The name NSM and its binary files are the BRAND of the original project and the original developer spent lots of time to build the project and build the brand. All the integration with the names required work and time built over time that the original developer had put in. Don't tell me it's just a name and has no value. If so, you guys won't pick the same name and same binary names.

Fork the project and pick another name. Spend the effort to market and build the integration with the new name. No one would have a problem.

Re: Non Session Manager vs New Session Manager by mxmilkiib on Saturday July 10, 2021 @03:55PM (#27796001)
Underhanded tactics? JML was abusive and has exaggerated.

I think it should be clear to anyone the relationship; the README mentioned JML from the get go, it's not framed as NON related, there is reference client and daemon, and it's just the same acronym because there's no reason to change.

The new projects name is New Session Manager.

Re: Non Session Manager vs New Session Manager by ww520 on Saturday July 10, 2021 @04:32PM (#27796220)
Picking the same acronym based on a similar name is VERY underhanded, especially when the acronym is used throughout as the name for the project. The term NSM is used more than a dozen times while Non Session Manager is used 3 times in their about page. NSM is basically the identity of project. http://non.tuxfamily.org/wiki/Non%20Session%20Manager

Using the same acronym and the same binary file names to push out Non from the distribution is very underhanded.

This looks like a deliberate aim to confuse the users and taking over the project code and identity. It's not cool.

I don't know JML and don't know his development style. Since he has been gracious enough to open source his project, I assume he's generous enough to share his hard work with others. If people don't like his style, fork the project with a different identity and compete on the merits, rather than stealing his project's identity with confusion.

Re: Non Session Manager vs New Session Manager by mxmilkiib on Saturday July 10, 2021 @07:35PM (#27797242)
Push out non nsm from a distribution? Mate, it was the individual distro packagers that decided enough was enough on that front.

You are trying to argue a course of action that would just have confused both users and devs.

Re: Non Session Manager vs New Session Manager by fundamental on Friday July 09, 2021 @11:10PM (#27790830)
For those interested, the linux audio consortium mailing list has archives available at: https://lists.linuxaudio.org/archives/consortium/ I see mentions of LAD mailing list archives elsewhere in the comments section, but for anyone looking for the public consortium emails they're here.
Re: Non Session Manager vs New Session Manager by explorigin on Friday July 09, 2021 @08:57PM (#27790168)
(citation needed)
Re: Non Session Manager vs New Session Manager by fgonzag on Friday July 09, 2021 @09:00PM (#27790180)
He literally stated where you can find the information.
Re: Non Session Manager vs New Session Manager by roenxi on Friday July 09, 2021 @09:15PM (#27790265)
He hasn't provided a citation. He's told someone they can do their own research an a mailing list. A parallel might be me claiming that we have a highly algorithm for factoring large primes and saying you can look it up on arxiv.org - I've pointed at a repository of knowledge, but not actually cited why I believe the fact.

Providing a citation is pointing at a specific place where the information came from at the smallest granular level. In this case, a citation would be something like links to specific threads.

Re: Non Session Manager vs New Session Manager by mxmilkiib on Friday July 09, 2021 @09:18PM (#27790290)
Your analogy is way off in terms of scale.

Edit: also, I've no obligation to provide a citation, I'm one of those that's bored by this particular drama, folk can go search for posts of they want, I've given enough to go by.

Re: Non Session Manager vs New Session Manager by pantalaimon on Friday July 09, 2021 @09:06PM (#27790223)
Hyperlinks were invented for a reason.
Re: Non Session Manager vs New Session Manager by quickthrower2 on Friday July 09, 2021 @09:37PM (#27790372)
For people at CERN to make bold claims, with citations
Re: Non Session Manager vs New Session Manager by AussieWog93 on Friday July 09, 2021 @09:00PM (#27790188)
>(citation needed)

>The full story is on the archives of the Linux Audio Development and Consortium mailing lists.

Re: Non Session Manager vs New Session Manager by bosswipe on Friday July 09, 2021 @09:06PM (#27790224)
How can you trust the mailing lost when the accused are the heavy-handed moderators of that list?
Re: Non Session Manager vs New Session Manager by test_epsilon on Friday July 09, 2021 @09:08PM (#27790231)
It is one sided, by definition.

However creating a fork with the same acronym and name for the daemon or binaries or whatever seems pretty under-handed.

Was a release announcement for the original software moderated, on a list where release announcements had been posted without moderation before the fork? Was the author banned from lists?

Re: Non Session Manager vs New Session Manager by fundamental on Friday July 09, 2021 @11:41PM (#27790944)
The Linux-Audio-Announce mailing list is a moderated mailing list and has been for quite a few years (10+ IIRC). It had been several years since the original non-* projects had a release announcement there and within those years the standard format of release postings had shifted from a more casual "tell us about your software" tone into "just provide changelogs and links to resources" type emails. The change over the years had not been documented in written list policies, so the initial LAA email was rejected. To the best of my knowledge no LAA ban was implemented, just a rejection of the initial submission after it entered the moderation queue.

A ban did occur on the LAD mailing list, but to the best of my knowledge the ban occurred due to some off list emails with one of the list moderators.

Re: Non Session Manager vs New Session Manager by viraptor on Friday July 09, 2021 @09:50PM (#27790448)
The same acronym is... a questionable choice. But the matching binary names are standard for projects which are compatible replacements for the other project. You're basically releasing something with a different name, but implementing "previous-software-name" interface. This helps with drop-in replacement distro packages to.

That's why Ubuntu has the alternatives system. And why mawk / gawk / etc. are often linked to /bin/awk.

Re: Non Session Manager vs New Session Manager by phendrenad2 on Friday July 09, 2021 @10:30PM (#27790663)
You don't actually need to name your binary after your project you know.
Re: Non Session Manager vs New Session Manager by test_epsilon on Friday July 09, 2021 @09:58PM (#27790500)
The same acronym is underhanded.

And it's entirely possible to use different software names for projects that implement a compatible API or service, the claim that it's for compatibility is pretty bogus. It's not "standard", especially not for an adversarial fork. And that's not why the alternatives system exists, the alternatives system exists so differently named packages can implement a particular service (i.e., exactly the opposite, for the equivalent in shell commands). So that's underhanded.

Re: Non Session Manager vs New Session Manager by viraptor on Friday July 09, 2021 @11:07PM (#27790814)
Alternatives works that way, because conflicting binary names are messy to handle, but at the same time it works that way, because that's the behaviour you normally want in your system. You want "a grep" and "an awk" and many others.
Re: Non Session Manager vs New Session Manager by test_epsilon on Saturday July 10, 2021 @01:16AM (#27791288)
I know how alternatives work, and they are not used to make packages with the same named binaries drop in replacements.

They are used to make packages with differently named binaries able to implement standard shell commands.

There is no need to match binary names. It doesn't really help with anything.