Jochen, I apologize for the delayed response. I don’t believe anyone else responded either. A lot of your questions about Mihini are probably better suited for the Mihini project mailing list. It is really up to the existing committers to decide if they would like to accept you contributions. As for the license, your contribution would have to come in under the project license, which I believe is EPL for Mihini. (I am flying right now so I can’t check.) The decision making in Mihini, and all Eclipse projects, is up to the existing committers. They get to decide the roadmap and elect new committers. For the Working Group, the decision making is done by the working group participants. Benjamin was selected by the participants to be the WG chair. I hope this answers some of your questions. Ian From: m2m-iwg-bounces@xxxxxxxxxxx [mailto:m2m-iwg-bounces@xxxxxxxxxxx] On Behalf Of Jochen Brunner
Sent: November-29-13 12:39 AM
To: m2m-iwg@xxxxxxxxxxx
Subject: [m2m-iwg] Working procedure to share code?
I am a specialist in colors (including photo, art, etc.), now working for an applied research institute and am interested in Lua and open source M2M.
I have seen that Eclipse does a lot in that area, and I am particularly interested in the Mihini project (and LDT/Koneki also).
The 0.9 release on Mihini is very good, and I started to write some code that extends it to fulfil my specific needs: chemical analysis based on data gathered from RGB light sensors. And I was wondering whether it would make sense for me to contribute that little Lua "library" of mine that can be made generic (for calibration and usage of an RGB light sensor).
So I have a few questions: 1) Would this be something that would be interesting for the Mihini project?
If yes, what's the best way to actually share the code?
Just finish and clean it, and then send it somehow as a whole (if so, how?)? 2) If I share code, it will be under the Eclipse Public License, right?
I'm asking because from the code headers I have read, it looks like most of the code so far is (C) Sierra Wireless (but apparently under EPL).
Also the support so far seems to come from Sierra Wireless on the mailing-list (which is great).
So it's great from you guys, thanks a lot, but this leads me to my two last questions. 3) How does the group/project work?
It looks like Sierra Wireless is doing a lot (again, thank you!). Contributing code, answering newbies questions, etc.
Benjamin is the boss :), being M2M Industry Working Group Chairman, Mihini project co-lead, even Mihini Git repository owner (and Koneki co-lead also...).
(Even if a lot of other people actually commit code and answer questions, okay)
So it looks like Sierra Wireless fuels a lot of these activities (I also read that someone was "expelled" in July!).
Who decides how the project evolves, is managed, and how? How are the M2M Industry Working Group chair / project leads chosen, and for how long? 4) What's planned for the future?
There's a lot of stuff in Mihini already, but I guess that more is planned for the future (v0.9 only for now). Is it rather more features (libs), or more stabilization?
I noticed that after a surge in activity in 2013, it looks like nothing much has happened in the recent two months (mailing-list, commits, etc.).
So are you consolidating the code right now? Something planned for Luna (with 'n' :) ? Is there a Mihini roadmap to see where this is headed in terms of features? I know that this is a lot of questions, but I'm just trying to understand how this all works.
Again, this is all very exciting, and a great deal of work! So thank you so much for taking the time to read, and for your answers,
Diese E-Mail wurde aus dem Sicherheitsverbund E-Mail made in Germany versendet: http://www.gmx.net/e-mail-made-in-germany |
