A bit of the summary of things since my last Blog Post - :-/


Home

To say I have been busy the last few weeks is an understatement at best. However, I don't think that is necessarily a bad thing, unless I don't stop to smell the roses in my life - my family, and they are awesome! My husband has traveled continuously for the last 5 weeks, stopping at home long enough to repack a bag, have meal with us and back out - we've missed him. My kids, they are awesome. There have been a few days I had appointments for various things and gotten home after they did, (They are teenagers so old enough to home for a few hours alone) and on those occasions, I have returned home to find they worked together to straighten up whatever it was I had missed doing that day. Gotta luv it when teenagers clean without being told - that is so awesome.

I've been spending more time with the kids after they get home from school, and after their homework has been completed taking time to laugh, watch a movie, talk about the day, play a game . I am not sure why but the kids were even more humorous than usual. I love laughing with them. Of Course they still throw in the occasional joke about "Ubuntu stole my Mom" or teasing me about "fine then I am installing " depending on the point they trying to convey it can range from other Linux distros to windows. That should be in the book of how kids of geeky Linux parents rebel. :-/

So I've been stepping away from my computer for a few hours, especially when they are home from school in the evenings and trying really hard not be on at night while they are still awake. This past weekend I took the kids out to eat, then to the mall, and to the movies. I was doing more than just smelling the roses I was attending to my garden. The fragrance is so much sweeter, when care is taken in the nurturing of them and yes they are in those teenage years so we still have some thorns that snag us everyone once in a while. We laughed, and talked about all the things that are on the calendar and they even added a few more things. In short we had fun!

We are still remodeling the house and due to the weather conditions our Kitchen installation had to be postponed a couple of weeks until the ground could dry out enough for the delivery trucks to make it up to the house without tearing up the driveway. Painting the living room, Kitchen, and dining room will get completed this week.


Events

SCaLE 8x
I have been working with the SCaLE 8x coordinators, and the CA Loco Team for the Ubucon event at SCaLE. I am giving a talk at the WIOS event at SCaLE - A Year NTEU the Ubuntu Community and the FLOSS World. I will also be giving one at the Ubucon at SCaLE - Every NTEU is someone's Guru - How to encourage the NTEU* in your organization. I'm also trying to see how many ubuntu community folks will be there and see if we can't grab a picture while there. I am looking forward to seeing the CA LoCo team members, Akkana Peck, Emma Jane Hogbin, and many many more folks in about 10 days or so.

(NTEU - Pronounced like In-To - stands for Non-Technical End User)

Southeast Linux Fest
I have also been working helping with the Southeast Linux Fest, as there will be an Ubucon there this year as well. The Call for Papers is still open so I don't know if I have been selected for the main event at SELF yet, but regardless it will be a great event and the Ubucon should rock. There will be an Ubuntu Booth at this event as well, any Ubuntu LoCo team who are planning on attending please feel free to volunteer your time to help staff the booth or help with the Ubucon. Please feel free to email suggestions for topics or submit a session for the Ubucon. Please include SELF Ubucon in the the subject line.

Atlanta Linux Fest
I have also been busy with Atlanta Linux Fest planning. There should be an announcement shortly as to the date and location of this event. The numbers from last year have pushed ALF beyond the capacity of all donated space we had. Good problem to have right. :-)

FOSSevents
I have also joined in on FOSScon, and FOSSevents discussions and planning. Though I can't claim to contribute much to these, but I am enjoying participating where I can. More on this in a separate post.

Did I mention I love event planning! :-)


Blogging

Not nearly enough. Though several posts are in some form progression I really need to polish them and get them added to both this blog , which is my personal one, and my You-in-Ubuntu blog, as there are several interviews in need of posting for my - People, Personalities, and Planners: Who's behind your FOSS events? series, Not to mention sending out questions for ongoing events. So you have events related to ubuntu, things that are happening in the community that Ubuntu Users can get involved in and contribute too - let me know let's get the word out. :-)

