Thanks to the Ubuntu Classroom team session at UDS we’ve got all the IRC Workshops planned already, along with spiffy ads to spread around.
After much discussion we have decided to “focus” the IRC workshops. Instead of one long week we’re smushing them up to just three days for each “week” but make the days longer to hit more time zones. So they will be from Tuesday to Thursday. Don’t worry, it’s the same amount of content, just concentrated.
And for OpenWeek we’re likely going to move to 30 minute sessions by default (though we can adjust this), which will mean instructors will have to be more prepared ahead of time. So, less typing wasting time, more time pasting in prepared material and answering user questions. No change for the Global Jam, keep rocking that!
juju Charm School is a virtual event where a juju expert is available to answer questions about writing your own juju charms. The intended audience are people who deploy software and want to contribute charms to the wider devops community to make deploying in the public and private cloud easy.
Attendees are more than welcome to:
Ask questions about juju and charms
Ask for help modifying existing scripts and make charms out of them
Ask for peer review on existing charms you might be working on.
Every Ubuntu Open Week we have a session called “Ask Mark”, where Mark Shuttleworth answers questions from the community in IRC.
Due to scheduling conflicts this didn’t happen last Open Week, so we’re holding a special standalone event on IRC where people can ask Mark questions.
Ask Mark will take place in #ubuntu-classroom at 1500UTC on Freenode. You’ll need to join that channel, and #ubuntu-classroom-chat, where you will ask questions, which will then get passed onto a bot and onto Mark.
Some tips for asking questions:
Mark operates at a macro level of the project, so questions like “How do I get Flash to work?” or “Why did you pick this specific version of the kernel to ship in 11.10” he’s likely to not know the answer to that. So unless you want a “Go ask the person who runs that team” answer try to ask questions about Ubuntu at a higher level than asking about plumbing.
Make your question count - put some thought into it, plenty of people will be asking good questions, so don’t waste an opportunity by asking something like “Where can I download 11.10?”
Here are the archives of the past sessions if you want to see what has been asked before if you want an answer.
It can get chaotic with the amount of people asking questions, so please be patient.
Here’s the classroom wiki page with information on how to participate if you need more detail. Hope to see you there!
and so on. Our teams provide IRC transcripts of all their meetings. Here’s the entire history of the Desktop Team’s meetings, and here’s the set from the Kernel team. And here’s a set from the Release Team. All our meetings are open to the public, and people are encouraged to participate.
Up until this cycle, Mark Shuttleworth has done an open Question and Answer session on IRC every 6 months for the past 5 years. And it’s not just Mark, we’ve subjected Rick Spencer (current head of engineering management at Canonical) and Matt Zimmerman (CTO for Canonical for years), as well as Kate Stewart (release manager) to open user questions on IRC.
(Mark was on holiday during openweek this cycle, but we’ll make it up to you).
We do try our best to respond to user ideas on Brainstorm, but for obvious reasons we cant’t scale so well at that, so we do our best to hit the top ideas every 6 months.
Despite these efforts, it can be frustrating to hear that Ubuntu is making decisions without input from “the outside”. How do you think we can improve our transparency?
IMO I think we do a decent job of being transparent, and people who follow Ubuntu know what to follow, but this might not be so obvious to people who are new. So maybe we’re awesome at being transparent, but not so much at communicating, which is fine, we can fix that.
For my part, this cycle I’m going to put my personal TODO list out there in the public. I used to use my own internal GTD-like thing but I’ved moved to Trello so here’s my every day TODO list:
Immediately you’ll notice that my TODO list totally doesn’t match my assigned blueprints. That’s because after UDS I went on a trip immediately and then we had a holiday on Friday, so at this time my TODO list and my assigned blueprints don’t match. And you’ll also notice that my user page on status.ubuntu.com isn’t updated yet. It will be up to me to update all of these to make sense. So yeah, you can see how behind I am, I haven’t even consolidated my tasks from UDS with my TODO list yet. On some of these TODOs you’ll see that I share them with other people.
And you can follow along with me as I work on this cycle. Follow my trello boards, find me on IRC, follow me on G+, follow my status reports, whatever works for you. I am going to make a concerted effort to make what I do as public as possible. I’ve outlined some ways that other teams outline their progress. Like I said, I think we do a decent job of being open, but maybe we need to do a better job at making that obvious to people, how can we improve this?