My point is, participating in a community project is not communication. Letting other people know what your working on is not a marketing announcement, it's simply avoiding duplication of effort.
I have also come across developers in a big company who were reluctant, as you say, to be associated with a project, because they were worried that their inbox would be flooded with personal mail, and they knew this was just one project assignment & they fully expected to move on afterwards.
The best you can do in this case is allay their fears, but at the same time, help them understand that the best way to avoid private emails about their software is to ensure that the software is maintainable, and developed in the open, so that the bus factor for the code is >1.
Posted Dec 10, 2010 16:24 UTC (Fri) by coriordan (guest, #7544)
[Link]
Hey Dave,
For me, it wouldn't so much the annoyance of getting mail but the annoyance of having my work follow me around, along the lines of "It's none of their business what I do for a living".
When I leave the office at 6pm, my work should have no more relevance until the following morning. Same when I quit a company. I might choose to tell people where I work/worked, but it should be a choice, and I should be able to choose how much I tell people about my work. Having mailing list posts and maybe even cvs commits might be too detailed. Maybe waaay too detailed.
In my current an previous job I've chosen to disclose lots about what I do, but that's because it's also my hobby. I "live" my job, to an extent. I wouldn't expect co-workers to automatically also publicise this much about their nine-to-five life.
I agree that public discussion *shouldn't* be seen as an endorsement or an announcement or an official communication, but it often is. Fixing that from the recipient's end requires changing modern culture / human nature - a big ask :-) Fixing from the sender's end will be easier IMO, and maybe pseudonyms would mostly fix it.