How to contribute code to the MySensors project
-
@Heinz said:
2012-1014
Yep, typo, should be 2013-2015. :)
This is where the project started: http://forum.micasaverde.com/index.php/topic,16170.0.html
-
@Heinz said:
2012-1014
Yep, typo, should be 2013-2015. :)
This is where the project started: http://forum.micasaverde.com/index.php/topic,16170.0.html
-
@Heinz said:
2012-1014
Yep, typo, should be 2013-2015. :)
This is where the project started: http://forum.micasaverde.com/index.php/topic,16170.0.html
-
Can anyone explain what the clahub github permissions actually mean? I was going to sign the agreement (which I have no problem with), but it sounds like the app permissions give someone (clahub? mysensors?) access to several things in my github account: all the organizations I belong to, all of my commit texts, etc. My initial reaction is to think that's seems a bit crazy - why does anything need permissions to anything in order for me to accept my agreement to a license? I'm not trying to argue about the need for a CLA - I get that - just wondering what I'm really agreeing to with the clahub application.
-
From what I can tell the most sensitive information needed by CLAHUB (we're running their hosted variant) is your email address (which isn't revealed to the public):
https://github.com/clahub/clahub/blob/040629c91a25043605a0a1c4b100d0bde9c4d74f/config/initializers/omniauth.rb#L22-LundefinedAnyhow, seems like the developer is looking for a new maintainer of the project:
https://github.com/clahub/clahub/issues/111The best alternative I've found so far is https://github.com/cla-assistant/cla-assistant (Demo: https://cla-assistant.io/). Like clahub you can self-host it which is nice. Might spin it up to test one of these days...
Meanwhile you can just write "I agree to CLA" in the pull request comment.
To be clear, It is only contributions to the core MySensors library we're talking about here. Upgrading or adding external libraries and new examples is ok without it.
-
OK - thanks for the info. The permissions it actually asks me for are:
- user data (email read only)
- repository webhooks and services (admin access)
- organization webhooks (admin access)
- commit statuses (read/write access)
- organization and teams (read only)
Then it shows my other organizations. So it sounds like it can access those (not sure why it would need to), and read any of my commit status messages. I don't know what the webhooks are for but the admin access level made me a bit hesitant. The popup on an org that I belong to says that it can be accessed using the permissions above (which would include admin webhook access which sounds bad). Perhaps it's supposed to mean that it can only access those things for the mysensors repository which makes more sense but the description doesn't say that which is why I was curious about it.
-
@TD22057 said:
Perhaps it's supposed to mean that it can only access those things for the mysensors repository
I surely hope so. I haven't digged through the CLAHub code enough to give a good answer on your (valid) concerns. So I suggest you skip the CLAHub signing for now until we have a less invasive solution up and running.
-
We have now made the development-branch default on github. The master branch will only be used for releases.
This means that all PRs (pull requests) from now on should be forked from and directed to the development-branch.
@Anticimex has done a tremendous work setting up a new build server (Jenkins) that automatically will build all incoming PRs against a few different hardwares. This will help us to keep up the code quality and generate documentation automatically (soon).
Note: Your PR will fail if it generates warnings, so make sure to enable warnings in the Arduino IDE (settings) and fix them before submitting the PR to spare you some time.
Happy hacking
The MySensors team -
@hek
Hi Henrik, I sent a mail directly earlier today, you can ignore that one. I just read through this thread on how to add examples/code to the DEV branch.
But I still have a question. How do you keep a forked branch in sync with the main development branch?
I have now a clone of the developemnt branch on my Dropbox (I have GIT on my Mac). In the Arduino IDE I point to this Dopbox so that I always have the lastest changes in the Development branch locally after I sync in Github. This allows me to compile my sketches always against a copy of the latest version of the libs and code in the development branch.
But If I fork the DEV to my own branch, how do I keep alle "base" files in sync with the development branch. That is not clear to me from the documentation above. -
@hek
Hi Henrik, I sent a mail directly earlier today, you can ignore that one. I just read through this thread on how to add examples/code to the DEV branch.
But I still have a question. How do you keep a forked branch in sync with the main development branch?
I have now a clone of the developemnt branch on my Dropbox (I have GIT on my Mac). In the Arduino IDE I point to this Dopbox so that I always have the lastest changes in the Development branch locally after I sync in Github. This allows me to compile my sketches always against a copy of the latest version of the libs and code in the development branch.
But If I fork the DEV to my own branch, how do I keep alle "base" files in sync with the development branch. That is not clear to me from the documentation above. -
-
Hi all,
I wrote new release of DHT humidity sensor sketch and posted it in github 1 year ago.
It's running on my home for more than a year, its code pubblication is still pending.
Can anyone help me to get it published?https://github.com/mysensors/MySensorsArduinoExamples/pull/35
