91–100 of 110 posts
Earlier quoted context omitted.
Dick pics fall into the category of "unwanted sexual advances", which is a form of harassment.
I guess some people could see it that way given the donglegate scandal, but it can't be harassment if it's not repeated. And if something is to be repeated, then lots of things can be used besides dick pics.
Pretty sure there are a LOT of women who would strongly disagree.
Earlier quoted context omitted.
I suppose that's part of the reason I've had trouble understanding this phenomenon: the couple of "code of conduct" documents I've read have seemed so inoffensively obvious that it is hard to understand why such a document would be necessary, much less why it would be controversial. It alarms me that people care so much about them that merely expressing confusion about the purpose or utility of such a document acts a…
I guess I don't interpret the presence of a code of conduct as an alienating, harsh, moralistic approach to anything. It's about as alienating/harsh/moralistic as a kitten, if the kitten was easily ignored and made of ASCII.
Earlier quoted context omitted.
I am completely serious and meant exactly what I said. I did not say that it was offensive; I said that I don't understand where the practice came from. I have never been part of an open source community where "stalking, doxing, or harassing" was a problem - or at least not a problem anyone talked about. It sounds very strange, and it's hard to imagine how people that immature could be capable of doing good engineeri…
A whole bunch of projects suffer from the issue - even (especially) ones as large as FreeBSD[0]. The issue usually winds up being that some minor contributor - or even just someone who hangs around in the dev channels - harasses some specific woman/trans person/other minority member, and the project has no official framework in which to approach this issue. Often in the project leaders' eyes, the project leader's job…
How does one know which of those four channels to use? Are people expected to follow all four of them if they want to keep informed about the project?
Wouldn't it be easier to have just one channel that is universally available? Email would be the obvious choice, and since you have to provide an email address to sign up at Github, you are already implicitly requiring your contributors to have email.
Earlier quoted context omitted.
> I'd love to agree. But with IRC you've no guarantee, for instance, that an offline user will receive notifications when they sign in (plus multi client handling). > Slack has search for history, which is huge. No more "eh we talked about it". For functionality like that it sounds like a mailing list would fit the use case better. > Onprem is great. But it's a hindrance for quick adoption. It's not either/or. Think…
> For functionality like that it sounds like a mailing list would fit the use case better. Then you're looking at an email with the visual noise of recipients and whitespace and signatures, and if the UI is really bad (mailing list websites, for example), every message is viewed in isolation without the responses.
Earlier quoted context omitted.
I guess some people could see it that way given the donglegate scandal, but it can't be harassment if it's not repeated. And if something is to be repeated, then lots of things can be used besides dick pics.
> it can't be harassment if it's not repeated Pretty sure there are a LOT of women who would strongly disagree.
> Simple Definition of harass: to annoy or bother (someone) in a constant or repeated way; to make repeated attacks against (an enemy).
Earlier quoted context omitted.
I guess some people could see it that way given the donglegate scandal, but it can't be harassment if it's not repeated. And if something is to be repeated, then lots of things can be used besides dick pics.
> it can't be harassment if it's not repeated Pretty sure there are a LOT of women who would strongly disagree.
Earlier quoted context omitted.
Are you serious or arguing insincerely? I can't tell. Codes of conduct are a direct response to ongoing harassment and stalking against various contributors of various open-source projects, followed by inaction on the part of the project maintainers or the excuse of "that just can't handle criticism". What is so offensive about saying "make it about the code, not about the person" and "don't stalk, dox, or harass peo…
He's quite sincere, and there are others of us who agree. Codes of conduct are a flavor of the month, and they don't achieve anything. I don't need to pre-announce that I will not accept patches from murderers or pedophiles, I can simply do it. The same is true for the types of offenses typical of a code of conduct. Perhaps it is generational, and the new guard will eventually win this battle one funeral at a time. B…
Otherwise you have owner arguing with contributor drama trying to explain implied etiquette. Of course unless the transgression was severe the owner is forced to be lenient for fear of appearing overly authoritarian (which would drive away some contributors), but they can't be entirely forgiving because the transgression might drive away some other (or same) people. CoC removes this bargaining.
It sounds like the author wants basically everything about how Emacs is developed to change in order to better fit their ideas about what open source looks like. There are plenty of established projects that don't use a "pull request" workflow, Emacs only recently migrated to Git; I don't have the discussion from ESR around migrating Emacs to Git handy, but it was a pretty slow process to "bring Emacs into the 21st c…
Can anyone explain slack to me? It just seems like a shitty reinvention of IRC.
In short: Slack is what you get when you have a team managing an IRC server with all the nice plugins and bots and building a single UI that does everything. You can spend your time setting up the same thing, or you can go to Slack.
Earlier quoted context omitted.
> I'd love to agree. But with IRC you've no guarantee, for instance, that an offline user will receive notifications when they sign in (plus multi client handling). > Slack has search for history, which is huge. No more "eh we talked about it". For functionality like that it sounds like a mailing list would fit the use case better. > Onprem is great. But it's a hindrance for quick adoption. It's not either/or. Think…
> For functionality like that it sounds like a mailing list would fit the use case better. Then you're looking at an email with the visual noise of recipients and whitespace and signatures, and if the UI is really bad (mailing list websites, for example), every message is viewed in isolation without the responses.