New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PLOTS Portrait #151
Comments
OK, here's a draft, where i put in some examples, which maybe wouldn't be in the final?: (link to Google doc: https://docs.google.com/drawings/d/1B0jkvNFpMGbmDHRl3NJQfBAgehbfnjBKwzRtOQ-HPPI/edit) |
I think this looks amazing, my only question would be should there be a visual link between partner organizations? flow diagram arrows? Can they be on working groups? second question could you make a similar diagram for the tool development tree? I'd love to be thinking with that too. This methods might be great to kickstart the working groups as it is easy to share concepts with images.....data rich ones :) |
OK, added arrows. Also two things which would be nice to explore, but which we might want to debate on the Team list:
|
oh, also - i added a second set of arrows indicating that one major role of staff and organizers is to help facilitate relationships with partner orgs. I'm thinking of some activist groups and nonprofits which follow a slightly more traditional structure and don't know how to engage with a communal and nebulous open source group. |
based on recent experience, i think that even between communities of collaboration there might be some degree of coordination needed that will require staff. i agree with removing the names of orgs (although it is helpful), and adding ALL the working groups as a nice transparency thing |
i had trouble listing them all in my head but we should have some text also too many arrows is not good - showing that although both partner orgs where would this live? /about ? publiclaboratory.org/wiki/how-it-works ? On Mon, Apr 23, 2012 at 6:57 PM, Liz Barry <
|
Looks great. I like it at /about or close by. Would it be weird to have a On Monday, April 23, 2012, Jeffrey Warren wrote:
|
hmm, maybe it's getting out of scope -- but mainly i worry that if we say maybe that's a different page? On Mon, Apr 23, 2012 at 7:55 PM, stewart long <
|
A separate outcomes page or diagram sounds good. Another idea to toss out On Mon, Apr 23, 2012 at 5:28 PM, Jeffrey Warren <
|
Looks fantastic. I like not putting specific orgs on the first chart, but having a subsequent chart with more details. Maybe click on a bubble? On Apr 23, 2012, at 6:47 PM, stewart longreply@reply.github.com wrote:
|
OK, I think the latest version looks pretty good. Now where do we put it?
or it's own page? |
I have been thinking that we could use these diagrams as ways of actually accessing information on the site. So for instance the tools page could actually be the tool development flow chart, each tool in process could be on the chart relevant to where it is on the process? I think this would help create more conversation between the tools that are in the same development stage. Perhaps this concept is harder to apply to the overall structure diagram but it might be a good way to organize the "about" information? clicking in staff tells you about all the staff, clicking working groups tell you about all the working groups? One immediate draw back of this approach is it moves away from the easily editable form of the wiki-pages to add this kind of graphical interface. |
I think it could go on all three pages and should go on the about and On Thu, May 17, 2012 at 4:06 PM, Jeffrey Warren <
Adam Griffith |
OK, it's on /about and /wiki/getting-started how does that look? |
looks good! On Fri, May 18, 2012 at 12:06 PM, Jeffrey Warren <
|
looks great! On Tue, May 22, 2012 at 11:00 AM, Liz Barry <
Adam Griffith |
closing |
a visual diagram of the PLOTS community - Jeff will draft and circulate for input
The text was updated successfully, but these errors were encountered: