I am just starting to work with IoTivity code and I can see there are a lot of 
warnings during compiling.
That's a bit surprising me!
So I think this could be one area to be improved as QA function:
* ensure no compiling warnings when building for different 
targets/configurations

/Shujuan


-----Original Message-----
From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Thiago Macieira
Sent: Thursday, March 17, 2016 5:31 PM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] Call for volunteer: QA Function leader

Hello

The ISG gave its blessing in December for the creation of a QA Function, 
responsible for the quality assurance of IoTivity as a whole. Previously, these 
responsibilities belonged to the Release Function, which meant that it was done 
on an ad-hoc basis and only at time of release.

We need more than that. This email is asking for volunteers to help establish 
this QA function, specifically the Function Leader. 

The ISG did not mandate a list of responsibilities, so this Function, once 
established, will need to do that. The following are ideas from me, just to get 
the ball rolling:

 * create a test plan for IoTivity
 * increase test coverage
 * participate in the release process and give go/no-go on releases
 * define the coding guidelines for ensuring quality in our sources
 * publish which sections of the code are under quality-control and which ones
    are experimental / unsupported
 * report to the ISG on the quality of the code

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

_______________________________________________
iotivity-dev mailing list
iotivity-dev at lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
----------------------------------------------------------------------
Intel Sweden AB
Registered Office: Isafjordsgatan 30B, 164 40 Kista, Stockholm, Sweden
Registration Number: 556189-6027

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Reply via email to