<p dir="ltr">Sorry this should have gone to the list too. Email fail on my part.</p>
<p dir="ltr">Tim</p>
<p dir="ltr">> On 20 March 2013 06:04, Joshua Hesketh <<a href="mailto:josh@nitrotech.org">josh@nitrotech.org</a>> wrote:<br>
>><br>
>> Howdy,<br>
>><br>
>> All this idea and all of the discussion around it is really excellent. Thanks for taking the initiative on this Tim.<br>
>><br>
>> The council will be sure to discuss it next week at out meeting.<br>
>><br>
>> In the mean time, some quick thoughts that I've had.<br>
>> - I agree that smaller teams allow for effective decision making but how will a smaller team take onboard the input from the wider community (we've already seen hands go up from lugs and previous organisers).<br>
><br>
><br>
> My original idea was as follows; I'm not 100% set on these ideas and open to changes.<br>
> * start with a small committee and have them agree to new members,<br>
> * keep the active group to less than 10 people,<br>
> * have a emeritus list for people who no longer able to commit time and honor their previous contributions,<br>
><br>
> All decision making and discussion will occur in public, so the community will be able to see and audit our activities. <br>
><br>
> Most of the people on this thread should definitely be added to my committee shortlist (assuming they are willing).<br>
> <br>
>><br>
>> - This leads to do you propose a leader for the subcommittee? Somebody responsible for making things happen.<br>
><br>
><br>
> I hadn't thought about this, maybe we should take a nominations once the subcommittee if formed?<br>
> <br>
>><br>
>> - What resources do you need for this initially. Primarily I'm imagining a mailing list and some compute power until you put in a grant request for hardware?<br>
><br>
><br>
> Primary a mailing list. Access to what conference budgets for recording and A/V.<br>
> <br>
>><br>
>> - What are the initial tangible outcomes. Is it primarily focusing around documentation that can then be used to support other conferences?<br>
><br>
><br>
> The first outcome I think will be a number of guiding statements include;<br>
> * why video recording and streaming is important asset to the Linux Australia community<br>
> * principles to follow when recommending and developing solutions (IE when to be pragmatic versus when to use FOSS)<br>
><br>
> Further documentation will also be provided, including setup recommendations for;<br>
> * small conferences (less than 3 tracks)<br>
> * large conferences (greater than 3 tracks)<br>
> * large LUGs (with committed A/V members)<br>
> * small LUGs (with no specialised A/V members)<br>
><br>
> We would also create grant proposals for seed funding for development and testing of software and hardware that fills current gaps or allows better experience in the future. I see most of these projects as being speculative.<br>
><br>
> Tim</p>