?

Log in

No account? Create an account

"you can't influence what Brian is saying..."

« previous entry | next entry »
Feb. 23rd, 2010 | 10:52 am

I both love, and appreciate this quote from Monty:

"You know Bryan and should know, as all his friends does, that you can't influence what Bryan is saying; He is always speaking his own mind!"

Ignore the spelling of my name, Monty is not a native english speaker, and writing for him is a chore (which I can relate too, since writing to me is a chore as well... and to the people who I ask to edit what I write).

Larry McVoy, yes the author of Bitkeeper, once told me that while he worked at Sun that they had his workstation setup so that every post to Usenet, (or was it email in general?), got passed to a VP who would then decide if it was to be posted or not. My joke for the last few months has been "what, they only gave you a VP? I got a CTO!".

While at Sun, about every other week, either an email would be generated by about one of three people saying "can your believe what Brian wrote in a blog/comment/etc...".

Typically the conversation was "What did I post?", "Was I right?", or "What I said was the legal definition, right?". Some of the email I shared with other DE's at Sun, and there was a running joke about taking odds on what blog of the week would elicit "yet another email".

At one point I wrote a comment up about some licensing issue, and at the same time, not in any co-ordinated manner, Tim Bray and Simon Phipps did as well. Who got the complaints? I did.

Sun was a large company, and some folks really have nothing better to do with their time, and there was a general consensus with both my peers and some of the VP's I shared the emails with that this was the case. Once or twice offered to resign if it was really an issue, and I got back a very affirmative "that is not what the company would like".

When I write, I write what I think, not what other's tell me to write. When I get up on a stage and speak? That is all me.

For me to support something, I really need to be able to support it. Through out the years at MySQL I really never found that there was an issue with that. The MySQL internal "Discussion" mailing list was evidence of just how big of a tent the company was for opinions, much to the chagrin of some. I've never made my opinions secret about licensing. I didn't begin working at MySQL with a strong opinion against copyright assignment, but after watching the toll it had on the project I certainly gained one.

Now I work for myself. All opinions expressed are solely the opinion of me, myself, and I...

Occasionally though?

Those opinions are shared with others :)

Link | Leave a comment | Share

Comments {3}

Hehe, it is liberating, isn't it :-)

from: anonymous
date: Feb. 23rd, 2010 08:42 pm (UTC)
Link

I guess I'm more conservative and/or conformist, I would usually try to think about what is "appropriate" to write. Sometimes I chose to write something I knew would get me in trouble, but decided it was worth it for the MySQL Community.

The one problem with MySQL AB though, that those lively discussions were mostly internal. One thing I realized over the past year is how big the disconnect is between those who were employed by MySQL AB and those on the outside. On both sides you have a variety of opinions, but it's like people live in different universes. Some topic taken for granted by a MySQL alumni will be totally lost on the average open source community.

Like some of them don't know the difference between Drizzle and MariaDB, etc...

The non-public discussion and development is my favorite pet peeve, copyright contributions has its complexities, but I still don't have it in my Top 10 "mistakes we did and want to avoid". But it's close to being 11.

Reply | Thread

(no subject)

from: _justanotherme_
date: Feb. 24th, 2010 09:29 am (UTC)
Link

Great Youtube clip / link of you talking, really had to chuckle while watching :)

Reply | Thread

my comment

from: anonymous
date: Mar. 3rd, 2010 02:38 pm (UTC)
Link

Oops, apparently forgot to sign. That's me in the first comment

Henrik Ingo

Reply | Thread