On Thursday 22 January 2015 10:55:37 Keane, Erich wrote:
> I agree with John. If at all possible, #1 would be awesome, and it
> would be worth exploring what it would take to make it public/free.
>
> #2 is definitely something I would be OK with, but if the generated code
> isn't very maintainable, we might be better off just scrapping the code
> if we can't do #1.
>
> #3 seems like a non-starter for me. Any open-source project that starts
> with "buy a $500 piece of software" isn't very open to me.
Oh, that's a good point. Option #3 is a sore, sticking point that our
competition will gladly publicise.
I had to be exhaustive in the options, but you're right, it's a non-starter.
And just to be clear, there's a fourth option, which is not to have the code
at all. So another option we need to explore is what the relevance of the code
is and what gets impacted if it's not there.
I think we need to answer these questions:
a) is the generated code readable at all?
b) is it possible to maintain the generated code by hand? How much effort?
c) what platforms does the generator currently run on?
d) how difficult would it be to reimplement the generator in (say) Python?
e) does the code need to be generated at all? Like Erich said, we may be
better off redoing it by hand,
f) what happens to the feature if the generated code isn't present?
g) what happens if we don't include the feature? Could it be moved to a
separate project, outside of IoTivity?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
