process Shanley's feedback

[chadwhitacre]

I had a conversation with Shanley on Twitter last night, in which she provided a good deal of feedback on "open companies" vis-a-vis marginalized people. I've collected her feedback here:

https://medium.com/building-gittip/2e39b7ed12d                        ^^^ Raw tweets there, see below for a copy/paste edited for readability.

What do we need to learn from this?

[Posting in the BG repo instead of www because this is big picture. Since this is important and not everyone is watching BG yet, I'll post and close an issue in www as a notification.]

[chadwhitacre]

The thing that jumped out at me the most is:

More important than "transparency" is consent, making people feel comfortable, privacy, and outreach.

How do we need to modify our understanding and articulation of what an open company is to account for this?

I'm also seeing a caution about letting a "theory of running a company [be] more important than applying judgement to situations." In what ways do I/we do that?

The third thing I'm seeing is:

Maybe your insistence on "Radical transparency" is alienating one of your top user bases and making them not engage with you.

How do we take this on board?

[chadwhitacre]

BTW, Shanley made it clear that she doesn't want to be involved in the details of this conversation:

guess it didn't occur to you i maybe have plans this evening besides fixing structural problems in your company for free? lol

https://twitter.com/shanley/status/467098076105019393

okay look i'm not interested in being the arbiter or judge of every act you've taken. i shared my thoughts, and that's it i don't want to have a dialogue about it with you.

https://twitter.com/shanley/status/467103601987301376

please note: just because i share my thoughts on your company doesn't mean i'm interested in a play-by-play or discussing it with you.

https://twitter.com/shanley/status/467103869026058240

After initially creating this issue I changed "Shanley" in the description to her GitHub @mention. Then I remembered these comments and I changed it back to "Shanley." I don't know if GitHub will have notified her or subscribed her in this case, but if so: Sorry, Shanley! I would unsubscribe you if I could (but you can at least unsubscribe yourself). :-)

[chadwhitacre]

Here's a copy/paste of Shanley's feedback, edited for readability:

[to me]

Honestly, I don't want an interview I do with you live streamed on the internet because "transparency." Not everyone is in the privileged position of being able to have all kinds of shit on the internet "openly" w/out getting harassed. But i might write a critique of how "open company" interpreted in that lens breaks down when you're NOT in that kind of privilege.

[to twitter]

So here's a thing someone wrote about "open companies":

Increasingly, I’ve been asking people who want to Skype if instead we can have an open call that we live-stream and post to YouTube.

This is not safe for many people, period.

[to me]

I also don't mind sharing that I find it INCREDIBLY concerning that you want to live cast everything online when many of your TOP users are from marginalized groups that get harassed and stalked endlessly online. Frankly a lot of the statements you've made about "open companies" don't seem to give a fuck about those users. shrug

[to twitter]

I love Gittip and increasingly myself and friends and companies rely on it, but i am scared of the philosophies of the person that runs it. If you look at the list of top people on Gittip - lots of diversity advocates in tech. They are driving a ton of adoption. Most of what I've seen from "open company" is hubris from privileged white men who think "Radical transparency" matters more than judgement. If your weird, overblown, overdramaticized theory of running a company is more important than APPLYING JUDGEMENT TO SITUATIONS, well ...

[to me]

I've noticed that a lot of people you are having "open calls" with are likely almost all men. Yet your top users are women and organizations focused on diversity. Maybe your insistence on "radical transparency" is alienating one of your top user bases and making them not engage with you. After reading some of the things you wrote about open companies, I thought REALLY hard about even joining Gittip. Not the only one.

[to twitter]

I run a company that relies on many people who are marginalized and underrepresented in the community, much like Gittip. More important than "transparency" is CONSENT, making people feel comfortable, PRIVACY, and Outreach.

Welp, I had that thing about Gittip waiting inside me for some time now. lol.

[retweet] People need to remember it's a means to an end and not always an appropriate one.

Honestly we need more strategies/philosophies for companies that come from WOMEN.

[patcon]

Just wanted to chime in to say that I'm thinking about this. To be honest, I find myself a little angry at Shanley for the way she approaches some of this. I also feel that my anger likely isn't fair, and is perhaps largely defensive, so I'm going to take some time to think through this and make sense of it.

[tshepang]

That was just too angry of her; I feel like these are undeserved attacks on @whit537 (unless she just talks that freely). Anyways, we had a big discussion about an issue like this in https://github.com/gittip/www.gittip.com/issues/1683.

[chadwhitacre]

I'd like to focus on the feedback she gave us and not the way she delivered it. I think the better we're able to do that the more productive this conversation will be. :-)

