I'm curious about how one would go about contacting/hiring a samba developer to fix a bug, or implement a feature. I've got a particular bug in mind (1493), but it seems like it would be a good thing to know in general. Thanks, Mark Roach
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Roach wrote: | I'm curious about how one would go about contacting/hiring a samba | developer to fix a bug, or implement a feature. I've got a particular | bug in mind (1493), but it seems like it would be a good thing to know | in general. | | Thanks, | | Mark Roach | If you're looking to contract someone to generally support/implement Samba, you might have a look at http://samba.org/samba/support/. If you're interested in contracting a Samba Team developer specifically, others could probably speak to that issue better than me. However, several team members do have their own companies or consulting services. A list of team members is available at http://samba.org/samba/team/. I would do some checking (google or the support list mentioned above) to see which team members are available for the sort of work you need, rather than just blindly contacting people. Cheers, - -- deryck - ---------------------------------------------------------------------- Deryck Hodge http://www.devurandom.org/ Cataloging Department http://www.lib.auburn.edu/ Web Editor, Samba Team http://www.samba.org/ GnuPG Key http://www.devurandom.org/gpg_pubkey.asc I am flawed but I am cleaning up so well. - --Dashboard Confessional, from "Vindicated"(2004) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBWWxy4glRK0DaE8gRAm5bAJ97B8nzQoxv8U6CLDncEsAUzIr3vACffNLW MXTauaKqWjG2pFzsKLywhK8=1OGk -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Roach wrote: | I'm curious about how one would go about | contacting/hiring a samba developer to fix a bug, or | implement a feature. I've got a particular bug in mind | (1493), but it seems like it would be a good thing to | know in general. This question has come up before so its probably a good one to discuss. If I understand you, you are really asking is: "What's the best way to get personalized attention to the bug report I just filed?" The core team members are stretched pretty thin on existing bugs, new releases, continued work, day jobs, etc... To me this would be a good chance for people in the community to step up get involved. I find that fixing specific bugs is a good way to become familiar with a new code base. New or potential developers can stop in on the #samba-technical IRC channel (irc.freenode.net) or email the samba-technical@samba.org ml to get some direction. But you have to be fairly self-motivated to work on Samba (and open community driven projects in general IMO). Once you have a patch, attach it to the bug report and add a comment that will catch our attention like "PROPOSED PATCH" or something. cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBbCcDIR7qMdg1EfYRAr56AKDEjptSAdY0bMsUpgLLTQQmTldSngCfeb2t Th7SqK36mjeMdmpbGVac/ws=aZmF -----END PGP SIGNATURE-----