On Thu, 03 Feb 2011 12:18:55 -0800 Arjan van de Ven <[email protected]> wrote:
> On 2/3/2011 11:54 AM, David Greaves wrote: > > On 03/02/11 10:14, Anas Nashif wrote: > >> Many packages will be moving around or even completely removed. > > > > Without knowing what they are; would it make sense to migrate any > > of these "completely removed" packages to the community OBS? Well, despite opinions to the contrary, I suppose no one can stop you from doing so ;) It is, after all, up to the community to decide, and one way to do that would be copy over those being removed from core OBS, and then give the community some time period during which people can sign up to become maintainers of these packages. After said time limit expires, those packages remaining for which no one is willing to step up to maintain, would then be formally removed. This would be how *I* would do it... but I am not the community, just a member there-of. > I doubt it... we'd only remove things that are no longer useful Arjan, what you and/or the MeeGo Core team determine as useful can't be assumed to be useless to the broader, as-yet-still-forming, community. Seems a rather presumptuous position to take IMHO As an example (and true story), lets say core OBS has no need for tftp... fair enough. Turns out, for me, at home, as "Joe Community" user of MeeGo, I did need it in order to flash a new dd-wrt image to my router. If it had been in community OBS, I would have used it. It was not, so I started it in my home project in a local build on my home MeeGo system. So, while tftp may not be an example of a project in core today, it is an example of one not "needed" by core OBS, yet it is most definitely "useful" (if not needed) by the "community". I think all David is asking for is the opportunity to be informed of the list of those to be removed, as they are determined, and given the chance to "copy" them over to the community OBS. I can't see how this is of any concern or issue to the Core OBS team, or why it's package contents policy must be imposed on the community OBS. > (and just keeping a package around is not really value, not for meego > obs not for community OBS; with things like autospectacle the > packaging part just doesn't matter as much anymore) Yet, if the package is already created, and the maintainers of the community OBS find it valuable, why *force* them to redo the work. Let them decide what's useful or not. Respectfully, Shane... _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
