On quinta-feira, 2 de mar?o de 2017 14:16:26 PST Thiago Macieira wrote:
> Hello all
> 
> Finally getting to my action items from previous meetings of the Steering
> Group. I will send an email on each of the two, new proposed functions,
> detailing what is expected. We're looking for volunteers to assume the
> position of Function Lead for organising IoTivity's API as well as
> Buildsystem. We're asking for candidates since there is no natural
> candidate.

The first of the two proposed functions is the API Review one. We need a person 
or a team to be willing to look into any API we design that is meant to be 
used by anyone except ourselves, and make sure that the API is consistent. 
Soon, we'd also like to make sure that our API is backwards compatible, so 
applications written with IoTivity version X will continue to compile and work 
with IoTivity version Y, provided Y >= X.

This team will probably be tasked with reviewing the existing API as well, 
proposing changes, and establishing guidelines on how to review. The latter 
point will impact releasing: when is the API review supposed to happen, 
relative to the feature freeze and the releases? When is the API frozen for a 
given release? (note that Dino's release suggestion timetable had some 
elements of this)

This is a technical function and the Function Lead is expected to be 
knowledgeable of C and C++ API designs[*].

[*] the team may propose dropping the C++ API.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Reply via email to