Categories
Diversity Technology

Number 9 Number 9 Number 9

Recovered from the Wayback Machine.

I wanted to welcome you all to this, the third annual Burningbird Bash of ETech! This year’s show promises to be the best ever, especially considering that O’Reilly has, after all these years, finally broken the 10% rule for percentage of presenters that are female!

Yes, indeedy, this year’s female participation is a whopping nine percent (9% or 0.09)! Nine percent! Why, I bet there’s more Windows users in the audience than women presenters!

I want to take a moment now to send out congratulations to Tim and the gang and say, “Job well done! You finally found the solution to the 10% problem!”

Okay, so this introduction to what has become my annual report on the lack of women at O’Reilly’s Emerging Technology conference is a little over the top. Every year, though, I and others say the same thing and nothing changes except this year things are worse instead of better. Once this fact hit me in the face, like a too-dead squid thrown by a fish monger, I had to scramble to find a bigger soap box and louder sound system. I even thought about hiring a troop of clowns to entertain the kiddies while we talk–but my heart just wasn’t in it because all I could see is that 9% rather than the 11% or, gosh, even 15% I had hoped to see.

So much of my discussion lately, though, has been on diversity that I almost decided to forgo this writing. However, where much of the previous discussion has been about diversity in weblogging, this is about diversity in technology–specifically, the lack of female representation at many of the technology events. Still, too much of anything is like eating a cake that’s 90% frosting: no matter how good it is, you’re going to get sick of it before you’re through.

I finally decided to go ahead anyway on this one writing, primarily because there are a few things different about the discussion this year. Now, I don’t know if the differences add to the discussion or to the noise, but since I like discussion and noise, here goes.

I submittaled a paper with a female origination

Whatever the representation of women at ETech, I can say I did my part. Unlike the conferences in the past, I submitted a proposal to ETech this year. Previously when I pointed out the lack of women presenters at the conference, one or more people would come back at me with, “Well, did you submit a proposal.” Now I can say, “Yes, I did”. It wasn’t accepted, but what’s more important is that I did try, I tried to be part of the solution. So, neener, neener, eat your wiener.

I found out in a post at David Weinberger’s that only 5% of the proposals were submitted by women. If we compare percentages, then, a larger percentage of women’s proposals were accepted than men. Now, how many men were invited to speak without proposals, invited to submit proposals, and leaving aside the fact that some of the committee members that decided on the proposals also spoke at the conference–whatever led to the event, a drop in women presenters this year is not a positive direction.

Danah Boyd also submitted a proposal this year, which, like mine, was also rejected. She wrote:

I was actually part of the 5% who applied to etech, only my application was rejected because it wasn’t emerging.

I don’t know if my submittal/submission/proposal was ‘emerging’ or not. It talked about semantic web and achieving critical mass with schemas, so there were all sorts of geeky terms present. But there was also poetry and words to the effect about bringing the semantic web to the butcher, the baker, and the candlestick maker. On reflection, now, this could have been a mistake.

I have a feeling, though, that the proposal lost out as soon as selection committee saw the title: I, Poet. Compared to “How to geek out your car”, poetry and semantics probably seemed less than interesting. But, as Ms. Boyd points out, there is interesting and then there’s interesting.

After a conversation last night, i wanted to clarify a few things. In conferences like SXSW and Etech, there’s no clear delineation of what is an acceptable topic or not (as opposed to say CHI). I mean – what is interactive or emerging? Additionally, the review panel consists of a very small number of people (all of who are pretty much guaranteed a slot). At CHI, there are hundreds and hundreds of blind reviewers. At SXSW and Etech, the metric is “interesting” – this is where we get ourselves into trouble. Interesting to whom? To the un-diverse review committee?

It wasn’t until I saw in comment in David Weinberger’s post on this issue that I knew who the committee was: Andrew “Bunnie” Huang, Clay Shirky, Cory Doctorow, Brian Jepson, and Marc Hedlund. No, “I, Poet”, a discussion on semantics and poetry wouldn’t have rung any bells here.

But would it have done so if the planning and selection committee were a little more diverse? Say, having one woman on the committee? Or perhaps some faces that weren’t so familiar? Would Danah Boyd’s proposal had been accepted if the committee were more diverse or had stronger ties to the social software industry? Hard to say, and that’s part of the problem, and the concern.

What makes this issue of diversity an even more pertinent one is that across the country, an event was held that did result in a much greater diversity than ETech: SxSW.

It burns so good

