News‎ > ‎

20120717 Open-H2O.org meeting

posted Jul 17, 2012, 11:37 PM by Cesar Harada   [ updated Jul 18, 2012, 1:59 AM ]

20120717 Open-H2O.org General meeting



20120717 Open-H2O.org General meeting

-People

Introduction

Relations between Open-H2O, OpenROV, Protei and future members

Discussion about the use of Open-H2O.org

Community users profiles & Privileges

Type of media hostes on our server

Functions & Architecture

Layout & Workflows

Proposed Distribution of work

Project management



https://docs.google.com/document/d/1LeJtF2YHfQ6p8NxAVGEZMgP-ZSZ8hzjNdiq3WQ7PHHA/edit

  People


  • Gabriella Levine
  • David Lang
  • Noe Lutz
  • Brian Poissant
  • Kasia Molga
  • Cesar Harada



Introduction

We are in the process of developing Open-H2O community website.
It is important that we start by stating what is Open-H2O, what is the mission of Open-H2O and what the website would provide.


Open-H2O mission is to promote and support the development of Open technologies for the study and protection of the ocean.

Open-H2O community is a global on-line community that is a place to

  • Co-develop project (ala Instructables)
  • License (simple as Creative commons but with an Open Hardware license for water applications in particular)
  • Share environmental data (ala pachube / cosm, probably a google maps mashup)

And when we mean share data, beyond real-time environmental data collected by remotely operated vehicles, we are talking also about providing a forum, a wiki and more services for the community.
Allen Jiang is also interested in developing the marketplace to compare/ comment/ sell fabrication materials, sensors and other DIY and Scientific Equipment. A very long tail amazon tailored for specialist communities...


Relations between Open-H2O, OpenROV, Protei and future members


http://www.flickr.com/photos/worldworldworld/7027862399/sizes/l/







Discussion about the use of Open-H2O.org


OpenROV is building it’s own wiki, it has it’s own blog, it has currently around 1000 members on it’s Ning platform but it is meant to migrate to a more advanced CMS sometimes.
OpenROV is interested only in using
  • the licence (Open Hardware H2O license) and perhaps
  • sending commands to remote machine through a web interface and receive real-time  environmental data through a web interface : which Noe is interested in building.
OpenROV is a good example of future community member that may not want to use all the functions of Open-H2O and keep its independence and centralize information about its own technology.

  • On the other hand Protei and Open-H2O would have a very different relationship :
  • Open-H2O (non-profit) would be the community developping Protei technology.
    Protei inc (C-corp) would mainly manufacture, distribute and operate Protei commercially.
In that sense, Open-H2O would provide all the infrastructure for Protei, Protei will only own a basic storefront website, selling Protei. The bigger idea is that even if Protei is not an immediate commercial success, the technology and the community behind Protei keeps growing strong.


https://docs.google.com/drawings/d/1Ra9GRW8BbSYm65SFQU9xxKapydFDZM3Fe9au95qBDUk/edit
Archive : http://www.flickr.com/photos/worldworldworld/7595359202/sizes/l/in/photostream/


Community users profiles & Privileges


  • Kids
  • DIY hero, hobbyist
  • Environmental activist
  • Coastal / lake resident
  • Student undergrad
  • Researcher graduate
  • Professor
  • Industry
  • Government
  • Military
-- on our side we would have different levels of privileges in the CMS
  • Superadmin
  • Admin
  • Editor (can edit all pages)
  • Moderator
  • Groups owner
  • Contributot
  • Susbscriber


Type of media hostes on our server


  • Text (basic, code)
  • Images
  • 3D files
  • pdf
  • KML, XML, JSON  
NOT Hosted by us :
  • Sound (soundcloud)
  • Video (youtube)
  • ...

From my experience it’s a good idea to have a simple simple FTP to exchange large file and archive some of our content in a clean URL, check protei.org/download/?C=M;O=D





Functions & Architecture

The idea is to have a stable and modular CMS that we would build over time.
  • Level 0. The core is Drupal.
Than we implement the essential functions.
  • Level 1. We login using either facebook, Gmail, OpenID (TBdiscussed). Captcha.
  • Level 2. notification / subscription system. Like facebook, we want to create a social environment that is vibrant and encourage people to interact if not to get totally addicted to this community. It is important that users can subscribe to single thread, to group activity, or to a keyword that would come up through the blog feed.  I (cesar) love how http://disqus.com/ works (facebook, Twitter and much more integration)
  • Level 3. Static pages and blog.  (“Co-design” ala instructables and “Licence” ala Creative commons  can be done with these, and specific templates)
At this stage it would be great to implement an automatic back up of the the website, perhaps a simple CRON job.
  • Level 4. Groups and subgroups. Multilingual.
  • Level 5. Private and public pages
  • Level 6. Forum
  • Level 7. Wiki
  • Level 8. “Share Data” ala pachibe that is the mashup to send commands to machine and log real-time environmental data.
  • Level 9. Shop / compare products

Edit this diagram here :
https://docs.google.com/drawings/d/1v5zt0jn-3HnvpswC0tbQodAkTzFQvTeQauXgsfo8hyU/edit
Archive : http://www.flickr.com/photos/worldworldworld/7595239036/sizes/o/in/photostream/





Layout & Workflows


At this stage, these are just early thoughts of how the website could look like, based on a simple grid with some space for our sponsors.


http://www.flickr.com/photos/worldworldworld/6983796194/sizes/l/


Proposed Distribution of work


  • General drupal distribution and plugins : Brian, Cesar
>> Can you install drupal on your server and give us access
  • UI, Wireframe, Wokflow : Kasia, Cesar
>> Based on the existing wireframe, propose more detailled workflows. Propose template for static pages, blogs, propose widgets.
  • Real-time data to browser (control room, google mashup) : Noe, Kasia
>> Noe could you speak to Kasia about what’s been done so far with the oil compass and how we want to data to be structured. Keep in mind that there will be 2 main uses for the data : control the robots in real time and get environmental data AND mashup on a google map + whatever you suggest :)
  • Real-time data to browser (cockpit view, inside machine) : Noe, Kasia, Gabriella
>> Noe and Gabriella, you want to talk about the communication between the server and each machines.
  • Feedback : David Lang
>> No homework, just if you could give feedback. What you will use is one thing | another thing is what you wish was there in a community that develops open source technologies for the ocean (regardless of what OpenROV is currently doing - or perhaps that OpenROV would love to have but does not currently have the resource to undertake)




Project management


  • Meetings : Google hangout once every 2 weeks. As soon as static pages would be ready on the website I suggest we embed a hangout on a static page, so we meet at a given time on a URL.
  • Documentation : Google docs (like this one). All documents are shared with people that have an address@open-H2O.org
  • Mails : I have bought a google apps account so we all have an address@open-H2o.org. It does cost me 5$ / person / months, so please do not create more users, we cannot afford more users at the moment.
  • Project management : Trello. https://trello.com/openh2oorg please simply create
  • GitHub (or other) : I let you guys set this up.
Comments