[duckinator]

First off, let me just say that I agree with @whit537's last comment: what anybody thinks of how Shanley presented it doesn't matter at all. It truly doesn't. People's thoughts on that is wholly irrelevant to the issue at hand. What she has said, however, is still important. Thanks for starting a discussion about this, Chad.

I believe Shanley has a very good point. As much as I love this idea of radical transparency, it seems anything that can be accurately described as radical has a very high risk of leaving out those who are already marginalized. The level of transparency in GIttip is by all means radical. I am an exception -- not the norm -- in that I am both part of one of these marginalized groups (by being a trans woman) and am willing to take part in the most transparent portions of Gittip. It is honestly probably not the best idea for me to do so, and I feel I have an obligation to point that out on behalf of those who aren't willing to take that risk. Because it is a risk. It is a huge risk.

Some of the most significant Gittip users are part of demographics that frequently get screwed over in the most terrible ways, and it's simply not always safe for them to take part in that level of transparency. While I applaud the attempts so far at accommodating them, I think we need to find a way to accommodate them without the unintentional connotation that we prefer those who are willing to take part more publicly.

I am not sure how to do this. The way to approach this needs to be a community decision, and we need to explicitly get feedback from people in these groups. I just want everybody to be able to be directly involved in Gittip if they want to be, and this has to be acknowledged before we can accomplish that.

[duckinator]

There's also these two Tweets, which I think summarize the issue very well:

i've noticed that a lot of people you are having "open calls" with are likely almost all men.

yet your top users are women and organizations focused on diversity.

Basically: By trying to force a level of openness that is not safely attainable for some of our largest userbases, we're inherently biasing Gittip as a whole.

[chadwhitacre]

we need to explicitly get feedback from people in these groups.

Besides yourself, @duckinator, who else do we need to hear from? @rummik and @Changaco both decline to participate in video calls, so we should at least hear from them. Who else?

[duckinator]

I reached out on Twitter. Hopefully somebody will speak up there, here, or privately (I offered to discuss it privately via email with anyone who wishes to do so).

[galuszkak]

As far I remember I was one time call with @thefoxis ;) So there are some women out there on gittip calls :)

[duckinator]

@galuszkak that's true, but a few women being willing to join doesn't mean we're done. It's not merely a checkbox of demographics we need to snag a certain number of people from. It's an ongoing issue -- we're going to continue running into situations where Gittip's openness and transparency butts heads with some people's well-being. We have to handle that fully, not partially, and that means continually iterating everything about how we work.

[rummik]

Hm. I'm not really sure what my suggestions for this are. Though I do know that I personally feel a bit left out when recorded calls are happening that I should be part of, and text is a very slow medium for me, so when I am participating via chat, I lag behind. <.<; I'm fine with private calls though, so long as it's with people I know IRL, and not being left open to anyone who feels like popping in.

[rummik]

Sorry about that. I keep reading 'close' as 'cancel'. :/

[duckinator]

From various discussions: it seems a good starting point may be to offer both an open call and to talk privately when initially asking someone to talk. Don't specify the mediums -- just ask if they want to talk, and offer to do so via either an open call or privately. Decide on the medium after that decision is out of the way.

