Community Group Meeting 18 May 2004

Action items from last meeting

• Ted to write up goals that arose out of PyCon on a wiki page; Ducky to link to it from CommunityHome. Ted sent first draft via email
• Ted to start coordinating with working groups re PyCon goals. in progress
• Ted to write up risks/rewards of making PyLucene a separate project from Chandler. done (email)
• Pieter to continue looking at Creative Commons licenses and recommend ones for Wiki and Web site use. recommendation done, see below
• Pieter to ask Jürgen about notice that #chandler is logged. done, Jürgen will put it in the topic
• Ducky to continue looking into VOIP and collaborative real-time editing, including for conferencing. some progress made into shtoom by RTFSource
• Ducky to write up first pass of Community FAQ. not done
• Ducky to write and post meeting notes. done
• Ducky to check with Heikki on what exactly he's done with PyEGADs and M2Crypto. He has not in fact released PyEGADS to Source Forge, awaiting licensing decisions
• Ducky to follow up on institutionalizing method for tracking inbound and outbound licenses. clarification sought
• Mitchell to talk to Siobhan to ask about academic research.
• Mitchell to put out a draft contributor license soon.

Creative Commons

Web site and wiki would be under Creative Commons license; default license would have very few limitations; different individual contributions could choose different ones e.g. share-alike.

Discussion about whether or not we should do "Attribution Only" or allow people to do "Share Alike".

Some discussion of how to figure out who contributed to the wiki pages. Pieter suggests that the wiki guide says that if you want attribution, put your authoring line on the page; Ducky suggests that it would be easy to write a script to pull out who authored that page. Ducky and Pieter to take this offline.

Questions about OSAF logo and trademark and so on. If you use the Creative Commons logo, you must have it link back to the home page; Pieter would like to see us do the same with the logo. Open questions about trademark etc now.

PyLucene

Some discussion about who should own PyLucene; discussion about how tightly this should be integrated in with normal Chandler development. Ted said that when taking code from a company, ASF assigns a mentor to them to make sure they understand the "ASF way". Some discussion about how we want this project to happen and we want it to succeed, because if we don't, then someone else will do it.

Action items for next meeting

• Ted to put PyCon goals on a wiki page; Ducky to link to it from CommunityHome.
• Ted to start coordinating with working groups re PyCon goals.
• Ted to put risks/rewards of making PyLucene a separate project from Chandler on wiki.
• Pieter to continue looking at Creative Commons licenses and recommend ones for Wiki and Web site use.
• Pieter to ask Jürgen about notice that #chandler is logged.
• Pieter and Ducky to figure out what mechanism is needed to get proper attribution to authors.
• Ducky to continue looking into VOIP and collaborative real-time editing, including for conferencing.
• Ducky to make link to inbound and outbound licensing information more prominent.
• Ducky to write up first pass of Community FAQ.
• Ducky to write and post meeting notes.
• Ducky to look at wiki pages for inbound and outbound licenses, possibly revising.
• Mitchell to talk to Siobhan to ask about academic research.
• Mitchell to put out a draft contributor license soon.

-- DuckySherwood - 12 May 2004