>I'm not sure how many times I have to say it:

How long until you get clued in that maybe the problem is not with the end users but with your UI?

This is, however, kind of counterintuitive for most people. Principle-of-least-surprise suggests you could do something about this; split the dashboard, say, into projects you participate in (indicated by having committed) and projects you've been invited to. You don't need the separate approval step there, so the workflow's the same, but it'd feel much more obvious.

Also; with the "professionals" thing - I totally get what you mean, and it's abundantly clear you guys are doing things for the right reasons, but the tone kind of jarred with me a little bit there. Nothing drastic, but I'm a person first, a professional second...

In a different thread jmaygarden said:

I got "dong markup" in my RSS reader from pull requests to zedshaw/mongrel2 today. So, the trolling was very much in public view.

So, there are ways to publicly troll someone on GitHub, even if not in this precise way.

Up until just now, I didn't know that. And if you didn't reply to my comment just now, I still wouldn't know it.

And you explicitly telling people about how being a collaborator works isn't a scalable way for people to find out. And it sounds like this question/issue has come up before. Perhaps it can be made clearer somehow?

In any case, thanks for clarifying when you become visible as a collaborator, even if only in this one comment to me.

Your comment [1] is a direct reply to one where kneath explicitly states it [2].

    [1]: http://news.ycombinator.com/item?id=2606063
    [2]: http://news.ycombinator.com/item?id=2605804

For me, it was pretty obvious because it doesn't show up on the profile under 'Public Repositories', only on the dashboard in a list of projects you have access to.

I think he means making it clearer in the UI. It would be weird for Github to depend on HN to inform users.

The thing is that this is amazingly rare. The handful of times it's happened, the 'victim' most likely just removes the repo (which has always been possible) and that's the end of it. Others might say to their friends on IRC "Hey, can you see dongml in my projects list on github?" and sure enough the answer will be 'no'.

It's easy to say "oh just add it to the UI", but to actually do it is another story. Before you know it you've got hundreds of preferences, and then people will be complaining that there's too many options and it's too confusing (a-la facebook privacy settings). Honestly, GitHub's preference pages already need some work, so I for one am glad they don't add drop downs for every person's pet feature.

Regardless, it doesn't matter now. Now you just remove the project and block the user (or, presumably, just blocking the user might remove the repo... either way), so that's that.

I'm not sure we're talking about the same thing. I mean making it more clear in the UI that there's a separation between projects where you're a committer, and where you're just invited (to use another poster's words). If an (apparently) Github employee feels the need to wonder how often he's going to have to explain it, it seems that there exists a common confusion in the distinction.

Yea sorry I tangent-ed a bit there. Probably because I just think this is a non-issue. It's in the UI in that it's listed in your repositories you have access to, but not on your profile. I don't see what kind of UI change they could make that would make it clearer short of text or a tooltip or something, and I think that the %0.001 of users who would ever care is just not worth the time to even considering it. The reason kneath was wondering how many times he had to say it is because it's all over this thread -- including the direct parent of the asker in this case.