DataPortability San Francisco & Silicon Valley Meetup- April 30th MountainView, CA (LinkedIn)

On this page:

Announcement 

This month's Local SF/Bay Area meet-up will be in Mountain View. Thanks in advance to Jim Meyer, Challenge-Oriented Problem Solver at Linkedin for volunteering their space!

Please Reserve on upcoming : http://upcoming.yahoo.com/event/472061/?ps=5 

WHO: DataPortability Bay Area (and visitors!)
WHAT: April Local Monthly Meetup
WHEN: April 30th 6pm
WHERE: LinkedIn Office, MountainView **
DIRECTIONS: 2029 Stierlin Ct. Mountain View, CA
WHEN by Time Zone: 6pm PST  (Local Call-Ins/Video)

**CAR Pooling? Need a Ride/ Want to Leave a Ride? Please leave your name/email below:

- Daniela Barbosa. SF downtown>MountainView on the way home i can drop you off at Colma/Daly City-BART - danielavbarbosa@gmail.com

MEETING GOALS:

•  Meet and Greet South Bay DataPortability folks
•  Finalize DIY Club (Do It Yourself) and

AGENDA:

• Introductions
• DIY - Do It Yourself Club-
  • What is the DIY and how it came about
  • Discuss Message Calendar for the next 6 months
  • Discuss and Agree to details of first DIY Project which is drafted to be around rel=me implementations. Please join us in defining this project that was proposed by Phil Wolff, Kevin Marks and David Recordon
  • How do we get the community (Developers and Users) to participate in this first project
• Time to Mingle and discuss projects attendees might be working on

PRE-WORK: 

• N/A

Minutes

Attendees: Name / Skype Name / Affiliation

picture: http://www.flickr.com/photos/tantek/2479273911/?addedcomment=1

• [Daniela Barbosa]
• Phil Wolff- Skype Journal
• Jim Meyer- LinkedIn
• Steve Ganz- LinkedIn
• Tantek Celik-
• Kevin Marks-Google
• Chris Saad
• Ryan Parman- Warpshare
• Vada Dean- Warpshare
• Michele Ursino- Foldier
• Mary Trigiani- Foldier
• Rajesh Kadam- earchyogi.com
• Bob Ngu-
• Taylor Singletary- LinkedIn

Attendees via uStream/Skype

• [Trent Adams]
• [Brady Brim-Deforest]
• Mark Laymon

Minutes

DIY OF THE MONTH DISCUSSION

• Possibilities for the Project to give microformats.org some support and use cases. 
  1. Link the dataportability community to the microformats specialists community
  2. Provide examples of conversion to rel=me
  3. Next focal point?  Importable friends and contacts.* Rel=me implementation considerations# Establish the context as well as define the program for both technologists and users
  4. The Project could offer help in consuming all the information being created in new implementations -- in terms of how people "touch" it
  5. Define how rel=me benefits the user; remember that very few people know how to install a plug-in -- rel=me is much easiert to implement at the user point, so it shortens the route to making a person's data more portable -- maybe that's the benefit
  6. Then drive a focus that results in a use case
  7. Plaxo is a possible use case example; they've implemented a Google social graph URL; another is Dopplr, the contact utility, which is a potential example because it shows how to use rel=me without the user having to worry about knowing what it is
  8. Make sure to tell the story from the user's point of view -- whether it's an individual or a corporate executive
  9. Security:  avoid search by email; don't publish the email address -- not even a hash of it; avoid scenarios that will scare the user; consider opt-in linking to a blog, letting the user decide whether to consolidate his identity; keep everything visible to the user -- don't publish anything invisible
     

• Think of May as Identity Consolidation Month, with rel=me as the project # Create a roster of startups that are first movers

1. 1. List existing adopters
   2. Create links to movers, adopters and general information
   3. Think about creating an instruction list on instructables.com

MAY'S MESSAGE CALENDAR

• The Project is close to finalizing a technical roadmap for data portability implementations; it's a framework that we will embellish bit by bit and then connect.  This is not THE way to do data portability, but A way -- based upon current use cases, technical experience and interoperability success.
• We need people who want to review and debate it
• Discussing:  an end-to-end, piece-by-piece way to port data for different types of networks -- social, business/professional, family, niche
• Creating:  a tasl force that will organize meetups for technologists to examine and debate rel=me
• Building:  use cases that will appeal to corporate management types who want to achieve data portability for customers and employees but don't know how 

COMMENTS ON TECHNICAL ROADMAP DEVELOPMENT

• Process suggestions:  benchmark Yahoo's FireEagle, which has implemented OATH and has an excellent description page
• Address implications for enterprises AND individual users
• Documentation:  Make sure to move any meaningful discussion in the Skype chat rooms over to Google Chats and Confluence 

Action Items 

CHRIS/DANIELA/TRENT/PHIL/BRADY? 

• Determine a Method for Documenting Skype Conversations on the Wiki

Conference call recording, back channel transcript

Next meetings 

Feedback on the meeting itself