Well, I feel pretty tired today. I am not yet convinced that this is the "UbuFlu" That I have heard about. I suspect it is more like a product of the pace and intensity of the sessions I have been a part of. I'll know more tomorrow. :-)
The Kernel Roundtable was first on the agenda as per normal. We discussed the things we all attended the day before and discussed work items that came about as a result.
The first session I attended today was about making Harvest more useable. This is a really useful tool that I am hoping to add to the items I use on a daily basis. I provided feedback where I could but this was only the second time I had seen it (a situation that was entirely my fault as it was on my TODO list).
Next was a private Kernel meeting to discuss a few topics followed by a very well attended session on multitouch support and its place in the next release. This was a packed house and I got a great deal out of the current support level versus what is expected to be ready for inclusion in Maverick. I hope they moved the follow on session to a bigger room. I was unable to attend the follow on.
Lunch was as normal, great selection with fantastic desserts. :-)
Plenaries covered the forward work planned for ARM followed by a quick look at Lucid workflow success and the Maverick Development plan as it stands now (more on this later). and lastly was a brief chat about translations (what a great group of people!) and an overview of the new font layout from the foundry. Very Exciting.
After Plenaries I was part of a session on Kernel Wiki 'gardening' which I hope will aid our community in finding information more easily as we move forward. Some relevant topics were, how to break out information on a per-release basis so that even as releases occur and information gets updated, our community will have access to relevant legacy information. This will also help us narrow the triage scope for specific subsystems community members are interested in and help us provide a better bug interaction. All big wins for the community as well as the bug reporters. I was also able to chat briefly about an idea that Steve Conklin had concerning the subsystems and triagers that focused specifically on subsystem bugs. The hope is to provide them with specific training from the triaging experts in these systems to allow us to not only grow their understanding of the specific sections of kernel work, but to also allow them to gain a foothold in kernel debug. The consensus was that this was a great idea and that the first iteration should be conducted electronically so that we can see the initial benefits without interrupting schedules of community members. This would also help us to live triage of specific bugs with an expert looking on and coaching. A side-effect that I hope we see is an expansion of the subsystem focused wiki pages that will come about as a result of the learning that occurs. I hope to use this as a model going forward for community based training that will eventually elevate current triagers into subsystem hackers and eventually kernel devs if they are interested. I guess you can sense my excitement. :-) More on this to come.
Next was a block of 2 hours devoted to kernel config which I opted to miss so that I could get a break and hopefully recover some energy for the final sessions of the day. The first was on Patch Review. Here again the Kernel Team is a bit different, but i took the time to try and understand how the other packages use it. The session was very informative. I now know exactly how the kernel patches deviate from this model and I understand more of the why. The last session I attended was apport and its possible use to gather information on installation failures. I always enjoy hearing the thought process that Colin Watson uses when determining what he needs to do to address an issue and this was a perfect opportunity to listen in. I was also mainly interested in what this might mean for kernel installation failures that might occur. i suspect I will be getting pinged by Colin should he encounter any of those in the testing. I look forward to it.
I've foregone dinner in the hope that rest will replenish me a bit more for tomorrow. We are 3 days down and 2 to go. :-)
Take aways from today's sessions:
*Read up on Harvest and pull the branch so that I can provide more feedback from a user perspective.
* Work with Andy to define the first needs of the wiki reorg
* Work the list of 10 for the initial foray into wiki updates
* Get arsenal scripts that pull bugs that have upstream SHA1 commits in them and generate a readable/clickable report for use in verifying that they either need to be or are in the latest kernel.
* develop a plan for the first 'triager summit' and announce intent to team list.
* Put the new Bug call plan in place and plan to start it one week from Monday the 17th of May.
* Work out a better bug report and have it update automatically through the day.
* Identify easily distinguishable bug tags to effectively break out the bugs as to what subsystem is affected (i.e. kernel-sound, kernel-suspend, etc.)
* Work up automated scripts to identify and tag as such above.
* roll triage wiki with links to the bug lists as broken out by the tags above.
* Determine best practice to expire bugs appropriately and work with Brad Figg to implement appropriately. (I have halted running the expire script until we have this down and i have reviewed all currently expired bugs)
* Work with Brad to identify the process arsenal scripts should use and document it.
* Rewrite arsenal scripts as needed due to the above.
* Identify Python training to attend over the cycle.
More tomorrow. :-)
Moving on From GitHub
3 days ago