In David’s post, an interesting discussion about the lack of women at Etech arose in his comments, and are worth a read. Several were written by Liz Lawley, who also wrote about choosing to attend SxSW instead of Etech at Many-to-Many.

That’s another factor that sets this year’s discussion apart from previous years: the overlap between Etech and SxSW. More importantly, where Etech achieved only 9% participation, SxSW achieved significantly higher numbers.

Nancy White, who did such a great job liveblogging the sessions she attended, also tried to keep a head count of women in each. From what she and others have written, women made up anywhere from 25 to 50% of the participants at SxSW. That’s double to almost five times the numbers of ETech.

This level of participation at SxSW is important in relation to that of ETech for a couple of reasons. First, it shows that women are interested in participating in conferences related to their profession. Secondly, it also shows they’re willing to take the time and cover the expense.

One response that’s been raised time and again about the lack of women at O’Reilly conferences is that woman are less interested in attending conferences, or lack the financial means and/or time to do so. With SxSW and ETech happening virtually at the same time, we can compare the two, side by side, and see that this isn’t necessarily true. Women have the interest, and are willing to commit the time and resources following through on that interest. In fact, one reason there could have been a drop in women’s participation at ETech is because so many chose SxSW, instead. And the question then becomes: why?

Looking at both conferences more closely there some major logistical differences between the two. One is cost–SxSW’s fee is peanuts compared to O’Reilly’s normally quite expensive conference fees. The second is location–the central part of the country, even if it is south-central (well, if we must, south-by-southwest), is more accessible to more people than the California coast; cheaper to visit, too.

A third difference is when the conference was held. SxSW was over a weekend, while ETech was held during the work week. For women, who are usually the prime caregivers for children, it might be easier to arrange care on a weekend than a weekday.

However, I think the major difference was the players. Both conferences had names, though SxSW had more human-interaction and design names than ETech, which focuses more on ‘to the metal’ geeks. But there is more of an intimacy surrounding the players at SxSW than there is at ETech. Frankly, when I looked through the lists of Big Names at both get togethers, the SxSW Names were all people who struck me as being more approachable.

In fact, I think the same could be said of the entire SxSW conference — it encouraged participation, even from the audience. Lively discussions in the hallway aside, O’Reilly’s ETech conference is fairly passive. People sit in rows and listen to a speaker. People go to birds-of-a-feather sessions for interactivity, but these are an aside to the whole experience. Even the entertainment has an orchestrated aspect to the whole thing. Bluntly, ETech is very formal, very superior alpha-geek, somewhat passive, and even rather intimidating.

SxSW, on the other hand, is formed of beloved chaos, tenderly nutured in a solar vat consisting of an odd mix of creative anarchism and social responsibility. I don’t know whether one appeals more to all women more than the other, but I know that if I had my choice, after reading the reports from both conferences, I’d rather go to SxSW than ETech. And I consider myself a ‘to the metal’ geek.

That’s a key point, too, in this discussion. If there are many conferences and people can choose between them, why should we care if conferences such as ETech have only about 10% attendance, as compared to ones like SxSW? After all, these events are open, and nothing is stopping people from participating.

Shake that networking booty

We are living in a time when outsourcing IT companies are charging 3.00 US an hour for labor, and there are fewer and fewer IT jobs every year. It’s becoming tough to be a tech. No, change that: it is tough to be a tech.

One way to keep ahead in the tech industry now is through networking and contacts, and attending conferences is a big part of this. If I were to coldly and dispassionately sit down and choose between SxSW and ETech from this perspective, I would pick ETech. After all, it had folks from Yahoo, Google, IBM, Amazon, Nokia, and movers and shakers from most major IT companies. It’s also a closer match for my skills and experience.

So, then you’re saying: Okay, so what’s stopping you and other women from attending?

One major reason is no one wants to be the freak in the crowd; or worse, invisible. If you’ve never been the only woman in a room full of men (or the only black in a room full of white people), you may not understand how intimidating and uncomfortable you can be made to feel. Especially in technology, where women’s visibility is usually compromised anyway.

It’s hard to network if you just aren’t seen There was another comment in David’s weblog post that I think highlights this. In it, the commenter, Jo, wrote:

I spoke at etech the year previously. Meeting clay shirky after my talk, he made a couple of comments to the effect that “your guy” should look into something, “your guy” might find something interesting. I was too quietly stunned and post-talk-drunk to frame a better reply than “er, i do write my own software, you know.” As a female with a gender-neutral name, i am often assumed to be male by conference organisers, people online, etc. I’m quite used to being the only woman at BOFs, at user group meetings, etc. It’s hard to even notice it any more; it’s just the way i grew up as a geek. I always assumed it would slowly change. But if that’s the case, it’s not reflected on the public platform.

