Never belittle your customer and never assume that they hold you as the pinnacle of excellence. Most customers understand with success come mediocrity. For those customers that don't, learn tact and how to close the conversation GENTLY or pass the support to your manager.
If you don't feel offended by the entire tone of this post, then I think we live in two very different worlds. Paying customer or not, public interaction is very difficult to manage well.
..... from Kyle...
Will,
For reference, I deal with 89 repositories I have access to. I have no issues with the repository lists. Keep in mind:
If you don't know what repository you want to work on, alphabetical order will have absolutely no effect. Alphabetical order is only helpful when you know what the repository starts with. If you know this, use the filter.
If you're coming to a new project, I sure hope your co-workers / manager have told you what the name of it is. Just type in a few letters of that name and you've got it.
I have a really hard time believing you don't know any portion of the project's name you're looking for. I can see not knowing the entire name, but even two or three letters usually narrows the list down to ~5-10 repos.
If this is really important to you, you can always use our API to develop a custom dashboard for your company and implement all these features. http://develop.github.com/ — or even write a chrome extension / greasemonkey script to re-order/re-arrange the repository lists as you see fit.
Really, if the problem is you need to communicate to your employees that certain repositories are important for a period of time... tell them. Email, phone, in-person. We don't deal with communication problems on GitHub, we deal with technical problems.
I know it can be sort of heartbreaking when companies don't accept your feature requests, but we're here to look out for all of our users, and a lot of times that means not implementing features for the greater good.
I have to hand it to Kyle. That's just how we roll on 3rd shift!!! But on a serious note, I suppose this just shows that customer service is quite a difficult thing to balance. I recall seeing some similar interactions between 37Signals and their customers as well. If you build opinionated software then unfortunately not all opinions agree with yours. But how you handle the exchange of opinions is quite a fine art.
I particularly like this line "We don't deal with communication problems on GitHub, we deal with technical problems."
ok...I'm done with my break. Time to go deal with those damn customers again. Can you wake me about 15 minutes before 1st shift arrives? I need to prepare the handoff report for the EMEA guys. :)
If you don't feel offended by the entire tone of this post, then I think we live in two very different worlds. Paying customer or not, public interaction is very difficult to manage well.
..... from Kyle... Will,
For reference, I deal with 89 repositories I have access to. I have no issues with the repository lists. Keep in mind:
If you don't know what repository you want to work on, alphabetical order will have absolutely no effect. Alphabetical order is only helpful when you know what the repository starts with. If you know this, use the filter.
If you're coming to a new project, I sure hope your co-workers / manager have told you what the name of it is. Just type in a few letters of that name and you've got it.
I have a really hard time believing you don't know any portion of the project's name you're looking for. I can see not knowing the entire name, but even two or three letters usually narrows the list down to ~5-10 repos.
If this is really important to you, you can always use our API to develop a custom dashboard for your company and implement all these features. http://develop.github.com/ — or even write a chrome extension / greasemonkey script to re-order/re-arrange the repository lists as you see fit.
Really, if the problem is you need to communicate to your employees that certain repositories are important for a period of time... tell them. Email, phone, in-person. We don't deal with communication problems on GitHub, we deal with technical problems.
I know it can be sort of heartbreaking when companies don't accept your feature requests, but we're here to look out for all of our users, and a lot of times that means not implementing features for the greater good.