I want to propose that we have a common CVS area for package source code.
Unless there is a more suitable place (perhaps associated with openwrt.ksilebo.net), then the existing (but unused) SourceForge CVS repository would be a good place for this. We could fairly openly give write access to OpenWRT developers (as opposed to users who would just have read-only access if they wanted to get package source code) by making them members of the OpenWRT SourceForge project. We could use the bug tracking mechanism there to track package bugs. We would still use the forums here for discussion about packages and package development.
The benefits of a common CVS area for package source code are:
1/ We comply with our GPL responsibilities for GPL'd packages without any extra effort. No-one can make the sort of accusations which have previously been levelled at Sveafost, Wifi-Box and even OpenWRT (all of which have now released source code, but the repercussions of the accusations still cause bitterness in the WRT54G third-party firmware community).
2/ We always know where the latest bleeding-edge version of every package lives, and we can help fix bugs in each other's packages.
3/ We can use CVS tags to define the latest "stable" set of packages, and perhaps even use that to automatically generate the public packages area on openwrt.ksilebo.net.
4/ We get to see each others code and hopefully converge on a common packaging environment (as opposed to the existing common openwrt buildroot environment which is currently used for building the initial firmware, not packages). It would be good if the buildroot environment and the packaging environment were one and the same tree.
5/ The main OpenWRT developers have access to a test suite of package source code which they can use (if desired) to check that changes to the basic OpenWRT code and modules don't have an adverse effect on packages.
What do you other developers think ?