HackSoyuz
Dev Week -- Hacking Soyuz to get your builds done -- noodles775, cprov and wgrant -- Fri Sep 4th, 2009
Contents
UTC
Outline
Here's an outline of what we can expect during the Hacking Soyuz session - but like most UDW sessions it will be flexible and might stray with the right questions 
Grill a new soyuz hacker
OK, so William isn't exactly new to Soyuz - but he has been Soyuz's biggest community contributor since the open-sourcing. Being a relatively new soyuz hacker myself (noodles), I was keen to hear William's thoughts and responses to the following questions: (if you've got questions for William too, ask them in #ubuntu-classroom-chat too!)
Question 1
How did you originally get involved with Soyuz - and why do you stay involved?
Question 2
If you wanted to describe Soyuz to an Ubuntu/Debian user, what analogy would you use and why? (It could even be worth seeing if any participants have analogies too - exploring where each is good and where each fails? Just a thought).
Question 3
If a person came to you who was competent in Python, had some packaging experience with their Launchpad PPA and was really keen to hack on Soyuz, how would you recommend they get started?
Perhaps leading into a topic/segment that wgrant would like to lead?
A tour of the Soyuz code-base
Celso's guided tour of code, documentation, API's and concepts.
Setting up a Soyuz test scenario
For this section, you'll need a working Launchpad development environment. We'll be using:
- make run - to view our soyuz publications
- make harness - to publish new packages and simulate builds completing so that we can view them in our browser.
See Testing launchpad soyuz features for the screencast and code snippets.
How can I get involved / General questions
What are the plans for PPA/Desktop integration, different strategies people have adopted, pros/cons.
What are the plans for the soyuz-upload handling.