I enjoy blogging to, I really had know idea all the cool stuff you can find to talk about. Don't you just hate it when life interferes with all the fun stuff you like to do. (just kidding - well maybe)



Ubuntu Projects
Ubuntu Women Project
The Ubuntu Women Project is moving forward. As the team has defined that the "official " team member list will come from Launchpad. Subscribers to the mailing list and forums as well as those who are in the IRC channel are encouraged to join the LP team in order to participate in any voting issues. Also members on the Team on LP who are subscribed to the mailing list are encouraged to do so as well, this is another step ensuring communications of all current activities are disseminated to team members. Once the team defined who would vote, a condorcet vote was sent to the LP team members and a decision on the IRC channels was made. Almost all blueprint goals for the Lucid cycle have been meet and soon it will be time to look toward UDS-M.

The International Women's Day Competition will end in just a few weeks. February 22, 2010. If you are a women or know a who uses Ubuntu encourage them participate in this Competition. There's a great prize pack, sponsored by Canonical, Linux Pro Magazine and Ubuntu User Magazine also included in Jono Bacon's newest book, The Art of Community.

If you a woman in the Ubuntu Community and not a member of the Ubuntu Women Project please consider joining. There are women who's skills range from the highly technical to the just installed ubuntu and everything in between. So whether it's spring boarding into community contribution, developing a talk for an event, planning events, advice on dealing with sexism, or how to encourage women to get involved in Ubuntu and Open Source and more - the Project aims to provide an opportunity for women who want to be involved in the Ubuntu community thereby increasing the diversity in Ubuntu-Linux. Go here to learn more.




LoCo Leadership Series
At UDS-L, the idea for a LoCo Leadership Series was rolled out. It was The goal is to have Chapters 1-3 completed by UDS-M. Chapter 2 has been written now Chapters 1 and 3 need to completed. If you want to help with that email me.

USTeams
Ubuntu USTeams - New interview series targeting approved LoCo teams. These interviews will be posted on the USTeams Website, and the goal is to have the 1st one completed and ready fr March 1st. Looking for a place to help out and like to getting to know people in the community interviewing them is a great way and I already have some questions to start with if you are worried about how to start.

NC LoCo Team
Luv it - Ubuntu on a local level. The team is really working hard on becoming an approved LoCo team. There are now Ubuntu Hours in Winston Salem and a regular basis, and the folks in the Asheville area are looking at setting up regular Ubuntu Hours. Members of the LoCo team are working on building up the wnclug group as well. Right now it has an IRC channel on freenode (wnclug) and a mailing list. If you are in NC and you are interested in all things ubuntu please considering joining the team.

Ubuntu Weekly News
This is my Saturday/Sunday activity. It's fun seeing all the stories folks find to add to the newsletter and helping summarize them. The news team rocks! If you have links to articles or blog posts you would like to see included please send email to: https://lists.ubuntu.com/mailman/listinfo/Ubuntu-news-team

Oh I am sure there is something else I've been working on but it escapes me at the moment :-) Here's to another awesome week!

I had the opportunity to participate in a focus group on NASA's new "citizen science" project, called Moon Zoo, with a bunch of other fellow lunatics, amateur astronomers and lunar enthusiasts.

Moon Zoo sounds really interesting. Ordinary people will analyze high-resolution photos of the lunar surface: find out how many boulders and craters are there. I hope it will also include more details like crater type and size, rilles and so forth, though that wasn't mentioned. These are all tasks that are easy for a human and hard for a computer: perfect for crowdsourcing. Think Galaxy Zoo for the moon. The resulting data will be used for planning future lunar missions as well as for general lunar science.

It sounds like a great project and I'm excited about it. But I'm not going to write about Moon Zoo today -- it doesn't exist yet (current estimate is mid-March), though there is a preliminary PDF. Instead, I want to talk about some of the great ideas that came out of the focus group.

