The devel:ARM:Factory:Contrib:RaspberryPi3 repo is for the 64bit
variant which doesn't exist in raspberry foundation land.

Then, we might have a 2nd image which follow upstream and where we
might have some things missing such as WiFi.
If more versions are needed for testing/developing purpose, then we
should use staging projects.

Yes, hence my suggestion to remove the RPi3 contrib and just move it
all to Tumbleweed.

Yes, but the condition would be to not loose any functionality in the
switch.

The current RPi3 contrib can do exactly as much as 4.8 can, so we don't
lose anything :). If we started to enable wifi in the contrib now, we'd
lose something. That'd be bad.

Moreover, the current RPi3 Contrib is more a Leap 42.2 Contrib since
it uses the 42.2 kernel. Maybe we could just rename it?

42.2 should just natively support the RPi3, we don't need a contrib.

This is how is handled Raspberry Pi 1.

For RPi2, we have only a downstream image since JeOS-raspberrypi2
package is missing in Factory:ARM. I think we could add it. Dirk,
could you do it, please?

For the RPi2 we're in the same situation: A downstream 32bit kernel
with video decoding and an upstream 32bit kernel (that should work
fine with the Tumbleweed kernel) that does not have video decoding
capabilities.