Every year when i see the Etech highlighted speakers’ list with speaker photos, i scroll down disconsolately for the inevitable token non-male face. The 9% don’t get much of a look-in.

O’Reilly’s organisers *are* in a position to “counteract the prevailing cultural forces” in Fred Brooks’ wonderful phrase. How much backlash, of a New-Labour-Women-Only-Parliamentary-Shortlist flavour, would that provoke from those who had been cut out by a defacto quota?

From the recent discussion on women in weblogging, we can answer Jo’s last question about quotas, openness, and what is the chance of folks being provoked into a backlash with a simple answer: a lot. When the status quo suits one group over another, we can’t expect to the former to willingly give it up in the interests of fairness.

People are resistant to change. People are even more resistant to change unless they see the problem impacting on them personally. People are especially resistant to change when the change means they have to give something up. Pigs refusing to leave a particularly fine pool of mud comes to mind.

If ETech is a success for O’Reilly, what is the impetus for the company to change? If the type of sessions and the opportunity to network is a success for the majority of its participants–and the majority of technologists in this country are still white, male, as reflected at ETech — what is the impetus to change? If even among women, some don’t see this situation as an issue, or only do so from a personal perspective, where is the force that could generate the impetus to change?

Why change? Because Etech will be better.

Where have all the semanticians gone, long time passing…

One thing I noticed about both SxSW and ETech is both conferences featured much on XHTML attributes and tags as the wave of the future in the semantic web, but very little representation from what has been the semantic web community for many years. Some–many?– might say this was a positive aspect to both conferences, but is it really so?

In the long run, I don’t think so. I’ve noticed that more of the activity and work related to the semantic web, outside of folksonomies that is, is happening in Europe or Canada rather than the United States. Is it that our country is so caught up in gizmos and gadgets and mini-macs and iPods and cheap and easy solutions and meme of the minutes that we no longer want to take the time and energy to understand the more in-depth and complex, and perhaps less flamboyant, aspects of technology? Are we becoming a nation of fad technologists?

In addition to technology diving into the shallow end of the pool, if you read down the list of presenters, you see, repeated again and again, the same company names: Yahoo, Google, Microsoft, Apple, IBM, Amazon, BBS, Wired, Nokia — all well known technology or media companies, many of whom are indugling in some fascinating advances in technology. Yet there seems to be fewer and fewer representations from smaller companies and independents–to the point where I’m surprised that O’Reilly is even bothering with submissions outside of a picked group of organizations.

Technology as it used in specific well-known companies can be interesting, but the problem with it is that much of the time what each company is doing is unique to that company; and the information can’t be extrapolated to other uses. Not everyone has the same system requirements as Google. Not everyone needs to own a dam.

And frankly, who is to say that how each company uses the technology is the best use of that technology? If you have enormous resources and funding, you can afford to spread out. Smaller companies may need to come up with innovative ways of doing the same thing for less. Yet if an employee of Google is presenting on web services and Jane Blow in off the street doing the same–who is going to be picked? This isn’t always in the best interests of the audience. Thanks to the Google’s fame, we know how it uses web services; I kind of want to hear what Jane Blow has to say. Maybe she has a new twist, and a new idea.

Not just the same companies keep showing up — the same people, too. I read in a weblog from one attendee (and my apologies for no permalink; I had read several and forgot where I saw this one), that when he arrived at the conference he looked around and noticed that it didn’t look all that much different than the year before, or at other events he’d attended in the last year. Same faces, same folks, same groups, and similar topics–the only change being the ‘it’ topic for the year, such as tags and gizmos this year (thanks to folksonomies and O’Reilly’s new gizmo magazine, Make).

Okay fine. Big companies, less depth, familiar faces. But what does all of this have to do with lack of women presenting?

Well, it all comes back to the lack of diversity.

O’Reilly tends to pick from a non-diverse pool of people when planning ETech, and this is reflected not only in the lack of female participation, but also in the fact that the conference is beginning to resemble more of a annual meeting of a club than a conference celebrating innovation. The sessions might be interesting or even entertaining, but they don’t necessarily challenge the attendee–how can they? So many of the attendees are no different than the people presenting.

This lack of challenge, and the resulting epiphanies and excitement that can result from same, shows in so many of the weblog entries about the conference. The sessions were interesting, the people enjoyed them, but no one came away jumping up and down with enthusiasm. Well, except for the Ruby on Rails photo. (For the best take on folksonomies at ETech, also see Sam’s wonderfully ironic posting.)

