Anonymous sniping is masturbation at best.

I agree that this would be interesting. In the case of my own stack, I tried to stick to software that I've worked with directly or have configured in some non-trivial way. Because if this, I left out ... [More] stuff like GTK+, hal, dbus, udev, libpng, etc., despite the fact that I use many of them every day. It would be nice for the developers of those projects to get credit for the fact that their software made the development of the stuff I did put in my stack possible. One tricky thing would be what to do about projects like Fedora, where there are a lot of potential dependencies that might not be used by all Fedora users. A good example is GNOME, which most Fedora users use, except the ones that choose KDE :) [Less]

I believe you should be able to claim your preferred name and then use the "alias" feature to combine the contribs of the two logins (under "Edit" -> "Aliases").

I think the issue is that the enlistment for Sawfish's repository was already part of the GNOME entry.

Hmm... This seems to have sorted itself out. I guess the only question now is whether I ended up creating a duplicate. The contributors list for the project seems correct.

I just added an entry for the Sawfish Window Manager. After adding the enlistment, the status on the enlistments page was immediately "Ohloh update completed 13 days ago". However, the "Code" tab ... [More] indicates that the report is in progress and there is no contributors list. I did a search for "sawfish" before creating the project, but maybe it already existed and I missed something. [Less]

Thanks for the reply. When I was talking about tagging projects for language affinity, I was really talking about using tags like "portuguese", "brazil", or "brazilian" on projects, not about ... [More] translating tags themselves (although that's its own can of worms). If you wanted to get into real i18n/l10n, you'd probably want to represent the languages used by a project as first-class metadata, not just normal tags. That way you could localize the description of which language(s) are used/supported by a project's developers and user community into the site user's own language. As you say, localizing tags in the more general case could be problematic to say the least. After I posted my message, I noticed that the GamesToolsBr project already had descriptions in Brazilian Portuguese and English. This works when the descriptions are short and there are only two languages, but the 800 character limit could become a problem when you start getting longer descriptions and more languages. I'll take a stab at translating GSW since the description is relatively short; I'd imagine that anyone that gets interested in the project will quickly notice that the developers and users are all using a language other than English :) [Less]

You would be better off asking your question in the Hibernate forums at http://forum.hibernate.org/

I've been playing around with Ohloh for the last few days and I'm impressed by the breadth of projects already represented. Despite the fact that many of these projects have been created and ... [More] maintained by non-native speakers of English, it looks like the vast majority of project entries are in English. However, I just came across the "GSW" project that has a description in Portugeuse. My question is this: What do the people running and using Ohloh think of this? Should all entries be written in English as a lingua franca or should they be in whatever language the original poster decides to use? Should it be possible to categorize or tag projects with their language affinity? Should it be possible to maintain descriptions in multiple languages? I don't expect there to be canned answers to any of these questions, and I didn't see any discussion in the archived forum posts (I searched for "English"). I was thinking about translating the GSW entry into English, but then I figured I'd ask what other people think. One potential issue I can see with translating such entries is that it could give the false impression that the developers of these projects are willing and able to deal with people speaking languages they may not understand. [Less]