Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
The "Linux community" didn't do this, kid. Arguably, since a forum serving the Linux community was what was defaced, the Linux community was the victim here. This was one troll over in Transnistria or somewhere, and you, like you people do, are attributing their actions to an entire unrelated group, and victim-blaming in the process.
Shanley is an infamous cow herself, getting into a famous feud with the Linux userbase after she (being an outsider) wanted to kick Linus Torvalds out of his own project and making a joke of herself in the process. Not only was it revealed she used to be pals with Weev at one point but after that came out Gawker questioned if she was an elaborate troll op.
 
Saddle up, boys, girls, and non-gender-binary-conforming individuals, we have an incoming.

Domain-driven design is the name of one of those software development processes that process nerds like to sperg on about while normal coders are actually getting work done. Can you imagine what could be problematic about such a thing, though? Go on, try to figure out what it is. Hint: It has nothing to do with the process itself, but with the name of the process.

Give up? The answer is that its acronym is DDD, which could be pronounced "triple-D." DDD is also a rather large bra cup size. So that means whenever you are discussing or practicing domain-driven design, you are actually thinking about big breasts and by extension oppressing women, who are not to be sexualized in any way, you pig.

Of course this makes sense if you're a dangerhaired Ruby dev in San Francisco with pronouns in your Twitter byline. Tweet thread here. Couldn't get it to archive correctly.
 
Ironically, all Sarah Mei opinions should be automatically redirected to the trash.
upload_2018-12-14_14-50-34.png
 
I can only say as a white guy, the only thing I enjoy more than genociding trannies is oppressing women. It's good to be white. I also plain don't like people with a darker skin color than me.

(I also never heard of this DDD stuff which is probably because I am not one of these computer people that color coordinate their Visuaural Studio IDE with their Electronic Soy Editor or whatever it is these idiots use these days)
 
Of course this makes sense if you're a dangerhaired Ruby dev in San Francisco with pronouns in your Twitter byline. Tweet thread here. Couldn't get it to archive correctly.

She claims to have some kind of position in Ruby but so far as I can tell, does nothing but respond to tweets calling her an idiot all day long.
 
  • Agree
Reactions: altkiwi01
She claims to have some kind of position in Ruby but so far as I can tell, does nothing but respond to tweets calling her an idiot all day long.

Yeah, I can't say I've ever seen anything productive come out of her account. For real though, even if the use of `DDD` was problematic, there are bigger fish to fry and things more worth everyone's time and energy.
 
(I also never heard of this DDD stuff which is probably because I am not one of these computer people that color coordinate their Visuaural Studio IDE with their Electronic Soy Editor or whatever it is these idiots use these days)
I think it's another one of those corporate bastardizations of agile for working around organizational dysfunctions and politics instead of solving actual technical problems. Just look at the tools section of the wikiedia page (java, java, uml, java/.net, java, java/.net and c#). If you haven't heard of it I'd take that as a a good thing.
 
DDD, which was first described in the most boring book imaginable, is worth your time to learn the basics of. You might be surprised at how it helps you conceptualize software before you build it. Things like ubiquitous language can save you from hell as a project scales. Like anything, including agile, it can go really wrong and make tons of pointless meetings.
 
Recently a developer called Iliana Weller made a Github repository with code that prints a stream of "e", located conveniently at the URL below:

https://github.com/eeeeeeeeeeeeeeee...eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee (archive)

Last week, they wrote a blog article (archive) about it.

TL;DR it broke Github at various parts (such as actually cloning the repository), because apparently Github doesn't actually validate inputs or test extremely long inputs that they allow. obviously such a brilliant project will be very popular so it made it to Github's trending repos, exposing the breakage to a decent audience, which promptly complained about this stupid repo in its issues.

So Github did the right thing: took it down and stonewalled the author for a while. Here's copies of the e-mail communication the author posted in their follow-up (archive) about the whole thing unravelling. They quit using Github over this.

Date: Tue, 11 Dec 2018 20:10:01 +0000
From: iliana weller <ilianaw@buttslol.net>
To: "Avery (GitHub Staff)" <support@github.com>
Subject: Re: e30e/e98e
User-Agent: Mutt/1.5.21 (2010-09-15)

