Meeting 09/03/2016

Participants

  • Cedric CTH
  • Daniele DGA
  • Stéphane SLA

Minutes

TC Chair and OW2 Context

  • CTH: It's important to be in a win-win situation for Daniele, Engineering, OW2.
  • CTH: The OW2 Management Office aims at an efficient bureaucracy The counterbalance is one one hand the board of directors (long-term vision and on the other hand the TC that represents the community. The TC CHair represents the political part. Balance and guidance. The TC is a Chamber. Daniele has been elected, Cedric and Stéphane have not. Different legitimities. The Chair helps the CTO making sure the flow makes sense to project leaders and new projects. Stéphane runs the TC The Chair is an authority who checks the agenda, poke the project leaders. It's yours. Don't be shy. Usually people just look at what's happening, they remain silent, they step in only if they disagree.
  • CTH: Prioritiy: we need to revamp the TC. Since Alex left, we have not recovered the momentum of the TC
  • CTH: Context: OW2 evolution: the Java application server world changed base (RedHat acquired JBoss, loss of interest in JOnAS). OW2 is going though a transition period. We need to accept that and to agreen on the fact that the situation is more complex today. We are at then end of a cycle.

Past cycle

5 years ago, Cedric presented 3 layers:

  • Technology layer, the backdrop of future enterprise applications around 4 common resources: cloud computing resources, big data resoures, privacy and security resources, future internet resources
  • Quality layer: that was SQuAT, which becomes OSCAR. It started bottom-up. We need to be transparent. be transparent. Give users confidence, Remove some of the uncertainty. Surrounding projects: RISCOSS (a way to add value to the raw information provided by FOSSology, Antepedia, combine the info and infer data helping people make better decisions). We have plans to evolve OSCAR into scorecards.
  • Marketplace layer: brag about the projects. AppHub project.

At the end of 2016, these layers will be in place. In parallel, we have to think about the next cycle (already shared with the OW2 MO). We need to provide value to the market and the users: integrators, service companies, industry.

New cycle: the OW2 Process

4 steps:

  • Technology
  • Community: good governance will create quality, it creates the difference, it creates predictability
  • Quality: OSCAR
  • Delivery: projects can be easy downloaded, support the implementation, the usage of the projects. Cover all the issues that user will be confronted to when downloading software from OW2. Make large end users have a better strategy with open-source software. Governance from the standpoint of the usage.

Discussion

  • DGA: we need to make the community stronger. Interested in working in this direction as a first step.
  • CTH: having projects naming themselves "OW2..." is a great satisfaction. We need to give project leaders good reason to doing that.
  • DGA: emphasisis should be put on the infrastructure. We should aim at providing a secondary home for the projects. 
  • CTH: Quality and Marketplace are bringing differentiators
  • DGA: in charge of the corporate infrastructure at Engineering, which raises much interest to the developers as it solves concrete problems that they're facing in the field of infrastructure and visibility.
  • DGA: promote stories on OW2 site about concrete usage of the OW2 process as testimonials. How they use the infrastructure, tell about the benefits, and tell about customer stories (success stories). People need facts.
  • CTH: success stories were left on the back-burner but they exist at Success_Stories. A template exists already. DGA will talk to Cristina about it.
  • CTH: before the TC, OW2 had a "College of architects". Discussions revolved around key APIs around Java Application Servers. Visionaries vs people taking it to the next stage. The TC is not only about managing the community. The TC could identify potential candidates for the code base.
  • DGA: the TC could be an incubator of new ideas.

Actions

Community

  • TC revival: agree on and send the mail proposed by CTH:

Dear Technology Council, we have some 100 names in the TC mailing list and this does not reflect the TC activity. As a result many of you receive mails that might not be of interest. We propose to establish a time-out rule to gradually clean up this list: the TC mailing list will be refreshed every six months and only active email addresses will be kept in the list. Your email will always be kept on the project-leaders list which will keep receiving call for presentation, exhibition opportunities, etc.

Please let us know what you think; you can also use the following options for your reply:
[  ] Please keep me in the TC list no matter what.
[  ] Thank you for removing my email from the TC list, please leave in the project-leaders list
[  ] I'm taking this opportunity to ask you to remove my email from both TC and project-leaders lists.
[  ] I'm taking this opportunity to ask you to replace my email address by this new one: ....@....

  • Success story template update, elaborate a strategy to recruit success stories. Share the strategy with the whole TC.
  • Contest: recruit topics and teams esp. in Europe
  • Next IRC: Contest + Forge / Infra / Testing (STAMP)?

Quality: OSCAR

  • Daniele: can we know more about the existing and future corporate infrastructure at Engineering for quality management

Technology

  • Review the existing projects / upgrade some to mature / some others to archive
  • Forge requirements roadmap review

Marketplace

  • Reconcile the AppHub charter (spin-off of OMM) with OSCAR / OMM: launch this discussion on the TC