[sudo-discuss] event proposal

Matthew Senate mattsenate at gmail.com
Sun Aug 31 22:33:35 PDT 2014


Yes, +1 and I'm happy to help. I've given you an account on the sudo room
calendar, so you can post a date when things come together.

Whenever details are settled, we should ensure the time(s) are available
with The Omni and bring it to a Thursday Omni Collective meeting for
nominal checking and approval.

// Matt


On Sun, Aug 31, 2014 at 11:42 AM, niki <niki.shelley at gmail.com> wrote:

> This sounds awesome!
>
> :)
>
>
> On Fri, Aug 29, 2014 at 4:51 PM, refugia <refugia at zoho.com> wrote:
>
>> I'm looking to organize a farm hack event in February. Would sudo want to
>> host it? It would be full day event, probably on a Saturday with 30-60
>> people. Farmhacks are are always free to attend but I would like to support
>> the space financially.
>>
>> I'm thinking that it would be part hackathon and part hands on skill
>> share with various presentations and discussions throughout the day.
>>
>> http://farmhack.net/tools
>>
>> Saludos,
>> Patrick
>> What are the core elements of the FarmHack culture?
>>
>>    - Biology before steel and diesel, software before hardware – is
>>    there a way to approach this problem by using biological systems that add
>>    to soil health – such as cultural practices like cover cropping, mulching,
>>    crop or animal rotations etc, is there an approach that eliminates hardware
>>    through greater systems understanding?
>>    - Holistic approach – does this tool make me enjoy working with it as
>>    much as getting the job done faster?
>>    - Designed to empower owner of tool to use, modify and improve –
>>    different from industrial tools which user does not own in the sense that
>>    there are aspects of the tool that are inaccessible to the user. If you can
>>    not modify a tool you do not really own it, but are just borrowing it from
>>    the system that created it.
>>    - Designed for transparent function – functional components are
>>    clearly laid out and purpose is clear.
>>    - Modularity – functions can be removed and replaced without
>>    reengineering entire tool. Tool function can be changed by adding or
>>    subtracting parts.
>>    - Adaptability- tools can be used for many functions and can be
>>    changed to new functions easily.
>>    - Design for Disassembly – modularity/if welded easy access to joint
>>    for cut/ no hidden bolts/ exposed bearings/belts/ Belt and chain tensioners
>>    have enough play to enable easy removal
>>    - Universal couplers/fastener spacing – use of standard quick
>>    connects for electronics/hydraulics/air lines/power take offs
>>    - Design with replicability in mind -- Could this part be recreated
>>    in a farm shop in a small town – Use of common dimension materials. for
>>    example design for welded and machined parts rather than castings
>>    - Use of “off the shelf” or commonly available components, or
>>    components that are or can be re-purposed – can a more easily sourced part
>>    do the job as well?
>>
>>
>>
>>
>> _______________________________________________
>> sudo-discuss mailing list
>> sudo-discuss at lists.sudoroom.org
>> https://lists.sudoroom.org/listinfo/sudo-discuss
>>
>>
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss at lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/sudo-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/sudo-discuss/attachments/20140831/adbd888c/attachment.html>


More information about the sudo-discuss mailing list