felipec

He acts as if he is though.

If you don't care about authoritarianism in the Git project, then why did you read a blog post titled "authoritarianism in the Git project"?

It's a good practice to a) split commits into logically atomic changes, and b) revert a change the moment it's understood that it introduces a regression.

GNOME developers don't follow these good practices. This is a fact.

The problem is solved for me.

Every time I have an issue on Xfce, it's always due to GNOME, and always due to bad coding practices. In this post I dig deep into my last issue, how I fixed it, and why it's still not solved upstream after three years.

So many things, but if I were to pick one, I would add a `git stage` command to work with the staging area (wrongly called "the index").

git stage add (git add), git stage delete (git rm --cached), git stage diff (git diff --cached), git stage edit (not possible today)

No, Linus Torvalds did not realize that, he thought he was going to get cancelled, so he _claimed_ he was going to change.

After the stormed passed he went back to being Linus.

I have successfully contributed *thousands* of patches to many large projects. I don't need help.

And as is very typical you are concentrating on the wrong thing. I am not important.

The bugs that ruby users are experiencing *today* are important. If I die tomorrow that's not going to change.

That's a red herring. If you want to discuss that incident feel free to comment on that post. This is different.

Thank you for the translation, I've updated the blog post with them. I don't see any new actual information though. For example in chunk 2 what I gathered from Google Translate was:

> What I call a date includes time. It's like a name given on a point on the time axis.

And now it's:

> When I say date, I am including such time. I think of this date as a kind of name assigned on a time axis based on certain rules. In space, it is like a milestone. There are actually more imperfect dates, which are also dates. Sometimes they can be identified by context and other information, and sometimes they can't.

What information did we gain?

Anyway, in chunk 1 you said:

> Since this is not common DateTime.parse('2001-02-03T04:05:06').new_offset('+0900') This is not common, so the description would be something like

But that's not a correct sentence, I changed it to:

> Since this is not common, the description would be something like DateTime.parse('2001-02-03T04:05:06').new_offset('+0900').

You can argue that attaching a time zone to a `%s` doesn't make sense, but a lot of people do it, and more importantly: it doesn't hurt.

If you do `Time.strptime('0 +0100', '%s %z').to_i` you get the correct result: "0". That is: the number of seconds since the epoch is correctly parsed. The time zone is extra information that doesn't affect `%s` in any way. In other words: it's orthogonal.

Just because people say it doesn't mean it's true.

And the reason why I made the post is that there's an actual important issue with rubygems, but I'm not allowed to comment. Users are being negatively affected for no reason. I have the fixes.

Ask any user negatively affected by this and they would tell you I should be heard. In fact, I've received emails personally thanking me for persisting and trying to get it fixed.

There's more important things than tone.

The comments are open. Any translator willing to help would be more than welcome.

Yes, it's the same time in different timezones. "0 +0000" is "00:00 +0000", "0 +0100" is "01:00 +0100": same time.

Yes, every culture has their idiosyncrasies, which is precisely the reason why mentioned them. If every culture is different, then different cultures... are *different*. Being aware of the differences helps understand where the potential frictions might be.

You are making assumptions about me, but what about Tanaka and Matsumoto? They are Japanese and they couldn't get Funaba to understand either.

Ultimately Funaba wasn't angry with me, he just ignored me, he was angry with Matsumoto for listening to me and telling him what to do. Could Matsumoto have picked "less combative words"?

Or is it possible that there was a problem with Funaba?

Pointing out idiosyncrasies about a language is not racism. I didn't even complained about the verbosity, merely pointed it out.

Moreover, if I didn't like the language why do you think I learned it?

Back in 2012 I encountered a bug that took me through many hoops to get fixed, all because of a single developer, which compelled me to start an infamous email thread.

This illustration begins with an example Linus Torvalds presented in order to explain his idea of good taste in code, and then digs much deeper.

Not many demanded a CoC. In fact then the CoC was proposed it as merely as a "just in case" proposal that others agreed was not needed at that particular point in time because the community was "relatively calm".

And I didn't engage in tone policing myself. I'm perfectly fine with people disagreeing with each other using whatever tone they'd like.

The fact that you are good at writing or reviewing code doesn't mean you are a good judge or moderator.

Yes, but if you have ten bugs you don't have time to analyze correctly you don't attempt to fix all ten poorly.

You pick the most important one and analyze it at depth.

What you want is to pick the most egregious alleged violation and explore it at depth so that it can be prosecuted correctly, defended correctly, and judged correctly.

You don't put ten allegations on the docket and then say "we don't have time for the defense, so guilty on all counts".

I don't think somebody dragged to court for ten accusations of crimes can be considered a "professional victim".

I did not choose to make this a thing, it was a thing even before I was notified of the verdict.

Personally I don't see the need to make this a thing and involve the PLC. If Elijah Newren had a problem with me, he could simply ask me "please don't contact me in the next three months" and I would gladly do that.

Enforcement should be necessary only after other methods of agreement have failed. But Elijah never attempted to contact me, and the PLC did no attempt to do any mediation.

One day I was simply notified: this is your punishment. And that's that.

Everyone already agrees "staging area" is the best term. That's the whole point of the post.

Isn't this a bit of a false dichotomy?

It can be *both* that git users should do a better job at trying to learn git, and that git developers should try to make the interface more user friendly.

Personally I prefer to focus on what developers can do because any change in the user interface done by one developer can potentially impact thousands, if not tens of thousands, if not millions of users.

Maybe next time try to actually read the article before criticizing it.

> The people that "broke" (hey, see the quotes?) the user experience you expected and liked are the people that steer the project. They are free to do that,

Yes, they have all the freedom to destroy their project.

> He _hated_ it.

We still do.

> That's cool. Move on. Use what is best for you.

You didn't understand the point of the article. Breaking user-experience is the absolute worst thing any software project could do. It goes against the "Linux way".

> The larger Gnome diaspora has been pretty instrumental in draining the swamp of hardware problems and dumb broken things.

True, but not particularly more than KDE, or any other environment.

Thunar.