Hi Jens, Yes, I did notice the commit that mentions my name, and am glad for the attribution. What I was getting at, though, is that such attributions should be part of SQLite policy and should happen automatically and every time.
To your question, I don't particularly care if I have write privileges to the repo. In fact, I don't think it would be a good idea because (1) I'm a relative newbie to SQLite and could easily break things and (2) I'm not and will not be a regular contributor. I DO care about being acknowledged as the author of the patch, however. On the e-mail address question, I tend to think that they should be required as well. Any patch that is committed may cause integration problems down the line. SQLite has numerous extensions which can be baked into it, and it is impossible for any single contributor to perform regression testing on all these permutations. Ergo, it may be necessary to contact the author of the patch for them to try to rework it and/or explain how the patch's functionality is supposed to interoperate with the new feature/change which caused the breakage. SQLite is a relatively small project, so we can probably get away with not publishing e-mail addresses, since the 3 maintainers probably know who submitted what and can contact them if needed. For larger projects (e.g., GCC), having e-mail addresses of contributors known to everyone is absolutely essential. Thanks, --Zem _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