Unfortunately it's still not clear what GitHub considers to be short
enough as you work to fix the UI issue.

If you can provide a clear, unambiguous limit for a temporary name
change I will be able to make the change.

--
iliana weller <ilianaw@buttslol.net>

On Tue, Dec 11, 2018 at 08:00:54PM +0000, Avery (GitHub Staff) wrote:
> Hi iliana,
>
> Thanks for the detailed reply, and we understand your frustration here.
>
> Your repository name has uncovered an issue with our UI that we’re currently working to correct. But to clarify, that issue is affecting the UI of other GitHub users who haven’t starred or otherwise interacted with the repository (outside of the Explore page and emails). As a result, we received a large number of
reports from confused/affected users, which also impacted our ability to provide support to other users. I recognize I could’ve been more clear about that in my original reply, so I apologize for not having included more detail.
>
> While we work to correct the issue on our end, we’d appreciate it if you’d be willing to temporarily shorten the repository name to minimize the disruption to our Support team and other users. We want to help you get back to work here, while being mindful of other users’ experience.
>
> All best,
>
> Avery

Date: Tue, 11 Dec 2018 16:13:43 +0000
From: iliana weller <ilianaw@buttslol.net>
To: "Avery (GitHub Staff)" <support@github.com>
Subject: Re: e30e/e98e
User-Agent: Mutt/1.5.21 (2010-09-15)

Actually, let me just be more blunt.

I don't think people reported this repository because the name or
description were disruptive; maybe that was the reason they gave staff,
but I think they reported it because they interpret it as a waste of
resources.

I'm not interested in shortening the repository name to appease these
people. I am willing to shorten the repository name to help resolve any
*purely technical* concerns of GitHub staff provided sufficient reason
for doing so. For instance, if you were to decrease the maximum length
of a combined username + repository name, I would be willing to comply
with that.

But anybody can make repository names of this length still. The only
reason mine was disabled was because it was popular enough to distract
people who... do what? Use the Explore email?

This repository turned into a really cool art project that a lot of
people care about. The length of e's doesn't matter. But it's really sad
that GitHub staff is bothering to listen to people who think that the
repository doesn't have a serious purpose.

--
iliana weller <ilianaw@buttslol.net>

On Tue, Dec 11, 2018 at 04:01:18PM +0000, iliana weller wrote:
> > We would be interested in hearing more about the purpose of the project.
>
> https://linuxwit.ch/blog/2018/12/e98e/
>
> > Thanks for your offer to shorten the repository name – that should help reduce the distraction. We’ve re-enabled the repository for the next 24 hours to allow you to make that change.
>
> What exactly is your threshold for the repository name length, and why
> is it not the limit you have in place (100 characters)?
>
> A request to shorten the repository name against an arbitrary rule is
> not actionable.
>
> On Tue, Dec 11, 2018 at 03:10:53PM +0000, Avery (GitHub Staff) wrote:
> > Hi iliana,
> >
> > Thanks for taking the time to write in about this. The e30e /eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee repository was disabled following reports of abuse of GitHub’s Terms of Service. Keep in mind, people use
GitHub to learn, to work, and to be productive. Generating disruptive content on GitHub can go against our prohibition against spam. We would be interested in hearing more about the purpose of the project.
> >
> > Thanks for your offer to shorten the repository name – that should help reduce the distraction. We’ve re-enabled the repository for the next 24 hours to allow you to make that change. If, after 24 hours, the name is the same, we may need to re-disable the repository
around this time tomorrow.
> >
> > Please let us know if you have any questions.
> >
> > All best,
> >
> > Avery
>
> --
> iliana weller <ilianaw@buttslol.net>

Date: Tue, 11 Dec 2018 20:40:51 +0000 (UTC)
From: "Avery (GitHub Staff)" <support@github.com>
To: iliana weller <ilianaw@buttslol.net>
Subject: Re: e30e/e98e

Hi iliana,

Thanks for your reply, and for your cooperation. We'd ask that you limit the organization and repository names to 10 characters each for now.

All best,

Avery

