User interface with website- involvement in projects

[sdosemagen]

Point person: Shannon Team: Liz, Sara, Mat (passive) Importance: High

This project will address involvement questions such as how to host a meet-up, how do I get involved in a regional Public Lab project or on a Public Lab tool. We’ll also be developing a system to address topics that people are requesting assistance with.

As a user how do I get involved in project/what can I give to that project/what do I need help with

• Mirror in the place page- whether there is a development/place page (different question)
• At top of tool page- localities to get involved in/features to get involved in
• Need templates for prospective features timelines- so people have a format- new tool- what features can be developed with it
• Better bug tracking/features for tools

roposal- Github issue/sketches/wireframes/minimal requirements from programmers

[rjcorwin]

Better bug tracking/features for tools On FarmHack.net we have "Research Notes" (just referred to as Forum topics) split up into 4 categories: Problem, Idea, New Information, and Question. So on the topic of problems, when a problem is solved, we have to do silly things like put [solved] in the header. But... This is the sacrifice we are putting up with for the sake of the simplicity of having a Tool made of a Wiki and Forum Topics. It's working OK for now but I would imagine it might become cumbersome when a Tool matures... Anyways, as for the public labs site, the ideas off the top of my head include:

• expand the Research Note concept by adding a field to distinguish between a traditional research note and a bug

or

• add issue queues to each tool

Just a guess, but I think the latter might work better for the Public Labs community. It seems to fit better with the idea of publishing research and then working in an issue queue to solve problems collectively.