Jim, how about giving them a @opensolaris.org email address? I know some people that treasure their @apache.org addy.
The other thing is that you want to remember to keep the rules to an absolute minimum. You want the Very Best hackers out there to work on the code. These people are traditionally staunch non-conformists and generally dislike doing anything they see as pointless. For example: if you had a rule that said: "no email address in the code" then the hacker will think: "They had to make a rule for that? Silly people." Instead, encourage very strong collaboration. For the non-coders, their name and email, and/or web address on the documents they work on. For example, if there is a web page on the sun website, have a contact. See http://www.w3.org/MarkUp/, at the bottom, in contact. The guy's name links to http://www.w3.org/People/mimasa/, a page which has his email, and which he quite obviously authored himself. Now, the w3 is not some fly-by-night group. Note the guy's email addy: "[EMAIL PROTECTED]" That's gotta have street cred. And the fact that his name appears on one of the principal pages for the HTML standard body for the Entire World has got to have some street cred too. Also, in communications, use their full name. It really helps down the road when connecting the dots. If you say Matt worked on this function, it's not quite as effective as saying "Matthew Yardley wrote a function, it was great, Thanks Matt!!!" It just seems a little bit more formal, a little bit more respectful, a bit less familiar, but I think in that sense formal is good too. Chris Mahan 818.943.1850 cell [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.christophermahan.com/ __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
