Community Group Meeting 20 Jan 2004

Past Action Items from last week's CWG meeting

• Everybody to think about what our 0.4 goals should be.
• Ducky to take and post meeting notes. Done
• Ducky to massage Mitchell's notes on mission statement into a first pass. Done
• Ducky to subtract 543 Howard Street accesses from wiki count (and Web, when it becomes available) Done
• Ducky to add metrics for various individual pages (Staff meeting minutes, management committee meeting minutes, status reports, status updates, working group pages) to QuantitativeCommunityInvolvementMetrics. Done
• Pieter to figure out what it would take to make and post a video of a demo. evaluating software options for content
• Pieter to put recent Community Working Group (CWG) progress into the Status Manager's "summarize" feature. not done
• Pieter to talk to Katie and John about what talk Apps could give at OSCON. not done yet
• Pieter is to see about getting us a 90 minute slot to talk about both Apps and Repository. sent request to O'Reilly
• Ted is to give Pieter a title and very brief description a repository talk. received
• Ted to suggest two possible sprint topics to the PyCon organizers -- sharing and WebDav -- and see if they like those. Done

Current topics:

• finalize mission statement (see CommunityGroupMeeting20040113)
• 0.4 goals
• brainstorming on StarterProjects projects for the Community Group

Office Hour topics for next week

We talked for a while about what would be good topics for the Office Hours next week. There were a number of ideas that came up under the broad heading of harvesting experience from other open source projects -- what has been helpful or a barrier in other open source projects participants have worked on -- licensing/copyright, check-in policies, code reviews, process for getting involved, etc.

There was also a request to ask if anyone had done a PyCon sprint before, and a suggestion of doing an Office Hour where we went through the StarterProjects.

We decided that Ducky would do double duty as moderator and presenter with Pieter jumping in as presenter if it got hectic.

Finalize Mission Statement

During the meeting, we worked out our finalilzed mission statement:

The Community Working Group's mission is to act as a catalyst for making community goals for Chandler come to pass. This includes the promotion of activities such as:

• effective interactions between different constituencies of the Chandler community;
• good communications mechanisms;
• software development processes and policies that help expand the Chandler community;
• tools and mechanisms that help members of the Chandler community work well together;
• involving the best people in the most effective way; and
• a broad community - based culture.

In other words, the Community Working Group represents the "open-sourceness" of the project.

Participation in other Open Source Communities

There was some thought that we should be participating more in other open source communities so that they know that we are still alive and doing useful and reasonable stuff. One possibility given was for Ducky to monitor the Python list and ping developers (especially Ted) if something of interest came up. However, there was some question about whether it made sense to invest the time in the Python list right now.

0.4 Goals

There was a sense that we needed to start getting developers to think now about what their goals are for community (not just code) for the 0.4 release. After Ted documents his current thoughts, we'll show other groups Ted's thinking as a way of stimulating their own thought processes.

Action Items

• Ducky to write and post meeting notes.
• Ducky to post a request for help on PyCon sprints to the StarterProjects.
• Ducky to set up the skeleton of a page that discusses code that the Chandler project has contributed back to other open source projects.
• Ted to blog that Andi contributed code back to the Lucene project.
• Ted to send out a note with his current thinking on how to expand the repository developer community.

Open Issues

• Should we invest time now monitoring the Python mailing lists?

Things We Didn't Finish This Week

• 0.4 thoughts (? or are we done?)
• Discussion about Planets (aggregations of all the blogs of participants in a particular open source community, e.g. PlanetApache). Ted says it's a few months too early to think about whether it would be useful for Chandler to have a Planet.
• Brainstorming on good StarterProjects projects

next week's CWG meeting

-- DuckySherwood - 15 Jan 2004