Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patches #5

Closed
bibi21000 opened this issue Aug 31, 2012 · 3 comments
Closed

Patches #5

bibi21000 opened this issue Aug 31, 2012 · 3 comments

Comments

@bibi21000
Copy link

Hi,
I've made some patches to build py-openzwave with the last release of openzwave.
Should I publish them here or fork this repository ?

@maartendamen
Copy link
Owner

Hi,

Please fork the repository and send a pull request. Thanks a lot for contributing!

Best regards,
Maarten

@bibi21000
Copy link
Author

I don't know how admin a git repository. As I am more familar with mercurial, I think I will use google code to fork.
Actually, changes are conséquent : remove openzwave directory, a small script to install and some documentation generation. There is also debian scripts to make a package. So, I don
There is no Licence information in py-openzave. So I suppose it's under GPL v3
Should I let your name in the authors or not ? Should I add a copyright ?
Should I put your email address ? What it is ?
And last question, should I use the same name or not ?
Best regards,
Sebastien (bibi)

@maartendamen
Copy link
Owner

Have you seen my no-fork branch? It doesn't contain the openzwave directory. I would prefer to keep all the changes to the project on one location (Github). I will mention your contribution in the readme. Please drop me a mail on m.damen AT gmail.com so we can work something out regarding the changes. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants