2011/1/5 <[email protected]>: > Hi, > > sorry for cross-posting (targeted audience for the 1st part) > >> It makes sense, if we don't yet have this. I am willing to take one >> package off the important list if this is open to community >> participation. Question is, what's the process to make sure someone is >> able to maintain pkg X , e.g. how do we evaluate skills? (In the hope >> this can be open to non former Maemo or just current MeeGo >> contributors) > > We don't have: > - mentoring program [1][2] > - new maintainer process [3] or guide [4] > - IRC training session [5]
Or a way to sponsor uploads of package changes :) That is, someone with build.meego.com 'commit right' sending a submitreq for someone else's changes to Trunk:Testing OBS might make sponsor uploads easier, with osc copypac and such. Signed-off-by should be kept in mind here. /Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
