Just noticed this change on http://wiki.meego.com/Release_Engineering/New_Package_Checklist :
Step 1: agreed upon by copyright owner Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful. For package owned by Intel, please make sure it passes open source PDT. Nokia has similar process inside. While this is great, considering the latest 'scare' in Android about copying Oracle code, I have a suggestion to formalize it a bit, as we seem to be missing this in package process: Consider applying the signed-off-by method agreed by the TSG (quite some time ago) for package modifications/new packages? That is, http://meego.com/about/contribution-guidelines/signed-process . In practice, this would mean adding Signed-off-by: in submit requests description. Then we also have a trail of who originally submitted/who's to blame for uploading code they had no right to - and a official process that can we can show to lawyers that someone misrepresented their contribution to MeeGo. It would also open up for safe 'sponsored uploads', where someone with build.meego.com account helps someone without to submit a change towards Trunk:Testing. How does that sound? Best regards, Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
