Sorry for the late response.
If you want to contribute there are several ways to do it:
· General tips or documentation, you can do it directly in the Mihini wiki.
· Code sample that are actually ‘external’ to Mihini (like application that uses the Mihini framework). I would recommend to setup an external github and put your contribution there. You can then add a link to your github in the wiki pages
· Mihini actual fixes or improvements. In that case I recommend to do a “pull request like” over email (git patch mechanism). Longer term the ideal situation would be to make you a committer (or even project lead if you are more involved), so you can directly integrate changes in Mihini.
Let me know if you have other questions.
Thx,
Cuero
From: mihini-dev-bounces@xxxxxxxxxxx [mailto:mihini-dev-bounces@xxxxxxxxxxx] On Behalf Of Niranjan Babu (RBEI/EMT1)
Sent: Wednesday, February 04, 2015 7:36 AM
To: Mihini project developer discussions
Subject: Re: [mihini-dev] Interested to contribute to mihini
Hello,
I have been trying out mihini for an year or so, in this process I have developed many examples and prototype.
If I will have to contribute these to mihini, Which might be helpful for others to understand using mihini better
What is the procedure to do the same?
Regards,
NIranjan BAbu
Great! Most welcome!
Thijs
I am NIranjan Babu, working at BOSCH, India.
We are using mihini for our internal demonstrators and prototypes, In this process we have a lot of documentation, examples that we have created and we would like to contribute the same.
We would also like to start off with some bug fixes also. But there are some policies at my organization, and there is a process to be followed before we commit to OSS projects.
I have already triggered the process and will be able to start my activity on mihini project as soon as the process is complete.