[ARMedslack] Raspberry Pi support for Slackware ARM 14.1

[Stuart Winter]

> I can't help wondering if what we really need for all of these community
> supported platforms is one standard site (maybe a subdomain from
> slackwarearm), done like a wiki type site, where each community
> supported platform can have it's own section, and those who contribute
> can sign up to have editing/uploading permissions. I have webspace, and
> bandwidth I can donate to that, but I don't have the time to setup and
> run such a site.

This has occurred to me as well, but so far I've kept out of suggesting
any structure for the RPi support (initially to see how it'd pan out).
Perhaps a better approach would be to host the RPi page on
http://docs.slackware.com and link to the externally hosted downloads from
there.

The issue I see, going forwards, is that support is fragmented.  Somebody
finds that <x> doesn't work, so instead of suggesting/supplying a fix to
the author of the work they were using, they start their own version which
has additional issues.

Does anybody want to be the lead owner of a RPi page on docs.slackware.com
(assuming we can put it on there -- I have no input in to that site so
have not yet checked whether we can (although I can't imagine why not!)).
Ideally there'd be a single Rpi installer and/or image available that has
all of the fixes rolled up into it.  In the typical model for this
type of thing (given that it's a binary blob of an image/installer
image), the project owner essentially becomes the gate keeper so has to be
able to dedicate some time to folding requests and fixes back in to the
distributed images.

Thoughts? Any takers?

-- 
Stuart Winter
Slackware ARM: http://arm.slackware.com