<p dir="ltr">+9000 to AJ's suggestion. Publishing a miniconf schedule has traditionally been quite the pain.</p>
<p dir="ltr">--Chris</p>
<p dir="ltr">Sent from a mobile device, whilst mobile.</p>
<div class="gmail_quote">On 1 Sep 2012 23:37, "Anthony Towns" <<a href="mailto:aj@erisian.com.au">aj@erisian.com.au</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 1 September 2012 15:25, Michael Still <<a href="mailto:mikal@stillhq.com">mikal@stillhq.com</a>> wrote:<br>
> So, what else could we automate? The layout of time_slots / events /<br>
> schedules in zookeepr is another obvious example.<br>
<br>
This seems like it could help with miniconfs (just giving miniconf<br>
organisers permission to schedule their room for the time they have<br>
it, so that the main team don't have to take any action when miniconf<br>
schedules change/update), and with BOFs and other during-the-week<br>
planned events.<br>
<br>
Cheers,<br>
aj<br>
<br>
--<br>
Anthony Towns <<a href="mailto:aj@erisian.com.au">aj@erisian.com.au</a>><br>
<br>
_______________________________________________<br>
linux-aus mailing list<br>
<a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br>
<a href="http://lists.linux.org.au/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/listinfo/linux-aus</a><br>
</blockquote></div>