We have now mapped the tiny corner of our creek and given names to nameless places, extending human dominion to yet another junkyard and mudflat.
As I kayaked around with my friend Adina she babbled to me charmingly of how we were in the same place but in a different place. Everything about the land and the water became different because we were on the water looking at the land. I agree! Distances open up hugely and pinch themselves up into almost nothing depending on the wind and current and tide. The parking lot of an office, a boring place, turns out to be the best fishing spot on the creek, full of families hanging off their truck tailgates.
Many of my names for the creek are jokes but they reflect the way we are using the creek as kayakers and what we think is important. The places where trash collects, the strength of the current, the mudflats, the sticks and pilings and pylons that are landmarks, the place where the grebes hang out, the wind shadow of Middle Bair Island.
We remap our minds by traversing the edge of the known map. I was thinking about frontiers, wastelands, and edges. At Open Source Bridge I said some stuff about wastelands. When you hear a place described as empty, reach for your gun. Just kidding. No, when you hear a place described as empty, you can be sure someone is exploiting it. The desert, the wasteland, and the frontier, are obfuscations.
So in my naming of these places I open up different possibilities of exploitation, but since no space is unnamed and unobserved -- they are named and observed and mapped by governments and corporations -- I would prefer that they be named and observed in a decentralized way by anyone at all. (Which is one reason I adore Open Street Map and Open Sea Map.)
As I look back on the history of Bair Island and Redwood Creek I keep finding ghost places - like "South Shores" which was an attempt by a developer to rename the slough as a suburban extension of "Redwood Shores". Or like Deepwater Slough, which still has a faint track on the satellite photo - the C shaped trace that loops across Middle Bair, across from the Port - the dredged mud and pickleweed it encloses still privately owned and still named "Pacific Shores" probably for some totally screwed up future condo development scheme.
The Bair Island history, its battles, and its 2006 EIR are all deep background good for anyone interested in the proposed 12,000 household development of the wetlands-turned-salt-ponds owned by Cargill. On the maps they're the pink rectangular areas that barely even look like bay anymore.
A neighbor of mine across the harbor is gearing up for that battle on another blog, Virtual Saltworks. The ponds are still part of the bay and still supposed to be open space and wetlands. We could use a little bit of digging into maps and history - what was First Slough like before it was diked? What would it take to restore it at least to the state that Bair Island and Corkscrew Slough are in now?
Soon the abandoned docks and the piers for electric company access to overhead cables will be decorated underneath by pirate mailboxes where Milo and I will leave secret messages for the world.
I have some great ideas for Community Kayaks. They'd be like the civic projects for free bicycles anyone can use without fuss. It would be very easy and cheap to start and maintain a simple flotilla of boats free for anyone to use. More local people would use Redwood Creek, would see the edge of our town, the cultivated-wild places that exist right next to the industrial port where oceangoing cargo vessels offload their gypsum, sand, and gravel and load up clanking waterfalls of scrap metal. People barely care about the Creek because they don't know it's there. If they paddled around on it they might get fond of it.
I got a little obsessed with the Alviso boat ramp opening. If you live in Redwood City - do you know where the public boat launch ramps are? There are two that I know of!
What is the Bay for? Who gets to go on it? You shouldn't have to be rich - or go on a giant ferryboat - or treat it like a sort of horrible wet golf course -
Where are my beautiful floating islands made of trash and full of ecological minded Burning Man hippies cultivating flats of pickleweed and nesting habitats for Caspian Terns? I also imagine a beautiful anarchosocialist cooperative marina with art projects and rogue marine science. It would be easy for us here in the harbor to be monitoring water quality, observing the plants and birds and fish, and so on. Decentralized maps and some kind of visionary open data project could make for some great open source science - I'm sure someone's doing this already.
Friday, June 11, 2010
What it might mean to make maps
Posted by
Liz
at
5:01 PM
0
comments
Labels: boats, ecology, maps, open source, Redwood City, Redwood Creek, science fiction
Monday, September 07, 2009
WordPress security checkup
If you aren't using the latest version of WordPress, your blog might have been hacked. There's an attack going on right now that creates and then hides administrator accounts.
You can see if this has happened on your blog by going to the Dashboard and then the Users panel. The number listed in parentheses after Administrators should match the number of actual admins that you have for the blog!
If that number is higher than the amount of admins for the blog, you probably have hidden users. You could try turning Javascript off in your browser to see those hidden users.
Then, delete them (if you can) from the panel. I didn't try this myself, but I think it will work.
Or, you can use mysql or phpmyadmin to delete those users from your database. If you don't remember how to connect to your database, look at the files in your wordpress folder and read the contents of wp-config.php. That will have the username and password and database host name. You might also need to look at the help or FAQ files for your web host.
In phpMyAdmin, you can find and delete the hidden users by connecting to your database, then browsing the users table. Check the boxes by the wp_users and the email fields (or just check all of them) and then click Browse again. This should show you a list of all the users on your blog.
This is what a row of user data should look like in phpMyAdmin:
This is what a "hidden user" account will look like. It'll be a name that doesn't show up in your WordPress Dashboard, and it won't have an email address in that 5th field. Might be a good idea to delete these users right away.
I followed Lorelle's instructions for how to recover from my WordPress blog being hacked. That worked fine:
* I did an xml export from the Dashboard and made sure I knew what that file was named and where I saved it.
* I did an sql dump of the whole blog (from the mysql command line, but you could do one from phpMyAdmin too) Just to make sure I would have everything, and so that I could do some forensics later on the contaminated db.
* Then I deleted that db, made a new db, and saved the information on how to log into it. You could also drop all the tables in the old one, I guess, and keep using it. While you could leave the old db there, it seems unwise.
* I deleted all the stuff in my wordpress folder on my server. If I'd thought, I would have saved a few custom banners and images first.
* I downloaded WordPress latest version, 2.8.4 and unzipped it, along with some themes and plugins.
* I then went to the url for my blog and told the install screen a blog name and my email address, and got a new admin password. Voila, new empty blog.
* Then, from the WordPress Dashboard, went to Manage and then Import. I imported the xml file as a WordPress import, with its attachments. This brought me all my pages, posts, comments, and so on.
A little tweaking and my blog was as good as new. (While Danger is Eminent sometimes, I don't think that's what the signmaker meant!)
I think for your average user, who finds upgrading and installing a bit scary, this will seem even more scary. But it's not bad at all. It just requires you to follow the steps, write down or cut and paste all the information you will need to keep track of:
- one set of info for your web host account
- one set for your sql database account and phpmyadmin
- the information for your blog itself, for the WordPress install
- where you're saving the export file with your blog posts and comments!
In a pinch, if you really mess up in this process, you can get a backup and restore from your web host.
Now, even though I went through this process, I think that someone might potentially write a plugin or script to reveal and delete those hidden users. It might not catch all the modified data touched by those users, though. Spam may already have been inserted into your old posts, or some other havoc wreaked, which you could catch with Exploit Scanner or some other useful tool. The problem with this approach might be that there are multiple versions or exploits based on this security flaw and no one is sure yet if it's modified core WordPress code or created some other exploitable security hole. So at this point, I think it's best to do a clean install if you think you can manage it.
If you're not sure, turn off Javascript in the browser, go to the Users panel, and delete the people who shouldn't be admins -- at least. And maybe there will be an easier fix in a few days -- keep checking the WordPress development blog to see if it says something more useful than "OMG, you dumbass, why didn't you upgrade right away, never, never, never do that again!" (Thanks... I know... thanks for the lecture, grumpy sysadmin...)
When I did this -- and I had to, because "upgrade WordPress to latest version" was not #1 on my to do list, and a blog of mine got messed with -- I had to re-install my plugins and go through the steps to re-create my blog. This goes to show that it's a good idea to keep a worklog of all the things you've done to a blog, or a wiki or any sort of installation, so that you can recreate it from scratch! You can do this on your blog itself, by creating a section in your About page or somewhere else, listing the plugins you use, and when you've upgraded, and so on. It is especially useful to share this information a group blog where you might have more than one administrator. If you haven't done this you could just be sure to do it next time and then write a really cranky blog post about how you don't understand how anyone in the world could be so clueless. HA.
Good luck and here's some more links on the subject!
WordPress Codex FAQ: My site was hacked
Old WordPress Version attack warning: please upgrade
Checking your WordPress security
Posted by
Liz
at
9:54 PM
1 comments
Labels: open source, software, upgrading, WordPress
Sunday, August 02, 2009
OSCON fashion, Ignite, and beyond
I had a fabulous time at OSCON! In the spirit of my notes on the geek dress code, here's an OSCON fashion report.
Glasses were definitely IN. Me and Mario G. spaced out for a long time wearing these Trip Glasses! Maybe that's why we got into such deep conversation later in the corner of the Open Source Politics session.
Ingy döt Net models his 5 pairs of sunglasses. I'm not sure if this was a particular message about redundancy in code or if it was just one of those Ingy things.
Librarian Avenger Erica had the best shoes:
But seriously, OSCON. I had a good time and talked to a lot of smart interesting people. I hung out with Denise and Mark from
Skud's keynote Standing Out in the Crowd was great. I'm still kind of absorbing some of the reactions to it from O'Reilly Radar and from Linux World News. Women in any tech field, don your best armor before wading into those threads. My feeling is that it could have been a lot worse though and maybe we've reached a tipping point where enough people understand there's some problems and have a clue what might be helpful. For me, one of the more depressing things that happens in this field is when women with about 100 times the status and skill level I have end up giving the (private) advice that while they agree with all this and still feel it, they think it is bad for one's career to mention sexism or feminism ever. In this case, hurrah, that just didn't happen (at least that I'm aware of.) However, I think it's still the case that the vast majority of women I know in my field do feel the effects of misogyny and sexism and are often enraged by it in ways difficult to express. I would like to go further out on a limb here and say that the intersections of geek fandom culture and open source/tech people combined with the ongoing discussions of race, class, gender etc, like Racefail '09 for example, have upped the level of awareness and of discourse and have really changed some people's perspectives. Not that that translated into anyone in this discussion going "Hey, how about the rather low number of African American and Latino/a folks represented in open source at this conference and others in the U.S.?"
Anyway!
I enjoyed speaking at Ignite OSCON and hearing the amazing lightning talks.
Selena Deckelmann's talk on the election in Nigeria was pretty great. As a Postgres expert she went to connect with a few IT guys in Nigeria who were scanning and analyzing the fingerprints on a large sample of ballots. Some huge percentage of them were duplicate fingerprints. After a long legal battle, Olusegun Mimiko was declared the legal winner of the election and the governor of Ondo state.
My own talk was a short version of the DIY for PWD talk I gave at ETech.
Here's what I said, more or less:
Hi, I'm Liz Henry. Would you like a flying jetpack? I really, really would! To get them, we're going to need to apply DIY and open source ideas & organization to hack accessibility - and the idea of disability.
My wheelchair is a machine, a tool to get my body from one place to another. I'd like for it to be easy -- and possible -- for me to fix and hack. Like a bike, or a car. It's no more complex. I want root on my own mobility.
You can easily find information on how to fix a car. even though a car is like a giant polluting killing machine. There are books, tools, manuals available. The barriers to entry are low, so lots of people start car-fixing businesses.
You can find out how to fix a bike. There's tons of information freely circulated to the public. There are 20 million bike riders in the US. There's little independent bike shops everywhere. It's an industry.
But how to fix a wheelchair. 55 million disabled people are NOT feeling lucky. It's very hard to find information on how to fix a wheelchair. Or build one. How to sew your own seat back, build lightweight interchangeable parts. Nope!
Oddly, rather than being just a tool like a bike or a car, a wheelchair, walker, even a cane, is considered a MEDICAL DEVICE. Its invention, distribution, maintenance are under the control of powerful elites.
Why should you care? Well, because YOU will likely be disabled or have significant physical impairment for around 8 years of your life. That's the average in industrialized countries. No amount of individual power changes the systemic problems disabled people face.
How can you avoid this fate? Dick Cheney, one of the most powerful people on the planet, threw out his back and ended up in the worst vehicle ever. 50 pounds of cold steel, it might as well be a wheelbarrow. You can't get around in that. Bang, he's lost his independent agency.
It's not all about wheelchairs. As coders you might think about hand functionality, dexterity. People invent stuff to help with that. Most of that info's in out of print books, and on a couple of personal blogs. Can vanish into the mist ... like a geocities page...
Why should you care now? Until you need it, you don't care. When you do need it, you're busy. you're poor. and you're in pain. No telomere-fixing nanobot is going to save you from age and impairment. Impossible utopian nanobots are why we don't HAVE jetpacks.
Why isn't disability hacking more popular? Two big reasons. Attitude, and socio-economic factors. Bad attitudes are: Fear of mortality. Medical experts. Expectation of charity. Isolation. Lack of information sharing.
The second factor is systemic and socioeconomic. Your impaired body makes you disabled, so you fall under the control of the medical industrial complex. Your wheelchair repair manual or voice control hack might get you sued. Might violate copyright or a patent, might ruin someone's profit.
At some point YOU will need assistive technology. And you will want to hack it. You'll need a DIY attitude about access. You'll really need open source information structures and communities. Big projects, and the ability to customize things.
Here's some cool DIY hacks. Bicycle crutch holders made from PVC pipe. I can ride a bike, I just can't walk too well. Soda bottle prosthetic arm: a bottle, a plaster cast, and a blowdryer: cheap but it works. Crutch pockets to help carry things when your hands are full.
Here's a great project you could join. Tactile maps, a brilliant mashup for people with visual impairments. Email them an address, they print and snail mail you a raised print map. Software and hardware people are collaborating on this.
And another, oneswitch.org, a brilliant collection of hacks with step by step instructions on building one-switch interfaces to electronic devices. Control with a finger or by puffs of air. Others: Whirlwind Wheelchair international, open prosthetics project.
People with disabilities need open source culture. But existing open source culture needs the physical inventiveness and software adaptations driven by necessity, made by people with disabilities. Everyone disabled has a cool hack or two. They *have* to. Pay attention to them.
In the future... Will you be a sad lonely person fumbling to epoxy tennis balls onto the feet of your totally World War II looking hospital walker ? The recipient of charity, pity, mass produced help, at the mercy of what elite "experts" think is good for you?
Or will you be hacking your burning man jetpack as part of a vibrant community that supports serendipity, free access to information, non hierarchical peer relationships, and a culture of invention?
What will our future be? A DIY approach to hacking ABILITY... will help everyone. We'll invent cool shit! We'll open sourceily collaborate our way out of nursing home prisons run by the evil medical industrial complex AND... the future will be awesome!
Thanks.
For a bit more burbling about OSCON and BlogHer '09, see my post on blogher.com: From OSCON to BlogHer.
Posted by
Liz
at
9:19 PM
2
comments
Labels: conferences, fashion, open source, oscon, people
Sunday, February 01, 2009
She's Geeky - Tour of WordPress template code
There were 20 or so people at this talk, including non-programmers and programmers wondering if they should install WordPress, and bloggers and admins already familiar with WordPress. We did a round of introductions:
* Graphic designer interested in what degree of control she could have over a WordPress blog.
* Benay, running a blog connecting seniors with caregivers.
* Collie, looking for help with a WordPress upgrade on a complicated blog. Where is community to find help or pay someone to help? (Collie and others: you might try Heather L. Sanders. Anyone else have recommendations?)
* Person who installed WP to force herself to learn more code. Curious about plugins. Which are most useful?
* Terri - uses WP at her job for blogging, thinking about running her own for personal use.
* Nadine - Installed WP for other people many times. Does a lot of troubleshooting.
* Laura - Has installed and messed with WP many times. Wants to create a template from scratch.
* Stephanie - has an HTML site. Might want a blog.
* Olya - is a blogger. sometimes has language barrier while troubleshooting.
* Estella - artist, craisin.com.
* Crystal Marie - adding a blog to her existing web site. Looking at WP and Drupal.
* Beth C - Loves WP. Would like to do more customization.
* Michelle - Is a coder
* Vee - Blogs for her company. Knows HTML.
* Min - Uses MoveableType, is curious
* Karen M. - Thinks there might be entrepenurial opportunities with WP
* StephanieBamBam - Personal blog
I've been using WordPress for several years and administer a group blog. As part of my job, I do tech support for bloggers who run into template problems and quite a few of them use WordPress, so I look at a lot of different templates and help people troubleshoot. (The other part of my job, I munge data, write back end tools and infrastructure-y scripts in Perl, Python, and PHP in an aspiring codemonkey way.)
I started out by saying that WordPress was blogging software that you can either use on wordpress.com, or can download for free and install on your own server or web host. You will need an account somewhere and need to have it clear in your mind that you've got a username and password for that server account. In that account you'll be making a folder where you install WP, and then you'll have an administrative username and password for the WP admin and blogging interface. You may need to pay attention to this in order to change file permissions and make your theme files writeable if you want to edit them from the Theme Editor web interface. This tends to confuse people who aren't used to web hosting. Also, some people use web hosts which have one-click installs or who install WP for you and then charge to upgrade or maintain it.
We looked at the files and folders in a WP installation. There was some discussion of how you move files around and edit them. (Either from the command line on your server, from the admin interface for theme files, or with FTP; you can download the WP files, and extra themes and modules, to your computer, then upload them to your web host.) It's a good idea to just look through all the folders, so you know what's there. You may want to read through the wp-config file. But most of what people deal with is in wp-content, in the themes and plugins folders.
We then looked at the WP administrative dashboard, a bit at Widgets, and then at the Appearance menu and the Theme Editor. I said that editing code in the Theme Editor window sucks. While it's great for making quick changes, I recommend you edit the files in a text editor that will color code the code and indent it nicely, like vim or Textmate. You can pass code back and forth with other people by putting it into pastebin.com, which will also color code and indent it nicely. Also, it's amazingly helpful to print out all the template code, and mark it up with pen, and see which bits you can understand; or at least understand more or less what it does.
I explained briefly that anything that looks like a command with parentheses after it, like get_header, is a function and you may need to look for it in functions.php to figure out what's happening. We looked at index.php for a little bit. It is helpful to read through it. You should be able to mark what is header, what is the content (including "The Loop" which will cycle through your posts), and what's the footer.
The WordPress codex is your friend. Here's some great starting points:
* http://codex.wordpress.org/Using_Themes
* http://codex.wordpress.org/Stepping_Into_Templates
* http://codex.wordpress.org/The_Loop
Take a look at your sidebar.php file, header.php, footer.php, and page.php for individual post pages.
At some point, I mentioned the site to look for and download WordPress Themes. You can specify whether you want fixed width or floating; one, two, or three columns; and other parameters such as the main color. It is often best to start with a fairly popular theme.
Keep track of customizations you make to the theme you pick, because at some point you will want to upgrade or change it. Make backups.
There was some discussion of plugins as well. All in One SEO Pack (which sounds a bit evil, but which is great since it makes your URLs a bit more human readable as well as search-engine-friendly) had good recommendations. Stats, Sitemaps, and various Flickr or photo plugins were mentioned by bloggers at the session. On the group blog I co-administer, we had written some code to pull in a list of all our plugins onto a static page called "What we use", which has come in handy many times when we want to recommend useful plugins to other people. (Whoops; when I tried to show this off, I found that our recent upgrade to 2.7 had broken this code.)
The post template plugin was mentioned for its usefulness and for being able to pick a post or a page and "template-icize" it. This sounded intriguing!
Someone else mentioned that people should be aware that new plugins might break other ones and if you run into trouble, uninstall some plugins and see if that fixes the problem.
Someone else asked if there are good books for learning WordPress theme development or php. I don't know about books, but php.net is fantastic, and the WP Codex is quite good. The Codex is also editable by its users, so if you use it a lot, make an account, log in, and fix any documentation that's wrong when you figure out a solution. I also recommended blogging your template or code problems or posting on forums, and then posting the solutions to those problems when you figure them out. This is hard to do sometimes, but the more of us who do it, the better.
When I mention IRC at this conference my general impression is that people aren't using it that actively and many people don't know what it is. People who were techy or coding at all or playing on MUDs or smoething before the web, or before about 1995 or 96, know what IRC is. People who learned their stuff or got involved with online worlds after that, it's much more hit & miss. In any case, I continue recommending people try IRC and hang out in channels on freenode that have to do with the tools or languages they're using. Here's some explanation & guidance on IRC and WordPress. Lurk for a while, pick up the culture of the channel, and you might be surprised you can actually answer other people's questions: when I do this I tend to feel better about asking questions myself.
At some other point I mentioned MAMP again. It's very handy and easy to install, if you want to run a local web server off your Mac in order to develop and test. While I was doing this hour long talk, at least two people downloaded and installed MAMP and WordPress and got it running on their laptops.
I enjoyed this session! We didn't go all that deep, but we covered a lot of ground and people seemed energized by the ideas and possibilities. If you were there, thanks for coming, and let me know how your project turns out!
Posted by
Liz
at
2:42 PM
2
comments
Labels: blogging, open source, php, She's Geeky, tech, WordPress
Saturday, January 31, 2009
She's Geeky - Install Drupal on your Mac
In this session we talked about Drupal in general, and a few people, including Margaret Rosas from Santa Cruz Geeks and CrystalMarie, got it installed and running. I have to apologize for being a bit incoherent; I was tired and unprepared. It was worth the session anyway to introduce the idea that you *can* run drupal on your laptop and use your laptop for development and testing! Margaret and others saved the day by having plenty to say about Drupal, Drupal 6 modules like Original Groups, what will be new in Drupal 7, and how interesting the process has been for re-organizing the Drupal web site.
If I had do-overs, here's how I'd run this session:
- First of all, have already rewritten Installing Drupal on a local MAMP setup to improve its instructions.
- Quick description of what Drupal is. Show drupal.org site.
- Quick introductions around the room.
- Pass around a few USB drives with zipped MAMP and Drupal files, with versions 5 and 6, for people to install and copy over to their laptops.
- Pass out a printout of Installing Drupal on a local MAMP setup.
- Ask people to team up in pairs.
- Give an overview of the install process, but without doing it.
- Then everyone is free to do the install.
- People who get it installed should then go around the room and help other people get it done.
- Mention IRC, #drupal-support, drupalchix, and drupal.org documentation as good resources.
We ran into various difficulties. Some people had file permissions problems; it worked to make the entire drupal directory and all its files and directories readable and writeable, though that seems less than ideal. Also, we had some difficulty doing the first login, which I'm still going through with Laura from Indie Craft Gossip.
Thanks to everyone who participated! I didn't take down your names, but if you want to comment and link back to your blog or Twitter or your company, I'd love it. Also, if you're in the Bay Area and want to hang out messing around with Drupal, ping me and let's have a Drupalchix meetup sometime in February.
Posted by
Liz
at
11:20 AM
0
comments
Labels: drupal, open source, She's Geeky
Monday, December 22, 2008
SCALE conference: Women in Open Source
I heard about this conference, the Southern California Linux Expo, only because they have a Women in Open Source track. It showed up on my Google Alerts and on several of my mailing lists. Here's their call for proposals to give talks.
Since I've never been to the conference I wondered what kind of talks they've had in the past. How can I know what to propose, otherwise? Or if what I might talk about would be useful (or hard core enough) to their participants?
I went looking to see what the past Women in Open Source tracks were like. Here's the schedule for SCALE 2008, with links to the talks and participants. I would have gone to the Education panel, the long spam-fighting talk, community manager talk, open source mentoring talk, Building Websites with Drupal, and the women in open source panel discussion. The 2008 BOF schedule was posted too. I might have liked the EC2 and the MySQL groups! In 2007, there was a Women in Open Source mini-conference or track.
It is not so much that the topics are different in the years before there was a Women in Open sorce focus, but the fact they have bothered to take steps to show women's participation makes me feel much more certain the conference will be interesting and I won't feel out of place.
It's nice to see someone doing it right.
If you miss OSCON because you'll be at BlogHer in July, this looks like a good conference to go to!
Posted by
Liz
at
12:27 PM
0
comments
Labels: conferences, gender, open source, tech, women
Saturday, November 01, 2008
Gadget love - Messing with my G1
Look, my G1 made friends with my Chumby!
So far I'm very happy with the G1. It has a great feel, it's easy to type on, its phone and net coverage is great so far in the SF Bay Area, and every day people are posting new new apps for it. If you are a sanfransocial chronic fidgeter like me you'll be snicking this thing open & shut all day, because of its pleasant slide-y feeling. And because you will be all like OMG I HAVE THE MOTHERF*CKING INTERNET IN THIS BORING ELEVATOR.
The first thing I did was to try out everything on the phone. My contact list, which is a giant mess, is in there from my old Razor's sim card. Seriously, it's a huge mess. The few people that I call all the time, I starred to move them over to the "Favorites" tab in the Dialer. The phone dialer is nice; I like dialing on the touch screen rather than with the numbers. The other thing about Contacts/Dialer that I like is the long, detailed call log. It took me a few minutes to figure out how to add new numbers from the call log to my contacts list: click and hold on a log entry, which pulls up a new menu including one to save to contacts.
I find it a little perturbing that I can't tell if I'm closing an app, or just backgrounding it. Is that stuff all still running in the background?!
In the browser, I logged into my gmail account. Suddenly a wealth of data is there for me, since I'm a heavy Google user. The top bar slides down window-shade style to show new email, messages, calls, or other notifications.
Maps - Fabulous. Try street view, then the compass.
Market - Works great for me so far. Fun to browse. I like the comments/reviews on each app, especially how they are often frivolous and rude.
Amazon MP3 - addictive, good browsing, works beautifully. Buy mp3s, move them over to your computer or server with no problem at all. I already love Amazon MP3 for its lack of DRM and its great selection especially in Latin music.
Browser - Okay, but I have a little trouble zooming, clicking, entering data into tiny boxes. I think it takes practice with the tiny trackball.
Calendar - Scary good if you use Google Calendar already. I have 4 calendars going at once. So far I find week view the most useful - there's no text on it but you can tap a colored block for a quick popup that gives details.
Gmail - okay, but I wish I could delete
Camera - still playing around with it. Works very well in low light! Seems a bit slow, but autofocus works well.
Music - Slick!
Pictures - Works just fine
Youtube- haven't tried it yet
Voice Dialer - Works! neat! Will I actually use it? No.
I stuck some photos on it and changed my desktop to a photo from my Flickr account. Therer's a Flickr group with 640 x 480 photos to use for wallpaper, and you can find more wallpaper on the various community forums. Moving from the left and rights sides of the desktop to the middle & back is strangely addictive and beautiful. I tried for a while to move apps by flinging them, or holding them and scrolling, but couldn't get that to work. INstead, if I want to move something from the center screen to the left or right, I click and hold, drag it to the trash; then go to the side screen, click and hold on the background, and add the alias to that app or shortcut.
After a while I looked at App reviews and "tips and tricks" on some of the forums: Android Forums, Tmobile G1 forum, androidcommunity.com.
When you plug in the G1 to a Mac with a USB cable, you will see just 3 folders: albumthumbs, dcim, and Music. Poke around in there and see what you can see. Drag some music over to the G1's Music folder and it shows up in your Music app.
When you are browsing, click and hold on a photo to download it. Not sure if this works with pdfs, movies, or sound files - I haven't tried yet. When you download something from the browser, a new folder is created that you can see when you poke around with a USB connection. Same for amazonmp3 and BlueBrush - they create folders you can access through a USB and your computer's filesystem.
At some point I downloaded some apps and messed around with them. when I first got this beast early this week, there was barely anything except like 500 different tip calculators. Hello dorkwads, take the tax, double it and add a dollar or two, you don't need to whip out your $300 phone to calculate the tip ... OR DO YOU...
Amazed - a simple marble-in-a-maze game.
AnyCut - looks useful to make shortcuts.
Barcode Scanner - Interesting! But has way more potential
Bluebrush - I have not really explored it but it looks like a collaborative whiteboard drawing app. I would not call its menus or icons intuitive... Flailed a while then left.
Cab4me light - Great potential! I need this! Needs more cab companies, data, a button to turn the GPS on and off.
ConnectBot - YAY I can ssh from my phone! This makes me happy. If I could ssh into my phone as well, maybe use scp, wouldn't that be nice?
Es Musica - Tried this for fun. Hey, bikini boxing!
iSkoot - Skype for the G1!
Langtolang dictionary. Simple translation dictionary for several languages.
Shazam - This is good. It listens & samples a few seconds of whatever music you're listening to and identifies it. I tried it with a range of music. It had great accuracy.
Strobe Light - this is really great if you're a total asshole. Of course I downloaded it.
WikiMobile - How handy. Will never have another restaurant argument again. Am already a know it all trivia-hole, and now I can prove it on the spot. I haven't tried the other Wikipedia app yet. How do the different versions compare?
Here's what I'd like to have on my G1:
* password/keychain manager. What a pain in the ass entering all this stuff.
* a plain old compass app, unrelated to Street View.
* Ecto, or some equivalent, so I can post quickly to any of my 24812469 blogs, which are not all on Google/Blogger/Blogspot.
* Photo uploaders. Better extensions to send photos out very quickly to Flickr, my various blogs, Twitpic, or whatever. Hot buttons, so that I can snap the photo, and hit a single on-screen button to go "send to X" rather than pull up a menu, connect with gmail, start typing, and send to my Flickr email. It should be seamless, so I can take another photo or act like a human being instead of a little gnome fiddling with my magic box all day long.
* G1-Thing, to hook up one of the barcode scanners with LibraryThing.
* Inventory functions. More "barcode scanning a list of objects" functions. When I scan a bar code I don't necessarily want to look it up on google or amazon or ShopWhatever. I might want to just add it to a list of Junk in my Trunk. I could see people scanning their CDs or books or DVDs here. Or hooking in the list of stuff in their pantry to somewhere like FoodProof, to figure out what they could cook without having to shop.
AAAAAA! Did I just mention computers and recipes in the same breath? Maybe I should go back in time and buy a Honeywell Kitchen Computer!
* GPS. I would really, really love some cool GPS functions. I love the satellite tracker/detector screen on my old (borrowed) Garmin eTrex. I would just turn that thing on and stare at it for 10 minutes to see how many satellites would pop up. I'd like to know what satellites so I can look them up online. Better yet pop me up some info and tell me all about it. Holy crap! SATELLITES are flying around over us in SPACE. That never ceases to be cool.
Some geocaching apps that hook in to geocaching.com would rock.
* Tide tables. I have no reason to care, except that when I'm driving up to the city, if it happens to be low tide or a super low neap tide I might swing by the beach to poke some anemones and harass a hermit crab or two. If I were still surfing, a surf report app might be nice.
* Nethack. The real kind not the graphic version please!
* Auto rotate. Last but not least. I wish that the screen view would rotate when I turn the phone, not just when I open the keyboard! Or is that a setting already, and I've missed it?
Posted by
Liz
at
9:25 PM
17
comments
Labels: computers, gadgets, open source, software, tech
Thursday, June 19, 2008
Installing Eeebuntu on an Asus Eeepc 900
Last night I installed eeebuntu on my Eeepc 900. You see how I love this little beast!
The instructions and forums on eeebuntu.org were helpful. I realized while I was doing the install that there's Ubuntu Eee as well and that eeebuntu is basically just this one guy, Steve or "bezdomny". Since he is super responsive on the forums and people report good experiences with the install, I figured it is a good bet as an OS. Ubuntu Eee also looks good!
I didn't take good notes but here is my memory of what I had to do. I first tried to create a bootable USB stick from my Mac, but was missing syslinux so I used Oblomovka's MacBook running Ubuntu to reformat it with parted (set 1 boot on). Then put the eeebuntu iso file on the USB stick with bezdomny's isostick.sh script.
Then my eeepc booted from the USB stick. I hit "escape" during bootup and got a screen with 4 choices; the 4GB and 16GB drives on the eee, and two partitions on the USB stick. I chose a USB partition at random (wrong one) and then the other, which worked beautifully! It took a few minutes to boot. Wireless didn't work, but when I plugged an ethernet cable into my Eee, I was on the net within about 15 seconds without having to configure anything.
So, I tried to follow this advice to get wireless working,
http://eeebuntu.org/forum/viewtopic.php?t=175&highlight=wireless
But then got a little bit confused because I wasn't sure where I should install madwifi and if it would work if I rebooted from the USB. At that point I decided I'd just take a chance and install over the totally working, but annoying and ugly and Windows-like, Xandros linux install that came with my eee. (Seriously, look at this, even their web site gives me hives.) It occurred to me that I might keep Xandros on the 4GB drive and install eeebuntu on the 16GB drive, and be able to boot either one. Which, if I couldn't get wireless working on eeebuntu, would spare me scrambling around trying to re-install Xandros. I went on IRC at irc.freenode.net and asked on #ubuntu-eeepc if anyone knew if that would work. No one answered. I got on #ubuntu-women just to feel braver but didn't ask anything. After some more poking around forums I decided to hell with it, blow away Xandros and if I have to reinstall it, comprendo bastante este video guía para instalearlo.
So I installed on the 4GB drive. It went completely smoothly, quickly, I rebooted, hey presto magic huzzah, I had working ubuntu on my eeepc. Plugging into ethernet worked smoothly again. I got the madwifi fix with wget and installed it. It didn't work... I re-read the thread on the forums for the millionth time. They kept saying "turn on the wireless" and finally Oblomovka and I got it that we had to turn on wireless in the BIOS. So, reboot, hit F2, looked at "Advanced" and "Devices" or something like that, it was pretty intuitive, and got a list of stuff enabled and disabled. I enabled wireless and the webcam. Rebooted, and wireless worked SO beautifully. (Not like Xandros which was incredibly clunky and failed to get me onto my own home network half the time.)
More wireless links: https://help.ubuntu.com/community/EeePC/Fixes
Next problem to fix. The mousing was crazy. Or, really, the touchpad. I don't have a mouse, but I still think of it as "mousing". There was a system preferences panel for mouse and display, but nothing for the touchpad. A bit more reading and I was lost... but then a bit MORE reading and google-fu and I found that going to Applications, then Add/Remove, then searching All Available applications for "touchpad" or "synaptic" would get me the control panel that I needed. That worked but during install I got a warning to change a setting in xorg.conf which I will tell you is in /etc/X11. It's helpful to look at some examples of xorg.conf options. Then, while in vi putting in the setting, I realized my keyboard is messed up and thinks that the " key is actually an @ sign. So I'll have to go figure that out and fix it -- I know I chose US keyboard layout -- what could it be?
What I need to be able to work off this machine on my trip:
Firefox, Greasemonkey
A good chat client
vim, perl (python would be nice)
the touchpad not to be freaking crazy. Tap-to-click OFF. Who uses that! Omg! Sucks!
Not sure if I will just suck it up with email and go back to Pine, or install Thunderbird and migrate my mailboxes, or use webmail of some stripe (ugh) Currently am favoring Pine because I'm lazy; Thunderbird only if I have time to install it.
Oh also, I'm resolving to document this more formally and contribute docs-writing to eeebuntu.
** further updates later today **
Posted by
Liz
at
9:51 AM
4
comments
Wednesday, May 21, 2008
Free Idea: Use ChaCha's structure for disaster relief
On the drive up to Seattle a few weeks ago, Cindy and Sarah Dopp and I were playing with ChaCha and wondering how they make money. Around here we all go "What's your business model" right away... and then snicker.
So I think I might just have figured it out. Do it for free for a bit with your VC money and show how it works. Then, sell "Enterprise ChaCha" or something like it, to a big institution. (I was looking at Indiana University's page about it.) You'd sell the structure and the setup, and the institution creates its own number (and password or validation system) and pools its own experts. So, sell it to Exxon or something for its corporate librarians and geologists. Or to the military, obviously. Here is the military's answer to its perpetual search for AI. "Human assisted search".
Anyway, this could also work for disaster relief, because it's ideal for situations that change very rapidly. I was looking at Jon's empty wiki and thinking, well aside from all the problems with the whole idea of that, which I won't go into, might a Twitter feed be better? I thought of myself on the 2nd floor of the Astrodome after Katrina, gathering and putting out information that was extremely up to date, and how quickly things changed on the ground. Would I want a wiki for it? (I tried. It is hopeless without a core of people already trained to use one and to work together with one.) Maybe I wouldn't want one. Maybe a feed would be better. Page back through the "2nd floor astrodome" Twitter feed and see what's up. Combine many different channels of all the people at various stations in the Astrodome and you'd know who says what is true, right in the moment.
But even better -- a private setup for a ChaCha-like thing. You get 100 people together to monitor and answer questions and you would have an instant backup, fit for the general of an army. Or fit for a reporter on the ground in a rough situation. I think of how I combed google news all day long for the Back to Iraq guy back in like 2003 and emailed him updates on whatever was going on or being bombed in the area near him. How much better, if he could have called a phone number like ChaCha's, and tapped into a network of people like me. Someone would have texted him back the information he wanted within minutes. And if there were sort of a combination of Ning and ChaCha, you'd be able to set up your own information broker network and invite people to join it.
The Red Cross should be using this (okay, maybe in 20 years if they can get it together that fast). But, I offer the idea up to whatever nonprofits or disaster relief workers can use it.
Posted by
Liz
at
12:15 AM
0
comments
Labels: disaster relief, ideas, information, open source, software, tech, web2.0
Sunday, May 04, 2008
DIY: Access Hacks project
For the second year in a row, I thought of the wheelchair modification and disability access projects that could and should be at Maker Faire. I'd like to make that happen next year.
At Maker Faire this year, I talked with Miguel Valenzuela, who was showing Lift Assist, a toilet lift device that can be built for $150 out of bits of PVC and junk from a hardware store, powered hydraulically from your own water system. That kind of thing costs thousands of dollars if you buy it as a medical device. If it were a DIY kit, and if it had open source plans and instructions up on the web, it could be useful to thousands of people all over the world.
So I got to thinking. Who would I even hook Miguel up with, to get his plans used? What other projects are spreading disability access devices, open source? Could things like this just be given over to an organization like Engineers Without Borders? How can they be open sourced or copylefted? Who's collecting that information? Certainly not the U.N. committees on disability - ha!
There are specific projects like Whirlwind Wheelchair International and its design for the Rough Rider chair, developed by Ralf Hotchkiss and students over many years and meant to be distributed to shops or factories or organizations in developing nations. In other words, partnership with actual manufacturers. There's the Free Wheelchair Mission which has a kit to build wheelchairs for under $50. They seem to take donations and then ship a giant crate of wheelchair kits to somewhere in the world. Those both look great. But neither of them were for a disabled person who might want to build their own stuff.
Then I found some nifty sites like Marty's Gearability blog, which has a DIY category for "Life with limitations and the gear that makes things work". She has made dozens of posts on modifications she's made for her dad, who uses a wheelchair. I especially enjoyed the how-to for a wheelchair cup holder and the elegant, blindingly useful offset hinges to widen doorways.
I'm also somewhat familiar with Adafruit Industries and its projects like SpokePOV. What if assistive devices used something closer to this model? Rather than people patenting, and trying to sell their designs to a medical supply company, which marks it up a million times until disabled people in the U.S. can't afford them unless they have insurance or can wait 5 years and fight a legal battle with Medicare.
I found organizations like Remap in the UK, that takes applications from individual disabled people, and hooks them up with an engineer who will build them a custom device. This I think exemplifies the well meaning but ill advised attempts to help disabled people through a "charity" model rather than through widespread empowerment. If an engineer is donating time and an invention, why not have them write up and donate the plans for whatever they are building, and post the DIY instructions for free? Then, thousands of people all over the world could build that invention for themselves.
Here's another data-sucking black hole of information that should be out there on the beautiful, wild, free internet: academia. This paper on bamboo wheelchair designs is probably super great, but who knows? Only the libraries who have the bound copy of the conference proceedings of the 5th international bamboo conference back in 2002. This makes me very, very sad. OneSwitch, on the other hand, has the right idea. It's a compendium of DIY electronics projects to build assistive devices. Perfect!
Meanwhile, I went looking for the latest news in open source hardware. What's up with the Open Source Hardware License?
My own inventions for assistive devices have tended towards the creative yet slapdash use of duct tape. For example, my Duct Tape Crutch Pockets, an idea easily adaptable to small pouches for forearm crutches and canes, or to get more storage space onto your wheelchair.
My own canes and crutches that fold (with internal bungee cords) could use simple velcro closure straps to keep them folded up while they're in my backpack or in the car. There are some ingenious ways, also, to attach canes or crutches to a wheelchair.
I have thought of, but not made, ways to extend storage space further. For example, I think that the lack of pockets in women's clothing is a political issue. Women's clothes are mostly designed without pockets, because of cultural pressure to look skinny, so women end up encumbered by bags and purses. If you think about how wheelchairs are made, it is interesting that they are assumed not to need storage space, cup holders, things like that. People hang little backpacks off their chairs. And there are a few custom made pouches for walkers, crutches, and wheelchairs, like this thin armrest pouch. You won't find them in an actual wheelchair store - and rarely in a drugstore or medical supply house. Why not?
As wheelchair designs continue to evolve, I hope that manufacturers will create customizable backs and sides and seats. Nylon webbing with d-rings, sewn into the backs and under the seats of wheelchairs, would mean that custom pouches and packs could clip onto a chair. Then it would be easy to set up your chair with interchangeable bits. My laptop could go in a pouch under the seat, for example, so that it wouldn't affect my center of gravity so drastically as it hangs off the seat back in a backpack.
I'd like to see more and more mods for chairs and canes and crutches that are just for fun. The little holes in adjustable-height, hollow metal walking canes -- don't they seem like the perfect size to stick an LED light in there?
Also, meanwhile, I had posted briefly the other day for Blogging Against Disablism Day 2008 with a list of ideas for Practical actions that will help, like smoothing out steps into a small business (ie just freaking pour some asphalt in there or build a wooden wedge even if it is not exactly to code; people do nothing, for fear of being sued, rather than spend thousands to do a to-code ramp, and I'd rather they just stuff in a slope and bolt a rail to the wall than do nothing!). After I made the list, I went looking for online instructions on how to do the things I was suggesting. What did I come up with ? Jack shit! Nothing! Nada!
So, here's what I propose we do:
- Compile free and open source how-tos, plans, designs, etc. on Disapedia. I have made a page for DIY equipment.
- I will go and interview Hotchkiss and his class, and write up more detail on how their open source project works.
- A meeting to share access hacks and start to add to that wiki page on Disapedia.
- I'll head up an effort to organize a really good disability/accessibility hacking booth for Maker Faire next year.
For the Access Hacks booth, I'd like to pull in:
- craft/sewing people for stuff like mobility device storage and mods with velcro and fabric
- metal working people
- electronics people (like the OneSwitch folks)
- Maybe invite Tech Shop and the Bay Area wheelchair stores to participate
- obviously, disabled crafty/makery people. I thought I could try to pull in GimpGirl and put the word out in other communities
- Flyers on how to open source your hack and make it free - license info, where to post, hook up with places like WikiHow.
This could make a super fantastic real life application for hardware/craft hacks. I would love to just hang out all weekend with a bunch of other people with disabilities and share whatever hacks we've already come up with. That in itself would be productive without even doing it at Maker Faire. I'd like an Access Hacks meeting around here and I wonder if people would host them elsewhere and then post tips on Disapedia. (I would like to use them rather than host a new wiki, but I'm willing to make an access hacks wiki if that's what people would like.)
Please, leave feedback in the comments.
Posted by
Liz
at
2:14 PM
11
comments
Labels: disability, gadgets, ideas, mobility, open source, tech, wheelchairs
Monday, November 26, 2007
Folk logic computing for every gadget
Midnight blogging! I was thinking of all the science fiction about smart houses, like Smart House (Kate Wilhelm) or Remains (Mark Tiedemann). I don't want to talk to my house, and I don't want it to be a master controller of Everything in my living environment. Instead I want all my household gadgets to be more like my Chumby. I don't want to freaking "program" my VCR or my coffeemaker. I want to swipe the widgets that my friends hack up. A couple of years ago I talked at the first Barcamp about social networks and trusting small areas of expertise. But now I think that idea will be played out better through folk logic. My co-housing mate obsesses on automatic control of our houses' heating and so I bought a fairly cheap gadget with the most annoying user interface ever and now can never control the damned heat level of my house without consulting a 10 page user manual and going bleep bleep bleep oh whoops hell beep beep beep damn oh I give up, and then it reverts to how it was 12 hours later anyway. Screw that. The damn thing should run linux, like everything else should, and then I could log in to it and tell it to use Max's program which he had the patience to set up. Likewise, I don't care enough about TV to even mess with Tivo. (Count the number of media players in the world that right now are flashing 12:00, 12:00, 12:00, 12:00.) I would rather just copy my friend Laura's setup because I am likely to like anything she likes; we have the same taste in many areas, as you can see from our LibraryThing profiles. There are areas where I put in a lot of time and have tons of expertise, so my friends or fans would rip whatever widgety things I hacked up.
I can't quite imagine how or why we would program our fridges or bread machines or coffee makers but they sure as hell have oddly sophisticated computer chips in them already, and someone will think of something good. So why not -- my coffee maker should be truly "programmable" and have some kind of open source layer so that people can write stuff for it.
Everything computery should be hackable. I'm not going to have the time to hack everything, but someone in my social network will.
Posted by
Liz
at
11:51 PM
3
comments
Labels: gadgets, open source, tech, web2.0
Friday, September 14, 2007
A culture of free as in free beer, trust, and ethical payment
The other day I was checking out the developer preview of Songbird's music player, and had a few ideas. Right now you can use it like a browser, reading blogs and downloading mp3s from those blogs. In about 5 minutes I had found great music from búscate un novio and fuck me i'm twee (I've been listening to a lot of girly pop/punk lately.)
I'd really love to change the whole model of music distribution. Rather than buying the rights to do whatever I like with a song, I'd like to download it and listen to it without feeling like a criminal. I'd like it to be licensed under Creative Commons in some sensible way. And then I'd like my music players to include a tip jar.
If I like a song, I'll tip the artist, or the consortium of artists, or whoever does their distribution. For example, I'd like a guarantee that the original artist gets a particular percentage of the tip. Even if I knew they would get 50%, that would make me more likely to tip than I'd be if I had zero information.
Skyrocketing downloads, as music consumers felt the confidence that they weren't doing anything illegal, would fuel the music industry. We'd tip a song, or an artist, more than once. When I made a mix CD for someone and put my favorite song on it, I might tip again. Over the many years of listening to a song, I might tip its creator many times... generating more money for the creator, and for anyone in the middle like Songbird could be, than a simple "pay 99 cents for it" model.
I'd see in my music player that I'd tipped 3 times for a particular song or album. I could sort my music on paid-for or not, which would encourage me to want to pay more artists and feel good about my own habits.
Further, I could earn a reputation as an ethical consumer. My own profile -- on Songbird, or on some public site -- maybe on a badge I stuck on my blogs -- could proclaim that I've tipped musical artists 1052 times, or dollars worth of tips, in the last 5 years.
This information could build relationships between consumer and artist, or label or consortium. Kathleen Hanna would know that I'm her loyal fan to the tune of $30 over several years, and might send me announcements, concert information, free stuff, tshirts, or free new music.
This might also avoid the morass of micropayments. Create small payment structures for specific industries, instead of a grand scheme of people passing around the same .001th of a cent whenever they read a web page.
Posted by
Liz
at
3:10 PM
1 comments
Labels: collaboration, digital rights, ethics, ideas, open source
Sunday, March 11, 2007
SXSWi: Non-developers to Open Source Acolytes: Tell me why I care
Elisa Camahort is moderating. Annalee Newitz, Dawn Foster, Erica Rios.
Annalee Newitz explains the entire complicated insane definition and history of the Open Source movement in less than 3 minutes. Free redistribution, available source, derivative works okay, no restrictions on tech or users (http;//www.opensource.org/docs/definition.php) Licenses: gpl, MOzilla public license, BSD License. Commonly used open source software (oss): Firefox (MPL), OpenOffice (LesserGPL), GNU/Linux (GPL), BSD (BSD), WordPress (GPL), Apache (Apache License), Rails (MIT License), PHP (PHP License). The GPL is viral and powerful. Anytime you use software that uses GPL that you intend for redistribution, you have to release under GPL.
Elisa: I know some of the names of this software. But Rails? Apache? Okay, well, really I know what Apache is. But why does this matter to me?
Dawn Foster talks about OSS structure and leadership. It looks chaotic from the outside. Random people contributing code. How in the world can you end up with anything reasonable? But that's not how it is. You'd be surprised how hierarchical it is. OSS community structure.
Users.
Bug Reports: Community members submitting bugs to improve the project.
Contributors: Community members contributing to committers for review.
Committers: Trusted community members with access to modify code.
Maintainers: Direction and decisions for a portion of the project.
Leaderships: Strategic decisions, project direction.
Elisa: So, I'm not the only one who had no idea that all this existed behind the idea of open source. Erica is going to talk from the point of view of a company using open source software.
Erica Rios: My role at the Anita Borg Institute is to maintain the technical aspects of the organization. We use WordPress, for example. I see myself as a customer for these tools. I want help with installation, configuration. Is it going to have an impact on my server maintenance, what cron jobs I should run, what about backups, patches. When I hire people I need to know what kind of time and money I need to invest to maintain the software. What kind of customer service support do I get from a tool? The staff, my users, who are also the customers for this software. Does the tool do what they need it to do? Is it easy to use? Are they going to be able to figure it out, with or without support? There's a self-sufficiency question. Will everyone be coming to me for that help? I think of it like hardware. We're lucky enough to have HP Labs donate space to us. Our machines are still on warrantee and I can get service. Do I always need to know the details behind why something's not working? Is the community "friendly"? Am I going to go looking for help and be told RTFM? Because I've already tried.
Elisa: When you were looking at open source tools, was that part of your due diligence, did you look at the friendliness of that tool's open source community?
Erica: Absolutely. And it doesn't have to be a hierarchical traditional manual or documentation scenario. The community is so robust that I can type my question into Google and get an answer right away.
Guy in audience gets up and takes a mic. A lot of people don't realize some open source tools and projects offer paid support. Ubuntu, etc.
Dawn Foster talks more about open source and paid support.
Erica Rios. Developing friendships with other users and developers. If you have a personal relationship then people are much nicer in their explanations. With documentation, when it's written in plain language, it's more helpful. I have a degree in computer science, but I appreciate documentation in plain language, and it helps me communicate to my less technical users. Quality community can demonstrate their intelligence through the quality of a product but not feel ego-driven to demonstrate it in their documentation.
Elisa invites questions from the audience.
Same guy from audience: Questions about where the open source software came from. Fear of patent suits from big huge companies, etc.
Annalee Newitz: I've heard people talk about their management saying "You can't use an open source code because it'll creep into our code and we'll be sued." People need to be educated about the legal ins and outs of open source licenses. For example the GPL is one of the most radical ones... A company lawyer is good to go through the license and explain to management. There's a lot of online explanantions written by lawyers, for example through the EFF or some from Creative Commons. It's sad that people move away from the GPL but from a business perspective it makes a lot of sense.
Dawn Foster: It's less of a risk, because if there's proprietary code in there, someone's going to have noticed it. Or they can notice it. It's not really that different.
Annalee: I would strongly agree with that. The fact that you can look at the code means you can tell if there's a problem.
Audience member: Myth of putting it al out there and it being exploited.
Dawn Foster: I tend to worry less about being exploited by open source Eric Raymond "with enough eyeballs... all ... are shallow" I worry about backdoors and things in proprietary code, that I'll never know is there. The empowerment of being able to look at the code
Annalee: That's why you hire security auditors, etc. BSD, used by the miliatry, you can lock it down.
Liza: I'm going to be the downer here. THere is a cost for making it useable for people with no technology background. For example WordPress, it's so beautiful! But it's hard for people to use and to understand. So, users assume that level of customer service is free and that it's going to be free and that there's no cost to maintain it. And this makes it hard for developers and consultants to monetize what we do. Upgrading, security issues, etc. People coming into open source, think that it's going to be free .
Dawn quotes Richard Stallman, Free as in freedom, not free as in free beer. There are costs, time and money.
Annalee: When you're looking for a return on investment, long term will it be more costeffective to have this invest in maintaining this rather than paying Microsoft for a new license every couple of years? So yes, the long term costs are way better.
Erica Rios: We look at it that way at Anita Borg Institute. That's one of the key philosophical reasons I put to management, the flexibility we get.
Kimberly (from audience): Speaking as soneone who once upon a time had all sorts of Microsoft certifications and has now gone more into open source, there is more flexibility, there is very little barrier to entry, it's really a meritocracy. They can contribute and there's opportunities for them, they can build stuff for non-profits. To get Microsoft certified you pay a lot of money and yes there's support and community but open source has way more opportunity.
Elisa: Is there a way in open source to validate what level they are in an open source community?
Kimberly: I've had people use me as a reference
Woman in back: It depends on the community.
Erica: Now that I've gone through this process I look at how much a person has contributed and how much of it has been accepted in to the main trunk fo the software.
Dawn Foster: It's good for companies and hiring and companies can see people's code and status in a community before hiring them.
Frank (from audience): Reliability and continuity. You can always get someone to maintain it because it's not proprietary. Voting machines and cryptography. If the source isn't out there there's always someone out there who is so clever they can't see their own mistakes. But a community can see it and can find the broken places. As American people we need to get the source out there so we can rely on our voting machines.
Elisa: Thank you so much for bringing that up and articulating it. Let's talk about the philosophy and the reasons for supporting it. HOw many of you buy organic food, and free trade coffee? (Show of hands) We make economic decisions based on philosophical, emotional, ethical reasons. How many of you make technological decisions based on that? (Show of hands, a fair amount)
Guy in grey hoodie: (question)
Elisa: Kaliya Hamlin, getting non developers involved with open source communities. It's extremely intimidating, I can tell you. I'm a wannabe, but there's an idea that it would contribute to the greater good. Anyway, what's the ethical reasons to use open source?
Annalee: Oviously there's a lot of technical reason to choose it. And that's an ethical choice too, to make the technical choice that would benefit the most peopl.e But when yo have a product made by people donating their time, or a company is giving 20% of their time to give back to open source, you simply get a higher quality. People are working together. They own it. When people own the stuff they produce, it will be better. When you produce software that is proprietary and your company owns it, you are alienated from it. But with open source you put your love into it. You can play with it, deploy it, use it with your friends, fix its security holes...
Erica Rios: analogy of the free library. If we can't contribute and have free access to intellectual knowledge, we undermine democracy. Women and systemic reasons why girls and women often drop out of technical fields. Access. Open source is a unique opportunity for all women to have access to knowledge. If all software code was proprietary, I would never have looked at a pice of code in my life. I couldn't have afforded it. Period.
WOW
Erica: Dr. Fran Allen, just announced as a Turing Award winner, first woman to be granted this award. It's highly likely that a girl at the high school level right now, who has access to open source code, may achieve something as great as Fran. It gives other people access and opportunity and to contribute at higher levels. It's a key consideration in us achieving equality between genders in technical fields, and as we increase participation, we'll increase innovation.
Jory Des Jardines (audience): The Wisdom of Crowds. Ran an open source business project, because people didn't ahve the motivation, aka, pay. Does money mean motivation? Money makes it easy to commit, people are flowing in and out of this project. The explanation you're giving explains the structure, but what is the motivation for an engineer to bother?
Annalee Newitz: There are other rewards that people work for. We're at a conference where there are artists. They're hoping to make money, but they want people to appreciate their work. They want to create something beautiful and be acknowledged for it. Why do people want to have a higher reputation on Digg? They're not getting money for it. Well, some of them are. (laughter ... re. crowdhacking prank.) But there's a point, Hey, I've spent 4 years doing this kickass thing, now pay me.
Dawn Foster: Contributors to the Linux kernel. They pay people fulltime to do nothing to contribute to those projects. Those companies are motivated for that software to be good.
Guy: Dispel that there's anything anticapitalist about open source. More of them are libertarian than anti-capitalist. And about self interest and profit, my company went to open source, time, energy, money chasing clients on IP issues, waste of time. We got a better rate for our time to offer consulting services around it and provide the software as open source.
Erica: Who is mostly willing to work for free? Women. the motivation to work is there. There's a lot of stereotypes that we default to when we look at what it is that isn't working. There's probably a lack of supportive culture. Asked by Mozilla to tell what could help keep women developers. My answer was I don't know, ask the ones who are there and ask the ones who are leaving.
Woman with short black hair in audience: Ideals, but as a business manager, of a sucessful open source consulting and educaiton company, we charge a fair amount. It's a myth that keeps developers away from open source. Like it kind of smells like patchouli a little bit...
Elisa: You will not find musicians in an orchestra playing for free. Actors will do it for free. Bloggers used to do it for free but that's changing. Now we have blog consulting. People had passion that seemed to translate into not getting paid, Oh if I love doing it i shouldn't get paid. Open source has that too, if I'm passionate about it I shouldn't charge.
Annalee: You don't have to do it for free, just get your boss to let you spend 50% of your time doing it because it helps improve the product.
Guy in audience: I'm not understanding, please explain, what is the distinction between building proprietary products on top of open source software.
(Well, it depends on the license! )
Annalee: that's a good question and it gets debated a lot in open source communities. They are spelled out in the licenses. For example what will happen with Google and the GPL license. People need to be a little bit geeky about legal language and licensing.
Audience: How geeky do you need to be to say you're into open source?
Erica: For example our crm system....Not important for us to customize that part. But to customize web solutions is very important. If we don't need to hack it, let's not do it.
Technorati Tags: conferences, liveblogging, open source, sxswi2007
Posted by
Liz
at
10:31 AM
0
comments
Labels: blogher, conferences, events, liveblogging, open source, sxswi, tech
Friday, February 02, 2007
Women in Open Source
Women in Open Source - at SCALE in LA next weekend. Stormy Peters, Jean T. Anderson, Strata Chalup, Celeste Paul, Bdale Garbee, Randi Harper, and Dru Lavigne.
The Southern California Linux Expo (SCALE) will host a Women in Open Source Event as part of their upcoming 2007 conference, SCALE 5x.
The focus of this event is on the women in the open source and free software communities. The goal of this event is to encourage women to use technology, open source and free software, and to explore the obstacles that women face in breaking into the technology industry. The Women in Open Source event will be held on February 9, 2007 at the Los Angeles Airport Westin Hotel.
Time
I'm so tempted to go...I could probably get a plane ticket and fly down there and back the same day. Or, Strata said she could put me up in her hotel room if going back and forth on the same day would be too exhausting.
Posted by
Liz
at
7:23 PM
0
comments
Labels: conferences, events, gender, open source, tech, women