UnConferences are only loosely structured, and so we don't mean to schedule out every minute in detail, but we do mean to broadly define what's going on at what time blocks. That is, the contents of the freeform collaboration blocks are freeform, but those freeform blocks are themselves scheduled, and some blocks are more formally scheduled.
Having more structure early in the agenda to get things off to a good start, and periodic structure to bring things back together, seems a good idea.
Activities to be scheduled
These are mostly seeder ideas at this point – we need more activity ideas, and we also need to resist the inclination to schedule all of the available time.
Activity |
Duration |
Type |
Description |
|---|---|---|---|
uPortal framework code clinic |
1h |
Kiosk-ish. Can run in a corner concurrent with other activities. |
~awp9, Eric Dalquist, Peter K. sorts of developers have a desk in a corner and everyone is welcome to bring over their uPortal-touching code (channels, mods, plugins, anything) and look at it with an "expert" who will comment as to what it is doing well and how it might work better, and guide as to where to go next with the code (how to effectively open source it if appropriate) |
Fluid-sponsored user experience design code clinic |
1h |
Kiosk-ish. Can run in a corner concurrent with other activities. |
Fluid designers and developers available at a desk in a corner and everyone is welcome to bring over their user interfaces and look at them with an "expert" who will comment as to what is done well, what can be improved, and guide as to how this relates to Fluid work if appropriate. |
Spring / Portlet clinic |
1h |
Kiosk-ish. Can run in a corner concurrent with other activities. |
John Lewis, Cris Holdorph, Eric Dalquist sorts of developers have a desk in a corner and everyone is welcome to bring over their Spring-using and/or JSR-168-implementing code and look at it with an "expert" who will comment as to what it is doing well and how it might work better |
Open-sourcing clinic |
1h |
Kiosk-ish. Can run in a corner concurrent with other activities. |
~awp9, Eric Dalquist, Jason Shao, Matt Young sorts of people at a desk in a corner and everyone is welcome to bring over their code and look at it with people who have open sourced software before, and talk through options for taking the code forward as open source software, building a project, getting activity on it, how it fits into the JA-SIG ecosystem. |
Schedule
Day 1 (Tentatively, Monday November 12)
Time |
Activity |
|---|---|
|
|
Day 2 (Tentatively, Tuesday November 13)
Time |
Activity |
|---|---|
|
|
Day 3 (Tentatively, Wednesday November 14)
A room to work, wireless and wired Internet, power, and coffee available for anyone who wishes to remain at the UnConference site for post-conference collaboration.
Possibly, Unicon may offer more formal training on this day as a co-advertised activity. The idea is that by co-locating and adjacently-scheduling these activities, the value proposition of making the trip can increase and draw more participants. Still working this idea out.
Day 4 (Tentatively, Thursday November 15)
A room to work, wireless and wired Internet, power, and coffee available for anyone who wishes to remain at the UnConference site for post-conference collaboration.
Possibly, Unicon may offer more formal training on this day as a co-advertised activity. The idea is that by co-locating and adjacently-scheduling these activities, the value proposition of making the trip can increase and draw more participants. Still working this idea out.
Day 5 (Tentatively, Friday November 16)
A room to work, wireless and wired Internet, power, and coffee available for anyone who wishes to remain at the UnConference site for post-conference collaboration.
Possibly, Unicon may offer more formal training on this day as a co-advertised activity. The idea is that by co-locating and adjacently-scheduling these activities, the value proposition of making the trip can increase and draw more participants. Still working this idea out.