-
Notifications
You must be signed in to change notification settings - Fork 38
take duckinator's article on board #76
Comments
(cc: @duckinator) |
I this suggestion has some merit
BUT!! So we don't publish the chat logs at all? |
Next paragraph:
|
So, basically, I love this, @duckinator. Can we start there? I love this. Thank you. :-) !m @duckinator I want to digest this piece and process it into +1s and new tickets for Gittip. Forthwith ... |
I've got a really long comment in the works but I'm out of time for right now. Will pick up with this later/tomorrow ... |
Yes. Yes. Yes. Yes. One thing that's had me scratching my head this past month is that, when I first started getting traction with the open company idea in the wake of "Turning Down TechCrunch," I explicitly said this very thing! I've gone back through the five interviews I did in the first week after "Turning Down TechCrunch" to review what I said at the time, and I've found some very interesting passages in the first three of them that I think reveal the roots of the Gittip crisis. This is all in early May of 2013, over a year ago, just a couple months after activists started using Gittip in earnest. First InterviewHere's a passage from the very first open interview I gave, wherein you can watch me arrive for the first time at the idea that, "somehow, openness and transparency are goods, but they're not absolute goods."
Second InterviewIn the second interview I did, you can see that I've embraced this idea that openness is not an absolute good, and that the point of having open companies is to mitigate the squishing of individuals.
Third InterviewThe third interview I did, with Gabe Stein, was much more in depth. Gabe brought up "the performative aspect" of open interviews, and we talked for a while about how the democratization of media has also democratized the problem of managing one's public image, and navigating the relationship between one's public and private identities. We also talked about how social pressure is not always bad, and is in fact how communities are formed. Then I struggled pretty hard to say something on camera that is part of my private identity, but which I wasn't comfortable sharing publicly for fear of being "squished by the collective."
What Was I Trying to Say?Speaking anachronistically, I Resent You is the thing I was trying to say there on camera over a year ago. |
On my reading, this is the main thesis of your piece, @duckinator. I love it. Per the above, I'm trying to build companies that don't squish people, which aligns with your goal of "creating companies that are run in a way that makes them as trustworthy as possible." There's a lot of theory to continue developing around this. On the practical side, the four concrete suggestions for Gittip that I'm seeing in your piece are:
Are there other concrete suggestions in there that I'm overlooking? |
Re: "[D]iscard the self-selected salary approach" ... "that was one I expected you to entirely disregard, tbh :P" IRC |
Interview 3 was hard to read, and I don't get the point, even if you say it's somehow related to I Resent You. Do you mind explaining a bit @whit537? What were you uncomfortable expressing? |
@tshepang That interview was soon after PyCon 2013, scene of "donglegate," and I was struggling to articulate my discomfort at the way "donglegate" (even just the name) revealed the radicalization of the tech industry. I identify neither with militant feminism, nor with men's rights activism. I believe in dialogue, encounter, openness to one another, kindness, listening, forgiveness, and reconciliation. I had thought of myself as part of the Python community and the tech scene more widely. Now I feel as if my continued participation in the Python community would have to involve some measure of activism of my own—for dialogue, forgiveness, and reconciliation. Accepting the role of an activist would conflict with my leadership role in Gittip, if only because that'd be a lot of work and I don't have time to do both properly. My stammering in that interview was an early attempt to come to terms with this. I've generally been trying to squelch these opinions for a year, but clearly they've leaked out here and there, culminating in I Resent You a month ago. Am I answering your question? |
I think I get it. As someone practicing transparency, it is challenging for you when and when not to share. You would love to say "you approaching this wrong" but can't, because that would derail the (supposedly) more important conversation. So you constantly have to try to keep that balance. Not easy. |
@duckinator et al. It seems like #71 is the place to pick up with the discussion of points 1 and 4. Eh?
|
@whit537 commented 15 days ago:
Is this being entirely dropped? Did it get an issue of its own? IRC logs look like @whit537 & deltab express skepticism, but @duckinator makes important points that there are underlying issues that too easily get swept under the rug:
On this point, I would also include Buffer's Open Salaries post as a successful example of "clear terms for specifying how much somebody is compensated". |
@dsernst What's your proposal re: salaries at Gittip? |
Frankly, I don't have a clear solution yet. But I can relate with the Really glad to see you following up on the matter, though, despite the I'd suggest for now that the way to approach this is to explicitly identify I'll keep thinking on this. On Monday, August 11, 2014, Chad Whitacre [email protected] wrote:
|
@dsernst You should go for it! Raise your take to $0.02 and see what happens! :-) |
Prioritizing this in two ways: assembling the Safety Team over on #84, and I've added safety as a brand value in 88705d5:
|
The values change will land here: http://inside.gratipay.com/big-picture/brand/. |
Landed. :-) |
Picking up over at #319 (comment) with ...
https://modelviewculture.com/pieces/on-open-companies-consent-and-safety-among-other-things |
"On Open Companies, Consent, and Safety (among other things)"
http://modelviewculture.com/pieces/on-open-companies-consent-and-safety-among-other-things
The text was updated successfully, but these errors were encountered: