> Is there any documentation or examples on-line describing preferred > form, method and criteria for offering contributions to the memcached > project? My group at work has a number of significant performance > improvements - some generic, some platform-specific #ifdef - we'd like > to offer. However, we'd like to do so in a way that minimizes thrash, > maximizes utility, assures upward compatibility and provides easily- > incorporated value.
Best way is to make those changes as small as possible, as well documented as possible, and have a lot of patience. We don't have a lot of resources for merging patches, so it could take a while. We could also end up matching your ideas with new ones that may work better more generically. So putting up a git repo somewhere and describing the patchset work well. >From there it's up to you, but sending something to the mailing list is a requirement. Also keep in mind that we're presently trying to reconcile the 1.6 tree, so it's difficult to tell where changes should go (1.4 or 1.6). -Dormando
