Present: @eirinimal @alberto, @alessandro_contini @rossana_torri @moushira @noemi @patrick_andrews @costantino, Silvia
Agenda for the call:
1. Alberto’s Big Picture for Open Care Year 1: we need to collectively contribute to a post publicly outlining our work this year. If no one wants to do it, Alberto volunteers to write it
Related topic here: Documentation.
Even from last weeks call we discussed some of the constraints in bringing stories from the very ground (In Milano) online and the barriers to participation.
Alberto: It is worrying that documentation is perceived as hard to get, as we wrote it in the proposal and now have to execute.
Rossana: We are waiting to hear from people we are engaging and who would be more comfortable to tell us things that may be private. On the 4th of May we are starting activities of co-design with Milano communities and it would be a better time to collect stories. Also, video operator needs time to process the material etc.
Costa: we are not active on the website, but we will as soon as we have confirmation from the community and partners we engage.
The offline activities are not aligned at the moment with online activities.
Our 1 hour events are not enough to onboard them - Milano events are not conversations yet, they go one way. These activities are more of a warmup, our hope is to get their attention in the co-design sessions.
Eirini: I know of this EU funded project (crappy UX> sorry). http://www.innovvoice.com/ it’s platform where you can post your challenge/problem and then receive comments and collaborate further on the develpment of some projects (the hacking @alessandro). quite familiar idea (crowdsourcing innovation). but this is what you are actually proposing as far as I understand maybe take some ideas from those guys in order to facilitate this sharing and co-creating
2. Costa & Co. proposal for a new Open Care landing page (complementary to the one we have now)
A very hard project because it is a meta-project: we strive not to build something, but first understand what is the right approach to solving a problem.
We propose a new landing page above the content and landing pages already there. A one page website - very simple and clear and explain OpenCare in one minute to anyone. Link to proper resources so people can get more involved. Hosted outside of edgeryders.eu .
Example: https://openideo.com/
Alessandro: user story example “If I’m a developer and want to dig right into the code - I should be able to access the github rep immediately”
Needs to answer key questions: What is OpenCare? How can I find more info? Who is doing it?
Tools have to be as simple as possible.
WeMake are preparing a clear HowTo guide mapping the environment of relevant projects in the Care field (DYI, Maker world). Should speak to people who are not accustomed to online tools, but also the more skilled in using Internet tools.
the reason of a landing page
- this is a redirect, that helps people find relevant information, and we aren't creating a new destination.
- the "elevator pitch" is hard to get
- it is hard to find answers to these questions:
- what is opencare?
- how do I get involved?
- who is doing it?
landing page design criteria
- it shows in a brief intuitive way what the project is and it redirects to online spaces of the project
- it will answer these questions:
- what is opencare?
- how do I get involved?
- where can I find more info?
- who is doing it?
- picture
- statement that describes the project
- call to action button: share your story
- call to action links:
- opencare community page
- opencare research page
- (github repo)
- (youtube channels)
- twitter feed
- partners logos
to do & roadmap
- we'll use github pages (as a start using WeMake organization page)
- the repo can later be transfered to Opencare organization page on github
- we have a nice template (similar to OpenIdeo)
- we'll post it on the research page and we'll manage the issues using the repo issue un github
- only in english for now (a simple page is easier to be translated)
- before the next community hangout will be publish and shared on the research page
Alberto, Patrick, Noemi were OKish with building a new page, and paging here @nadia for input too. Advantages: removes the technical constraints imposed by Drupal. Disadvantages: Content Experiments cannot be used – testing of comparative performances of different landing pages impossible. One more thing that can break and needs maintenance. Edgeryders does not take responsibility for web pages outside of its website.
This was about it. Everyone, let us know what you think as we’re collecting input before and after each meeting, so that we save some time (one hour is not enough to get everyone’s opinions on topics).
Next call is on Monday, 16:30 CET. (check the Meetups page for updated event)
PS @eirinimal can you please re-post the link to the online room we will be using and any other useful info? I will make sure to include it in the event page. Thanks so much, and again, let us know if this conversation made sense to you at all