If you're willing to try both, you need to list both at the start, not ask for the one you prefer (open calls), and only offer the other (private communication) after they recoil. You also want to avoid listing the mediums used at the start, because it's entirely possible that they may not have access to or choose not to use the specific ones you choose to list. Once you've decided on public vs private, list what you're able/willing to use, ask them to do the same, and basically play it by ear from there.

@whit537 thoughts?^

[duckinator]

Note that the idea I mentioned above doesn't solve this entirely. It's only the first step. There's still other issues to handle. For example: the standups being in Hangouts is awesome. However, while we try to accommodate people who aren't willing to be in a public video chat, they are very much treated as second-class citizens: we entirely fucking forget about them sometimes. And when we don't, we still aren't letting them speak for themselves -- they provide a summary, and someone speaks on behalf of them. They're not given any other choice, really. These are the kinds of, often very subtle, things where our openness and people's ability to directly contribute to Gittip are in conflict, and we've got to resolve it somehow.

[patcon]

Part of me wants to play it safe as I'm an outsider to the main concern, but I have a thought in regards to psychology and sales-think: In sales, you usually try to make it as easy as possible to say "yes" to the thing you prefer. So you try not to have a big open-ended spiel like "so here is fact X and fact Y and qualifier Z, an what do you want to do?". Instead, you present it in such a way that it's a simple "yes" or "no". As in, "here are all the details and here's specifically what I'm hoping we can do, and are you interested?"

That's not to say I want to force people into open calls, as obviously we'd want to still talk if someone were uncomfortable with that. But I don't see a problem with framing it like an open call is preferred, as I think Gittip's philosophy dictates that it usually is.

Most everyone will say "private" if presented both options, and who are we to say that one person's concerns deserve private while another's don't? Hence me preferring to lean on "open", and allow private with minimal rationale for those who feel strongly.

[duckinator]

@patcon there's two majorly different approaches:

1) Ask for an open call; if they recoil and say no, offer to have a private call 2) Ask to talk with them, offering both an open and private call at the start (possibly even saying we'd prefer the open one as long as they're okay with it)

If you want to go the psychology/sales-think route: don't upset the person you're trying to get to make a decision, because they'll often just avoid any decision at all or choose an even-less-preferred third option (such as not talking with us at all).

[patcon]

My understanding is that, framed the right way, the third option doesn't tend to happen :) Hence the reason the psychology of sales hasn't abandoned that approach.

I mean, I say this because I think we have a preference -- openness. I personally want to throw that under the bus for the sake of conversation, but we have a preference nonetheless. (as I understand it)

[duckinator]

It's entirely okay to have a preference. It's even entirely okay to explicitly state that.

However, as we've been doing it, we're basically withholding that information unless a problem arises. I find it weird to withhold the fact that we're 100% okay with putting someone's comfort above openness until they're about to give up, which is effectively what we're doing. It serves no purpose but to cause stress.

[duckinator]

There's also a third option I've never seen presented: a private conversation, followed by a written follow-up, the contents of which are not published until agreed upon by all parties involved.

[duckinator]

IRC

[chadwhitacre]

Let's also be clear on some distinctions here, between:

