<p dir="ltr">Indeed. Having seen the schedule editing features, I'm entirely unsurprised by this.</p>
<p dir="ltr">Would make a nice feature request for next year though.</p>
<p dir="ltr">--Chris</p>
<p dir="ltr">Sent from a mobile device, whilst mobile.</p>
<div class="gmail_quote">On 2 Sep 2012 10:58, "Michael Still" <<a href="mailto:mikal@stillhq.com">mikal@stillhq.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 01/09/12 23:05, Anthony Towns wrote:<br>
> 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>
The problem here is that the UI for editing schedules is truly insane at<br>
the moment, and lacks anything I could describe as a permissions model<br>
(access to edit schedules for a miniconf currently also implies complete<br>
team level access).<br>
<br>
I agree this would be good to fix, but my team is unlikely to have the<br>
time to progress this.<br>
<br>
Mikal<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>