>> Another thing we can do to avoid duplicated work, is to commit and push >> individual packages as soon as we have them. For instance, as soon as >> you have a working libextractor, go ahead and push it.
Sounds good. > That is what I do. But I am not fond of pushing packages for which I > would still like to add more inputs; it is possible to push > libextractor without lots of optional dependencies. This is what my > proposed patch for vorbis-tools does, there is a FIXME explaining > which inputs are missing. But then there is a higher risk of > forgetting to add them. I suggest to announce such things on the list. >> Or maybe we should use an Org file somewhere, or a wiki, or some sort of >> locally-hosted Web 2.0 task management thing. Can Savannah be used? > Anything would be fine for me as long as it is easy. Maybe a wiki > would be easiest for the time being. I guess that the easiest thing is to stick with this list. Nikita
pgpTKck22a9Yl.pgp
Description: PGP signature
