Bug#886599: RFH: broadcom-sta -- Broadcom STA Wireless driver (non-free)

[Eduard Bloch <edi@gmx.de>]

Hallo,
* Roger Shimizu [Mon, Jan 22 2018, 07:29:40PM]:
> Dear Eduard,
> 
> Thanks for your email!
> 
> On Wed, Jan 10, 2018 at 8:02 AM, Eduard Bloch <edi@gmx.de> wrote:
> > Hello everyone,
> >
> > thank you. I am not the biggest fan of collab-maint group, to be honest,
> > so I will setup a group project on salsa soon (ASAP, RTFM comes first).
> > Roger gets write access and Rowan and Yao with some notification
> > automation if you don't mind.
> 
> I didn't find any existing repo by the search:
> - https://salsa.debian.org/search?utf8=%E2%9C%93&snippets=&scope=&search=broadcom
> 
> If you don't mind, I can create a team for this, and import current
> git repo to salsa.
> The only question is, what'd the team name be like?
> - pkg-broadcom-sta-team
> - kernel network driver team
> - kernel non-free driver team
> - dkms driver team
> - any other option?

Hello Everyone,

I took the liberty to do this by myself.

I am sorry for the delay, I was short on spare time recently and my
private network link also became unusable. Anyhow, I prefered a simple
name since hardly anyone would maintain public source there. Therefore:

check https://salsa.debian.org/broadcom-sta-team/broadcom-sta/

So far I added Rosh as developer but could not find anyone else as user.
If you wish to use the services there, please register and/or request
permissions as needed. Check:
https://wiki.debian.org/Salsa/Doc#Users:_Login_and_Registration
https://salsa.debian.org/help/user/permissions

The rules of packaging are quite simple. So far we had:

 * amd64/i386 contain the particular stuff from Broadcom
 * local patches are applied on amd64 tree only, and this tree is used for both target archs, only the particular blobs are copied over from i386 folder at build time

Basic conventions:
 * patches pulled from other Distros (Arch, Gentoo) are marked prominently with the origin, at least, or include the full headers including Signed-Off stuff
 * git-buildpackage is the regular tool (see config files for it)
 * regular dpkg 3.0/quilt format is used (with the sophisticated name scheme, see current branches)
 * for backports, the usual rules shall be obeyed
 * the names of those foreign patches are adjusted to follow the existing rules, patches are rebased as needed

Proposal for the future:
 * let's track the progress in the issue tracker on salsa. Whoever wants to work on a topic, please assign the issue to yourself

I created https://salsa.debian.org/broadcom-sta-team/broadcom-sta/issues/1 - so, if rosh wants to work on it, please raise your hand in the next days.

Best regards,
Eduard.