UDS-M Day 5
What an amazing week it’s been, it’s true the week flies by when you’re having fun, but you’re also working and yet it doesn’t feel like work.
Last day of the roundtable, besides reviewing the week and the topics we’d covered at UDS, we also mentioned how the LoCo Council will be pushing the use of the LoCo directory and not the wiki any more for events.
Following on was the Ubuntu Women session. We had a jam packed cycle for Lucid. Many action items were crossed off our list and we really started to function well as a team. I’m not saying it’s perfect, but it has come a long way.
There is once again a roadmap for the cycle. We will be looking at 3 key areas such as the Mentoring Program: Reviewing and Rewriting our documentation to reflect the program. Update and reference existing programs within the community that we can point women to who want to get involved.
Ubuntu Women Logo Redesign: A new logo which is consistent with the Ubuntu branding guidelines
Redesign Ubuntu-Women.org website: We will also be moving much of the static content to the wiki.
We also have the Leadership Election coming up and an reviewing and evaluating the success of our new IRC channel infrastructure.
One stream I kept trying to pop in and out of was the Design track. It was really interesting and had some great discussions in it. Their team seems to have grown and adapted to the Ubuntu Community really well. I found myself in the Ubuntu Usability session as I was curious about it having read about what they were doing.
What we do now
* different ways to involve users input *usability testing: showing people an interface asking them to try it out, see what they can do and see where they fail
* We have been thinking about the way we use the methodologies and we have been using them in a very traditional way.
They are designed to help designers make decisions. We have started to challenge our methodologies and look at how we can feed findings into the open-source community. We did some work with Empathy and showed them a traditional report to look at how we can make it more dynamic. How to communicate in a way that helps make it more useful
* conceptions of Ubuntu community
* Usability liability—unfamiliar terminology
* Important to manage first-impression
“How can I make this mine? I want to use this tool, this tool has to be mine”
* Desktop background
We sit beside them, we have a script, we guide them and we ask them clarifying questions. This is more exploratory than testing: we avoid leading them. We want to understand.
* We are testing _the software_, not testing _the participant_.
* New question: can we put clips of you online
** Opposite to traditional “don’t worry, this won’t be seen” approach
** During session, only document facts, don’t draw conclusions
*** Not always suitable to share transcript, eg. includes introductory rapour
** Avoid leading questions, but can be useful to extend conversation
Community Team Process We’re a bit all over the place and need to clean up our wiki! So this cycle is going to be a massive spring cleaning session with some pruning and merging pages together. We’re going to start on the Building a Community page and work around those pages for the teams
[czajkowski] Review and improve the ‘Team Resources’ BuildingCommunity section: TODO
[czajkowski] Update and refresh https://wiki.ubuntu.com/BuildingCommunity/RunningCommunityStands: TODO
[czajkowski] Update and refresh https://wiki.ubuntu.com/BuildingCommunity/Contacts: TODO
LoCo Council had two sessions this week. One reviewing our achievements of the Lucid cycle. We started the re approval process and did 22/30 teams, why didn’t we do all 30. Simple. Some teams did not reply to mails either on time or were not able to commit to a date/time. Also it did take us some time in getting started, creating the wiki page, having the content up and then translated, selecting the teams and getting started. For the next cycle we are going to do the following:
[popey] investigate beneficial benefits for approved teams:TODO
[czajkowski] follow up with jane and canonical re loco banner for approved teams :TODO
[itnet7] create mail to locos and send to council to work on before it’s sent out:TODO
[popey] Ensure locoteams page on wiki is in sync with loco teams listed on launchpad:TODO
[jono] Set goal for number of re-approvals this cycle:DONE
[huats] Select more teams for re-approval:TODO
[huats] Update wiki page with new teams for re-approval:TODO
[czajkowski] Mail Teams which are up for re-approval:TODO
[huats] Archive re-approvals to /archives : DONE
[popey] Update locoteams-approved team to have correct dates for approval to calculate correct re-approval:TODO
[itnet7]policy and guidelines for the ubuntu loco council :TODO
[czajkowski] Write up a guide for Best Practices for a LoCo:TODO
[popey] sign up to first 8 teams for reappvovals mailing list and then send the mail :TODO
[popey] mail loco counil on how we deal with irc conversations with teams :TODO
Finally the closing of UDS with the summing up from the platform teams and then onto UDS All Stars! It was a great week and I’ll be sorry to say goodbye to folks! but I’m really looking forward to working on projects during the next few months! I’ve all my photos in the usual place