This, then, forms the impetus for O’Reilly to look more closely at how it manages its conferences, and to begin to diversify the community that both presents and attends: not just because it’s the ‘right’ thing to do; not just because it’s the ‘fair’ thing to do; but because it’s the smart thing to do.

Not unless O’Reilly wants ETech 2007 to look like Etech 2006 to look like Etech 2005 to look like…

number 9, number 9, number 9, …

Categories
Programming Languages

PHP and the corporate seal of approval

I did want to point something out before I forgot, but IBM is putting its corporate blessing on PHP with, among other things, a new PHP Weblog site. I was reminded of it today with a link in Dave Winer’s weblog, which disappeared.

(Hey, did I happen to mention Mark Pilgrim is back?)

Anyway, folks on the coast may not realize how significant this move on IBM’s part is. Companies in the mid-west and away from the coast tend to be conservative with technology, and usually want it vetted by one of four companies: IBM, Microsoft, Oracle, or Sun. Because of this, open source technologies and languages such as PHP rarely see the light of day in the development projects here. This, in turn, means people like me can search on jobs using PHP in Monster and not find one–one–in two months of looking.

It’s going to take a while, but I believe we’ll start to see a crack in the .NET/J2EE domination here abouts. This is good for the developers, and also good for the companies.

It’s funny but as time has gone by, IBM has become more like the Microsoft of decades past; while Microsoft, with the appointment of Ray Ozzie as CTO, has become the IBM of decades past. I guess we’ll wait and see if the Microsoft employees have to start wearing blue suits.

Categories
Technology

Microsoft gets Groovy

This was an eye opener today: Microsoft has bought Groove Networks and hired Ray Ozzie as new Chief Technical Officer.

Years ago when I lived in Boston, I had visited Groove and met the development team and Ray’s brother, Jack, when I was looking at doing a book on Groove for O’Reilly. I also interviewed with them, once, for a possible job.

It’s been a few years, but the Groove people I met were a loyal, sharp, enthusiastic group of people who seemed to have a lot of respect for the Ozzie brothers. I see from the press release, Microsoft has also hired the crew and they’re staying in the Boston area.

Microsoft buying Groove is one thing, but the kicker is the company hiring Ozzie as CTO. This signals a major shift in product direction, and product mentality, for the company.

Great Slashdot quote on the move:

 

Yup, that’s pretty much what all groupware is — it’s software that causes open source fanboys to say “I don’t see what the big deal is. I could do the same thing with NNTP, awk, MythTV, ReiserFS, two tin cans and a piece of string. All this “integration” and “working” stuff is just eye candy.”

Lotus Notes is the same thing, except that in that case the fanboys really could have done better with the cans and string.

Categories
Technology Weblogging

From Press to Form

When I post the Wordform files for download, I’ll provide details of the conversion from WordPress 1.5 to Wordform, but I thought I would provide an overview of the changes, upfront.

First, my decision to make such extensive modifications to WordPress that I decided to fork the code isn’t an indication that I think WordPress is a ‘bad’ tool, or is based on ‘bad’ coding. On the contrary: with this new release, I consider WordPress 1.5 to be one of the best weblogging tools on the market. The new themes design is absolutely brilliant, the user interface is intuitive and easy to use, and the code has been cleaned up very nicely–the developers can be justifiably proud of what they’ve delivered with this release. When the first bug release of the product is available for download, (1.5.1) I can, without hesitation, recommend this tool to any weblogger.

However, my views of what I want from a weblogging tool have been diverging from the WordPress developers for some time; luckily, since WordPress is GPL and I’m also a coder, I can do something about it.

Many of the changes I made to the code to take this tool from WordPress to Wordform are ‘under the covers’. For instance, I pulled all database queries into a separate file so that if I want to make changes to the underlying database I can easily without having to go through individual files looking to see what has broken. Of course, if I add or remove fields, I will have to change code, but in many cases, this additional separation of application and data can mean that even a significant change, such as multi-weblog support, can be made with relatively little impact on the application.

Other changes I made are very apparant to the user. For instance, I pulled all trackback and pingback code. Yup, every last bit of it, including dropping the table columns from the database. The more I looked at pingback and trackback, the more I didn’t like either: the former because it’s nothing more than referrer linking, and the latter because it’s too vulnerable to abuse. Instead of trackback and pingbacks, I’m incorporting the concept of ‘tagbacks’ into the tool, specifically as a focus for either a discussion thread, or as a multi-threaded topic. (More on this in a later post.)

