Hi Thomas,

> I've started using your great xpcc-library 3 years ago, studied it and
> learned a lot, exclusively about templates und just great, comfortable
> code. Until my Hardware experiments, i've written several drivers (for
> avr).

That’s great to hear!

> Some of them are finished and unit-tested, some of them are in progress.
> Of course, I've mentioned your code convention and design rules.
> Now it's time for me to colaborate my very first software-project :), so
> i've studied git.
> As i understand, i would open a Branch, push my code, and hopefully one
> day, everyone is happy and it get's merged. Right?

I saw that you already forked xpcc over to your Github account, which is 
exactly the right thing to do.
Essentially you test your contributions inside your own fork of xpcc, and then 
create a pull-request, which we can then merge back.

This is the preferred and supported way by Github and us:

We are preparing a huge release from our development branch within the next 
couple of months.
However, this release is not backwards compatible at all, but is essentially a 
complete rewrite of most of xpcc, the culmination of ~1.5 years of work.
The most drastic changes are in the way we generate architecture drivers (for 
e.g. SPI, UART, ADC, etc…) and an extensive use of cooperative multitasking.

We would really appreciate it if you could merge your contributions into this 
new develop branch.
If you are uncertain how to do that, just merge it into the master branch of 
your fork, and I will take a look at it.

There is also a website for the development branch of xpcc:
Incl. updated documentation (which is still missing platform documentation, I’m 
working on it):

The old documentation for the master branch is still available here:

xpcc-dev mailing list

Reply via email to