@bacicciosat: If one forks our repo there is a an indication like "bacicciosat/e2-plugins forked from openpli/e2-plugins", will that already be an obstacle?
If the openpli label is inhibiting to others, the only solution is to create a new label. But if we create the label it will still be our label and treated the same by other teams, or not? What are your thoughts about this?
Sjaaky, i think we can use github only if we make the team labeled git and a central general git (without labels).
The central git is the git that can be used as source in enigma2-plugins.bb and need to have at least these 2 rules:
1) Plugins have to be open source under Gpl
2) Plugins have to be generic and compatible with cvs images (and all team images)
I see in your git at github that there are too plugins image dependens and a Pli folder.
I think this structure is not good to use OpenPli as the central repository because it is team dependent.
And it should be not nice for many teams or develop to work under Pli label if they want to be and appear independent.
So finally i see this structure:
-E2-OpenPlugins
|--OpenPli/E2-OpenPlugins
|-- BlackHole/E2-OpenPlugins
|-- Vti/E2-OpenPlugins
|-- Sif/E2-OpenPlugins
and so on...
I think this is better because in this way each team is not under another label and can pull in the central git only the cvs plugins and not the plugin image-dependent
It is ok for me if you will admin the central git (E2-OpenPlugins)