Attendance : Ga‘l Blondelle - EBM WebSourcing - Chairman of the TC Cedric Thomas - CEO of OW2 Antonio Majori - Engineering Pierre-Yves Gibello - Experlog Petr HNETYNKA - Charles University ------------------------------------------------------ Part 1 : Organization of the TC ------------------------------------------------------ Reminder of roles in the TC : CTO acts as the General Secretary of the Council - he operates the TC Chairman of the TC represents the TC In 2007, Jacques Cayuela was CTO of OW2 as part of the BULL contribution. In 2008, Jacques Cayuela can no more be CTO of OW2. The issue is that there is no CTO in the consortium to operate the TC. Question : Can the TC operate without a CTO? Response : Cédric Thomas has discussions with a strategic member to appoint a new CTO. Until a new CTO is appointed be a strategic member, we have to work by our own to make things go forward on a best effrot basis. Every volunteer welcome. Another issue : Redefine the role of the TC Proposal from Cedric Thomas to seperate two areas : - Consortium infrastructure production would be done by the MO and the production team - Strategy part of the TC would be led by TC members on voluntary basis Two issues - On the production side : we need a team leader. - On the strategic part : Who lead it? Proposal : - Production lead sould be the sysadmin at BULL. Jérémi Casery from BULL is supposed to lead this part as soon as he is 100% operationnal. - Chairman of the TC leads the strategic activities of the TC ------------------------------------------------------ Part 2 : Technology vision as promoted by the TC ------------------------------------------------------ Technical vision: - Projects in the OW2 code base interoperate (that's the target) - Synchronized releases strategy vs Reference Implementation strategy Process: - We start with clusters of interoperability - Interoperability will propagate across these clusters Marketing: - We announce the *process*: code name "Himalaya" ------------------------------------------------------ Part 3 : Project selection process ------------------------------------------------------ - TC-related board issues (see below) Some project selection criteria are ecosystem issues and are handled by the EC : * competition with an existing project, ... Some project issues like dual licensing are to be handled by the board. Some project selection criteria are technical and handled by the TC Define Criteria to put projects in the Attic and the incubator Action : GB : Ask MO to create the Incubator and the Attic on the forge ------------------------------------------------------ Part 4 : TC work plan for 2008 ------------------------------------------------------ Deliverables are expected from the TC : GB - Product life cycle must be made more concrete : Draft due by the end of February PYG - Draft a list of criteria to accept a project in the incubator, to move a project from incubator to active, and to move a project from active to attic. PH - Existing project evaluation : code base audit : Starting ASAP, first statistic published to TC, EC and board lists by the beginning of March (before next board meeting) - A specific case to handle is Enhydra which is a "ten projects in one" hosted by OW2, and supported by a company which is not member of the consortium. Should bring us to implement the Attic - Create list of indicators used to order the projects - commits, download, mailing list activity, forum activity, ... Remark from GB : There were only 4 person attending this TC. We splitted the work between the present people, but it is clear that all volunteers are welcome to join the effort. I know that if you read this line, you are interested in the OW2 success. Be sure you can contribute to this success.