Closed calexity closed 9 years ago
@calexity
hehe. So there is not one perfect way. These are some of the things that I would do to find the appropriate contact. There are a few things though.
Web developer $COMPANY_NAME site:linkedin.com
. This will list names of people who are likely to work there, some of them in their profile will have contact information and often twitter accounts and/or personal Web sites. $COMPANY_NAME site:slideshare.net
or any appropriate keywords that will make you closer to a contact. Some companies have their developers going around at conferences speaking about issues with performances, etc. That said, be careful you might also find a lot of talks related to sales or marketing speeches, that will be a lot less interesting for contacting the right person. In the slides, there is often the contact information of the developer.firstname.lastname@company.example.org
or lastnameF@
etc. You can try to send an email. The person will be probably surprised on how did you get the email address. So there is a risk to anger the person. Be gentle, explain, don't request.@karlcow this is fantastic! Very, very helpful. I'd like to get a Volunteers page up soon and include these tips. It's ok that it is in progress. It's useful and will hopefully break down a few barriers to more bug diagnosers!
What do you think? We can add a note that it is in progress...
For sure, I love Work In Progress ;)
I have updated the bullet points, I'm pretty sure there will be more things coming. It would be good to ask @adamopenweb if he has more ideas/techniques for contacting people.
I wonder if @tagawa has more ideas too.
We had also talked about having UI to suggest company or individuals twitter handles based on the reported issue domain, so you can tweet them a link to the issue.
https://dev.twitter.com/docs/api/1.1/get/users/search seems useful.
https://developer.linkedin.com/documents/people-search-api seems like it might be difficult to use, unless we got their approval and added a "auth with linkedin" :nose: option (proxying api requests is specifically banned).
To add to the corporate email, I discovered today: http://www.email-format.com/d/mozilla.com/
Updating a couple of minutes later: I just tried with a well known French company. Attempt with the first pattern, mail server replied "NO", but second attempt with the second pattern, I received a positive answer and the contacts of the appropriate persons. \o/ Victory.
Nice find @karlcow!
Other things that have worked for me are looking in a website's terms and conditions or privacy policy for email addresses. They could be hidden in long blocks of text so a search for @
is helpful.
There may also be links in a website's footer to an investor or media relations page which could have a contact address, but be careful not to annoy the company by sending mails about bugs to addresses that are clearly not relevant (e.g. investors@example.com).
Additional hints
I added these notes into a Google doc so we have them compiled and ready for when the contributors page is done! cc @magsout @miketaylr @hallvors
https://docs.google.com/document/d/1JkHJcWZ0_uslNGMbjfRugI-qkJuMnIdhl_e2Bmzr2lU/edit
This is done!
Once a bug is diagnosed, how do i find the person to report this to?
We could automate this via Twitter or LinkedIn. I'm sure @karlcow has some tricks of the trade to add here.