r1 - 02 May 2006 - 09:07:51 - SheilaMooneyYou are here: OSAF >  Journal Web  >  MeetingNotes > ManagementCommitteeMeetingNotes > OperationsGroupMeetingNotes20060425

Staffing Discussion

  • Interns
  • Bus dev person

Business Models

  • Mitch discussed thoughts on posible business models

Community Projects Update (Ted)

  • A number of projects on ted's list
    • Portal
      • making progress on taxonomy - will soon have a proposal with navigation and template of pages
    • Google summer of code
      • Deadline is next monday May 1
      • Working on a list of projects
      • People have volunteered to be mentors but they need to have a specific project crafted
    • Growing cosmo and scooby community - on demand basis
      • Getting the teams participating in google summer of code
      • Important to ramp up these projects
    • Targeting community participation
      • OSU - we got as much out of that as we can
      • Darshana is thinking of applying for google summer of code for funding
    • Commit policy - need to work on that
    • Governance - discussing certain issues
    • Policy for dealing with UI contributions - or dev contributions that have a ui component

CSG report (Mitch)

  • About to do the CSG report
  • It would be helpful to make sure there is a pointer to the most recent summary info
    • Sheila - tatus of 0.7 product status - roadmap, product plan
    • Ted - status of community efforts
    • Katie - eng architecture update
    • What about cosmo/scooby - John
  • Get to Mitch by the end of the week
  • We will mention the strategy stuff to them

Sprint week agenda (Katie)

  • Katie sent out a link to the ops team
  • Constraints - main sprinting around testing - 2 days when john and matt are in office
  • Set of lightning talks - want people to be around for that - we could do this at the staff meeting
  • Leave some time at staff meeting for strategy

OSAF related IT projects and priorities (Jared and Katie)

  • Goal was to get a cross group view of projects
  • Things that support community - portal
  • Things that support build/release stuff
  • These would be the 2 top priority areas
  • Next steps: focus on build/release and portal areas - sort those out

1.0 Beta

  • Get to users sooner than 12-18mos
  • We will work on 0.7 + plan and ecosystem design for 1.0
  • Message about the "ecosystem"
    • Cosmo/scooby not in the shadow
    • They support ecosystem but not independent projects
    • Need to be consistent about that message
    • How do we talk about the team? there is a cosmo/scooby server team (bobby and john) working on both sides
    • Probably need to update the dev page

  • Products and services
    • The chandler service
    • The chandler client
    • The chandler web client
    • The chandler desktop client
    • Use chandler as a name for overall system and ecology
    • TM chandler - todd and erin have done this for foxmarks

Open Issues

  • Bounties (Heikki and Jared)
    • Something that are bountiable could hopefully be done via summer of code
    • Not really a budget issue
    • We will work towards summer of code - using this

-- SheilaMooney - 02 May 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.