Sorry Scott, but we're going to have to disagree on that point. Fundamentally ubuntu development is based around launchpad, and you have to get involved in that if you want to deal with bugs, upgrades and the like.
To then require people to learn an entirely different system for new packages is frankly a waste of community effort. With REVU out of action, this is the time to seize the moment and merge the new package system with the sync and update regimes already in place If the MOTU community is genuinely interested in encouraging new software into the universe (and from my own experience it doesn't feel like that at all), then you need to reduce the learning curve and harmonise the processes. Not increase it on ideological grounds. Now I'm sure that MOTUs don't believe that they are alienating developers. But your current processes will leave people with that feeling. What you have to remember is that developers are busy people too. I certainly don't have time to sit on IRC shouting forlornly into the ether until somebody deems it appropriate to answer just to get a package reviewed. Much more sensible that I subscribe the 'motu-reviewers' group to a [needs packaging] bug and come back later once I get an email telling me that something has happened. That way I can get something else done in the mean time. I would ask that you all consider the load that you place upon people want to contribute to Ubuntu. QA is a good thing, but when it becomes alienating then it is failing its purpose. NeilW -- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
