2010/1/8 James Westby <jw+deb...@jameswestby.net>: > On Fri, 8 Jan 2010 10:58:04 +1100, Martin Pool <m...@canonical.com> wrote: >> Here are some specific things people can do to help with hottest100: >> >> * work out how to make package-product links (explain that here :-) >> and create them when they're missing > > Just a note that > > https://edge.launchpad.net/ubuntu/+upstreamreport > > has live data to help with this. > > "Missing corresponding project" means that a package-product link needs > to be created (and sometimes a product too). The lack of a Bazaar icon > means there is no default branch. > > Note that I went over this list a few weeks back registered a bunch of > imports, and created the LP question to have them set as the development > focus. That's still not done, and that's why I keep bringing it up, > because you will often be duplicating effort if you look in to them.
Thanks for pointing that out. Other things on my list may be redundant with other posts too, so my list was more of threads for people to pull on. > This says nothing about how up-to-date all that information is though. A > (preferably semi-automatic) check that everything is up-to-date would be > good. > > This does raise other questions in my mind. Are we excluding some > packages before we really start? I don't know. I guess we only would be if the top 100 list was not actually the 100 most important packages. I'm not actually sure where that list comes from. Ultimately there are more than 100 packages that matter, and starting with 100 fairly important packages is reasonable. We can go on to more later. > Is implementing bzr-monotone going to > be something that falls under the hottest100 project? If some of them are in mt that will be useful data. I doubt it will be so many of them that it represents a good cost/benefit tradeoff, though it might be worth doing a fastimport from mt. I think it's reasonable for us to conclude this project with some number of packages essentially classed 'wontfix (for now)', if they would require a lot of work that would not help many packages. But there should be few like that, and it should be a specific justified decision. > There are also a > few cases where we have two packages for one upstream repo, and some > where there isn't really an upstream (aside from things like > update-manager, linux-restricted-modules for instance). What will be > done about the KDE packages, their upstream is one mega-repo. I don't know yet. I'd like to start by getting those packages marked with a bug number that describes the situation. The larger point of hottest100 is to allow daily builds of those packages. If there is no upstream I don't know if the question even means anything. If there is an upstream but it's quirky again perhaps it's reasonable to say we just don't support it yet. -- Martin <http://launchpad.net/~mbp/> -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
