So cool to see the collaboration happening here. Free Software and all its freedom on full display. Absolutely fantastic.
G3N-es, you mention you're getting familiar with git so figured I'd mention it might make more sense for you to maintain your own forked repo rather than simply work from a branch. I say that because you may find yourself wanting to work on one or more feature branches simultaneously as opposed to working from a single branch. In my experience, the easiest way to facilitate that clean separation it to work from a fork where you'd submit pull requests back upstream as each feature branch is developed. Of course, you'd also want to keep your fork's master branch up to date as well as upstream would be expected to change. There's plenty of information out there that goes into greater detail on this pretty standard work flow.
So cool to see the collaboration happening here. Free Software and all its freedom on full display. Absolutely fantastic.
G3N-es, you mention you're getting familiar with git so figured I'd mention it might make more sense for you to maintain your own forked repo rather than simply work from a branch. I say that because you may find yourself wanting to work on one or more feature branches simultaneously as opposed to working from a single branch. In my experience, the easiest way to facilitate that clean separation it to work from a fork where you'd submit pull requests back upstream as each feature branch is developed. Of course, you'd also want to keep your fork's master branch up to date as well as upstream would be expected to change. There's plenty of information out there that goes into greater detail on this pretty standard work flow.