The primary question: How do we get people -- both amateur astronomers and the general public, people of all ages -- interested in contributing to a citizen science project like Moon Zoo?

Here are some of the key ideas:

Make the data public

This was the most important point, echoed by a lot of participants. Some people felt that many of the existing "citizen science" projects project the attitude "We want something from you, but we're not going to give you anything in return." If you use crowdsourcing to create a dataset, make it available to the crowd.

Opening the data has a lot of advantages:

• People can make "mashups", useful sites that display your data in useful ways or combine it with other data. This can generate more interest in your project and more contributors.
• School groups can work on class projects or science fair projects, probably contributing more data along the way.
• It might help the next generation of scientist get started.
• It shows openness and good faith: witness the recent blow-up over the leaked IPCC emails and the debate over how much climate data has been kept private.

Projects like Wikipedia and Open Street Map, as well as Linux and the rest of the open source movement, show how much an open data model can inspire contributions.

Give credit to individuals and teams

People cited the example of SETI@Home, where teams of contributors can compete to see who's contributed the most. Show rankings for both individuals and groups, so they can track their progress and maybe get a bit competitive with other groups. Highlight groups and individuals who contribute a lot -- maybe even make it a formal competition and offer inexpensive prizes like T-shirts or mugs.

A teenaged panel member had the great suggestion of making buttons that said "I'm a Moon Zookeeper." Little rewards like that don't cost much but can really motivate people.

Offer an offline version

They wanted to hear ideas for publicizing Moon Zoo to groups like our local astronomy clubs.