• Interview requests to me from journalists.
• Conversations we have in the course of building Gittip together.
• Conversations we have about our users (see https://github.com/gittip/www.gittip.com/issues/2125).
• Conversations we have with our users.

The situation with Shanley was actually the last [edit; I had switched the order of the list and neglected to change here:] first of these. She and her former business partner reached out to me in December asking for an interview, and it didn't work out at the time because they were in stealth mode and I only do open interviews if I can help it. We left off in December saying "let's touch base down the road." That was the context for my question whether now was a good time to revisit the idea of an interview, after a mutual follower suggested a collaboration.

@duckinator What context are you referring to when you say, "it seems a good starting point may be to offer both an open call and to talk privately when initially asking someone to talk"?

[duckinator]

@whit537 I was actually referring to the discussions with Shanley yesterday.

See this:

@whit537 honestly i don't want an interview i do with you live streamed on the internet because "transparency"

and this:

@whit537 not everyone is in the privileged position of being able to have all kinds of shit on the internet "openly" w/out getting harassed

If we want to truly be inclusive, we need the option of private calls to be presented up-front. Regardless of whether or not this is intended (I don't think it is), offering to talk privately only after an open call is refused appears closer to begrudgingly giving up on what you want than actively prioritizing their comfort and safety over your ideologies.

Open calls won't always work, and I feel that trying to force them will cause considerably more issues than it solves. I feel that in all of the cases where someone is talking to another person/company on Gittip's behalf, we need to find multiple approaches to offer, and go with the one they're most comfortable with. There may be cases, e.g. with companies, where private calls are rarely (if ever) done. Perhaps any other methods we come up with won't work in certain circumstances, either.

[chadwhitacre]

I was actually referring to the discussions with Shanley yesterday.

With journalists, I've decided on a personal policy of only doing open interviews. What would be the reason to make an exception in Shanley's case?

If Shanley had emailed me and said, "Chad, as a user of Gittip I have feedback that I'd like to share with you confidentially out of concern for my {safety,privacy} and/or the {safety,privacy} of others," then of course I would accept the feedback confidentially. But she didn't contact me as a user of Gittip, she (actually her former business partner; Shanley cosigned and was cc'd on the email) approached me for an interview as a member of the media.

I see the matter of my open interview policy as being something between me personally and the media. That's the terms on which I'm personally willing to deal with the media. I recognize and accept the opportunity cost associated with that policy, namely, not doing some interviews.

Since this thread is about Gittip as an open company, I'd like to take my personal policy re: open interviews off the table.

[chadwhitacre]

Instead, I'd like to focus this conversation on the latter three categories:

• Conversations we have with each other in the course of building Gittip.
• Conversations we have about our users.
• Conversations we have with our users.

To which we might add:

• Conversations we have with our business partners.

[duckinator]

@whit537 I get the impression that sometimes people in the media don't feel comfortable being in an open call for their own personal safety, not because of reasons related to media and such itself, and that that is where Shanley was coming from. I'm genuinely unsure how to approach that.

Setting that aside, and looking at the other things you mentioned:

• Conversations we have with each other in the course of building Gittip: we can still be transparent without requiring audio/video recordings of things. Perhaps we should look into a way to use Hangouts -- but not on-air, generally -- to discuss things, and a written summary available somewhere?
• Conversations we have about our users: (nothing atm)
• Conversations we have with our users: unless these are in a public medium (IRC, Twitter, GitHub), these should default to private; explicit permission before discussing publicly. On public mediums, there are special cases -- e.g., there are cases where you would want to ask before retweeting things on Twitter. There was a case earlier where I probably should have, but didn't.
• Conversations we have with our business partners: I believe these should default to being open calls. These are the things where we may not want everyone to be able to join in, but there will be a ton of people who aren't joining in but will be interested.

[pjf]

I'm running errands today, and so I haven't read the bulk of the discussion on this ticket. However I am someone who's brought up issues of Gittip being too transparent, and for not checking consent before sharing details of support tickets in the past. It's certainly not a secret that I fall very much into the intersectional feminist camp, and one the greatest reasons I adore Gittip is because it is supporting diversity advocates, and I strongly believe that's making the world a better place.

I'm really, really glad these issues have been raised. It's important that we don't have a reaction to feel that we're being judged here. Greta Christina has brilliant article on how homogeneous groups can completely miss issues relating to different demographics, simply because they've never been in a position to experience those things as concerns. It doesn't make them bad people.

In fact, I'm delighted that we're having this discussion. Gittip is already head-and-shoulders above so many other projects in terms of governance, and I think with a little work we could reach Dreamwidth levels of awesomeness. (Dreamwidth is my gold standard for inclusiveness and diversity in an open source team, and they rock so hard.)

For the record, I agree strongly that consent should trump transparency. I'm sure I'll have oodles more to write when I get back to my keyboard and have a chance to read through the thread properly.

~ Paul

[kittenpies]

it is i, the evil shanley.

RAWRRRRRRR

literally eating pies made out of kittens as i type this

so.

i scrolled past a bunch of the tone policing defensive bullshit and typical pontificating about hurt feelings from sensitive crybaby bros, but just wanted to chime in with a thought.

(please note that i am overcoming my severe hatred of github to do so, so as a tribute, fuck you pay me, you can see my payment address at gittip.com/shanley where i am not only in the top 3 of Gittip receivers, but one of the top 3 of Gittip givers, so yes, while y'all fucking complain about how angry i am, i am one of your top users, one of your ONLY power users and you should treat me with some fucking respect while you're at it)

without commenting on specifics of your policies and approaches which i found TLDR, i think that it is essential you keep the following in mind, a premise that i have not seen reflected in any way in the operations of gittip, which is:

People from marginalized groups are the most important group of users on gittip.

Let me say that again.

People from marginalized groups are THE MOST IMPORTANT group of users on gittip.

people from privileged groups are doing JUST FUCKING FINE on the normal funding mechanisms, and have no SUBSTANTIVE reason to seek non-traditional funding sources like gittip. (note: californian faux-liberalism and rich white dudes who are like "oh cool bro A CROWDSOURCED ECONOMY" do NOT live up to the bar of 'substantive reason'.) thus they are, and will never be, an appropriate user base for an alternate funding mechanism such as gittip. (i guess unless you basically want to be known as the platform where dudebros trade cups of coffee as a proxy for heteronormative male bonding instead of a platform where people who need it can actually "depend on money received through Gittip in order to pay their bills" which last i checked your about page, is on your goddamn about page.)

This hypothesis, specifically:

"People from marginalized groups are THE MOST IMPORTANT group of users on gittip."

is easily proved out by your top users. Of your top 9 users, 6 of them are individuals or organizations members of, and/or dedicated to community development, advocacy, outreach, activism etc. among, marginalized groups. So. there you go.

If you are NOT at EVERY DECISION your company makes PRIORITIZING the needs, concerns, etc. of people from these groups then you are basically directly undermining not only the source of all of gittip's current success but also its future success.

I have to seriously question your commitment to that success when the company's founding principles seem to be more focused on radical transparency, which is incredibly alienating and threatening to your core audience, than on a company philosophy that is acknowledging and empathetic to that audience.

Again, not a comment on any specific policy, but an overriding impression of gittip i have as one of its top users.

Carry on.

[duckinator]

FTR, I'm entirely in agreement with @kittenpies' comment on this issue, I just wasn't able to articulate it as well.

[juliepagano]

I think it is useful to look at what happened in my feature request from a few months back. That was a case of me interacting with potential users of the system, hearing their feedback, and then advocating for it.

The people I got that feedback from would have likely recoiled and been upset if my response to their concerns was "let's do an open call about this" instead of having a more private conversation where I was able to do a lot of listening and understand their needs. I think they also would have been frustrated navigating some of the back and forth that happened on the issue on gittip (mostly useful discussion from a company/development standpoint, but not necessarily something a user wants to engage with). In that situation I acted as a sort of "user advocate," and I think that may be a useful model for handling similar situations in the future.

I think user advocates need to be people who are a bit more separated from the core structure of the company. Someone who is heavily invested can often feel the need to direct the user's conversations a certain way, take criticism personally, or even try to argue with the user. Think of doing user studies - it's often best when the developer of a feature doesn't run the study because they can be a bit too invested. Ideally, a user advocate is having a conversation with the user and learning about their wants, needs, concerns, etc. - they are listening and collecting information. They can then summarize that information, present it to developers, and advocate for changes that will value those users. It would be useful to have advocates who understand and have experience with the demographics you want to engage with (e.g. feminist activists, members of various marginalized groups, artists, OSS developers), so that they have a better sense of how to have meaningful dialogue with them.

On another note related to this topic...several times now, I've seen someone mention something related to gittip (or potentially related like the "open company" thing), but not directed address the gittip twitter account, and have someone related with gittip respond and push them to engage about it publicly (either on twitter or suggesting a public call) and often a bit aggressively. I think this is meant in the spirit of open discussion, and I can see being concerned about criticism about gittip. However, it can be a bit frustrating or even intimidating for people, and I think it's often doing more harm than good. It reminds me a little bit of the overaggressive "brand" twitter accounts that tweet at people who mention anything vaguely related to them. They generally do not engender positive feelings, and I think you want to avoid straying into that territory.

I think you need to provide better avenues for your users to provide feedback. Right now, the only ways I know of are to create an issue on github, tweet at the gittip twitter account (140 chars is not really conducive to clear feedback), or bother one of the contributors I happen to know in person (not a feasible option for most of your users). If you want to care about users besides OSS developers (your top receivers and conversations I've had with members of the project suggest you are), posting an issue on github should not be a requirement for providing feedback.

Shanley's comments above are spot on. A lot of focus seems to be on the open/transparent/etc. company part of gittip. I see and hear less about the focus on the users. I remember you doing some user studies early on. Maybe it's time to do another round and think about how you want to balance things as your user base has changed.

[ashedryden]

Chiming in as someone who is also at the mercy of the open company policy and a top user of Gittip --

I've had multiple issues where my personal safety and comfort have been trampled because of Gittip's policies:

1. Being peer-pressured into communicating with someone who has had a sustained campaign of harassment against me on twitter, requiring multiple requests from me and other people for the behavior to stop before it did.
2. On multiple occasions people being retweeted by either the gittip account or Chad, I don't remember which, that were attacking me either for my "panhandling" through gittip or the fact that they don't think I'm a programmer and therefore unworthy of receiving the compensation for the work I do.

Giving harassers a platform to harass marginalized people, especially where their income is involved, has serious implications on the safety of the service for marginalized people. These are excellent examples of how this policy is ill-suited to understand or account for the safety, needs, or consent of marginalized people using Gittip.

It's frustrating, disheartening, and scary because I've been lucky enough to be able to support myself off my earnings from Gittip, which puts me in a precarious position. Bringing up these issues reminds me that a small group of people controls my income, regardless of the large number of people who contribute money to me. I feel that I'm locked into a platform now that may not even be considering my safety or other needs/wants as a user.

You might consider reading http://www.ashedryden.com/the-risk-in-speaking-up and http://modelviewculture.com/pieces/dissent-unheard-of

[ncoghlan]

In addition to the points that have been well made above, the recent Twitter exchange (which Chad quotes above) reminded me of the issues around the use of pseudonyms on social media networks. For those that haven't been following those discussions, see https://en.wikipedia.org/wiki/Nymwars and particularly https://www.eff.org/deeplinks/2011/07/case-pseudonyms and http://geekfeminism.wikia.com/wiki/Who_is_harmed_by_a_%22Real_Names%22_policy%3F for context.

I believe that, unless managed carefully, "radical transparency" in an organisation can have the same excluding effect that "real name" policies do in social media, because acceptable levels of risk vary based on individual circumstances. While I personally think radical transparency is an interesting approach to tackling many of the issues that make many modern enterprise organisations toxic cesspools of humanity, there are also good reasons for forgoing transparency in particular cases. For example, Gittip deliberately keeps the giver/receiver links private, as the aim is to be a vehicle for "no strings attached" support, where funders want recipients to be free to do what they want to do.

I see shifting the perception and fact of Gittip's organisational model from "transparency at any cost" to finding a more nuanced balance between a baseline desire for transparency at the organisational level, while respecting the privacy of the individuals that interact with the organisation as the core concern here. The "user advocate" concept @juliepagano mentions above reminds me of the ombudsman role that exists for various industries, as well as the independent reporting officers and hotlines that may be put into place within large organisations to help provide a trusted avenue for reporting issues without the individual reporters facing personal retaliation from their management chains. Individuals in such positions are obliged to treat issues as being reported to them in confidence, while still also being able to take action to address concerns that are raised.

In many ways, these aren't new problems - they're ones that have existed in organisations since time immemorial, and there is a lot of information and experience available regarding what does and doesn't work. Perhaps, like Github, Gittip needs to figure out a way to bring greater expertise to bear on some of these concerns. Unfortunately, unlike Github, "just start hiring professional HR staff" isn't an available option.

[rummik]

@ncoghlan Anonymity is probably the only reason I've been safe as I am, and is also the reason I don't fully participate in open calls. And though lately I've been trying to leverage that a bit more and keep it as part of my online persona, I don't really like that it's something I've had to do for so long.

@whit537 In regards to categories and interactions using Hangouts and calls: I talked a bit about it on IRC.

Since Hangouts is the medium I have the most trouble with, and it interferes a bit with my anonymity, and I know the problems I'm faced with when using it, I'm probably going to be focusing on that and areas that can be improved in. Hopefully it'll wind up helping other people too.

[duckinator]

@kittenpies @juliepagano @ashedryden @ncoghlan: thank you all very much for your input here. I really appreciate all of you putting in the time to write such detailed responses. I've split out a few things from this issue into smaller, more easily actionable tasks. Please let me know what you think of them.

---

1. We need to draft a policy — or, more likely, a group of policies — that, basically, reigns in our transparency when it has the potential to harm others. I'm all for transparency -- but we have clearly crossed lines more than once, and it needs to be addressed properly. See #54.
2. I really like the "user advocate" idea. I think we need to look into creating a proper separate team for this, made up of (as @juliepagano suggested) people who are not as close to the actual development of the product. See #56.
3. We need a better way to handle support for non-technical issues. This seems to be an ongoing weak spot for us. See #55.

[catch56]

Another thing to remember with open calls, even if recorded, is that they are heavily biased against people who aren't able to attend at the actual time, whether work/family/time zones etc. Just because theoretically anyone can attend doesn't mean that they actually can in practice. It ends up skewing things towards those with no commitments and lots of time om their hands.

A non-broadcast conversation with minutes, or anonymous chat log is no less transparent than an open video call. Since it's then text search/scan readable after the fact. As mentioned earlier in the thread it's always possible to get summaries/transcripts signed off by the people involved if you're worried about misrepresenting people, and it saves a lot of the exposure/privacy concerns of having every single conversation public in real time (and to an extent allows onee party to be anonymous while Chad or whoever isn't).

I can somewhat see the arguments for the people who run gittip being always transparent, but not forcing that on everyone who interacts with you.

[pjf]

+1 @kittenpies, @juliepagano, @ashedryden, and @ncoghlan. +1 especially @duckinator for spawning off issues, suggesting we get policies and codes of conduct on communication, and organising things. Thank you.

[Changaco]

@whit537

@rummik and @Changaco both decline to participate in video calls, so we should at least hear from them.

I'm not sure what you want from me, really.

All I can say is that I don't share @rummik's feeling of being "left out", and that the transparency of Gittip doesn't bother me.

[chadwhitacre]

Hey all, quick note to say thank you for participating in this conversation, especially @kittenpies @ashedryden @juliepagano @ncoghlan and @catch56. In Turning Down TechCrunch I said that "my ideas on when to agree to private calls and when to insist on openness are still very much in formation," and that's still true. I DON'T believe that "radical transparency" is an absolute good or an end in itself (is that even a term I've used? not seeing "radical transparency" here here or here), and I DO believe transparency (sharing information) and openness (sharing control) need to be balanced with "CONSENT, making people feel comfortable, PRIVACY, and Outreach." This is awesome feedback and an important conversation whose time has come, and I know it's going to help us make Gittip and the concept of an "open company" even better! So THANK YOU for the feedback and also THANK YOU FOR USING GITTIP. You're all doing great work and I'm humbled and honored that you've chosen to trust Gittip so far! THANK YOU! :-)

Secondly, a couple apologies:

@kittenpies I'm sorry for tone-policing you above by changing your all-caps to lowercase. :-( I've reverted that.

@ashedryden I'm sorry for trampling on your personal safety and comfort and making you feel frustrated, disheartened, and scared about being funded on Gittip. That totally sucks, and I hope we can fix it. :-(

(Please let me know who else I need to apologize to.)

Okay! With that, I'm signing off for the weekend and then on Monday I have a client engagement (I've started experimenting with "pay what you want" consulting to supplement my Gittip income). I've read everything in this thread at least once and will continue to reread and digest. I plan to be back in the mix on Tuesday at the latest and will see where things stand then. Keep up the good work! :-)

!m *

[duckinator]

For anyone who's not seen #56 or my relevant Tweets: I've stepped up as Gittip's first User Advocate.

As I said on Twitter, this is basically a formalization of the roll I've been filling to some extent for Gittip since I first started helping out.

Further discussion regarding UAs, their roles, and how to build the User Advocate team should take place on #56. Thanks for all of the input so far, and I look forward to getting more!

[chadwhitacre]

In addition to the tickets @duckinator has made (#54 #55 #56), I think our response here should also include:

• landing account cancellation (https://github.com/gittip/www.gittip.com/pull/2412)
• writing a document about our open company philosophy (https://github.com/gittip/www.gittip.com/issues/2422)

I propose that we tackle these five tickets and then write up a blog post for blog.gittip.com.

[chadwhitacre]

In addition to these structural changes, I've also reached out to Shanley (private email), Ashe, and Nina to see if I/we can start building trust at the interpersonal level.

[chadwhitacre]

I would also like to thank @duckinator for stepping forward to convert this feedback into actionable tickets and for also stepping up as our first UA! :D Yay @duckinator! :D

[tshepang]

Nina is even more colorful than Shanley:

@whit537 Privilege is power, idiot. Exercise your power to do the right thing, or concede to being a spineless dick on the issue.

Wow!

[chadwhitacre]

@juliepagano

I think you need to provide better avenues for your users to provide feedback. Right now, the only ways I know of are to create an issue on github, tweet at the gittip twitter account (140 chars is not really conducive to clear feedback), or bother one of the contributors I happen to know in person (not a feasible option for most of your users). If you want to care about users besides OSS developers (your top receivers and conversations I've had with members of the project suggest you are), posting an issue on github should not be a requirement for providing feedback.

Interesting. We've actually had a support@gittip.com email address for seven months now, since https://github.com/gittip/www.gittip.com/pull/1254. However, we haven't had a clear policy on consent and privacy related to that channel, so let's add https://github.com/gittip/www.gittip.com/issues/2125 as a sixth ticket to land as part of this wider issue.

[chadwhitacre]

I see shifting the perception and fact of Gittip's organisational model from "transparency at any cost" to finding a more nuanced balance between a baseline desire for transparency at the organisational level, while respecting the privacy of the individuals that interact with the organisation as the core concern here.

+1 @ncoghlan

[juliepagano]

@whit537 It's probably telling (both a little on me and a little on gittip) that I didn't realize that email existed. I just took a look at the site to figure out where to find it listed. They only place I easily found it was the about page, which was not the first or even second place I would expect to find it.

I'd recommend adding it to the FAQ page under a question about "Who do I contact if I need help" or something like that. I'd also recommend adding a "support" page of some sort explicitly for this sort of stuff and giving that page a link in your bottom navigation. That was the first thing I tried to look for. At the same time, the bottom nav is starting to get pretty crowded already. It might be worthwhile to put some time into considering the information architecture of the site to clean that up.

[chadwhitacre]

They only place I easily found it was the about page, which was not the first or even second place I would expect to find it.

Yeah, that's the place it's listed right now.

It might be worthwhile to put some time into considering the information architecture of the site to clean that up.

I've added a +1 for you to #39. :-)

[chadwhitacre]

Anything else to reticket from this one?