|
2 | 2 | <li class="contributors__list__item">
|
3 | 3 | <span>Find a bug that is labeled "Ready for Outreach"</span>
|
4 | 4 | <div class="contributors__list__screenshot">
|
5 |
| - <img src="../img/1readyforoutreach.jpg" alt"Ready for outreach snapshot"/> |
| 5 | + <img src="../img/1readyforoutreach.jpg" alt="Ready for outreach snapshot"/> |
6 | 6 | </div>
|
7 | 7 | </li>
|
8 | 8 | <li class="contributors__list__item"><span>Now it's time to track down someone to help get the fix implemented, but first a few tips on doing outreach:</span></li>
|
|
18 | 18 | <li class="contributors__list__item contributors__list__item--lvl_down">
|
19 | 19 | <span>Chrome bug reports: <a title="Chrome bug reports" href="https://crbug.com/new">http://crbug.com/new</a></span>
|
20 | 20 | <div class="contributors__list__screenshot">
|
21 |
| - <img src="../img/chromebugreport.jpg" alt"Chrome bug report snapshot"/> |
| 21 | + <img src="../img/chromebugreport.jpg" alt="Chrome bug report snapshot"/> |
22 | 22 | </div>
|
23 | 23 | </li>
|
24 | 24 | <li class="contributors__list__item contributors__list__item--lvl_down"><span>Firefox bug reports: <a title="Firefox bug reports" href="https://bugzilla.mozilla.org/enter_bug.cgi">https://bugzilla.mozilla.org/enter_bug.cgi</a></span></li>
|
|
32 | 32 | <li class="contributors__list__item contributors__list__item--lvl_down">
|
33 | 33 | <span><strong>Does the web site have a support email or an issue tracker?</strong> This is a simple one, but there's no guarantee that your request will be addressed. Most of the time the responses are automatic but it's better than nothing. If in return you get an ID and/or a URI, put it in the issue comments.</span>
|
34 | 34 | <div class="contributors__list__screenshot">
|
35 |
| - <img src="../img/2lastbullet_comment.jpg" alt"Comment snapshot"/> |
| 35 | + <img src="../img/2lastbullet_comment.jpg" alt="Comment snapshot"/> |
36 | 36 | </div>
|
37 | 37 | </li>
|
38 | 38 | <li class="contributors__list__item contributors__list__item--lvl_down">
|
|
47 | 47 | <li><strong>Slideshare.</strong>
|
48 | 48 | When you can't find the information about a developer, you might want to try to search something such as $COMPANY_NAME site:slideshare.net or any appropriate keywords that will make you closer to a contact. Some companies have their developers speaking at conferences about issues with performances, etc. Be careful of talks related to sales or marketing. In the slides, there is often the contact information of the developer.
|
49 | 49 | <div class="contributors__list__screenshot">
|
50 |
| - <img src="../img/slideshare.jpg" alt"Slideshare snapshot"/> |
| 50 | + <img src="../img/slideshare.jpg" alt="Slideshare snapshot"/> |
51 | 51 | </div>
|
52 | 52 | </li>
|
53 | 53 | <li><strong>Github, etc.</strong>
|
|
56 | 56 | <li><strong>Web designer.</strong>
|
57 | 57 | Sometimes when you can't reach a web developer, you may try to reach web designers who have also their own type of social networks such as dribbble.com. Usually they have contacts with web developers and may be able to give an introduction. In some web agencies, the web designer will be a good initial contact. Again, be tactful and don't make the life of the web designer harder in his/her own company.
|
58 | 58 | <div class="contributors__list__screenshot">
|
59 |
| - <img src="../img/webdesigner.jpg" alt"Webdesigner snapshot"/> |
| 59 | + <img src="../img/webdesigner.jpg" alt="Webdesigner snapshot"/> |
60 | 60 | </div>
|
61 | 61 | </li>
|
62 | 62 | <li><strong>Corporate emails.</strong>
|
|
0 commit comments