There's already been more than one "mirror" of both the tracker and forum. Yes, really.
When site is down, doesn't feel that way...
BTW -- to be clear, I currently do NOT have IPv6 access nor use a NaT'ed IP, so as things are now, I would not benefit and software being what it is, would likely experience more problems if it was done, only because it would be such a large change, so it's not for any specific feature that I'd suggest such.
You are assuming "open source" is always good and/or necessary.
No, I'm only assuming the current developers are saying that they are so overloaded that it's not likely in the near future. Is that not what jardin's comment indicated?
That is not the case; as I mentioned above, herding open-source cats can be more of a drain than it's worth. Remember, also, this site is not even remotely close to a democracy, nor was it ever presented as such. It's a free service that they run as they see fit, that simple, for good or ill.
Am more than a bit familiar with such projects and and your reference to herding cats. While any opensource depot might be more "open" than the current source, having an open-source depot doesn't mean the main-source has to track-it. It could be most useful for the current main to do occasional 'dumps' of sufficiently changed+working code to the open-source repo, but it isn't necessary that the current source take anything back unless they like a particular idea. I.e. the open source repo could be a test-bed of ideas -- *most of which* are not included.
However, if the test-bed produced __anything__ useful, that could
be included, that's where I'm thinking it might be useful -- with the full understanding that code-submissions to the open-repo would be "gratis-ideas" and anything more than that would be up to the existing master code site (developers).
Certainly, it could also benefit when bakabt does periodic calls for new "slaves" (er, I mean "help"), that they could have a resource to see who seems to know something about coding (if they've contributed to the testbed) and perhaps have an inkling of how well they might fit in if at all.
Furthermore, BakaBT just went through a large tracker update. Now is probably not the best time to agitate for changing the tracker, as they're busy ironing bugs =) .
You probably won't see anything happen along these lines, until many more clients and trackers support IPv6.
Which is exactly why I thought tossing the bundle over one-way wall as a means to provide a possiblity for extra-hands/eyes to look at the code and improve it, might be useful. OTH, if the current code-"owners" feel it would be likely to cause more trouble than good, then there's little anyone can do to convince them otherwize until they come to want to do so on their own -- that's acknowledged.
Indeed, I often have had code I'd be unwilling to share at a given point in time -- at least until I'm finished with a current block of work, and even then sometimes not depending on the code. But at other times I wouldn't mind throwing some pieces of code onto a hosting site if someone else found them useful and the code was sufficiently "non-ugly"... ;-)
So please don't take my suggesting a more open-site for code hosting meaning to be that's where active development takes place and may never take place depending on current code-owners' whims.
I just, occasionally try to see "in between" different points of view and think what might work for different parties. I'm not trying to convince anyone of a specific solution -- just, "explicitly" presenting options rather than assuming
all options have already been thoroughly thought through or vetted.