(One side benefit of removing pingback and trackback is that the tool is very fast now. It was fast before I made the change; afterwards, updates and new posts are instantaneous. In addition, I think not having to manage these within the code has also simplified much of it, and simpler code (or more focused code), is easier to maintain.)

Picture of Bam-in-a-CanAnother change I made was to the new WordPress Desktop. Instead of scraping in the WordPress Development weblog and Planet WordPress syndication feeds, I’ve incorporated a page that uses Feed on Feeds, a server-based aggregator that works somewhat like Bloglines. Feed on Feeds is just one of the external applications that can be installed with Wordform, and it allows you to subscribe to various sites. Then, when you access the Wordform Desktop (which has been renamed to “Bam-in-a-Can!”, for no other reason than it’s such a cheerful phrase), you’ll see the updated feeds from all your subscribed sites.

I pulled all implementations of ‘nofollow’ from the tool. I was going to detail how to do this for WordPress users; unfortunately, though, if you want to use WordPress as a tool, you’ll actually have to modify the tool libraries to remove this attribute, not just modify the tool templates. I’m reluctant to provide a ‘how to’ on this, as this will make the tool incompatible with future releases. If you want this information, you’ll need to send me an email.

I also added an option to turn on or off the enclosure functionality. Right now, if you link an MP3 in your post in WordPress, it’s automatically added as a syndication feed podcast. I’d rather give people the option whether to list this as an enclosure or not in their feeds.

I pulled in-page preview from the edit page, and added preview as an option for the main template. With this you can preview a post ‘in context’ –within the page design. I also added spell checking to the edit page, and am pulling the Quicktags in favor of a more sophisticated designer bar (which can be switched out for the existing Quicktags if you prefer the older design bar).

Some other major architectural changes:

  1. Creating a page literally creates a hard page, which can be individually moved. If .htaccess is writable, the page is linked to a virtual directory location; otherwise, you have to move it.
  2. I pulled private posts. The one time I’ve seen this, I didn’t like it. Here you have a weblog with this big “PRIVATE POST” blob in the middle of the page, taunting the readers with what they could not access–the plebians. I figure if a person wants private posts, they should think about having a private weblog. And again, this change nicely simplified the code — the old fewer moving parts, less breakage thing.
  3. I’m incorporating the concept of Wordform Application Modules (WAM) into the underlying tool architecture. These are full featured applications, wrapped to work with Wordform, as compared with plugins, which are bits of code written specifically for Wordform (or I should say, WordPress, as I’m keeping the plugin architecture the same so that Wordform can use most WordPress plugins). The Feed of Feeds implementation in the Bam-in-a-Can page is a example of a WAM.
  4. Comment and post status are pulled from the database and populated in a dropdown box. This allows application module and plug-in developers to add new statuses. I used this myself to add comment moderation on a post-by-post basis.

There are other new changes that I’m still working on, and hope to roll out with the first beta release of the product, some time next week or so.

I did incorporate my old comment management system in Wordform, and pulled the existing WordPress whitelisting functionality. I’m not crazy about whitelisting, and I don’t like blacklisting. What I’m doing is providing an option that allows a person to turn off comments older than a certain date. However, the comment itself isn’t turned off until the first comment that post received after this date. That comment is moderated and than the post is turned off. This allows the weblog user to see if the comment is spam, and if it isn’t, to make a decision whether they want to turn comments back on with that post.

I’ve also added in my old throttle, which will keep a person from being crapflooded; and am enhancing the manageability of the pages that display comments and posts — providing NEXT and PREVIOUS page functionality so a person can page through results. People can also search for comments and posts based on dates and post or comment IDs.

The post-comment editing functionality can take multiple tool backends, so you can use this with WordPress, Textpattern, Movable Type or other weblogging tool. In addition, I have a comments.php file that will work with both Wordform and WordPress, and which will enable spell checking, live preview, and post-comment editing.

While this is all going on, I’m also keeping an eye on the WordPress codebase, to incorporate relevant fixes to functions in Wordform, as they occur. And I have a couple of patches for the WordPress folks that I need to drop into the WordPress bug system, soon as I have a spare moment.

I’ll say one thing with all this effort: if you need help with your WordPress weblog, I’m your woman: I’ll probably know the code almost as well as the developers when I release Wordform 1.0a.

Categories
Technology Weblogging

Wordform 1.0a in test

Wordform 1.0a is in development and test at Burningbird. This site has not been updated to most recent version, though I hope to by week’s end.

I also hope to have the first alpha release of the code ready for download next week. Knock on wood.