Date: Wed, 12 Dec 2018 09:01:02 +0000
From: iliana weller <ilianaw@buttslol.net>
To: "Avery (GitHub Staff)" <support@github.com>
Subject: Re: e30e/e98e
User-Agent: Mutt/1.5.21 (2010-09-15)

I have to apologize, because I said that given a precise limit, I would
make the change.

But 10 characters for each component does not reflect reality and is an
absurd request compared to these other repositories that happen to be
listed on github.com/trending:

https://github.com/GokuMohandas/practicalAI
https://github.com/MisterBooo/LeetCodeAnimation
https://github.com/scutan90/DeepLearning-500-questions
https://github.com/google-research/google-research

I've made the repository read-only, and stalled my final response in
order to make what I consider a sufficient backup of the repository and
related content. That backup is complete.

What happens with the repository is entirely in your hands at this
point. We're not going to protest any changes made by GitHub staff, but
we're not going to make them either.

I want to apologize as well for e98e's impact on your ability to provide
support to other users. That's not fair to you or users of GitHub. But I
must ask your organization to consider the following:

- If GitHub Support is significantly impacted by the load of users
reporting a repository, is the current system for reporting
repositories sustainable?

- Does your current system harm targets of widespread harassment? For
example, if a person of color or a trans person builds a legitimate
software project that becomes incredibly popular, does the current
system effectively allow their harassers to disable the repository
with no immediate recourse? (Will they not be given an initial
response for 19 hours either?)

For the record, I've published two blog posts regarding this repository:
https://linuxwit.ch/blog/2018/12/e98e/
https://linuxwit.ch/blog/2018/12/everything-that-lives-is-designed-to-end/

And, finally: your development team should probably add a character
limit to the repository description field, lest this happen again:
https://twitter.com/joseluis_q/status/1072637228361375744

Unless you have further questions or concerns, this will be my last
email to support regarding e98e.

--
iliana weller <ilianaw@buttslol.net>

On Tue, Dec 11, 2018 at 08:40:51PM +0000, Avery (GitHub Staff) wrote:
> Hi iliana,
>
> Thanks for your reply, and for your cooperation. We'd ask that you limit the organization and repository names to 10 characters each for now.
>
> All best,
>
> Avery

There's one thing I'd like to bring up from the emails:
- Does your current system harm targets of widespread harassment? For
example, if a person of color or a trans person builds a legitimate
software project that becomes incredibly popular, does the current
system effectively allow their harassers to disable the repository
with no immediate recourse? (Will they not be given an initial
response for 19 hours either?)
Clearly any harassment coming this repo's way is because the author is transgender (he is) or a person of color, not because it's in fact breaking Github and is a barely legitimate repository anyway.

Also, check out this neat game of life implementation, which may be the only legitimate thing in here.

49709410-c8420b00-fbf9-11e8-995e-ea3a2270f161.png
 
GitHub now has unlimited private repos for free accounts

But Microsoft was supposed to be the death of GitHub

It's like they don't want my 7 bucks. Now if only Google would start giving me google apps for domains for free, I could buy a whole extra footlong sandwich each and every month!
 
  • Like
Reactions: Marvin
It's like they don't want my 7 bucks. Now if only Google would start giving me google apps for domains for free, I could buy a whole extra footlong sandwich each and every month!
The more accounts they snag (free or otherwise), they get more people creating services like Travis or Coveralls which only support Github.

I'm doing a project on gitlab and a lot of these things don't work with it. (The built in CI is a nice touch though.)
 
GitHub now has unlimited private repos for free accounts

But Microsoft was supposed to be the death of GitHub
GitHub's largest competitor, BitBucket, has been allowing free accounts to have private repos for… I don't know, a decade or so now? Given that (pretty much) everyone already has a GitHub account and (pretty much) all open-source projects already have a presence there, it was (pretty much) the only reason you'd choose to use BitBucket sometimes instead (unless you were one of those people that flipped out over the Microsoft buy-out, I suppose). Now that GitHub can be partially or wholly subsidized by M$, I'm guessing someone in charge decided the revenue stream from the smaller paid accounts was less valuable than being able to stick it to a distant but still present competitor.
 
Back