Skip to content
This repository has been archived by the owner on Sep 27, 2020. It is now read-only.

Contribution workflow #75

Open
4383 opened this issue Sep 11, 2017 · 2 comments
Open

Contribution workflow #75

4383 opened this issue Sep 11, 2017 · 2 comments

Comments

@4383
Copy link

4383 commented Sep 11, 2017

Hello guys

I want to help you by contributing to this project, what's the right contribute work flow in use on this project?
I don't see a develop branch dedicated to merge pull request from contributors?
I suppose that the Dropzone_integration branch was dedicated for merge contributor works but this branch was behind the master over 21 commits... can you explain the semantic of this branch?

So I've decide to fork this project create a develop branch on my fork, add a little fix and send a pull request to you on the master branch.

I can help you to industrialize this part and we can introduce a standardized git flow for every contributors.
Do not hesitate to ask me a question for more informations.

@4383 4383 changed the title Contribute workflow Contribution workflow Sep 11, 2017
@sveetch
Copy link
Member

sveetch commented Sep 12, 2017

Hi 4383, i don't think there is a "worflow" yet. I dont really work anymore on this project, seems the recalbox team is keeping it alive on their own branch instead of master.

First thing to do should be to talk with the team on IRC irc.freenode.net/8001 channel : #recalbox or at least on forum: https://forum.recalbox.com/

@4383
Copy link
Author

4383 commented Sep 13, 2017

@sveetch Thanks for your response.
I'm going to try to talk with us on IRC.
Have a nice day!

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

No branches or pull requests

2 participants