5 ms·
" This browser is created and maintained by the team behind Pale Moon..." These guys https://github.com/jasperla/openbsd-wip/issues/86 https://github.com/jaspe
by michaelmrose 8y ago
" This browser is created and maintained by the team behind Pale Moon..."
These guys https://github.com/jasperla/openbsd-wip/issues/86 https://github.com/jasperla/openbsd-wip/issues/86
How about not.
- andai 8y agoHave you read any of Linus Torvalds' emails?
- michaelmrose 8y agoWhataboutism is rarely a useful argument. Also even Linus now asserts that he was a bit of a jerk. Also linus only calls for you to be retroactively aborted he doesn't threaten lawsuits normally.
- dotdi 8y agoClassical whatabout-ism. Linus was arrogant, condescending and abusive in his emails. Those guys were arrogant and condescending. Being as bad as Linus when dealing with other people is really not something worth striving for and not something worth defending.
- tree_of_item 8y agoYeah, "those guys" who try to enforce their software's license. The nerve.
- deleted 8y ago[deleted]
- jrs95 8y agoI don't think it's fair to cherry pick 1 github thread and use it as a moral condemnation of an entire software project.
- Foxboron 8y agoIt's hardly a cherry-pick. They have attempted to pull this of on AUR as well on two occasions.
- jrs95 8y agoInteresting. That definitely doesn't sound good. Thanks for providing some additional context.
- AnaniasAnanas 8y agoGot any links?
- tokai 8y agoWhen it is such a cherry you only really need to see the one.
- grawprog 8y agoWow...that whole thread was utterly ridiculous...the pale moon people and that ibara guy were all acting like children. That was entirely counter productive in just about every way...
- cweagans 8y agoYou know, I just read that whole thread, and I don't see a problem. Maybe they were being jerks about it, or maybe some of that nuance was lost in translation. However, software licensing is a legal issue and legal issues are usually places where you don't want any ambiguity about intent and expected results. I don't think directness is necessarily a problem in this situation (think of how a cease and desist letter from a lawyer would read - it's not gonna spend a lot of time padding your ego).
- dagenix 8y agoYou will change your oppinion immediately. You must comply with this directive or you must stop distributing your oppinion. I will not be as educational next time.
- em-bee 8y agowe are palemoon of borg. resistance is futile.
- chrisseaton 8y agoHow can you possibly think that ‘You will revise your...’ and ‘I will not be as educational next time’ is an appropriate way to speak to someone? That set the whole thing down the wrong path from the start. What a waste.
- cweagans 8y agoAgain, I think the translation barrier may have been a big part in the specific phrasing even if they were intentionally being blunt. I don't speak dutch and can't say definitively if that's the case, but I have spent a lot of time working with people who's first language it not english, and they can certainly come off as harsh at times when they don't mean to. In this case, it is entirely possible that "You should revise your..." was the intended meaning. I don't think that "I will not be as educational next time" is bad if one is defending a license, especially since the license is pretty clearly written and distributed with the software. There shouldn't have been a need for the maintainer to explain the problem in the first place, but since they were kind enough to do so, I think it's entirely reasonable to say that the next interaction on this topic will not be amicable (to me, that sounds like getting lawyers involved). Yes, it's very direct. Yes, it's probably a little too far toward outright dickishness. But that's their prerogative as the holders of the copyright, and they have to enforce it as they see fit. Nintendo does the same stuff and people get annoyed by it, but at the end of the day, it's their right to protect their property.
- jancsika 8y agoThat whole thread makes me question current system packaging best practices even more than I already do. For example-- where is the introductory email from the would-have-been packager to upstream saying, "Hello, I'm so-and-so. I'd like to take a stab at packaging Pale Moon for so-and-so. Any docs or issues I should take into consideration before beginning? Sincerely, Obvious First Step" Especially considering Pale Moon is probably in that category of "top 20 most complex packages" for their system. I'll give another example of similar non-existent communication with upstream that ended up wasting my time as a Debian user: "Dear Firefox, Hi. It's the firefox-esr packaging team from Debian. Our current package for it is about to go EOL. Since our release schedule is slow and our security policy doesn't scale, we make an exception for Firefox by backporting the new ESR version in its entirety. Anything special we should know about major version 60? We know that some of the archs we support are considered tier 3 archs by Firefox, and we'd hate for an upgrade on our stable release to break FF completely for lots of users who run Debian Stretch on arm devices, for example. Especially given that nobody can build with debug symbols on some of our supported archs, making it difficult for them to adequately report the bug to you." I upgraded to Buster because of this. I.e., Firefox's "ESR" holds more meaning for me than Debian's "stable" does.
- yellowapple 8y agoSeems like a whole lot of drama and pain could've been avoided if that Tobin guy replaced his entire message with "Hey, so using system libraries instead of our own libraries for a 'Pale Moon'-branded distribution of our software is in violation of our trademark license (except in certain circumstances, but it doesn't look like your porting project is applicable to those exemptions). Please use the 'New Moon' unofficial branding instead until/unless we explicitly authorize the use of 'Pale Moon' branding with your customized build (which we can do provided you submit your changes to 'www/palemoon/patches')."