After a non evenful journey over to Orlando from Ireland and meeting up with some folks Sunday night in the bar which was great as I got to put the faces to the IRC nicks. Sleep was had!… Monday kicked off with chatting with folks over breakfast then we headed down to the Keynote. Which was kicked off by Jono covering some of the stuff that will be happening this week. Did you know…….This is the 14th release…
The idea of Ubuntu Developer Summit if you’re not sure what it’s all about just yet is “Getting face time together is really important” it helps us to get to know one another, puts the faces to the names/nicks which will help folks become more productive for the coming cycle.
There track have been re organised to get more cross-pollination:
* Application Developers
* Package Selection and System Defaults
* Performance
* Multimedia
* ununtu the project
* hardware compatibility
* cloud infrastructure
If you are trying to following the sessions and want to keep track of the documents, have a look at the new documentation path for sessions: session proceedings. Goto https://wiki.ubuntu.com/UDSProceedings/N
We’re all on Gobby JOIN US!!!!! Use gobby-0.5 to match the server version at http://gobby.ubuntu.com or get it from the Ubuntu Software Center.
Mark Shuttleworth then kicked off the next half of the keynote this morning talking about how well Maverick went and the plans for the future. There was a lot of new code in Maverick, on a shorter-than-usual schedule.
This was also the first release with a full Linaro cycle, it’s an attempt to create a forum for important upstream development work (in arm) and it’s a genuine move to create a common base. they are here UDS-N this time so if you want to talk to them or join their sessions do!
Key focuses for Natty:
* File Management. “Files and folders is completely broken.” We’re going to bring nautilus back onto the desktop. Also putting file manager on the launcher.
* From the developer point of view, lowering the barrier to participation. We should make it trivial for anyone to fix anything anywhere in the platform. Make merge proposal easy. Software center took a huge leap forward as well…
* Drivers and performance are the #1 issue. GL drivers, 3D on netbook for windows management, etc.
After the Keynote the sessions kicked off, now with the renaming that has been done I personally find them odd in trying to figure out which areas to go in, I know the reason is for more cross pollination but some of the sessions are very broad. Kicking off the day was a roundtable for Ubuntu the project. Nice way to plan the week and cover some topics that may not need a session and just bounce some ideas off one another. An advantage of these sessions if you find a topic that comes up and it needs more discussion we can create on on Summit. Some of the topics that came up that we’re going to be looking further this week were:
Governance Cruft (jcastro)
- not acting within the spirit of the community
- blockers for getting things done ????? Infrastructe / IS talking to canonical
- Canonical and Ubuntu community (mdz)
- Getting people vived up and on board
- Improving diversity at UDS
- Helping teams work together
- Finding the right person to help you - be great to have someone to know to go to talk to
What I came up with was an idea to work on Wiki clean up information moved to askubuntu.com and we’re going to have a session on this on Wednesday morning!
Events:
- Ubuntu Developer Week – Twice a year
- Packaging Training (initially once a week)
- MOTU Q&A
Feedback:
- Logs useful
- problematic when it gets closer to release, people busy at sprints, etc.
- homework? (model answer, simple merges, simple bugs)
- add “preparation notes”, things to use beforehand
Reach out:
- loco-contacts list, beginners list, womens list, ubuntu-user list, planet
- make more use of forums
- facebook group
Getting more people to run sessions:
- build confidence, encourage people
- when people explain something, get them to run a session
More sessions:
- Adhoc Sessions (come with your problem and a developer will help you sort it out)
- Get questions from the Packaging forums
- Rotate responsibility among teams
- Investigate “Beginner’s Programming Challenge”
I popped my head into the
Developer Advocacy session. Firstly to figure out what this session was about, we need to work out …
Who is our audience? Developers new to Ubuntu? People new to development in general
Common use cases:
* “I know some stuff, I want to help Ubuntu — how do I start?”
* “I am a l33t programmer, how can I get my software packaged?”
* Ubuntu Development Beginnings wiki https://wiki.ubuntu.com/BeginnersTeam/FocusGroups/Development/Devbeginnings
On this wiki, cover/link to things like:
- How to join Launchpad
- How to create SSH & GPG keys
* Quickly has work-in-progress to automate this
- How to get source
- How to submit a patch
* how to push back to launchpad
* How to use Launchpad to propose merging
- Putting these steps together to fix a bug (ie. link to https://wiki.ubuntu.com/Bugs/HowToFix), build, test, submit bug fix
- How to use Quickly
- How to install Eclipse (and other IDEs)
Introduction material:
- basically just “how to fix a bug”
- packages
- source & binary
- archive?
- command line
- editing text files
How to reach out:
- put introductory text on ubuntu.com/developer
- help people get the source and instructions (menu item?, applet?, link in launchpad bug?)
- presentation material for loco sessions
- identify overlap between ubuntu developers and loco people
So what I took away from this session is that I now have an action item – czajkowski to set up a frontdesk for loco + developer interaction
All in All it was a fantastic day and was topped off by a Pizza night event put on by the host LoCo Florida! It’s been great to meet and chat to folks and plan a week of working on loco council stuff while I’m here and can work hands on with people with issues.
If you have any LoCo Community thoughts or ideas give me a shout!
Powered by FireStats