I wish you all a happy new year too.

From IRB perspective, it would be good to see the support for the unified 
introspection xml format worked on.

Also, I’d like to +1 the more dynamic API for thin client: we’ve recently seen 
some discussion with the HAE group about how to deal with dynamically available 
device capabilities (e.g. where you can plug in/unplug a component from an 
appliance) that would be elegantly modeled with bus objects that get added 
to/removed from the bus. The major stumbling block for them was precisely that 
thin client doesn’t support that today.

-Dominique

From: 
<[email protected]<mailto:[email protected]>>
 on behalf of Marcello Lioy
Date: Thursday 7 January 2016 at 23:01
To: 
"[email protected]<mailto:[email protected]>"
Subject: [Allseen-core] Wish list for 2016

Happy new year all!

There is work going on at the board and TSC level to hire developers to support 
the working groups so that development is driven by TSC/working group 
priorities rather than individual companies desires.  As such we as the core 
working group we need to identify issues that we would like to have some of 
these developers focus on.  This was discussed in today’s Core WG 
meeting<https://wiki.allseenalliance.org/core/overview#meeting_minutes>, and 
some of the ideas for this work is covered in on slide 
8<https://wiki.allseenalliance.org/_media/core/allseen-corewg-01-07-16.pdf>.

I am soliciting input from others on the mail list for work that you think is 
valuable that would benefit the core (and ultimately the Alliance as a whole).  
Smaller items may be able to make it into the 16.04 release, and bigger ones 
would be targeted at 16.10.

Link to slides: 
https://wiki.allseenalliance.org/_media/core/allseen-corewg-01-07-16.pdf
_______________________________________________
Allseen-core mailing list
[email protected]
https://lists.allseenalliance.org/mailman/listinfo/allseen-core

Reply via email to