Dashboard > The DataPortability Project > 2008 > March > 17 > Steering ConfCall 2008-03-19
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Steering ConfCall 2008-03-19
Added by Phil Wolff , last edited by John Breslin on Mar 20, 2008  (view change)
Labels: 

On this page:

Announcement

WHAT: Steering Committee Conference Call

WHEN: Wednesday, March 19, 2008 at 21:00:00 UTC time

WHO: Open to anyone
WHERE: phone/Skype

DIRECTIONS: Skype call: +9900827041975640

MEETING GOALS:

  •  

AGENDA:

  •  

PRE-WORK:

  • Review previous two weeks' activity
  • Identify problems requiring discussion and possible solutions

Minutes

Steering Group Teleconference

Date: 3/19/2008
Time: 9pm GMT

Attendees:

Real Name (Skype Name)
Chris Saad (chris.saad)
J. Trent Adams (jtrentadams)
Bob Ngu (bobngu)
Christian Scholz (herrtopf)
Jacob Chaple (chap3l)
John Breslin (johnbreslin)
Triona Carey (triona.carey)
Drummond Reed (=drummond)
Brady Brim-DeForest (bradybd)
Paul Trevithick (paul.trevithick)
Dan Brickley (danbrickley)
Brett McDowell (myidiym)
Daniela Barbosa (medanielabarbosa)
Kaliya (identitywoman)
Steve (greenbes)

Call Flow:

1. State of the Project (Chris)
2. Update from the Action Groups (skipped per new call protocol)
3. Floor Discussion Topics
4. Summary and Next Steps

-------------------

Update by Chris:

  • Going to a lot of conferences, representing DataPortability Project on various tracks.
  • Selecting logo shortlist by three "celebs", final selection by community voting via TechCrunch voting system. Due diligence on final choices, Hope to reveal at TechCrunch party in April.
  • Moved Wiki platform to final domain.
  • So much to do in such little time = decision paralysis problems.

-------------------

Floor Discussion Topics (in order of discussion):

G. Teleconference Protocol Update

  • Single time for updates
  • Watch for hand raising
  • Conference Call times
  • Timeanddate.com
  • Use Upcoming or Google Calendar for schedling?
  • Proposals need to be accompanied by a champion on the call.

A. Support IRC chat channel

  • #dataportability (on?)
  • Perhaps using IRC, bridging between Skype?
  • No voice on IRC
  • No history on IRC?
    • Could leverage existing bots to support.
    • Some tender-loving care needing attention.
  • No-Op for now.

B. Commit to supporting open and royalty free solutions.

  • Unclear whether they meant in the stack or tools.
  • No champion on call
  • No-Op

C. General research & outreach update (eg. W3C, etc.)

  • What are we researching?
    • Communities
    • Solutions
  • Look into table listing what/who matrix kinda' thing
  • Goals:
    • Face time
    • Building the matrix
  • How can the W3C work with DataPortability?
  • Harry Halpin to act as liaison to W3C, potentially via Social Web XG

D. Recognition mechanism for contributors.

  • No champion on call
  • No-Op

E. Possible shift of DP acronym to DaPo

  • No champion on call
  • DP is fine for now
  • No-Op

F. Revisit concise mission statement

  • Need it to be nailed down.
  • Consider Purpose: "The purpose of this project is to put existing technologies, techniques, policies and initiatives in context in order to facilitate translation, education, advocacy and ultimately implementation of data portability. Portability is defined as both physically moving data or simply porting the context in which the data is used."
  • Purpose is not concise enough.
  • Needs to be more memorable.
  • Suggestion that we need a sound byte.
  • Create Wiki page for messaging to gather ideas, then compile results for adoption.
  • Recommendation that a small group work up ideas.
  • Possible need for more than one variant for alternate uses.
  • Put on agenda for next week to define and close out.

Side Discussion: More effective use of DataPortability.org site vis a vis the Wiki

