Food Solutions New England (FSNE) is a regional food systems learning-action network dedicated to advancing a sustainable New England food system. The FSNE network is organized around four interrelated activities:
A New England Food Vision, a bold vision that calls for our region to build the capacity to produce up to 70% of food that is produced in an environmentally and socially sustainable manner, that promotes health and is accessible by all New Englanders by 2060; New England state food planning initiatives; annual New England food summits and topical workshops; and related analysis, communication and visualization.
The UNH Sustainability Institute serves as the backbone organization for FSNE. Since its inception in 2006, FSNE has advanced its mission by linking a common agenda, shared measurement, continuous communication, and synergestic activities.
I think that this starts to overlap with the tool sorting/searching function discussion. I think it is important to have really low barriers to posting, and agree that it would be valuable to have a space where people can post and tag tools they find even with very thin documentation - sometimes that is all it takes to spark an idea, and we SHOULD promote that as much as possible. I also think that we need to not lose projects that are active and underway in the the middle.
For example, I think that the Root washer, FIDO, and oat huller are all tools that have users actively involved in farm hack and are projects with activity behind them. I think that these should maybe be in a different category and highlighted. Perhaps we list "tool browsing library" for casual listings and "tool documentation kits", or "tool projects" or something along those lines to indicate that there is member activity moving from concept to some type of action by the community?
There could be no barrier or permissions for posting to the browsing library, but if there are on-going projects then there might be a sponsor for moving the project - which would have the benefits mentioned above. I would suggest not adding any permissions requirements at all at first, but at some point I think the tool wiki should be editable by subscribers to the tool? This should not be not very complicated to manage, but just add one step to commit a little more to the project.