Russell Coker: Terms of Abuse for Minority Groups
Due to the comments on my blog post about Divisive Behavior [1] I ve been considering the issue of terms of abuse of minority groups a topic of which racial abuse is only one aspect.
It seems that there are many discussions about which terms are offensive and when they are offensive, most of which are very misguided. Solving this problem would be an almost impossible task, but I have some ideas which may help to improve the situation. I would appreciate any pointers to better ideas in comments or in blog posts that are inspired by this one.
One common mistake seems to be the idea that there are global objective criteria by which a statement can be proven to not be offensive. In any language that is constantly evolving (IE any language that s not dead) this seems impossible. It is particularly difficult with a language like English which is widely used in different countries and cultures. If a member of a minority group claims that you have just offended them then it seems most reasonable to have the default assumption be that you have said or done something which is actually offensive. In such a situation an immediate apology for the misunderstanding should be well accepted, but a debate about who s cultural standards should be used for determining what is offensive probably won t get a positive reception.
It seems extremely difficult (if not impossible) for a member of the majority group to properly understand what members of a minority group experience. So therefore attempts to understand why certain terms are offensive are likely to be doomed to failure. Sometimes if a certain word is used and then a group of people immediately get really angry you just have to accept the fact that it s not a good word to use. One common example of this is words that are associated with violence if someone associates a particular term with a threat of serious injury or death then you won t be able to convince them that it s not a big deal, but there are more subtle things of a similar nature.
It s worth trying to understand people and these things can be productively discussed between friends. But a discussion of such things is not viable during the course of a debate. If involved in a debate with someone you really dislike it doesn t seem like a good strategy to start a meta-discussion about whether they should regard one of your statements as being unreasonably offensive (regarding minority group status) as opposed to the level of offense that is acceptable in debate (something like that s the most ridiculous argument I ve ever heard may offend the recipient but is not inherently unreasonable).
Words tend to have multiple meanings. Claiming that your intent was significantly different from the way your message was interpreted probably isn t going to work well unless accompanied by an apology. Even I m sorry you were offended (which is not the best apology) will probably do.
Finally I m sure that anyone who does Google searches dating back to 2005 (as an arbitrary year that references my previous post) can find examples of me doing things that go against some of these suggestions. I ve learned things since then, it s an ongoing process.
Application Indicators: A Case of Canonical Upstream
Involvement and its Problems
I always thought Canonical could do a bit more to contribute to the GNOME
project, so I was happy to see the work on
Note: Please see
Everyone knows that exercise can heal the body. But why only a few people who routinely perform the activity? Ask yourself.
The answer is, maybe you less motivated to do so. A survey ever conducted to find out why people rarely do sports.
The survey involving 15,000 women from 25 countries showed that although nearly half of them know that exercise is very important for health, but less than 25 percent of it done. Why?
More than two-thirds of respondents said that they would exercise more often if the gym was fun. So far, they consider it as a routine or demand to stay healthy so feel burdened.
Although the facts say so, but it is unfortunate if people take sport as a less desirable activity.
If you are not motivated to do the morning run, bike or fitness, try these few tips that may improve your mood for a workout without having to feel it as a demand or load.
1. Participate In A Club

Yesterday, I arrived in Bruxelles, coming from the Issy/Paris
I was interested to see Adnan Hodzic discuss
Agile Business Analysts?
I have recently been fleshing out my thoughts on the role of business analysts in an Agile team. This is something I have historically addressed on a case-by-case basis with clients, but when thinking about it last week at a client site, I realized that I do have a general take on how the role and responsibilities of a business analyst change when a group moves to using an Agile process. Per the usual, I ll be using Scrum as the example process where needed.
The Classical Roles
Historically the business analyst has had two primary roles. In a process where cross-functional communication and collaboration are minimized, these roles are essential. What little communication that takes place between the business and the software development teams purporting to serve them passes almost exclusively through one or more business analysts. I view the business analyst in a phased development approach as having two roles; Translator and Gatekeeper.
The Translator
The business analyst is primarily tasked with taking the needs of the business and translating them into a written document that is then handed to the software developers and testers. This role s necessity is based upon some fundamental assumptions. First, programmers and testers are on the whole, too socially retarded to actually talk to the business persons and find out what they want. Second, the business is primarily viewed as being unable to focus its thought long enough to tell the programmers and testers what they need. Since a key value of an Agile approach to software development is to have individuals and their interactions be the driving force rather than processes an tools (see
I m using Gnome as my default DE after
News is slow this month on the FusionForge development front. We're
all busy gathering all the things that we want to go into the next
release, but there's no big news from the code. However, there is
something of interest.
You may have heard about the Coclico project, which is an initiative
aiming at collaboration and convergence between several forge engines,
most notably FusionForge, Codendi and Novaforge. That project was
started last October, and it holds regular meetings with its members.
The next meeting is scheduled for the 2nd of February in Paris, and we
thought we could host an open meeting on the 3rd for non-Coclico
members, a bit like the forge meeting we had last year (which is when
FusionForge was officially born), but with an emphasis on what Coclico
did so far. Since most of the FusionForge hackers are in Western
Europe, and several are in Paris (especially if we add those who go to
Paris for the Coclico meeting), we thought it would also be a good
opportunity to gather for a technical and social meeting.
It seems the Coclico open session didn't generate much interest this
time (at least, it hasn't so far), so I proposed to hijack the room
for this FusionForge meeting, and I didn't hear any objections. I
have several themes I'd like to discuss with people, and possibly
start implementing during that day:
