LoCo Teams in the Natty Cycle

Still trying to organize my thoughts after the UDS in Orlando. While the election results are distracting, I think it's important to analyze what lies ahead, and get moving before the holidays hit.

Washington Team
1. We need to hold leadership elections, and transfer power over the Launchpad team to the leadership.

2. We need to begin scheduling and hold regular meetings, even if they are only in IRC.

3. We need to get the official logbot in our #ubuntu-us-wa channel on Freenode. Linda is requesting that, so I hope it will happen soon.

4. We need to look at the calendar and plan some Team events, so advance planning can take place.

5. We need to figure out how to get monthly reports done monthly, so that we can get approval!

In the discussion about increasing diversity in the Ubuntu Community, Pici posted a great link, which might be helpful in how we conduct our LoCo team: http://freenode.net/catalysts.shtml


Ubuntu Community Local Teams
There are some exciting plans ahead. Some of them (from Ubuntu LoCo Council Items for the Natty Cycle):

* Community leaders to sign the Leadership Code of Conduct in Launchpad

* Team Re-approvals from the LoCo Directory instead of wiki pages

* Move content from the wiki to the LoCo Directory

* Standard Team Re-approval form

* https://wiki.ubuntu.com/LoCoGettingApproved

* Standards for teams, a set of guidelines: https://wiki.ubuntu.com/LoCoCouncil/Standards

* Update the standard Application to include Team reports and give more details

* Enforce the team naming standards [this can't happen soon enough, IMO]

PS: May 9-13 UDS-O, Budapest! Lay your plans now. :-)

Ubuntu Global Jam - Lessons Learned

At first our Jam experience seemed like a failure. We had two attend, and one of them was me. Thank goodness for Charles (acerimmer); his arrival made the afternoon fun. The first difficulty was Internet connectivity -- my laptop reported that it was getting a good wireless connection, but I was only able to use IRC and get webpages for about 10 minutes in the four hours at the library.

So the ability to connect with others around the state, and around the world was pretty much nil.

Technically, I was unable to load Kubuntu Mav in a virtualbox. I found out from Charles that I had not allocated enough memory, and that K/ubuntu's package might be missing a crucial xorg.conf file. Since the Kubuntu developers didn't mention this last point, more investigation is needed.

Also, I was unable to fully load the Mav LiveCD. I found out that my issues were not uncommon: https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview. This is still alpha software, after all.

My liveUSB key was also a fail, giving the same error message to both me and Charles. I found out that it wasn't my fault, but that of Lucid. After removing that useless LiveUSB install from my cute little 8-gig USB key, I copied the ISO onto it, but Charles was unable to load it into a virtualbox on his laptop either -- incompatible 64-bit systems! I'm not sure what that's about, but hope he'll file a bug about it.

After we talked some about upcoming LoCo events, we decided to leave early. We had both run out of options for testing.

However, the Jam continues through Sunday, and once I got home and got connected again, androidbruce gave me a great idea: swap out my present hard drive for my old backup one, and install on that! Although I was unsuccessful at partitioning off the old backup, which is mostly music, not much harm done to lose it, either. I had hoped to save it, just to be able to play some music during testing. Oh, well! So, as Scarlett O'Hara so wisely observed, Tomorrow is another day!

PS: Also -- more publicity is better! Craigslist? Any other ideas for spreading the word?