Alexandru Ardelean - 2015-06-03

Hello,

My name is Alexandru Ardelean.
I work for a company specializing in building some interesting network solutions (and equipments). Ocedo is the company name if you care to check :)

Anyway, we're in the process of integrating mstpd into our firmware.
Our firmware is based on OpenWRT and we generally try to upstream (to OpenWRT) whatever we can.

I currently keep a Github fork of mstpd here: https://github.com/commodo/mstpd/tree/openwrt
The master branch is vanilla mstpd (just as is on SourceForge).

Let me make it clear that I do not wish to take any credit for mstpd (other than the changes I add).
The fork is there, because git is more preferable for me.
Should Vitalii wish to move mstpd to Github, I'd be very happy and fork from Vitalii's repo.
( that was a subtle version of the question: would it be a good idea to move mstpd to Github ? :) )

Having said that, I'd like to contribute some of the patches in my OpenWRT git branch.
Some make sense only for OpenWRT, some are general stuff.
I'd also like to converge some Cumulus Linux mstpd patches (those which make sense) into my OpenWRT git branch, and also mstpd upstream.
Looking quickly through Cumulus' patches, it looks like they base on an older version of mstpd, they force RSTP (instead of MSTP) and all-in-all they end up with a set of patches that may be super-seeded.

So, a few questions:
1) How would I go about contributing some of my patches ? Would, showing you my git commits be sufficient ?
2) Any idea of the amount of patches in Cumulus can be ignored (as they may be already in msptd's SVN) ?

I'd also like to make mstpd part of the official OpenWRT packages and put it under this folder tree:
https://github.com/openwrt/packages/tree/master/net
I will put my name there as maintainer, unless someone else wants to do it before me.
It could be that there is another parallel effort for mstpd on OpenWRT, of which I don't know anything yet.

Other stuff that I'd like to ask, I'll add to a later discussion.

Thanks
Alex