-- [ Picked text/plain from multipart/alternative ] I think this is a neat idea. But your talking about open source collaboration on a closed-source product.
You couldn't make the source publicly available. But they've shown that they don't mind public collaboration on changes to it. So you could make your changes (only) publicly available. This makes things slightly tricky. You can't distribute the sources publicly so distribute public patches instead using a strict diff format. A strict diff format might be something that indicates change points using exact line numbers or byte numbers, instead of example lines from the unmodified source. Also doesn't include the file content when copying or renaming files, just the file names. This way its not necessary for the patch to contain any content from the previous version, only new content. Automate creating the patch once a day, and you've got your distribution method. You just need a few trusted commiters to take patches since your repository can't be public. I'd love to see all those snippets all over the forums and wikis merged into one version. If done well, I'm sure you'd get a few regular commiters. Jason Stillwell -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
