Replying to myself,
Below is a mail I sent to the Angstrom distribution list to seek some feedback on my thinking regarding oe-core/meta-oe/meta-angstrom etc. and how OpenPandora (or rather me in this context) can better work with upstream.
The feedback I got from that has been positive to working this way so I wanted to also gain some feedback from the OP guys who are not as close to OE/Angstrom. My plan is to follow this approach unless anyone has some major issues.
As I only got positive feedback on IRC and none on the mailing list I have gone ahead and started to do the split.
I have pushed the results of a quick carve-up to https://github.com/openpandora and I'll start to redo this as time goes on.
Anyone using the https://github.com/openpandora/openpandora-oe-environment setup scripts will need to
'rm build/conf/bblayer.conf' and 'git pull' the latest scripts before running './openpandora-setup.sh config' again.
Now this is done I welcome pull requests and patches ;).
I have also added a 'recipes-user' directory to meta-openpandora-vendor that will not be parsed by GIT for temp storage of recipes that are being worked on locally (an idea from aTc).
This should mean you can create in tree and move into the correct dir when you want to get it committed if you're mildly allergic to working in GIT full time ;).
Thanks,
John