Confirm
74
edits
Changes
m
* helping us find the right person
* negociating with the Web site for fixing the Web site
(mostly some grammar and spelling polish..)
* reporting an issue
* analyzing the issue
* helping us find the right person to contact
* negotiating with the Web site to get it fixed
== Reporting a Web compatibility issue ==
If you experience a Web compatibility issue with your Web browsers with regards to a Web site. It's useful for us to know which steps you have followed to reach the issue. If, for example, one must log in to see the issue, there's a need to be logged in, it is important to say so.
== Finding The Right Contact on a Web site ==
For solving the issues, we often need to find the right person on the Web site. It is the hardest part of the work, but it's where you can really make a difference. Some Web sites are written in a language that '''you''' are mastering.Some Web sites are in country where we do not have much context on how to contact the right person. You can help. The open Web is the work of everyone.
There is more than one strategy for finding a person related to a Web compatibility issue. Here are a few:
* Is there an email address for Technical department?
* If the company has an organigram of their management, search for people who are CTO, Marketing, Communications related, then check online if you can find either on twitter or linkedin. Be careful. If the person is obviously using the account for only personal stuff, do not bother them.
* Has Does the company have a twitter account?* Has Does the company have a githubGithub, bitbucket Bitbucket or google Google code account?
* As a last resort, you may try through the Press relations address which is usually open.
* Call a phone number of the company, you might be bounced around.
* Never ever be aggressive with the persons you are trying to reach out. We want a better Web, not an angry Web ;).
* Never assume you are contacting the right person, except if you really know you do.
* Do not harass people with a lot of emails (even if they are nice with you). A good rule of thumb is to wait one week in between two contacts. Then a month for the third contact. If nothing has happened during the 5 weeks. Give , give up.
* Never share publicly the emails, names of people in the bug report if they have not decided to reveal themselves. Sometimes people will be willing to help fixing a Web site without necessary telling their management. Exposing them would make their work more difficult.
* Invite people to participate to the bugzilla themselves.
* If someone doesn't want to open a bugzilla account but is willing to share his/her comments in the bug report, help them to publish it (really but only if they agreed)