I mentioned that I've often wanted to spread the word about Galaxy Zoo, but it's entirely a web-based application and when I give talks to clubs or school groups, web access is never an option. (Ironically, the person leading the focus group had planned to demonstrate Galaxy Zoo to us but couldn't get connected to the wi-fi at the Lawrence Hall of Science.)

Projects are so much easier to evangelize if you can download an offline demo.

And not just a demo, either. There should be a way to download a real version, including a small data set. Imagine if you could grab a Moon Zoo pack and do a little classifying whenever you got a few spare minutes -- on the airplane or train, or in a hotel room while traveling.

Important note: this does not mean you should write a separate Windows app for people to download. Keep it HTML, Javascript and cross platform so everyone can run it. Then let people download a local copy of the same web app they run on your site.

Make sure it works on phones and game consoles

Lots of people use smartphones more than they use a desktop computer these days. Make sure the app runs on all the popular smartphones. And lots of kids have access to handheld web-enabled game consoles: you can reach a whole new set of kids by supporting these platforms.

Offer levels of accomplishment, like a game

Lots of people are competitive by nature, and like to feel they're getting better at what they're doing. Play to that: let users advance as they get more experienced, and give them the option of doing harder projects. "I'm up to level 7 in Moon Zoo!"

Use social networking

Facebook. Twitter. Nuff said.

Don't keep results a secret

Quite a few scientific publications have arisen out of Galaxy Zoo -- yet although most of us were familiar with Galaxy Zoo, few of us knew that. Why so secretive? They should be trumpeting achievements like that.

How many times have you volunteered for a survey or study, then wondered for years afterward how the results came out? Researchers never contact the volunteers when the paper is finally published. It's frustrating and demotivating; it makes you not want to volunteer again. Lots of us sign up because we're curious about the science -- but that means we're also curious about the results.

With citizen science projects, this is particularly easy. Set up a mailing list or forum (or both) to discuss results and announce when papers are published. Set up a Twitter account and a Facebook group to announce new papers to anyone who wants to follow. This is the age of Web 2.0, folks -- there's no excuse for not communicating.

I don't know if NASA will listen to our ideas. But I hope they do. Moon Zoo promises to be a terrific project ... and the more of these principles they follow, the more dedicated volunteers they'll get and that will make the project even better.

Yesterday in #ubuntu, someone asked, "I am still confused about this. Everything claims that dist-upgrade actually *upgrades* distributions...can someone please clear this up for me"

So I told them:

<maco> apt-get dist-upgrade differs from apt-get upgrade in that it will remove obsolete packages and add new dependencies, while apt-get upgrade will not. this is necessary when upgrading from one distro release to another, but it is not the *only* time it is necessary. thus, in aptitude, dist-upgrade has been renamed to full-upgrade
<maco> apt-get dist-upgrade will only change you from one release to another if you've modified /etc/apt/sources.list to point to a newer release, but this method of upgrading is not recommended

They also asked "and if i do want to upgrade the distribution (not that i do), how do i go about that?" to which I responded:

<maco> the recommended way to change distro releases is sudo do-release-upgrade

They said it was the best explanation in the shortest amount of text, so I'm posting it here, hoping it'll make it easier for people to find. By the way, man apt-get does explain all this…just in slightly more technical terms.

It seems that even the cat is using Ubuntu… the kids have seemingly seamlessly adapted to Open Source Software. My computer has also taken sides and is so slow it’s definitely trying to tell me something. Finally I’ve admitted defeat and have had to ask Al to make the change, with one caveat – that I can still use iTunes. A robotic sounding “virtual machine” is apparently the answer – it will pretend to run Windows in a little bit of Bill-space and iTunes will be none the wiser that I’ve actually left the Dark Side at last.

I know my new look will take some getting used to and I just have to get familiar but it definitely feels quite different. The icons look more home-made and the whole thing seems less slick. I keep repeating “Kill Bill” and “It’s Free”. I know I will get used to it but at the mo I could almost say I felt sad although probably remembering the “helpful” paperclip will remedy that – Yes, that’s done it – I will give it a chance.

=============================================================

This is an excerpt from my ramblings on going over to Open Source Software. My husband (The Open Sourcerer) has persuaded me to put it on here but I’ve really no idea why. He said “people will be interested, you’ll be surprised.”

….surely they have better things to do??? I’d be interested in the work/chore that is so bad you’d rather read this than do it.

It’s that time of the year again when we need to start thinking about awesome ideas for GSoC. I just prepared a page on the community wiki to collect them. The list needs to be finished by March 8th. Got a great idea for a nice project a student could be working on for the summer? Add it! If you are unsure or have any questions ping me or the team of the app you have an idea for.

Right now there are 22 release parties all around the world on the wiki and of course there will be one in southern Germany as well. Previously we always did them in Stuttgart but it’s time all those Stuttgart people get to see Karlsruhe
So if you are in or around Karlsruhe on the 13th around 20:00 then feel free to join us for our release party at Vogelbräu. Please put your name on the wiki page or let me know by email by Monday latest if you are coming so we know how many people are coming.
If you are not anywhere near Karlsruhe check out the other release parties or organize one on your own

(special thanks to Lemma for taking care of the venue)

There’s only something like 2 and half weeks left for the women of all ages in all parts our community to tell us how they discovered Ubuntu for the International Women’s Day Competition.

That means that you really ought to get a move on!

The process is easy:

1. Women and girls email us (address and rules in announcement) a description of how they discovered Ubuntu. Whether it was at school, work, from a partner or because they were sleep-computing and woke up to the sound of drums — whatever!
2. In just over 2 weeks time, we put up the stories and let the community vote for their favourite
3. On March 8th, the favourite is declared, and we make Jono earn his keep by announcing it and drawing the second surprise winner from a hat on his ustream channel or vidcast or whatever it is kids call that funky video stuff these days.
4. Two lucky ladies get a share of this loot:

Amber describes the prize packs thusly:

***Prize packages are being sponsored by: Canonical, Linux Pro Magazine and Ubuntu-User Magazine. Package includes but not limited to: Ubuntu backpack, Ladies T-shirt, Ubuntu Key Chain, 1 year digital subscription to Linux Pro Magazine or a 1 year print subscription to Ubuntu User Magazine, and a copy of The Art of Community. Thank you all so much for your gracious support and sponsorship.

Help spread the word by telling all the women you know who use Ubuntu and by hitting up digg and /.

I spent a morning wrestling with git after writing a minor GIMP fix that I wanted to check in. Deceptively simple ideas, like "Check the git log to see the expected format of check-in messages", turned out to be easier said than done.

Part of the problem was git's default colors: colors calculated to be invisible to anyone using a terminal with dark text on a light background. And that sent me down the perilous path of git configuration.

git-config does have a manual page. But it lacks detail: you can't get from there to knowing what to change so that the first line of commits in git log doesn't show up yellow.

But that's okay, thought I: all I need to do is list the default settings, then change anything that's a light color like yellow to a darker color. Easy, right?

Well, no. It turns out there's no way to get the default settings -- because they aren't part of git's config; they're hardwired into the C code.

But you can find most of them with a seach for GIT_COLOR in the source. The most useful lines are these the ones in diff.c, builtin-branch.c and wt-status.c.

gitconfig

The next step is to translate those C lines to git preferences, something you can put in a .gitconfig. Here's a list of all the colors mentioned in the man page, and their default values -- I used "normal" for grep and interactive where I wasn't sure of the defaults.

[color "diff"]
	plain = normal
	meta = bold
	frag = cyan
	old = red
	new = green
	commit = yellow
	whitespace = normal red
[color "branch"]
	current = green
	local = normal
	remote = red
	plain = normal
[color "status"]
	header = normal
	added = red
	updated = green
	changed = red
	untracked = red
	nobranch = red
[color "grep"]
	match = normal
[color "interactive"]
	prompt = normal
	header = normal
	help = normal
	error = normal

The syntax and colors are fairly clearly explained in the manual: allowable colors are normal, black, red, green, yellow, blue, magenta, cyan and white. After the foreground color, you can optionally list a background color. You can also list an attribute, chosen from bold, dim, ul, blink and reverse -- only one at a time, no combining of attributes.

So if you really wanted to, you could say something like

[color "status"]
	header = normal blink
	added = magenta yellow
	updated = green reverse
	changed = red bold
	untracked = blue white
	nobranch = red white bold

Minimal changes for light backgrounds

What's the minimum you need to get everything readable? On the light grey background I use, I needed to change the yellow, cyan and green entries:

[color "diff"]
	frag = cyan
	new = green
	commit = yellow
[color "branch"]
	current = green
[color "status"]
	updated = green

Disclaimer: I haven't tested all these settings -- because I haven't yet figured out where all of them apply. That's another area where the manual is a bit short on detail ...

You're scaring me!

In the last couple months, we've learned that the new Sun will be going forward without Frank Wierzbicki, the Jython project lead, and now without Ted Leung.

The Oracle Technology Network is working hard to foster dynamic language use with Oracle. It's got publications, PyCon sponsorship, resources, and so forth. OTN delights me.

I'm afraid, though, that the larger Oracle corporation doesn't share OTN's interest. Oracle's absorption of Sun is proceeding without any apparent interest in dynamic languages. Oracle is discarding some of the finest talent it could possibly acquire, people who could have helped bring on a real flowering of dynamic language use in Oracle environments.

I, for one, would have loved to see Jython harnessed on Oracle's many Java-based tools and even the JVM in the Oracle database - imagine the wonders Frank and Ted could have worked with that, had Oracle assigned them to! Instead... there will be nothing Oracle-related from them. Meanwhile, Microsoft funds development of several dynamic languages, including IronPython, which integrate to SQL Server through .NET.

I don't know. I just dread the thought that, five years from now, SQL Server will be the proprietary database of choice for any environment where dynamic languages are used... which will soon be most environments. Oracle, you really want to give this market away?