H. Data Sharing Workshop and Summit

  • Should be considered a DataPortability Project supported event.
  • Encouraging open agenda items, draw from DataPortability Project
  • True working sessions, outreach into the identity commuity
  • Also see: Identity Camp Bremen (http://barcamp.org/IdentityCampBremen
  • Also see: NextWeb in Amsterdam (URL?)

I. Governance Models

  • Healthy discussion ongoing in threads.
  • Folds into discussion about legal framework.
  • More detailed update on next call.

J. Big Company Involvement Update

  • Microsoft providing legal advice and video
  • Yahoo submitted video
  • LinkedIn at meetup
  • Facebook at meetup
  • SixApart at meetup
  • Plaxo at meetup
  • Chris indicates all partners are:
    • committed
    • looking for what they can do to help the project
    • cautiously optimistic
    • looking for best practices documentation on "DataPortability Project" compiance.
    • likely to see the smaller companies move first, but they will move quickly afterward
    • understand that first getting the flood of goodness.

Possible Future Discussions:

A. What is the minimum requirements for a technical support.
B. Possible separate calls for other goups.
C. Discuss Christian's points on direction from his blog post.

Conference call recording, back channel transcript

Next meetings 

  • Proposed: April 1st, 2008 @ 9pm GMT

Feedback on the meeting itself

  •  

Meeting Notes (for integration above)

==State of the Project==  (Chris Saad)

1.  Public Relations:  DataPortability has had a presence at SXSW, MIX, and will at Next Web Conf in Amsterdam
We are generating a substantial amount of mindshare

2. Logo Competition:
Background: Red Hat Cease and Desist
We have had 250 logo submissions
Fifteen finalists will be chosen
The competition will take place at:
dataportability.techcrunch.com

3. Wiki platforms:  Full migration to Confluence powered Wiki

4.  Research Phase

5.  Big picture: 11 DataPortability questions, 11 responses to those questions

6. Legal issues:  TechCrunch and MS have offered pro-bono legal work to assist the Project.

A. Teleconference Protocol Update:
Suggested Action Group Conference Call protocol:
1.  Hand-raising in the chat room. This encourages full group participation in the call.
2.  Post notes on Wiki and GoogleGroups, for final inclusion in the meeting minutes.
3.  Identify yourself by name before speaking.
4.  Schedule conference calls in advance and on a regular basis.  Google Calendar and TimeandDate.com may be helpful scheduling tools.
5.  Mute microphone when not speaking.
6.  If the proposer of the agenda item is not present, the idea doesn't need to be discussed, and should be tabled for the following call.
7. individual agenda items should also list 'presenter' or 'proposer' name.

B.  IRC Chat Channel:
1.  Should we make IRC the official DataPoratbility Chat system?
    •Negatives:  doesn't support Audio
2. Conclusions:     • IRC can exist as a back channel
                           • The discussion should be tabled until the following meeting.
 

C. Supporting Open and Royalty Free Solutions Across the Board:
• This discussion was tabled until the following meeting.

D.  General Research and Outreach Update:

E.  Contributor Recognition:
• Consensus: Participants are acknowledged based on their contributions.
• This discussion was tabled until a following time.

F.  Usage of Acronyms:
• Consensus: Care should be taken to avoid abbreviating DataPortability.  If an acronym is needed, DP, or DPP is fine.  DataPortability.org should never be abbreviated as DP.org

G. The DataPortability Mission Statement:

H. TheDataPortability Website:

I. Data Sharing Workshop and Summit:

  • The Data Sharing Workshop, April 18 - 19 at the SFSU, Downtown Campus.
  • The Data Sharing Summit, May 15, at the Computer History Museum.

J.  Big Company Outreach: 

K.  The Logo Competition:
• Consensus:  It was determined that the three members of the expert panel would select 15 entries, which would then be vetted for trademark suitability before the public vote. 

Apologies for missing the call. I had proposed half the agenda items based on community feedback, and listening in now, it obviously made some of the call difficult that I wasn't there to explain. Sorry!

re royalty free standards: this was about ensuring our work is consistent with the w3c's request per my discussion with Harry Halpin. It's to ensure we don't support any standards and technologies that are somehow controlled for profit by another entity. I wanted to get a motion to affirm we all agree with this principle. It's obvious, but crucially important.

re recognition mechanism: this was in response to get more people contributing. I wanted to bring up issues that are hindering involvement by people, as well as developing a system to recognise contributors so as to reinforce positive behaviours.

re DaPo: Suggestion by someone in the community, who is now involved with DataPortability for an acronym change. But I think the call handled this issue so nothing further to add.

  March 2008
Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          

March 2008 report published
Steering ConfCall 4 March

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators