https://wiki.mozilla.org/api.php?action=feedcontributions&user=Mnyromyr&feedformat=atom
MozillaWiki - User contributions [en]
2024-03-28T19:46:23Z
User contributions
MediaWiki 1.27.4
https://wiki.mozilla.org/index.php?title=German_contributors&diff=1001487
German contributors
2014-07-30T19:49:25Z
<p>Mnyromyr: Redirected page to Contributors/Germany Austria Switzerland</p>
<hr />
<div>#REDIRECT [[Contributors/Germany_Austria_Switzerland]]</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Summit2013/Experiences/signups&diff=714967
Summit2013/Experiences/signups
2013-09-24T20:30:09Z
<p>Mnyromyr: /* Bar Delirium */</p>
<hr />
<div>Please sign up below.<br />
<br />
'''UPDATE:''' There are many folks who are also asking if they can add sessions to this. The answer is yes! And, there will also be white boards and post its in the main area of each venue for you to propose/add organic social sessions there as well. <br />
<br />
=Santa Clara=<br />
==Friday ==<br />
=== Photo Walk ===<br />
<br />
If you are interested in an early morning [6:30am] tour in the beautiful Silicon Valley, you are in luck! [https://mozillians.org/en-US/u/Ludovic Ludovic Hirlimann] and [https://mozillians.org/en-US/u/rolandtanglao Roland Tanglao]<br />
<br />
More information here: http://sietch-tabr.tumblr.com/post/60429342277/extra-summit-activity-part-1-santa-clara-photowalks<br />
<br />
Sign Up Here: <br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Bill Walker</td></tr><br />
<tr><td>Viking KARWUR</td></tr><br />
<tr><td>Shahmir Khan</td></tr><br />
<tr><td>Muhammad Mehmood Ali</td></tr><br />
<tr><td>Asad Sajjad</td></tr><br />
<tr><td>Shazia Rizwan</td></tr><br />
<tr><td>Nagasahas DS </td></tr><br />
<tr><td>Abdul Rauf</td></tr><br />
<tr><td>Jemmy RORONG</td></tr><br />
<tr><td>Finan AKBAR</td></tr><br />
<tr><td>Dimas ANDHANA</td></tr><br />
<tr><td>Fauzan ALFI</td></tr><br />
<tr><td>Artanto ISHAAM</td></tr><br />
<tr><td>Kalpa Welivitigoda</td><tr><br />
<tr><td>Ashkary Rahman</td></tr><br />
<tr><td>Irayani Queencyputri</td></tr><br />
<tr><td>Eriska Triana Primayasari</td></tr><br />
<tr><td>Deryan Everestha Maured</td></tr><br />
<tr><td>Nuri Abidin</td></tr><br />
<tr><td>Rahmat Dwi Jatmiko</td></tr><br />
<tr><td>Andi Darmawan</td></tr><br />
<tr><td>I Gede Bagus Kosha</td></tr><br />
<tr><td>Sayak Sarkar</td></tr><br />
<tr><td>Priyanka Nag</td></tr><br />
<tr><td>Soumya Deb</td></tr><br />
<tr><td>Swarnava Sengupta</td></tr><br />
<tr><td>Avik Pal</td></tr><br />
<tr><td>Gaurab Patra</td></tr><br />
<tr><td>Diwanshi Pandey</td></tr><br />
<tr><td>Subhashish Kundu</td></tr><br />
<tr><td>Shafiul Azam Chowdhury</td></tr><br />
<tr><td>Rahid Hasan</td></tr><br />
<tr><td>Hilary Ho Jia Hao</td></tr><br />
<tr><td>Gauthamraj Elango</td></tr><br />
<tr><td>Jayakumar Sadhasivam</td></tr><br />
<tr><td>Md Aminul Islam Sajib</td></tr><br />
<tr><td>Md Golam Mostafa</td></tr><br />
<tr><td>[[user:maktrix|Mahay Alam Khan]]</td></tr><br />
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr><br />
<tr><td>Zobayer Ahmed Khan</td></tr><br />
<tr><td>Benny Chandra</td></tr><br />
<tr><td>Yoe One Ariestya Niovitta</td></tr><br />
<tr><td>Rizqinofa Putra M</td></tr><br />
<tr><td>Gasper Derzanic</td></tr><br />
<tr><td>Atul Jangra</td></tr><br />
<tr><td>Akshay Aurora</td></tr><br />
<tr><td>Aji Kisworo Mukti</td></tr><br />
<tr><td>[[user:ahsan.net|Mashkawat Ahsan]]</td></tr><br />
<tr><td>Matjaž Horvat</td></tr><br />
<tr><td>[[user:rok.samsa|Rok Samsa]]</td></tr><br />
<tr><td>[[user:mythrobin|Robin Mehdee]]</td></tr><br />
<tr><td>Rohan Dasanayaka</td></tr><br />
<tr><td>Anup Kumar Mishra</td></tr><br />
<tr><td>Ankit Gadgil</td></tr><br />
<tr><td>Ajay Kumar</td></tr><br />
<tr><td>Ankit Kumar Mishra</td></tr><br />
<tr><td>Parmpreet Singh</td></tr><br />
<tr><td>Gary Chen</td></tr><br />
<tr><td>Clarice Wang</td></tr><br />
<tr><td>Dominic Kuo</td></tr><br />
<tr><td>Steve Chung</td></tr><br />
<tr><td>Kate Huang</td></tr><br />
<tr><td>Linear Li</td></tr><br />
<tr><td>Goran Kohek</td></tr><br />
<tr><td>Soumya Kanti Chakraborty</td></tr><br />
<tr><td>Jon Buckley</td></tr><br />
<tr><td>Rizky Ariestiyansyah</td></tr><br />
<tr><td>Ani Peter</td></tr><br />
<tr><td>Alex Lakatos</td></tr><br />
<tr><td>Sammy Fung</td></tr><br />
<tr><td>Kengatharaiyer Sarveswaran (Sarves)</td></tr><br />
<tr><td>Jim Chen (:jchen)</td></tr><br />
<tr><td>Muhammad Syafiq Mazli (:syafiqmazli)</td></tr><br />
<tr><td>Mohamed Aidid Jaafar (:aidid)</td></tr><br />
<tr><td>Haryati Salehin (:yadyadun)</td></tr><br />
<tr><td>Lai Chen Haw (:chenhaw)</td></tr><br />
<tr><td>Rishabh Narayan</td></tr><br />
<tr><td>Manoj Kumar Giri</td></tr><br />
<tr><td>Shankar Prasad (:shanky)</td></tr><br />
<tr><td>Krishnababu K (:Krishna)</td></tr><br />
<tr><td>Grigorios Petsos</td></tr><br />
<tr><td>Benjamin Pokharel</td></tr><br />
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr><br />
<tr><td>Luigi Tedone</td></tr><br />
</table><br />
<br />
==Saturday==<br />
=== Movie Night ===<br />
<br />
On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla. <br />
<br />
We may be showing another movie after this, if there is enough interest. <br />
<br />
We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Pascal Finette</td></tr><br />
<tr><td>Jon Hylands</td></tr><br />
<tr><td>Rob Hudson</td></tr><br />
<tr><td>Viking KARWUR</td></tr><br />
<tr><td>Shahmir Khan</td></tr><br />
<tr><td>Muhammad Mehmood Ali</td></tr><br />
<tr><td>Asad Sajjad</td></tr><br />
<tr><td>Shazia Rizwan</td></tr><br />
<tr><td>Alex Vincent</td></tr><br />
<tr><td>Gautam A</td></tr><br />
<tr><td>Nagasahas DS</td></tr><br />
<tr><td>Jemmy RORONG</td></tr><br />
<tr><td>Finan AKBAR</td></tr><br />
<tr><td>Dimas ANDHANA</td></tr><br />
<tr><td>Artanto ISHAAM</td></tr><br />
<tr><td>Fauzan ALFI</td></tr><br />
<tr><td>Kalpa Welivitigoda</td></tr><br />
<tr><td>Ashkary Rahman</td></tr><br />
<tr><td>Irayani Queencyputri</td></tr><br />
<tr><td>Eriska Triana Primayasari</td></tr><br />
<tr><td>Deryan Everestha Maured</td></tr><br />
<tr><td>Nuri Abidin</td></tr><br />
<tr><td>Rahmat Dwi Jatmiko</td></tr><br />
<tr><td>Andi Darmawan</td></tr><br />
<tr><td>I Gede Bagus Kosha</td></tr><br />
<tr><td>Sayak Sarkar</td></tr><br />
<tr><td>Priyanka Nag</td></tr><br />
<tr><td>Soumya Deb</td></tr><br />
<tr><td>Swarnava Sengupta</td></tr><br />
<tr><td>Ankit Gadgil</td></tr><br />
<tr><td>Diwanshi Pandey</td></tr><br />
<tr><td>Avik Pal</td></tr><br />
<tr><td>Gaurab Patra</td></tr><br />
<tr><td>Subhashish Kundu</td></tr><br />
<tr><td>Hilary Ho Jia Hao</td></tr><br />
<tr><td>Gauthamraj Elango</td></tr><br />
<tr><td>[[user:maktrix|Mahay Alam Khan]]</td></tr><br />
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr><br />
<tr><td>Zobayer Ahmed Khan</td></tr><br />
<tr><td>Benny Chandra</td></tr><br />
<tr><td>Yoe One Ariestya Niovitta</td></tr><br />
<tr><td>Rizqinofa Putra M</td></tr><br />
<tr><td>Jayakumar Sadhasivam</td></tr><br />
<tr><td>Atul Jangra</td></tr><br />
<tr><td>Akshay Aurora</td></tr><br />
<tr><td>Aji Kisworo Mukti</td></tr><br />
<tr><td>Matjaž Horvat</td></tr><br />
<tr><td>[[user:mythrobin|Robin Mehdee]]</td></tr><br />
<tr><td>Rohan Dasanayaka</td></tr><br />
<tr><td>Ajay Kumar</td></tr><br />
<tr><td>Ankit Mishra</td></tr><br />
<tr><td>Parmpreet Singh</td></tr><br />
<tr><td>Anup Kumar Mishra</td></tr><br />
<tr><td>Goran Kohek</td></tr><br />
<tr><td>Soumya Kanti Chakraborty</td></tr><br />
<tr><td>Jon Buckley</td></tr><br />
<tr><td>Tim Taubert</td></tr><br />
<tr><td>Rizky Ariestiyansyah</td></tr><br />
<tr><td>Ani Peter</td></tr><br />
<tr><td>Sammy Fung</td></tr><br />
<tr><td>Jim Chen (:jchen)</td></tr><br />
<tr><td>Muhammad Syafiq Mazli (:syafiqmazli)</td></tr><br />
<tr><td>Mohamed Aidid Jaafar (:aidid)</td></tr><br />
<tr><td>Haryati Salehin (:yadyadun)</td></tr><br />
<tr><td>Lai Chen Haw (:chenhaw)</td></tr><br />
<tr><td>Rishabh Narayan </td></tr><br />
<tr><td>Manoj Kumar Giri </td></tr><br />
<tr><td>Shankar Prasad (:shanky)</td></tr><br />
<tr><td>Krishnababu K (:Krishna)</td></tr><br />
<tr><td>Grigorios Petsos</td></tr><br />
<tr><td>Benjamin Pokharel</td></tr><br />
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr><br />
<tr><td>Luigi Tedone</td></tr><br />
</table><br />
<br />
=== Mozillians Pilates ===<br />
<br />
Not just any Pilates - Pilates instructed by [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] who is a certified Pilates trainer!(little known fact he also trains two Olympic B-Cadre Team USA marathoners)<br />
<br />
He's offered to lead a wake you up Pilates session for 15-20 people on Friday. If more would like to join, he will host it again on Saturday. <br />
<br />
If you are local, please bring a yoga mat or bath towel with you. We will provide a limited number of mats for those who need them. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Jennifer Bertsch </td></tr><br />
<tr><td>Iacopo Benesperi</td></tr><br />
<tr><td>Gautam A</td></tr><br />
<tr><td>Nagasahas DS</td></tr><br />
<tr><td>[[user:maktrix|Mahay Alam Khan]]</td></tr><br />
<tr><td>Aashish Jagini</td></tr><br />
<tr><td>Kathryn Meisner</td></tr><br />
<tr><td>Ani Peter</td></tr><br />
<tr><td>Jayakumar Sadhasivam</td></tr><br />
<tr><td>Mardi Douglass</td></tr><br />
<tr><td>Kate Naszradi</td></tr><br />
<tr><td>Manoj Kumar Giri</td></tr><br />
<tr><td>Shankar Prasad (:shanky)</td></tr><br />
<tr><td>Krishnababu K (:Krishna)</td></tr><br />
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr><br />
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr><br />
<tr><td>Luigi Tedone</td></tr><br />
</table><br />
<br />
=== Great America ===<br />
<br />
Are you up for a night of shows, fast rides, daring drops and good old fashioned American fair food? Did I mention they have a Halloween themed side of the park as well? If you'd like to join in the experience, come join your fellow Mozillians at Great America! <br />
<br />
There are plenty (200+) tickets available, but you must sign up by 10/1 to receive an admission ticket. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Pascal Finette</td></tr><br />
<tr><td>2 Jennifer Bertsch</td></tr><br />
<tr><td>3 Rob Hudson</td></tr><br />
<tr><td>4 Viking KARWUR</td></tr><br />
<tr><td>5 Iacopo Benesperi</td></tr><br />
<tr><td>6 Michelle Cristobal</td></tr><br />
<tr><td>7 Shahmir Khan</td></tr><br />
<tr><td>8 Asad Sajjad</td></tr><br />
<tr><td>9 Muhammad Mehmood Ali</td></tr><br />
<tr><td>10 Gautam A</td></tr><br />
<tr><td>11 Nagasahas DS</td></tr><br />
<tr><td>12 Abdul Rauf</td></tr><br />
<tr><td>13 Jemmy RORONG</td></tr><br />
<tr><td>14 Finan AKBAR</td></tr><br />
<tr><td>15 Dimas ANDHANA</td></tr><br />
<tr><td>16 Artanto ISHAAM</td></tr><br />
<tr><td>17 Fauzan ALFI</td></tr><br />
<tr><td>18 Ashkary Rahman</td></tr><br />
<tr><td>19 Irayani Queencyputri</td></tr><br />
<tr><td>20 Eriska Triana Primayasari</td></tr><br />
<tr><td>21 Deryan Everestha Maured</td></tr><br />
<tr><td>22 Nuri Abidin</td></tr><br />
<tr><td>23 Rahmat Dwi Jatmiko</td></tr><br />
<tr><td>24 Andi Darmawan</td></tr><br />
<tr><td>25 I Gede Bagus Kosha</td></tr><br />
<tr><td>26 Shazia Rizwan</td></tr><br />
<tr><td>27 Shafiul Azam Chowdhury</td></tr><br />
<tr><td>28 Rahid Hasan</td></tr><br />
<tr><td>29 Sayak Sarkar</td></tr><br />
<tr><td>30 Priyanka Nag</td></tr><br />
<tr><td>31 Soumya Deb</td></tr><br />
<tr><td>32 Swarnava Sengupta</td></tr><br />
<tr><td>33 Avik Pal</td></tr><br />
<tr><td>34 Gaurab Patra</td></tr><br />
<tr><td>35 Subhashish Kundu</td></tr><br />
<tr><td>36 Kaustav Das Modak </td></tr><br />
<tr><td>37 Galaxy Kadiyala</td></tr><br />
<tr><td>38 Vineel Reddy Pindi</td></tr><br />
<tr><td>39 Gauthamraj Elango</td></tr><br />
<tr><td>40 Faizal Aziz</td></tr><br />
<tr><td>41 Sara Khan</td></tr><br />
<tr><td>42 Hilary Ho Jia Hao</td></tr><br />
<tr><td>43 Md Aminul Islam Sajib</td></tr><br />
<tr><td>44 [[user:maktrix|Mahay Alam Khan]]</td></tr><br />
<tr><td>45 Zobayer Ahmed Khan</td></tr><br />
<tr><td>46 Abdur Rahman </td></tr><br />
<tr><td>47 Benny Chandra</td></tr><br />
<tr><td>48 Yoe One Ariestya Niovitta</td></tr><br />
<tr><td>49 [[user:ahsan.net|Mashkawat Ahsan]]</td></tr><br />
<tr><td>50 Jayakumar Sadhasivam</td></tr><br />
<tr><td>51 Rizqinofa Putra M</td></tr><br />
<tr><td>52 Gasper Derzanic</td></tr><br />
<tr><td>53 Atul Jangra</td></tr><br />
<tr><td>54 Aji Kisworo Mukti</td></tr><br />
<tr><td>55 Matjaž Horvat</td></tr><br />
<tr><td>56 [[user:rok.samsa|Rok Samsa]]</td></tr><br />
<tr><td>57 [[user:mythrobin|Robin Mehdee]]</td></tr><br />
<tr><td>58 Rohan Dasanayaka </td></tr><br />
<tr><td>59 Anup Kumar Mishra </td></tr><br />
<tr><td>60 Ankit Mishra </td></tr><br />
<tr><td>61 Parmpreet Singh </td></tr><br />
<tr><td>62 Ajay Kumar </td></tr><br />
<tr><td>63 Clarice Wang </td></tr><br />
<tr><td>64 Goran Kohek </td></tr><br />
<tr><td>65 Soumya Kanti Chakraborty</td></tr><br />
<tr><td>66 Jon Buckley</td></tr><br />
<tr><td>67 [[user:alefteris|Thanos Lefteris]]</td></tr><br />
<tr><td>68 Akshay Aurora</td></tr><br />
<tr><td>69 Rizky Ariestiyansyah</td></tr><br />
<tr><td>70 Ani Peter</td></tr><br />
<tr><td>71 Angela Leung</td></tr><br />
<tr><td>72 Alex Lakatos</td></tr><br />
<tr><td>73 Marcela Oniga</td></tr><br />
<tr><td>74 Nikki Tran</td></tr><br />
<tr><td>75 Kengatharaiyer Sarveswaran (Sarves) </td></tr><br />
<tr><td>76 Ankit Gadgil</td></tr><br />
<tr><td>77 Diwanshi Pandey</td></tr><br />
<tr><td>78 Jake Watkins</td></tr><br />
<tr><td>79 Jim Chen (:jchen)</td></tr><br />
<tr><td>80 Md Golam Mostafa</td></tr><br />
<tr><td>81 Muhammad Syafiq Mazli (:syafiqmazli)</td></tr><br />
<tr><td>82 Mohamed Aidid Jaafar (:aidid)</td></tr><br />
<tr><td>83 Haryati Salehin (:yadyadun)</td></tr><br />
<tr><td>84 Lai Chen Haw (:chenhaw)</td></tr><br />
<tr><td>85 Rishabh Narayan</td></tr><br />
<tr><td>86 Louis-Rémi Babé</td></tr><br />
<tr><td>87 James Kitchener</td></tr><br />
<tr><td>88 Manoj Kumar Giri</td></tr><br />
<tr><td>89 Shankar Prasad (:shanky)</td></tr><br />
<tr><td>90 Krishnababu K (:Krishna)</td></tr><br />
<tr><td>91 Grigorios Petsos</td></tr><br />
<tr><td>92 Benjamin Pokharel</td></tr><br />
<tr><td>93 [[user:Rifaz|Rifaz Nahiyan]]</td></tr><br />
<tr><td>94 [[user:Ashickurnoor|Ashickur Rahman]]</td></tr><br />
<tr><td>95 Sofanit Belay (Sofi)</td></tr><br />
<tr><td>96 Luigi Tedone</td></tr><br />
</table><br />
<br />
==Sunday==<br />
=== Mozillians Pilates ===<br />
<br />
Not just any Pilates - Pilates instructed by [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] who is a certified Pilates trainer!(little known fact he also trains two Olympic B-Cadre Team USA marathoners)<br />
<br />
He's offered to lead a wake you up Pilates session for 15-20 people. He is also offering a class on Saturday, if you haven't yet signed up there. :-) <br />
<br />
If you are local, please bring a yoga mat or bath towel with you. We will provide a limited number of mats for those who need them. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Kalpa Welivitigoda</td></tr><br />
<tr><td>Ani Peter</td></tr><br />
<tr><td>Mardi Douglass</td></tr><br />
<tr><td>Kate Naszradi</td></tr><br />
<tr><td>Krishnababu K</td></tr><br />
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr><br />
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr><br />
</table><br />
<br />
=Toronto=<br />
==Friday ==<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Vuyisile Ndlovu </td></tr><br />
<tr><td>Jose Junior Villagomez Melgar </td></tr><br />
<tr><td>[https://mozillians.org/en-US/u/prixon/ Matej Priteržnik]</td></tr><br />
<tr><td>Peter Radcliffe</td></tr><br />
<tr><td> </td></tr><br />
</table><br />
<br />
==Saturday==<br />
=== Movie Night ===<br />
<br />
On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla. <br />
<br />
We may be showing another movie after this, if there is enough interest. <br />
<br />
We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Gloria Meneses</td></tr><br />
<tr><td>Lianne Lee</td></tr><br />
<tr><td>Huda Sarfraz</td></tr><br />
<tr><td>Etienne Segonzac</td></tr><br />
<tr><td>Vuyisile Ndlovu </td></tr><br />
<tr><td>Peter Radcliffe</td></tr><br />
<tr><td>Amira Dhalla</td></tr><br />
<tr><td>Elsa Rodriguez</td></tr><br />
<tr><td>Sam Foster</td></tr><br />
<tr><td> </td></tr><br />
</table><br />
<br />
=== CN Tower Tour ===<br />
<br />
First time to Toronto? Fourth or Fifth time and you've never gotten to see the whole city? The CN Tower is ''the best'' way to catch a glimpse of the whole city. From the lookout level, the glass floor and all the way up to 447 metre (1465 ft.) via the skypod. It's a must visit if you haven't been. <br />
<br />
You will have to sign up by 10/1 in order to secure your spot. We have room for up to 50 people '''Full'''. <br />
<br />
For more information, check out this [http://www.cntower.ca/en-ca/plan-your-visit/attractions/skypod.html link]<br />
<br />
Sign up here: <br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1.Jane Smith</td></tr><br />
<tr><td>2.Adam Roach</td></tr><br />
<tr><td>3.Sabrina Ng</td></tr><br />
<tr><td>4.Mario Garcia</td></tr><br />
<tr><td>5.Patrick Dang</td></tr><br />
<tr><td>6.Luciana Viana</td></tr><br />
<tr><td>7.Andrea Guzman Siu</td></tr><br />
<tr><td>8.Reuben Morais</td></tr><br />
<tr><td>9.Marcelo Poli</td></tr><br />
<tr><td>10.Will Bamberg</td></tr><br />
<tr><td>11.Gabriela Montagu</td></tr><br />
<tr><td>12.Santiago Hollmann</td></tr><br />
<tr><td>13.Pablo Terradillos </td></tr><br />
<tr><td>14.Sandra Guevara </td></tr><br />
<tr><td>15.Dany Bautista </td></tr><br />
<tr><td>16.Dumitru Gherman </td></tr><br />
<tr><td>17.Dan Parsons </td></tr><br />
<tr><td>18.Huda Sarfraz</td></tr><br />
<tr><td>19.Erik Vold</td></tr><br />
<tr><td>20.Maicon Ferreira</td></tr><br />
<tr><td>21.Ally Gibely</td></tr><br />
<tr><td>22.Vinh Hua</td></tr><br />
<tr><td>23. Vuyisile Ndlovu</td></tr><br />
<tr><td>24. Jose Junior Villagomez Melgar</td></tr><br />
<tr><td>25. Eduardo Urcullú Madrid</td></tr><br />
<tr><td>26. Rocio Soledad Meza Arce</td></tr><br />
<tr><td>27. Evelyn Urcullú Madrid</td></tr><br />
<tr><td>28. Aldo Medina Ruiz Diaz</td></tr><br />
<tr><td>29. Leonard Camacho</td></tr><br />
<tr><td>30. Andrew Williamson</td></tr><br />
<tr><td>31. Victor Hugo Acosta Ortega</td></tr><br />
<tr><td>32. [https://mozillians.org/en-US/u/prixon/ Matej Priteržnik]</td></tr><br />
<tr><td>33. Adriano Cupello</td></tr><br />
<tr><td>34. Ricardo Panaggio</td></tr><br />
<tr><td>35. Peter Radcliffe</td></tr><br />
<tr><td>36. Joel Maher</td></tr><br />
<tr><td>37. Dylan Oliver</td></tr><br />
<tr><td>38. Sara Prussak</td></tr><br />
<tr><td>39. Lisa Gray</td></tr><br />
<tr><td>40. Lori Jashinsky</td></tr><br />
<tr><td>41. Matea Lisica</td></tr><br />
<tr><td>42. Andre Garzia</td></tr><br />
<tr><td>43. Elsa Rodriguez</td></tr><br />
<tr><td>44. [https://mozillians.org/en-US/u/nalexander/ Nick Alexander]</td></tr><br />
<tr><td>45. [https://mozillians.org/en-US/u/mythmon/ Mike Cooper]</td></tr><br />
<tr><td>46. Larissa Shapiro</td></tr><br />
<tr><td>47. Anthonie Nico Kensen</td></tr><br />
<tr><td>48. Melissa O'Connor</td></tr><br />
<tr><td>49. Lisa Brewster</td></tr><br />
<tr><td>50. Tracy Walker</td></tr><br />
</table><br />
<br />
=== Mozillians Hockey ===<br />
<br />
Hockey is Canada's national winter sport. Sign-up to participate in or watch a shinny hockey game* at the old Maple Leaf Gardens on Saturday, October 5, 9:00pm.<br />
<br />
Note: Skating is difficult. This game is open to anyone but it is suggested that only people who have previous skating experience participate in the game itself.<br />
<br />
*Shinny hockey, a Canadian tradition, is played with only skates, a helmet, gloves, and a stick. There are no goalies, no body contact, and no raising the puck or slap-shots.<br />
<br />
What you need to know: <br />
<br />
We will be meeting in the lobby of the hotel at 8:00pm. We'll walk to the rink and the game will start at 9:00pm. <br />
<br />
[https://mozillians.org/lmandel Lawrence Mandel] and [https://mozillians.org/lsblakk Lukas Blakk] have stepped up to help drive this. Please ping them with additional questions. <br />
<br />
'''Sign up here!'''<br />
https://docs.google.com/forms/d/1fhE8oVSAkk5gN9-pfoQ-lCJjQEO2My3kup2NcuAagW0/viewform<br />
==Sunday==<br />
<br />
=Brussels=<br />
==Friday ==<br />
=== Jellyfishing ===<br />
<br />
OMG Jellys! Yes, you read that right! Our very own [https://mozillians.org/en-US/u/rlord/ Rob Lord] is going to instruct and lead a group of Mozillians to Jelly Fish through the cobble streets of Brussels. <br />
<br />
Want to see more, check out this '''[https://vimeo.com/35285151 video]''' <br />
<br />
Sign up here, limit is '''20''' people: <br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Jane Smith</td></tr><br />
<tr><td>2 Mohamed El Sharnoby</td></tr><br />
<tr><td>3 Janet Swisher </td></tr><br />
<tr><td>4 Jeff Griffiths</td></tr><br />
<tr><td>5 Aashish Jagini </td></tr><br />
<tr><td>6 Onur Avsar</td></tr><br />
<tr><td>7 Piniel Romulia Hasibuan</td></tr><br />
<tr><td>8 Mubiru Jonathan </td></tr><br />
<tr><td>9 André Fiedler</td></tr><br />
<tr><td>10 Ilana Segall</td></tr><br />
<tr><td>11 William Reynolds</td></tr><br />
<tr><td>12 Laura Forrest</td></tr><br />
<tr><td>13 Fabio Magnoni</td></tr><br />
<tr><td>14 Wei Li</td></tr><br />
<tr><td>15 Yanfang Liu</td></tr><br />
<tr><td>16 Sharon Xiaoyun Yang</td></tr><br />
<tr><td>17 Curtis Koenig</td></tr><br />
<tr><td>18 Gervase Markham</td></tr><br />
</table><br />
<br />
==Saturday==<br />
=== Movie Night ===<br />
<br />
On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla. <br />
<br />
We may be showing another movie after this, if there is enough interest. <br />
<br />
We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested. <br />
<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>Jane Smith</td></tr><br />
<tr><td>Gene Wood</td></tr><br />
<tr><td>Mihnea Dobrescu-Balaur</td></tr><br />
<tr><td>Aashish Jagini </td></tr><br />
<tr><td>Netha Hussain </td></tr><br />
<tr><td>Liz Compton</td></tr><br />
<tr><td>Piniel Romulia Hasibuan</td></tr><br />
<tr><td> Mubiru Jonathan</td></tr><br />
<tr><td>André Fiedler</td></tr><br />
</table><br />
<br />
=== Chocolate Making (7:30pm) ===<br />
<br />
Mozillians in Brussels, you are in for a real treat! <br />
<br />
If you like making chocolate, or just like chocolate tasting we've got two options for you! <br />
<br />
On Saturday, one of Brussels top chocolatiers, Laurent Gerbaud will be conducting a chocolate making class (tasting also included) for the first 25 Mozillians to sign up. <br />
<br />
If you'd like to read more about them, check out them out [http://www.chocolatsgerbaud.be here]<br />
<br />
For those that are interested in tasting the many types of chocolate Brussels has to offer, please sign up for the Sunday session. <br />
<br />
Space is limited, '''25''' spots available and is now <b>FULL</b>.<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Marcia Knous</td></tr><br />
<tr><td>2 Doris Coleman</td></tr><br />
<tr><td>3 Mary Trombley </td></tr><br />
<tr><td>4 Tanner Young </td></tr><br />
<tr><td>5 Krupa Raj </td></tr><br />
<tr><td>6 Larissa Co </td></tr><br />
<tr><td>7 Gemma Petrie </td></tr><br />
<tr><td>8 Fernando García Gómez </td></tr><br />
<tr><td>9 Elio Qoshi </td></tr><br />
<tr><td>10 Redon Skikuli </td></tr><br />
<tr><td>11 Sokol Dollani</td></tr><br />
<tr><td>12 Altin Ukshini </td></tr><br />
<tr><td>13 Gent Thaci </td></tr><br />
<tr><td>14 Ardian Haxha </td></tr><br />
<tr><td>15 Berni Melero </td></tr><br />
<tr><td>16 Mavis Ou </td></tr><br />
<tr><td>17 Vien Doan </td></tr><br />
<tr><td>18 Jennifer Hayashi </td></tr><br />
<tr><td>19 Fabricio Zuardi</td></tr><br />
<tr><td>20 Benjamin Sternthal </td></tr><br />
<tr><td>21 Mohamed El Sharnoby </td></tr><br />
<tr><td>22 Maureen Hanratty </td></tr><br />
<tr><td>23 Sébastien Desvignes </td></tr><br />
<tr><td>24 Wilson Guaraca </td></tr><br />
<tr><td>25 James Graham </td></tr><br />
</table><br />
<br />
If your name is below, please make sure you add your name to a table that still has room<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>26 Aashish Jagini(Please accomodate me I love to make chocolate)</td></tr><br />
<tr><td>27 Mubiru Jonathan</td></tr><br />
<tr><td>28 Gina Yeh</td></tr><br />
<tr><td>29 Bella Su</td></tr><br />
<tr><td>30 Shelly Lin</td></tr><br />
<tr><td>31 Vit Lai</td></tr><br />
<tr><td>32 Ty Flanagan</td></tr><br />
<tr><td>33 Ioana Chiorean</td></tr><br />
<tr><td>34 William Reynolds</td></tr><br />
<tr><td>35 Kris Maglione</td></tr><br />
<tr><td>36 Wei Li</td></tr><br />
<tr><td>37 Yanfang Liu</td></tr><br />
<tr><td>38 Sharon Xiaoyun Yang</td></tr><br />
</table><br />
<br />
=== Chocolate Tasting ONLY (8:30pm) ===<br />
Space is limited, '''25''' spots available:<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Jane Smith</td></tr><br />
<tr><td>2 Marco Zehe</td></tr><br />
<tr><td>3 Sébastien Barbieri</td></tr><br />
<tr><td>4 Mathieu Laurent</td></tr><br />
<tr><td>5 Ioana Chiorean</td></tr><br />
<tr><td>6 Kris Maglione</td></tr><br />
<tr><td>7 Jorge Villalobos</td></tr><br />
<tr><td>8 Florin Bogdan Strugariu</td></tr><br />
<tr><td>9 Bartosz Piec</td></tr><br />
<tr><td>10 Leo McArdle</td></tr><br />
<tr><td>11 Yousef Alam</td></tr><br />
<tr><td>12 Jan Bambach</td></tr><br />
<tr><td>13 William Reynolds</td></tr><br />
<tr><td>14 Laura Forrest</td></tr><br />
<tr><td>15 Peipei Cheng</td></tr><br />
<tr><td>16 Yanfang Liu</td></tr><br />
<tr><td>17 Wei Li</td></tr><br />
<tr><td>18 Phoebe Chang</td></tr><br />
<tr><td>19 Jessica Jong</td></tr><br />
<tr><td>20 Sharon Xiaoyun Yang</td></tr><br />
<tr><td>21 Aleksandra Uzelac</td></tr><br />
<tr><td>22 Oskar Ivanić</td></tr><br />
<tr><td>23 Dejan Binder</td></tr><br />
<tr><td>24 Saša Jakovljević</td></tr><br />
<tr><td>25 Nino Vranešič</td></tr><br />
</table><br />
<br />
=== Bar Delirium ===<br />
<br />
More information coming soon. We may shift this to Friday. <br />
<br />
{| border="1"<br />
! Name<br />
|-<br />
| Jane Smith<br />
|-<br />
| Elio Qoshi <br />
|-<br />
| Redon Skikuli <br />
|-<br />
| Sokol Dollani<br />
|-<br />
| Altin Ukshini <br />
|-<br />
| Gent Thaci <br />
|-l<br />
| Ardian Haxha <br />
|-<br />
| Gene Wood (+1 for Friday)<br />
|-<br />
| Fabricio Zuardi<br />
|-<br />
| Vien Doan<br />
|-<br />
| Jennifer Hayashi<br />
|-<br />
| Sal Espinosa<br />
|-<br />
| Van Le<br />
|-<br />
| Wilson Guaraca <br />
|-<br />
| Chris More <br />
|-<br />
| Jessilyn Davis <br />
|-<br />
| Jeff Griffiths <br />
|-<br />
| Mihnea Dobrescu-Balaur <br />
|-<br />
| Aashish Jagini<br />
|-<br />
| Tauni Oxborrow (+1 for Friday)<br />
|-<br />
| Kris Maglione<br />
|-<br />
| Dietrich Ayala<br />
|-<br />
| Tom Schuster<br />
|-<br />
| Onur Avsar<br />
|-<br />
| Zac Campbell<br />
|-<br />
| Mubiru Jonathan<br />
|-<br />
| Gina Yeh<br />
|-<br />
| Bella Su<br />
|-<br />
| Shelly Lin<br />
|-<br />
| Jennifer Morrow<br />
|-<br />
| Vit lai<br />
|- <br />
| Raivis Dejus<br />
|-<br />
| Balazs Koren<br />
|-<br />
| André Fiedler<br />
|-<br />
| Sébastien Barbieri<br />
|-<br />
| Mathieu Laurent<br />
|-<br />
| Ty Flanagan<br />
|-<br />
| Justin Dow<br />
|-<br />
| Corey Shields<br />
|-<br />
| Shyam Mani<br />
|-<br />
| Dan Maher<br />
|-<br />
| Derek Moore<br />
|-<br />
| Bree Tipper<br />
|-<br />
| Hernán Rodríguez Colmeiro<br />
|-<br />
| Ilana Segall<br />
|-<br />
| Toni Hermoso<br />
|-<br />
| Justin Dolske<br />
|-<br />
| Ed Lim<br />
|-<br />
| Ben Kero<br />
|-<br />
| William Reynolds<br />
|-<br />
| Laura Forrest<br />
|-<br />
| Marc Schifer<br />
|-<br />
| Fabio Magnoni<br />
|-<br />
| Adam Newman<br />
|-<br />
| Phoebe Chang<br />
|-<br />
| Jessica Jong<br />
|-<br />
| Aleksandra Uzelac<br />
|-<br />
| Oskar Ivanić<br />
|-<br />
| Dejan Binder<br />
|-<br />
| Saša Jakovljević<br />
|-<br />
| Simon Sapin<br />
|-<br />
| Curtis Koenig<br />
|-<br />
| Hagen Halbach<br />
|-<br />
| Frank Wein<br />
|-<br />
| Jürgen Berg<br />
|-<br />
| Théo Chevalier<br />
|-<br />
| Karsten Düsterloh<br />
|-<br />
|}<br />
<br />
==Sunday==<br />
=== Chocolate Tasting (5pm) ===<br />
<br />
Mozillians in Brussels, you are in for a real treat! <br />
<br />
If you have heard about the many different types of Belgium chocolate, you are in the right place. like making chocolate, or just like chocolate tasting we've got two options for you! <br />
<br />
On Sunday, one of Brussels top chocolatiers, Laurent Gerbaud will be conducting a chocolate tasting for the first 25 Mozillians to sign up. <br />
<br />
If you'd like to read more about them, check out them out [http://www.chocolatsgerbaud.be here]<br />
<br />
For those that are interested in ''making and tasting'' chocolate, please sign up for the Saturday session. <br />
<br />
Space is limited, '''25''' spots available and is now <b>FULL</b>.<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Jane Smith</td></tr><br />
<tr><td>2 Krupa Raj</td></tr><br />
<tr><td>3 Marcia Knous</td></tr><br />
<tr><td>4 Gene Wood</td></tr><br />
<tr><td>5 Fabricio Zuardi</td></tr><br />
<tr><td>6 Wilson Guaraca</td></tr><br />
<tr><td>7 Mavis Ou</td></tr><br />
<tr><td>8 Mohamed El Sharnoby</td></tr><br />
<tr><td>9 Jean Collings</td></tr><br />
<tr><td>10 Jessilyn Davis</td></tr><br />
<tr><td>11 Richard Marti</td></tr><br />
<tr><td>12 Doris Coleman</td></tr><br />
<tr><td>13 Janet Swisher</td></tr><br />
<tr><td>14 Kim Ludvigsen</td></tr><br />
<tr><td>15 Ana-Maria Antolović</td></tr><br />
<tr><td>16 aleth</td></tr><br />
<tr><td>17 John Bevan</td></tr><br />
<tr><td>18 Mihnea Dobrescu-Balaur</td></tr><br />
<tr><td>19 Alexandros Mioglou</td></tr><br />
<tr><td>20 Aashish Jagini </td></tr><br />
<tr><td>21 Tauni Oxborrow </td></tr><br />
<tr><td>22 Netha Hussain</td></tr><br />
<tr><td>23 Ziga Milek</td></tr><br />
<tr><td>24 Dustin J. Mitchell</td></tr><br />
<tr><td>25 Fabio Magnoni</td></tr><br />
</table><br />
<br />
=== Chocolate Tasting (6:15pm) ===<br />
Limited to <b>25</b> spots.<br />
<table border=1><tr><th>Name</th></tr><br />
<tr><td>1 Curtis Koenig</td></tr><br />
<tr><td>2 Tom Schuster</td></tr><br />
<tr><td>3 Onur Avsar</td></tr><br />
<tr><td>4 Piniel Romulia Hasibuan</td></tr><br />
<tr><td>5 Zhenshuo Fang</td></tr><br />
<tr><td>6 Mubiru Jonathan</td></tr><br />
<tr><td>7 Gina Yeh</td></tr><br />
<tr><td>8 Bella Su</td></tr><br />
<tr><td>9 Shelly Lin</td></tr><br />
<tr><td>10 Vit lai</td></tr><br />
<tr><td>11 Balazs Koren</td></tr><br />
<tr><td>12 Marco Zehe</td></tr><br />
<tr><td>13 Ty Flanagan</td></tr><br />
<tr><td>14 Emily Goligoski</td></tr><br />
<tr><td>15 Chloe Varelidi</td></tr><br />
<tr><td>16 Bree Tipper</td></tr><br />
<tr><td>17 Irina Parievsky</td></tr><br />
<tr><td>18 Karen Rudnitski</td></tr><br />
<tr><td>19 Hernán Rodríguez Colmeiro</td></tr><br />
<tr><td>20 Kristin Baird</td></tr><br />
<tr><td>21 Tobias Markus</td></tr><br />
<tr><td>22 Brian Birtles</td></tr><br />
<tr><td>23 Kevin Brosnan</td></tr><br />
<tr><td>24 Allison Naaktgboren</td></tr><br />
<tr><td>25 Simon Sapin</td></tr><br />
</table></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode12&diff=401417
Community:SummerOfCode12
2012-02-27T19:48:25Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div>This page lists all the Google Summer of Code 2012 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode12:Brainstorming|the Brainstorming page]]. <br />
<br />
'''Potential students''': you may choose from the list below, '''but you do not have to'''. Feel free to submit a proposal for your own idea. However, before you do so, see the [[Community:SummerOfCode12:Brainstorming|guidelines for good ideas]]. You can also discuss your ideas or application in the #developers channel on IRC: irc://irc.mozilla.org/#developers .<br />
<br />
In addition to the specifically-named projects below, we have also tagged a number of bugs in Bugzilla with the keyword [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=student-project&resolution=--- student-project]. However, as the idea of a "student project" is wider than just the Summer of Code, students looking through the list will need to decide whether any particular bug listed there is actually the right size and scope for Summer of Code.<br />
<br />
==Application Advice==<br />
<br />
* Read the [http://www.booki.cc/gsocstudentguide/ GSoC Student Guide] and follow its advice.<br />
* Read [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] and avoid doing the things listed there.<br />
* Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]].<br />
* Apply on [http://www.google-melange.com/gsoc/org/google/gsoc2012/mozilla the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]).<br />
<br />
Questions of any sort? Send mail to [mailto:gerv@mozilla.org Gerv] and/or [mailto:chofmann@mozilla.org chofmann]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply.<br />
<br />
== Mozilla Platform (Gecko) ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Networking Dashboard<br />
|Build a UI for insight into Mozilla Networking. This is really both a gecko and firefox project. Show what connections are active, how fast connections have run in the past, what protocols are in use with protocol specific context information (http versions, spdy, websockets), allow management (e.g. shutdown) of particular connections, and even trigger some diagnostic tests.<br />
| mcmanus<br />
| mcmanus plus hopefully a ux sponsor<br />
|<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Improve Invitation support<br />
| While Lightning supports invitations, there are still some features that are not supported yet and others that are not quite as stable. Possible goals for this project include improving the UI to make sure users are not confused and implementing/adapting code to support previously unsupported features of invitations like delegations or counters. Lightning relies on the [http://tools.ietf.org/html/rfc6047 itip/imip] standard for invitations, which is also used by most other calendaring clients and servers, so an interested student should look into these. Related bugs are {{bug|420516}}, {{bug|426532}}, {{bug|445982}}, {{bug|538043}}, {{bug|720263}}, {{bug|624332}}, {{bug|433848}}. This is not the final list of bugs to be fixed, just to give you an idea of what can be done here.<br />
<br />
<br />
Skills Required: XUL, Javascript<br />
| [mailto:mozilla@kewis.ch Fallen]<br />
| ludovic?<br />
|<br />
|-<br />
| OS Integration<br />
| Lightning should improve its integration into the Operating system, most importantly on Windows. If you've ever wanted to doubleclick on an event to open it in Lightning, this project is for you. Note this might be a bit more tricky than it intially sounds, but you will have the chance to contribute to multiple projects, as some parts of this project could possibly be better solved within Thunderbird or even the Mozilla Platform. To get prepared, see the list of [https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&component=OS%20Integration&resolution=---&list_id=2260690 OS Integration bugs], and especially {{bug|352566}}.<br />
<br />
<br />
Skills Required: Windows API, C/C++, Javascript, possibly XUL.<br />
| [mailto:mozilla@kewis.ch Fallen]<br />
| Fallen+someone else?<br />
|<br />
|}<br />
<br />
== Thunderbird ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Thunderbird Get Satisfaction support dashboard<br />
| Create a real-time Thunderbird support dashboard by implementing i) a REST API to read Thunderbird support data from a MongoDB database ([http://rolandtanglao.com/archives/2011/12/23/mongohq-gs-api-mongopollrb-my-vps-emailreport2rb-cron-awesome-twice-daily blog post on the code that generates the MongoDB Database]) of Thunderbird Get Satisfaction Support topics ii) a JavaScript client that calls the aforementioned API in order to display a real time Thunderbird support dashboard in Firefox - (i.e. [http://blog.xulforum.org/index.php?post/2010/09/02/GetSatisfaction-dashboard-magic port the existing Thunderbird GS Dashboard to the new API])<br />
Level of difficulty:easy to medium<br />
Skills needed: JavaScript; Helpful: MongoDB & Information Visualization in the browser using JS and an infoviz toolkit like [http://mbostock.github.com/protovis/ protovis] or [http://mbostock.github.com/d3/ D3]<br />
| [mailto:rtanglao@mozilla.com rtanglao]<br />
| Roland Tanglao aka rtanglao<br />
|<br />
|-<br />
| Get ISPDB in production.<br />
| There are a few bugs remaining that the Thunderbird team hasn't had time to fix. It would be nice if we could fix them, and finally get the ISPDB up and running and in use. (If this task was too easy, we could also add in support for Thunderbird submitting working configs to the ISPDB.)<br />
Level of difficulty:easy to medium<br />
<br />
Skills Needed: Python, Some Django experience helpful.<br />
| [mailto:bwinton@mozilla.com bwinton]<br />
| sancus, bwinton<br />
|<br />
|<br />
|-<br />
| App tabs for Thunderbird<br />
| Firefox introduced the concept of app tabs - smaller, fixed tabs that contain a web app. We might want to do something similar for Thunderbird, as a foundation for things like: the Home tab, a Chat app tab, etc...<br />
Level of difficulty: medium to hard<br />
<br />
Skills Needed: Javascript, XUL/XBL, CSS<br />
<br />
| [mailto:mconley@mozilla.com mconley]<br />
| sid0, mconley<br />
|<br />
|}<br />
<br />
== SeaMonkey ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Shell Service<br />
| The Mozilla Suite only supported a shell service on Windows, and SeaMonkey has inherited that limitation. Both Firefox and Thunderbird support the shell service on other platforms, so it is technically feasible to implement the shell service for SeaMonkey on those platforms too.<br />
<br />
Skills needed: C++; some knowledge of GConf/GIO or Cocoa APIs as appropriate.<br />
| [mailto:neil@parkwaycc.co.uk Neil]<br />
| Neil<br />
| This proposal requires some knowledge of platform-specific APIs. Only one platform needs to be implemented by any particular student. I can only give limited support for the Mac but it may be possible to find another mentor.<br />
|-<br />
| Messenger Bookmarks<br />
| SM Mailnews provides access not only to mail, but also to NNTP news and even to RSS feeds, and maybe others in future as well. It would be quite useful to be able to bookmark specific news items for later use, e.g. specific postings of a discussion, etc.<br />
<br />
This should include full usual bookmark handling for those URLs, including sidebar support.<br />
<br />
Relevant bugs:<br/><br />
Bug 14988 - Allow bookmarking of e-mail/Usenet messages<br/><br />
Bug 77186 - allow drag and drop bookmarking of mail / news messages<br/><br />
Bug 77195 - support news, imap, mailbox message urls from the browser<br/><br />
Bug 178003 - Restore access to Sidebar from Mail/News, Compose and Addressbook<br />
<br />
Skills needed: JS, XUL; maybe C++.<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
|<br />
|-<br />
| Folder Views<br />
| We provide the ability to create and use message views for pre-filtering which messages to show in the thread pane. We don't have a comparable feature yet in the folder pane...<br />
<br />
While this would basically mean to port Thunderbird's bug 251296, the UI should be more in sync with the SeaMonkey look and feel, e.g. columns for unread count, size, etc; a drop down menu for switching views; allow custom folder views; ...<br />
<br />
Skills needed: JS, XUL; maybe C++.<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
|<br />
|}<br />
<br />
== Documentation ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Create examples for SVG Reference<br />
|The [https://developer.mozilla.org/en/SVG SVG Reference] needs examples! Lots of examples! We need live samples for all the various SVG elements and attributes, examples for how to do cool stuff with SVG in the DOM, etc. The goal would be to have in-line, live SVG samples, with the code and an explanation of how the code works, for every SVG element and attribute.<br />
<br />
Skills needed: SVG, DOM, moderate-to-good English writing skills.<br />
|Sheppy<br />
|Sheppy<br />
|Also talk to Jeremie Patonnier about helping with mentoring.<br />
|-<br />
|Create examples for HTML and CSS references<br />
|The HTML and CSS references on MDN need examples. While there are some here and there, someone needs to go through and ensure that every HTML element has good examples that cover a variety of use cases and interesting capabilities, and that every CSS property has good coverage as well. These would include live examples with the code and an explanation of how it works.<br />
<br />
Skills needed: HTML and CSS. Moderate-to-good English writing skills.<br />
|Sheppy<br />
|Teoli<br />
|<br />
|-<br />
|Add jsFiddle integration to Kuma<br />
|The new Kuma wiki for MDN needs to have good integration with jsFiddle for easily creating examples then editing, experimenting with, and embedding them into documentation. Should be able to view the source and live output, then experiment with the code in real time (either in place or, perhaps preferably, in a new window).<br />
<br />
Skills needed: JavaScript, HTML, CSS, Python. Django framework familiarity a big plus.<br />
|Sheppy<br />
|Sheppy,Luke Crouch<br />
|<br />
|}<br />
<br />
== Developer Tools ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Highlight JS that causes reflows to occur<br />
| Gecko developers are able to point out statements that trigger reflows from code inspection. We can do better: {{bug|453650}} discusses adding notifications for timing reflows and calls that trigger a reflow. With this information, we can create a tool that obtains stack traces when reflows are triggered, and order the results by duration, and link this to specific triggering JS statements.<br />
| [mailto:josh@joshmatthews.net jdm]<br />
| Someone from devtools, with platform support<br />
| C++ and JS required.<br />
|-<br />
| Highlight slow CSS selectors<br />
| We have a wiki pages of ways to write CSS rules that take advantage of Firefox's internals: https://developer.mozilla.org/en/Writing_Efficient_CSS. If we could add timing data to CSS selector matching, we could use that information to profile rules on a page and display a profiling view that links to specific problematic rules.<br />
| [mailto:josh@joshmatthews.net jdm]<br />
| Someone from devtools, with platform support.<br />
| C++ and JS required.<br />
|}<br />
<br />
== Foundation ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Slide Drive Improvements<br />
| Slide Drive (https://github.com/dseif/slide-drive) combines the deck.js HTML5 slideshow package with Popcorn.js. It was originally developed for Software Carpentry, but would be useful to many other people who want to move off PowerPoint and recorded video. Many enhancements are possible, the most important being accessibility support.<br />
| [mailto:greg@mozillafoundation.org greg]<br />
| greg<br />
|<br />
|}<br />
<br />
== Release Engineering ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Tryserver automation improvements<br />
| We currently have a trychooser syntax which allows developers to customize what they'd like to test their patch with (out of over 200 build & test options) - this syntax can use some improvements to allow for even more granular control and also needs a web-driven interface as well as logic that would let users specify a repo (mozilla-hosted), a custom test package, and much more. Bugs include [https://bugzilla.mozilla.org/show_bug.cgi?id=try_enhancements try_enhancement tracking] and most importantly {{bug|625463}}<br />
| [mailto:lsblakk@mozilla.com Lukas Blakk]<br />
| [https://wiki.mozilla.org/User:Lsblakk Lukas Blakk]<br />
| useful skills include some webdev and python programming<br />
|}<br />
<br />
== Instantbird ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Account import wizard<br />
|Goal: Ease the pain of switching to Instantbird<br />
<br />
Lots of users don't try a new IM client only because they don't want to spend time reconfiguring all their IM accounts. Being able to import accounts from other clients installed on the system would help Instantbird adoption. The student should focus on the dominant IM clients (Windows Live Messenger, AIM, ...) and on the other multi network IM clients (Digsby, Pidgin, Trillian, Miranda, ...). The student will need to study the way other IM clients store their profile data (reverse engineering may be required), think of an architecture to share as much code as possible between the various import modules, and implement import modules for some clients<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Protocol aware error console<br />
|Goal: Create a tool letting developers (and users) see what was exchanged for each account at the protocol level.<br />
<br />
A student working on this project will either extend the existing Error Console or create a new console from which it will be possible to see what data has been exchanged for each account. Example of desirable features: copying a log of whatever happened with an account from the beginning of the connection attempt; syntax highlighting of the exchanged data (requires some parsing of the data exchanged by protocols like XMPP, IRC, Twitter (JSON)); letting the user type and send a raw message to the server. <br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Voice and Video<br />
|Goal: Support voice and video communication.<br />
<br />
This project intends to explore the possibilities for Voice and Video communication using the Mozilla platform. The student will need to experiment both with usage of the microphone and webcam and with codecs available in the system on the three supported OSes. Compatible implementations of the various IM protocols that support these features is out of the scope of this project, but the student will at least need to prove that s/he has seriously investigated using the various open source projects that have started some work on this. A (mostly) working proof of concept is expected. UI mockups for what a well-thought user interface for voice and video could be would be appreciated.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|}<br />
<br />
== Emscripten ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Port the open source C++ project of your choice to the web<br />
| Emscripten lets us compile C++ to JavaScript. Porting a project involves building it with Emscripten and fixing any problems along the way (changes to makefiles, implementing missing library support in Emscripten) as well as analyzing the generated code and seeing how to optimize the code for the web. Any interesting open source C or C++ codebase would be a good project to work on here, some examples: GTK, Qt, SuperTux, PyPy, etc.<br />
| Alon Zakai<br />
| Alon Zakai<br />
|<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode12:Brainstorming&diff=401179
Community:SummerOfCode12:Brainstorming
2012-02-26T20:17:25Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
Mozilla community members - submit ideas here for 2012 Google Summer of Code projects with Mozilla.<br />
<br />
<b>Are you a students looking to apply to SoC with Mozilla?</b> Project ideas formally approved by the Mozilla SoC admins are [[Community:SummerOfCode12|here]]. You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.<br />
<br />
==How To Write A Good Project Proposal==<br />
<br />
Before adding an proposal to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Here are the ideas lists from previous years]].<br />
<br />
Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in the title. If there is no category for your part of Mozilla, add one!<br />
<br />
== Mozilla Platform (Gecko) ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Networking Dashboard<br />
|Build a UI for insight into Mozilla Networking. This is really both a gecko and firefox project. Show what connections are active, how fast connections have run in the past, what protocols are in use with protocol specific context information (http versions, spdy, websockets), allow management (e.g. shutdown) of particular connections, and even trigger some diagnostic tests.<br />
| mcmanus<br />
| mcmanus plus hopefully a ux sponsor<br />
|<br />
|}<br />
<br />
== Firefox ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Firefox Mobile ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Boot2Gecko ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Improve Invitation support<br />
| While Lightning supports invitations, there are still some features that are not supported yet and others that are not quite as stable. Possible goals for this project include improving the UI to make sure users are not confused and implementing/adapting code to support previously unsupported features of invitations like delegations or counters. Lightning relies on the [http://tools.ietf.org/html/rfc6047 itip/imip] standard for invitations, which is also used by most other calendaring clients and servers, so an interested student should look into these. Related bugs are {{bug|420516}}, {{bug|426532}}, {{bug|445982}}, {{bug|538043}}, {{bug|720263}}, {{bug|624332}}, {{bug|433848}}. This is not the final list of bugs to be fixed, just to give you an idea of what can be done here.<br />
| [mailto:mozilla@kewis.ch Fallen]<br />
| ludovic?<br />
|<br />
|-<br />
| OS Integration<br />
| Lightning should improve its integration into the Operating system, most importantly on Windows. If you've ever wanted to doubleclick on an event to open it in Lightning, this project is for you. Note this might be a bit more tricky than it intially sounds, but you will have the chance to contribute to multiple projects, as some parts of this project could possibly be better solved within Thunderbird or even the Mozilla Platform. To get prepared, see the list of [https://bugzilla.mozilla.org/buglist.cgi?product=Calendar&component=OS%20Integration&resolution=---&list_id=2260690 OS Integration bugs], and especially {{bug|352566}}.<br />
| [mailto:mozilla@kewis.ch Fallen]<br />
| Fallen+someone else?<br />
|<br />
|}<br />
== Thunderbird ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Search toolbar<br />
| Thunderbird comes with a powerful search feature. When performing a search, the results appear in a new search tab. This new tab allows you to drill down and filter the results of your search. We would like to expand this search result tab so that users can modify their search query as well. A WIP patch has already been started, and so if the project is completed with time to spare, there are a few other things we can add and rearrange to the search tab to make it better for our users. See {{bug|719008}}.<br />
| [mailto:mconley@mozilla.com mconley]<br />
| mconley<br />
|-<br />
| Thunderbird Get Satisfaction support dashboard<br />
| Create a real-time Thunderbird support dashboard by implementing i) a REST API to read Thunderbird support data from a MongoDB database ([http://rolandtanglao.com/archives/2011/12/23/mongohq-gs-api-mongopollrb-my-vps-emailreport2rb-cron-awesome-twice-daily blog post on the code that generates the MongoDB Database]) of Thunderbird Get Satisfaction Support topics ii) a JavaScript client that calls the aforementioned API in order to display a real time Thunderbird support dashboard in Firefox - (i.e. [http://blog.xulforum.org/index.php?post/2010/09/02/GetSatisfaction-dashboard-magic port the existing Thunderbird GS Dashboard to the new API])<br />
Level of difficulty:easy to medium<br />
| [mailto:rtanglao@mozilla.com rtanglao]<br />
| Roland Tanglao aka rtanglao<br />
|<br />
|-<br />
| Get ISPDB in production.<br />
| There are a few bugs remaining that the Thunderbird team hasn't had time to fix. It would be nice if we could fix them, and finally get the ISPDB up and running and in use. (If this task was too easy, we could also add in support for Thunderbird submitting working configs to the ISPDB.)<br />
Level of difficulty:easy to medium<br />
| [mailto:bwinton@mozilla.com bwinton]<br />
| sancus, bwinton<br />
|<br />
|}<br />
<br />
== SeaMonkey ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Shell Service<br />
| The Mozilla Suite only supported a shell service on Windows, and SeaMonkey has inherited that limitation. Both Firefox and Thunderbird support the shell service on other platforms, so it is technically feasible to implement the shell service for SeaMonkey on those platforms too.<br />
| [mailto:neil@parkwaycc.co.uk Neil]<br />
| Neil<br />
| This proposal requires some knowledge of platform-specific APIs. Only one platform needs to be implemented by any particular student. I can only give limited support for the Mac but it may be possible to find another mentor.<br />
|-<br />
| Messenger Bookmarks<br />
| SM Mailnews provides access not only to mail, but also to NNTP news and even to RSS feeds, and maybe others in future as well. It would be quite useful to be able to bookmark specific news items for later use, e.g. specific postings of a discussion, etc.<br />
<br />
This should include full usual bookmark handling for those URLs, including sidebar support.<br />
<br />
Relevant bugs:<br/><br />
Bug 14988 - Allow bookmarking of e-mail/Usenet messages<br/><br />
Bug 77186 - allow drag and drop bookmarking of mail / news messages<br/><br />
Bug 77195 - support news, imap, mailbox message urls from the browser<br/><br />
Bug 178003 - Restore access to Sidebar from Mail/News, Compose and Addressbook<br/><br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
|<br />
|-<br />
| Folder Views<br />
| We provide the ability to create and use message views for pre-filtering which messages to show in the thread pane. We don't have a comparable feature yet in the folder pane...<br />
<br />
While this would basically mean to port Thunderbird's bug 251296, the UI should be more in sync with the SeaMonkey look and feel, e.g. columns for unread count, size, etc; a drop down menu for switching views; allow custom folder views; ...<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
| [mailto:mnyromyr@tprac.de Mnyromyr]<br />
|<br />
|}<br />
<br />
== Camino ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Firefox Support (SUMO) ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== QA ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Documentation ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Create examples for SVG Reference<br />
|The [https://developer.mozilla.org/en/SVG SVG Reference] needs examples! Lots of examples! We need live samples for all the various SVG elements and attributes, examples for how to do cool stuff with SVG in the DOM, etc. The goal would be to have in-line, live SVG samples, with the code and an explanation of how the code works, for every SVG element and attribute.<br />
|Sheppy<br />
|Sheppy<br />
|Also talk to Jeremie Patonnier about helping with mentoring.<br />
|-<br />
|Create examples for HTML and CSS references<br />
|The HTML and CSS references on MDN need examples. While there are some here and there, someone needs to go through and ensure that every HTML element has good examples that cover a variety of use cases and interesting capabilities, and that every CSS property has good coverage as well. These would include live examples with the code and an explanation of how it works.<br />
|Sheppy<br />
|Teoli<br />
|<br />
|-<br />
|Add jsFiddle integration to Kuma<br />
|The new Kuma wiki for MDN needs to have good integration with jsFiddle for easily creating examples then editing, experimenting with, and embedding them into documentation. Should be able to view the source and live output, then experiment with the code in real time (either in place or, perhaps preferably, in a new window).<br />
|Sheppy<br />
|Sheppy<br />
|<br />
|}<br />
<br />
== Mozilla IT and Infrastructure ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Open Web Apps ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Identity ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Sync ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Developer Tools ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Highlight JS that causes reflows to occur<br />
| Gecko developers are able to point out statements that trigger reflows from code inspection. We can do better: {{bug|453650}} discusses adding notifications for timing reflows and calls that trigger a reflow. With this information, we can create a tool that obtains stack traces when reflows are triggered, and order the results by duration, and link this to specific triggering JS statements.<br />
| [mailto:josh@joshmatthews.net jdm]<br />
| Someone from devtools, with platform support<br />
| C++ and JS required.<br />
|-<br />
| Highlight slow CSS selectors<br />
| We have a wiki pages of ways to write CSS rules that take advantage of Firefox's internals: https://developer.mozilla.org/en/Writing_Efficient_CSS. If we could add timing data to CSS selector matching, we could use that information to profile rules on a page and display a profiling view that links to specific problematic rules.<br />
| [mailto:josh@joshmatthews.net jdm]<br />
| Someone from devtools, with platform support.<br />
| C++ and JS required.<br />
|}<br />
<br />
== Foundation ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Slide Drive Improvements<br />
| Slide Drive (https://github.com/dseif/slide-drive) combines the deck.js HTML5 slideshow package with Popcorn.js. It was originally developed for Software Carpentry, but would be useful to many other people who want to move off PowerPoint and recorded video. Many enhancements are possible, the most important being accessibility support.<br />
| [mailto:greg@mozillafoundation.org greg]<br />
| greg<br />
|<br />
|}<br />
<br />
== Release Engineering ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Tryserver automation improvements<br />
| We currently have a trychooser syntax which allows developers to customize what they'd like to test their patch with (out of over 200 build & test options) - this syntax can use some improvements to allow for even more granular control and also needs a web-driven interface as well as logic that would let users specify a repo (mozilla-hosted), a custom test package, and much more. Bugs include [https://bugzilla.mozilla.org/show_bug.cgi?id=try_enhancements try_enhancement tracking] and most importantly {{bug|625463}}<br />
| [mailto:lsblakk@mozilla.com Lukas Blakk]<br />
| [https://wiki.mozilla.org/User:Lsblakk Lukas Blakk]<br />
| useful skills include some webdev and python programming<br />
|}<br />
<br />
== Instantbird ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
|Account import wizard<br />
|Goal: Ease the pain of switching to Instantbird<br />
<br />
Lots of users don't try a new IM client only because they don't want to spend time reconfiguring all their IM accounts. Being able to import accounts from other clients installed on the system would help Instantbird adoption. The student should focus on the dominant IM clients (Windows Live Messenger, AIM, ...) and on the other multi network IM clients (Digsby, Pidgin, Trillian, Miranda, ...). The student will need to study the way other IM clients store their profile data (reverse engineering may be required), think of an architecture to share as much code as possible between the various import modules, and implement import modules for some clients<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Protocol aware error console<br />
|Goal: Create a tool letting developers (and users) see what was exchanged for each account at the protocol level.<br />
<br />
A student working on this project will either extend the existing Error Console or create a new console from which it will be possible to see what data has been exchanged for each account. Example of desirable features: copying a log of whatever happened with an account from the beginning of the connection attempt; syntax highlighting of the exchanged data (requires some parsing of the data exchanged by protocols like XMPP, IRC, Twitter (JSON)); letting the user type and send a raw message to the server. <br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Voice and Video<br />
|Goal: Support voice and video communication.<br />
<br />
This project intends to explore the possibilities for Voice and Video communication using the Mozilla platform. The student will need to experiment both with usage of the microphone and webcam and with codecs available in the system on the three supported OSes. Compatible implementations of the various IM protocols that support these features is out of the scope of this project, but the student will at least need to prove that s/he has seriously investigated using the various open source projects that have started some work on this. A (mostly) working proof of concept is expected. UI mockups for what a well-thought user interface for voice and video could be would be appreciated.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|}<br />
<br />
== Emscripten ==<br />
<br />
{| class="standard-table" border="1" style="border-collapse: collapse"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Port the open source C++ project of your choice to the web<br />
| Emscripten lets us compile C++ to JavaScript. Porting a project involves building it with Emscripten and fixing any problems along the way (changes to makefiles, implementing missing library support in Emscripten) as well as analyzing the generated code and seeing how to optimize the code for the web. Any interesting open source C or C++ codebase would be a good project to work on here, some examples: GTK, Qt, SuperTux, PyPy, etc.<br />
| Alon Zakai<br />
| Alon Zakai<br />
|<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Fosdem:2012:Attendees&diff=389439
Fosdem:2012:Attendees
2012-01-23T23:14:46Z
<p>Mnyromyr: /* Attendees */</p>
<hr />
<div>===Attendees===<br />
<br />
* Ziggy Maes (ReMo)<br />
* Mnyromyr</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=EU_MozCamp_2011/Participants/Full_List&diff=366681
EU MozCamp 2011/Participants/Full List
2011-11-08T18:14:52Z
<p>Mnyromyr: </p>
<hr />
<div>{| cellspacing="0" cellpadding="5" border="1" class="wikitable sortable"<br />
|-<br />
! First Name <br />
! Last Name <br />
! Country <br />
! I work on <br />
! Email <br />
! Blog/Twitter<br />
|-<br />
| Paul <br />
| Rouget <br />
| France <br />
| Dev Tools <br />
| paul@mozilla.com <br />
| @paulrouget<br />
|-<br />
| Majda <br />
| Nafissa Rahal <br />
| Algeria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Guillermo <br />
| Movia <br />
| Argentina <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Julian <br />
| Viereck <br />
| Austria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hugo <br />
| Acosta <br />
| Bolivia <br />
| <br> <br />
| hugo@mozillabolivia.org <br />
| @nex23<br />
|-<br />
| Benoit <br />
| Leseul <br />
| Belgium <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Aleksandar <br />
| Savic <br />
| Bosnia-Herzegovina <br />
| <br> <br />
| aleksandar@mozilla.ba <br />
| @aleksandar_s<br />
|-<br />
| Kerim <br />
| Kalamujic <br />
| Bosnia-Herzegovina <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pavel <br />
| Ivanov <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ognyan <br />
| Kulev <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bogomil <br />
| Shopov <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Margarita <br />
| Yordanova <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sasa <br />
| Tekovic <br />
| Croatia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pavel <br />
| Cvrček <br />
| Czech Republic <br />
| L10N <br />
| pcvrcek@mozilla.cz <br />
| @JasnaPaka<br />
|-<br />
| Pavel <br />
| Franc <br />
| Czech Republic <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Martin <br />
| Stransky <br />
| Czech Republic <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jesper <br />
| Kristensen <br />
| Denmark <br />
| l10n, support <br />
| mail jesperkristensen dk <br />
| http://blog.mozilladanmark.dk/<br />
|-<br />
| Soren <br />
| Munk Skroder <br />
| Denmark <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Haitham <br />
| Sakr El Ghareeb <br />
| Egypt <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ahmed <br />
| Soliman <br />
| Egypt <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Merike <br />
| Sell <br />
| Estonia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Paul <br />
| Adenot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Louis-Remi <br />
| Babe <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Bruant <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Cédric <br />
| Corazza <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Claire <br />
| Corgnou <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| René-Luc <br />
| D'Hont <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philippe <br />
| Dessante <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Serge <br />
| Gautherie <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michel <br />
| Gutierrez <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laurent <br />
| Jouanneau <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexandre <br />
| Lissy <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jean-Bernard <br />
| Marcon <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Marteau <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeremie <br />
| Patonnier <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sonny <br />
| Piers <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Quèze <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Antoine <br />
| Turmel <br />
| France <br />
| French l10n, ReMo, Promotion <br />
| antoineturmel@gmail.com <br />
| @GeekShadow<br />
|-<br />
| Jonathan <br />
| Protzenko <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Imke <br />
| Baehr <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Juergen <br />
| Berg <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Karsten <br />
| Düsterloh <br />
| Germany <br />
| SeaMonkey, Mnenhy, MailNews backend<br />
| mnyromyr@tprac.de<br />
| <br><br />
|-<br />
| Kai <br />
| Engert <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sebastian <br />
| Hengst <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Andreas <br />
| Kleinert <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Martin <br />
| Kliehm <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michael <br />
| Koehler <br />
| Germany <br />
| Website l10n, support <br />
| coce [at] nurfuerspam [dot] de <br />
| <br><br />
|-<br />
| Cédric <br />
| Menge <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bernd <br />
| Mielke <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wladimir <br />
| Palant <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Grigorios <br />
| Petsos <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wolfgang <br />
| Rosenauer <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Schloegl <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Scholz <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Thomas <br />
| Schwecherl <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Markus <br />
| Stange <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Richard <br />
| Sternagel <br />
| Germany <br />
| <br> <br />
| <br> <br />
| http://rsternagel.de<br />
|-<br />
| Frank <br />
| Wein <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Steffen <br />
| Wilberg <br />
| Germany <br />
| Firefox <br />
| steffen.wilberg web.de <br />
| @steffenw<br />
|-<br />
| Tobias <br />
| Markus <br />
| Germany <br />
| WebQA (mostly automation), SUMO<br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matti <br />
| Versen <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kwamena <br />
| Appiah-Kubi <br />
| Ghana <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alfredos-Panagiotis <br />
| Damkalis <br />
| Greece <br />
| <br> <br />
| fredy&lt;at&gt;freemail.gr <br />
| <br><br />
|-<br />
| George <br />
| Fiotakis <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Logiotatidis <br />
| Giorgos <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Nikos <br />
| Roussos <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kalman <br />
| Kemenczy <br />
| Hungary <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kalman <br />
| Szalai <br />
| Hungary <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Brian <br />
| King <br />
| Slovenia/Ireland <br />
| AMO Editor, Add-on dev, ReMo Council, Mozdev, and more <br />
| briks.si@gmail.com <br />
| [http://brian.kingsonline.net/talk/ Blog], [https://twitter.com/#!/brianking @brianking]<br />
|-<br />
| David <br />
| McNamara <br />
| Ireland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Amir <br />
| Aharoni <br />
| Israel <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tomer <br />
| Cohen <br />
| Israel <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Iacopo <br />
| Benesperi <br />
| Italy <br />
| l10n <br />
| iacopo.benesperi [at] mozillaitalia [dot] org <br />
| <br><br />
|-<br />
| Carlo <br />
| Frinolli <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Paolo <br />
| Iacobazzi <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Francesco <br />
| Lodolo <br />
| Italy <br />
| l10n <br />
| francesco.lodolo [at] mozillaitalia [dot] org <br />
| @flod<br />
|-<br />
| Giorgio <br />
| Maone <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michele <br />
| Rodaro <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Giovanni <br />
| Solone <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefano <br />
| Tintorini <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Issa <br />
| Mahasneh <br />
| Jordan <br />
| <br> <br />
| issa@jordanopensource.org<br />
| [http://twitter.com/yugi @yugi]<br />
|-<br />
| Cliff <br />
| Argwings <br />
| Kenya <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Munyasia Wafula <br />
| Kenya <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Raivis <br />
| Dejus <br />
| Latvia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Anas <br />
| El Husseini <br />
| Lebanon <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gorjan <br />
| Jovanovski <br />
| Macedonia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mohomodou <br />
| Houssouba <br />
| Mali <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mohammed <br />
| Amarochan <br />
| Morocco <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wim <br />
| Benes <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Otto <br />
| de Voogd <br />
| Netherlands / Estonia<br />
| <br> <br />
| [http://ottodv.com/contact Contact]<br />
| [http://ottodv.com/g+ Google+] [http://ottodv.com/tt Twitter]<br />
|-<br />
| Anthonie Nico <br />
| Kensen <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tim <br />
| Maks Van der Broek <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Marien <br />
| Zwart <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hatem <br />
| Zyoud <br />
| Palestine <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hubert <br />
| Gajewski <br />
| Poland <br />
| Aviary.pl <br />
| hgajewski@aviary.pl <br />
| [http://hubertgajewski.com hubertgajewski.com], [https://twitter.com/hubertgajewski @hubertgajewski]<br />
|-<br />
| Krzysztof <br />
| Glebowicz <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Grzegorz <br />
| Glogowski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Adrian <br />
| Kalla <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lukasz <br />
| Kluj <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Krzysztof <br />
| Kurzawski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sara <br />
| Prussak <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Katarzyna <br />
| Stawarz <br />
| Poland <br />
| l10n <br />
| <br> <br />
| @falkowata<br />
|-<br />
| Marek <br />
| Stępień <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Leszek Teo <br />
| Zyczkowski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Krzysztof <br />
| Wróblewski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefania <br />
| Chiorean <br />
| Romania <br />
| Firefox Mobile, Personas, Promotion, ReMo <br />
| [mailto:ichiorean@mozilla.com IoanaChiorean]; ([mailto:chiorean.ioana@gmail.com Gmail]) <br />
| [https://twitter.com/#!/ioana_cis/ twitter]<br />
|-<br />
| Valentin <br />
| Gosu <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laurian <br />
| Gridinoc <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Lakatos <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alina <br />
| Mierluș <br />
| Interwebs <br />
| opening communities, public spaces, civic/public engagement <br />
| contact [at] alinamierlus [dot] com <br />
| @alina_mierlus<br />
|-<br />
| Alexandru <br />
| Szasz <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tiberiu <br />
| Turbureanu <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Konstantin A. <br />
| Lepikhov <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexander <br />
| Slovesnik <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Rodionov <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mouhamoudou Moustapha <br />
| Camara <br />
| Senegal <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Branislav <br />
| Rozbora <br />
| Slovakia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vlado <br />
| Valastiak <br />
| Slovakia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vito <br />
| Smolej <br />
| Slovenia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Nino <br />
| Vranešič <br />
| Slovenia <br />
| <br> <br />
| nino@mozilla.si <br />
| @ninovranesic<br />
|-<br />
| Dwayne <br />
| Bailey <br />
| South Africa <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hugo <br />
| Acosta <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Inma <br />
| Barrios <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Bengoa <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Edu <br />
| Gamonal <br />
| Catalonia <br />
| l10n-ca <br />
| egamonal a softcatala.cat <br />
| @_egamonal<br />
|-<br />
| Pedro <br />
| García Rodríguez <br />
| Spain <br />
| l10n:es-ES QA Thunderbird<br />
| pgarcia@mozilla-hispano.org <br />
| @breaking_pitt<br />
|-<br />
| Fernando <br />
| Garcia Gomez <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Toni <br />
| Hermoso Pulido <br />
| Catalonia <br />
| l10n:ca, Promotion <br />
| <br> <br />
| @toniher<br />
|-<br />
| Guillermo <br />
| López <br />
| Spain <br />
| l10n:es-ES <br />
| willyaranda@mozilla-hispano.org <br />
| @willyaranda<br />
|-<br />
| Rubén <br />
| MartÃn <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Berni <br />
| Melero <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Elena <br />
| Palomo <br />
| Spain <br />
| <br> <br />
| palomo.elena@gmail.com<br> <br />
| @velvetbites<br><br />
|-<br />
| Joaquim <br />
| Perez Noguer <br />
| Catalonia <br />
| l10n:ca <br />
| joaquimperez a softcatala.org <br />
| @qpnoguer<br />
|-<br />
| Francisco <br />
| Picolini <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefan <br />
| Hermes <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mikael <br />
| Hiort af Ornäs <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Markus <br />
| Magnuson <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| HÃ¥kan <br />
| Waara <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Patrick <br />
| Brunschwig <br />
| Switzerland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jean-Yves <br />
| Perrier <br />
| Switzerland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sofien <br />
| Chaabouni <br />
| Tunisia <br />
| <br> <br />
| chaabouni.sofien@gmail.com <br />
| @chaasof<br />
|-<br />
| Jebdnoun <br />
| Melek <br />
| Tunisia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Selim <br />
| Sumlu <br />
| Turkey <br />
| <br> <br />
| selim at sum.lu <br />
| @maxcoder<br />
|-<br />
| Chris <br />
| Coulson <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| William <br />
| Duyck <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matt <br />
| Jukes <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ed <br />
| Morley <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ian <br />
| Neal <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Timothy <br />
| Babych <br />
| Ukraine <br />
| l10n:uk, l10n tools<br />
| tim.babych@gmail.com <br />
| @tymofiy, http://clear.com.ua<br />
|-<br />
| Kristin <br />
| Baird <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Chris <br />
| Beard <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeff <br />
| Beatty <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Dave <br />
| Berz <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Boswell <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Zbigniew <br />
| Braniecki <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Diane <br />
| Branson <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Fabien <br />
| Cazenave <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pascal <br />
| Chevrel <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Desigan <br />
| Chinniah <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Debbie <br />
| Cohen <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Carmen <br />
| Collins <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mary <br />
| Colvig <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jess <br />
| Davis <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Milos <br />
| Dinic <br />
| Serbia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Justin <br />
| Dow <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Raymond <br />
| Etornam Agbeame <br />
| Ghana <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Patrick <br />
| Finch <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jane <br />
| Finette <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ty <br />
| Flanagan <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ibai <br />
| Garcia <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Dumitru <br />
| Gherman <br />
| USA <br />
| IT Operations <br />
| dgherman[at]mozilla[dot]com <br />
| <br><br />
|-<br />
| Jeff <br />
| Griffiths <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeff <br />
| Griffiths <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jack <br />
| Guo <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jason <br />
| Haas <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Hawkes <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Axel <br />
| Hecht <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Christian <br />
| Heilmann <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ludovic <br />
| Hirlimann <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Havi <br />
| Hoffman <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Chris <br />
| Hofmann <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bobby <br />
| Holley <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matjaz <br />
| Horvat <br />
| Slovenia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Barbara <br />
| Hueppe <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Spencer <br />
| Hui <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| John <br />
| Jensen <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lufei <br />
| Jia <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gregory <br />
| Jost <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Erica <br />
| Jostedt <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Kaiser <br />
| Austria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gen <br />
| Kanai <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Makoto <br />
| Kato <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philip <br />
| Kewisch <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Marcia <br />
| Knous <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| John Curtis <br />
| Koenig <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mounir <br />
| Lamouri <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Delphine <br />
| Lebedel <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Christian <br />
| Legnitto <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michelle <br />
| Luna <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gervase <br />
| Markham <br />
| UK <br />
| An eclectic collection of things <br />
| gerv@mozilla.org <br />
| [http://blog.gerv.net/ http://blog.gerv.net/]<br />
|-<br />
| David <br />
| Mason <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laura <br />
| Mesa <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Aleksandr <br />
| Milewski <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vivien <br />
| Nicolas <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Johnathan <br />
| Nightingale <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tristan <br />
| Nitot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matej <br />
| Novak <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Nyman <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pierros <br />
| Papadeas <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jay <br />
| Patel <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| JB <br />
| Piacentino <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexandre <br />
| Poirot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Valerie <br />
| Ponell <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| WIlliam <br />
| Quiviger <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Arky <br />
| Rakesh <br />
| India <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Anthony <br />
| Ricaud <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lucas <br />
| Rocha <br />
| Brazil <br />
| Firefox Mobile <br />
| lucasr@mozilla.com <br />
| http://lucasr.org / @lucasratmundo<br />
|-<br />
| Paul <br />
| Rouget <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Irina <br />
| Sandu <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philipp <br />
| Schmidt <br />
| South Africa <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Margaret <br />
| Schroeder <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Justin <br />
| Scott <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tara <br />
| Shahian <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Henrik <br />
| Skupin <br />
| Germany <br />
| Test Automation <br />
| hskupin@mozilla.com <br />
| @whimboo<br />
|-<br />
| David <br />
| Tenser <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kosaka <br />
| Tetsuya <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michelle <br />
| Thorne <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lee <br />
| Tom <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Abdulkadir <br />
| Topal <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jorge <br />
| Villalobos <br />
| Costa Rica <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Erik <br />
| Vold <br />
| Canada <br />
| <br> <br />
| erikvvold@gmail.com <br />
| @erikvold<br />
|-<br />
| Philip <br />
| von Weitershausen <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Andrew <br />
| Williamson <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Arzhel <br />
| Younsi <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matthew <br />
| Zeier <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Rachel <br />
| Zhang <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Malolepszy <br />
| Stas <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tim <br />
| Taubert <br />
| Germany <br />
| Firefox <br />
| ttaubert@mozilla.com <br />
| @ttaubert<br />
|-<br />
| Stephanie <br />
| Schipper <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Susan <br />
| Chen <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bret <br />
| Reckard <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mike <br />
| Hommey <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Axel<br />
| Grude <br />
| Ireland <br />
| AMO-Editor, MDN, Extensions (QuickFolders, QuickPasswords, Zombie Keys) <br />
| ([mailto:&#97;&#120;&#101;l.grude@gmail.com Gmail]) <br />
| <br><br />
|-<br />
| Ken <br />
| Barbalace <br />
| USA <br />
| AMO Editor <br />
| ken@EnvironmentalChemistry.com<br />
| http://EnvironmentalChemistry.com<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=EU_MozCamp_2011/Participants/Full_List&diff=366679
EU MozCamp 2011/Participants/Full List
2011-11-08T18:13:45Z
<p>Mnyromyr: </p>
<hr />
<div>{| cellspacing="0" cellpadding="5" border="1" class="wikitable sortable"<br />
|-<br />
! First Name <br />
! Last Name <br />
! Country <br />
! I work on <br />
! Email <br />
! Blog/Twitter<br />
|-<br />
| Paul <br />
| Rouget <br />
| France <br />
| Dev Tools <br />
| paul@mozilla.com <br />
| @paulrouget<br />
|-<br />
| Majda <br />
| Nafissa Rahal <br />
| Algeria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Guillermo <br />
| Movia <br />
| Argentina <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Julian <br />
| Viereck <br />
| Austria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hugo <br />
| Acosta <br />
| Bolivia <br />
| <br> <br />
| hugo@mozillabolivia.org <br />
| @nex23<br />
|-<br />
| Benoit <br />
| Leseul <br />
| Belgium <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Aleksandar <br />
| Savic <br />
| Bosnia-Herzegovina <br />
| <br> <br />
| aleksandar@mozilla.ba <br />
| @aleksandar_s<br />
|-<br />
| Kerim <br />
| Kalamujic <br />
| Bosnia-Herzegovina <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pavel <br />
| Ivanov <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ognyan <br />
| Kulev <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bogomil <br />
| Shopov <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Margarita <br />
| Yordanova <br />
| Bulgaria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sasa <br />
| Tekovic <br />
| Croatia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pavel <br />
| Cvrček <br />
| Czech Republic <br />
| L10N <br />
| pcvrcek@mozilla.cz <br />
| @JasnaPaka<br />
|-<br />
| Pavel <br />
| Franc <br />
| Czech Republic <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Martin <br />
| Stransky <br />
| Czech Republic <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jesper <br />
| Kristensen <br />
| Denmark <br />
| l10n, support <br />
| mail jesperkristensen dk <br />
| http://blog.mozilladanmark.dk/<br />
|-<br />
| Soren <br />
| Munk Skroder <br />
| Denmark <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Haitham <br />
| Sakr El Ghareeb <br />
| Egypt <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ahmed <br />
| Soliman <br />
| Egypt <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Merike <br />
| Sell <br />
| Estonia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Paul <br />
| Adenot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Louis-Remi <br />
| Babe <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Bruant <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Cédric <br />
| Corazza <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Claire <br />
| Corgnou <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| René-Luc <br />
| D'Hont <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philippe <br />
| Dessante <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Serge <br />
| Gautherie <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michel <br />
| Gutierrez <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laurent <br />
| Jouanneau <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexandre <br />
| Lissy <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jean-Bernard <br />
| Marcon <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Marteau <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeremie <br />
| Patonnier <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sonny <br />
| Piers <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Quèze <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Antoine <br />
| Turmel <br />
| France <br />
| French l10n, ReMo, Promotion <br />
| antoineturmel@gmail.com <br />
| @GeekShadow<br />
|-<br />
| Jonathan <br />
| Protzenko <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Imke <br />
| Baehr <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Juergen <br />
| Berg <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Karsten <br />
| Dûsterloh <br />
| Germany <br />
| SeaMonkey, Mnenhy, MailNews backend<br />
| mnyromyr@tprac.de<br />
| <br><br />
|-<br />
| Kai <br />
| Engert <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sebastian <br />
| Hengst <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Andreas <br />
| Kleinert <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Martin <br />
| Kliehm <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michael <br />
| Koehler <br />
| Germany <br />
| Website l10n, support <br />
| coce [at] nurfuerspam [dot] de <br />
| <br><br />
|-<br />
| Cédric <br />
| Menge <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bernd <br />
| Mielke <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wladimir <br />
| Palant <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Grigorios <br />
| Petsos <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wolfgang <br />
| Rosenauer <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Schloegl <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Florian <br />
| Scholz <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Thomas <br />
| Schwecherl <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Markus <br />
| Stange <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Richard <br />
| Sternagel <br />
| Germany <br />
| <br> <br />
| <br> <br />
| http://rsternagel.de<br />
|-<br />
| Frank <br />
| Wein <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Steffen <br />
| Wilberg <br />
| Germany <br />
| Firefox <br />
| steffen.wilberg web.de <br />
| @steffenw<br />
|-<br />
| Tobias <br />
| Markus <br />
| Germany <br />
| WebQA (mostly automation), SUMO<br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matti <br />
| Versen <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kwamena <br />
| Appiah-Kubi <br />
| Ghana <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alfredos-Panagiotis <br />
| Damkalis <br />
| Greece <br />
| <br> <br />
| fredy&lt;at&gt;freemail.gr <br />
| <br><br />
|-<br />
| George <br />
| Fiotakis <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Logiotatidis <br />
| Giorgos <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Nikos <br />
| Roussos <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kalman <br />
| Kemenczy <br />
| Hungary <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kalman <br />
| Szalai <br />
| Hungary <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Brian <br />
| King <br />
| Slovenia/Ireland <br />
| AMO Editor, Add-on dev, ReMo Council, Mozdev, and more <br />
| briks.si@gmail.com <br />
| [http://brian.kingsonline.net/talk/ Blog], [https://twitter.com/#!/brianking @brianking]<br />
|-<br />
| David <br />
| McNamara <br />
| Ireland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Amir <br />
| Aharoni <br />
| Israel <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tomer <br />
| Cohen <br />
| Israel <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Iacopo <br />
| Benesperi <br />
| Italy <br />
| l10n <br />
| iacopo.benesperi [at] mozillaitalia [dot] org <br />
| <br><br />
|-<br />
| Carlo <br />
| Frinolli <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Paolo <br />
| Iacobazzi <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Francesco <br />
| Lodolo <br />
| Italy <br />
| l10n <br />
| francesco.lodolo [at] mozillaitalia [dot] org <br />
| @flod<br />
|-<br />
| Giorgio <br />
| Maone <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michele <br />
| Rodaro <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Giovanni <br />
| Solone <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefano <br />
| Tintorini <br />
| Italy <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Issa <br />
| Mahasneh <br />
| Jordan <br />
| <br> <br />
| issa@jordanopensource.org<br />
| [http://twitter.com/yugi @yugi]<br />
|-<br />
| Cliff <br />
| Argwings <br />
| Kenya <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Munyasia Wafula <br />
| Kenya <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Raivis <br />
| Dejus <br />
| Latvia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Anas <br />
| El Husseini <br />
| Lebanon <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gorjan <br />
| Jovanovski <br />
| Macedonia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mohomodou <br />
| Houssouba <br />
| Mali <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mohammed <br />
| Amarochan <br />
| Morocco <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Wim <br />
| Benes <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Otto <br />
| de Voogd <br />
| Netherlands / Estonia<br />
| <br> <br />
| [http://ottodv.com/contact Contact]<br />
| [http://ottodv.com/g+ Google+] [http://ottodv.com/tt Twitter]<br />
|-<br />
| Anthonie Nico <br />
| Kensen <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tim <br />
| Maks Van der Broek <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Marien <br />
| Zwart <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hatem <br />
| Zyoud <br />
| Palestine <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hubert <br />
| Gajewski <br />
| Poland <br />
| Aviary.pl <br />
| hgajewski@aviary.pl <br />
| [http://hubertgajewski.com hubertgajewski.com], [https://twitter.com/hubertgajewski @hubertgajewski]<br />
|-<br />
| Krzysztof <br />
| Glebowicz <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Grzegorz <br />
| Glogowski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Adrian <br />
| Kalla <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lukasz <br />
| Kluj <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Krzysztof <br />
| Kurzawski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sara <br />
| Prussak <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Katarzyna <br />
| Stawarz <br />
| Poland <br />
| l10n <br />
| <br> <br />
| @falkowata<br />
|-<br />
| Marek <br />
| Stępień <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Leszek Teo <br />
| Zyczkowski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Krzysztof <br />
| Wróblewski <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefania <br />
| Chiorean <br />
| Romania <br />
| Firefox Mobile, Personas, Promotion, ReMo <br />
| [mailto:ichiorean@mozilla.com IoanaChiorean]; ([mailto:chiorean.ioana@gmail.com Gmail]) <br />
| [https://twitter.com/#!/ioana_cis/ twitter]<br />
|-<br />
| Valentin <br />
| Gosu <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laurian <br />
| Gridinoc <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Lakatos <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alina <br />
| Mierluș <br />
| Interwebs <br />
| opening communities, public spaces, civic/public engagement <br />
| contact [at] alinamierlus [dot] com <br />
| @alina_mierlus<br />
|-<br />
| Alexandru <br />
| Szasz <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tiberiu <br />
| Turbureanu <br />
| Romania <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Konstantin A. <br />
| Lepikhov <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexander <br />
| Slovesnik <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alex <br />
| Rodionov <br />
| Russia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mouhamoudou Moustapha <br />
| Camara <br />
| Senegal <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Branislav <br />
| Rozbora <br />
| Slovakia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vlado <br />
| Valastiak <br />
| Slovakia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vito <br />
| Smolej <br />
| Slovenia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Nino <br />
| Vranešič <br />
| Slovenia <br />
| <br> <br />
| nino@mozilla.si <br />
| @ninovranesic<br />
|-<br />
| Dwayne <br />
| Bailey <br />
| South Africa <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Hugo <br />
| Acosta <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Inma <br />
| Barrios <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Bengoa <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Edu <br />
| Gamonal <br />
| Catalonia <br />
| l10n-ca <br />
| egamonal a softcatala.cat <br />
| @_egamonal<br />
|-<br />
| Pedro <br />
| García Rodríguez <br />
| Spain <br />
| l10n:es-ES QA Thunderbird<br />
| pgarcia@mozilla-hispano.org <br />
| @breaking_pitt<br />
|-<br />
| Fernando <br />
| Garcia Gomez <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Toni <br />
| Hermoso Pulido <br />
| Catalonia <br />
| l10n:ca, Promotion <br />
| <br> <br />
| @toniher<br />
|-<br />
| Guillermo <br />
| López <br />
| Spain <br />
| l10n:es-ES <br />
| willyaranda@mozilla-hispano.org <br />
| @willyaranda<br />
|-<br />
| Rubén <br />
| MartÃn <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Berni <br />
| Melero <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Elena <br />
| Palomo <br />
| Spain <br />
| <br> <br />
| palomo.elena@gmail.com<br> <br />
| @velvetbites<br><br />
|-<br />
| Joaquim <br />
| Perez Noguer <br />
| Catalonia <br />
| l10n:ca <br />
| joaquimperez a softcatala.org <br />
| @qpnoguer<br />
|-<br />
| Francisco <br />
| Picolini <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Stefan <br />
| Hermes <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mikael <br />
| Hiort af Ornäs <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Markus <br />
| Magnuson <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| HÃ¥kan <br />
| Waara <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Patrick <br />
| Brunschwig <br />
| Switzerland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jean-Yves <br />
| Perrier <br />
| Switzerland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Sofien <br />
| Chaabouni <br />
| Tunisia <br />
| <br> <br />
| chaabouni.sofien@gmail.com <br />
| @chaasof<br />
|-<br />
| Jebdnoun <br />
| Melek <br />
| Tunisia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Selim <br />
| Sumlu <br />
| Turkey <br />
| <br> <br />
| selim at sum.lu <br />
| @maxcoder<br />
|-<br />
| Chris <br />
| Coulson <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| William <br />
| Duyck <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matt <br />
| Jukes <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ed <br />
| Morley <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ian <br />
| Neal <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Timothy <br />
| Babych <br />
| Ukraine <br />
| l10n:uk, l10n tools<br />
| tim.babych@gmail.com <br />
| @tymofiy, http://clear.com.ua<br />
|-<br />
| Kristin <br />
| Baird <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Chris <br />
| Beard <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeff <br />
| Beatty <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Dave <br />
| Berz <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| David <br />
| Boswell <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Zbigniew <br />
| Braniecki <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Diane <br />
| Branson <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Fabien <br />
| Cazenave <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pascal <br />
| Chevrel <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Desigan <br />
| Chinniah <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Debbie <br />
| Cohen <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Carmen <br />
| Collins <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mary <br />
| Colvig <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jess <br />
| Davis <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Milos <br />
| Dinic <br />
| Serbia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Justin <br />
| Dow <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Raymond <br />
| Etornam Agbeame <br />
| Ghana <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Patrick <br />
| Finch <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jane <br />
| Finette <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ty <br />
| Flanagan <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ibai <br />
| Garcia <br />
| Spain <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Dumitru <br />
| Gherman <br />
| USA <br />
| IT Operations <br />
| dgherman[at]mozilla[dot]com <br />
| <br><br />
|-<br />
| Jeff <br />
| Griffiths <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jeff <br />
| Griffiths <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jack <br />
| Guo <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jason <br />
| Haas <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Hawkes <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Axel <br />
| Hecht <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Christian <br />
| Heilmann <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Ludovic <br />
| Hirlimann <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Havi <br />
| Hoffman <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Chris <br />
| Hofmann <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bobby <br />
| Holley <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matjaz <br />
| Horvat <br />
| Slovenia <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Barbara <br />
| Hueppe <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Spencer <br />
| Hui <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| John <br />
| Jensen <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lufei <br />
| Jia <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gregory <br />
| Jost <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Erica <br />
| Jostedt <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Kaiser <br />
| Austria <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gen <br />
| Kanai <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Makoto <br />
| Kato <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philip <br />
| Kewisch <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Marcia <br />
| Knous <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| John Curtis <br />
| Koenig <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mounir <br />
| Lamouri <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Delphine <br />
| Lebedel <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Christian <br />
| Legnitto <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michelle <br />
| Luna <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Gervase <br />
| Markham <br />
| UK <br />
| An eclectic collection of things <br />
| gerv@mozilla.org <br />
| [http://blog.gerv.net/ http://blog.gerv.net/]<br />
|-<br />
| David <br />
| Mason <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Laura <br />
| Mesa <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Aleksandr <br />
| Milewski <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Vivien <br />
| Nicolas <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Johnathan <br />
| Nightingale <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tristan <br />
| Nitot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matej <br />
| Novak <br />
| Canada <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Robert <br />
| Nyman <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Pierros <br />
| Papadeas <br />
| Greece <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jay <br />
| Patel <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| JB <br />
| Piacentino <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Alexandre <br />
| Poirot <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Valerie <br />
| Ponell <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| WIlliam <br />
| Quiviger <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Arky <br />
| Rakesh <br />
| India <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Anthony <br />
| Ricaud <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lucas <br />
| Rocha <br />
| Brazil <br />
| Firefox Mobile <br />
| lucasr@mozilla.com <br />
| http://lucasr.org / @lucasratmundo<br />
|-<br />
| Paul <br />
| Rouget <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Irina <br />
| Sandu <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Philipp <br />
| Schmidt <br />
| South Africa <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Margaret <br />
| Schroeder <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Justin <br />
| Scott <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tara <br />
| Shahian <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Henrik <br />
| Skupin <br />
| Germany <br />
| Test Automation <br />
| hskupin@mozilla.com <br />
| @whimboo<br />
|-<br />
| David <br />
| Tenser <br />
| Sweden <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Kosaka <br />
| Tetsuya <br />
| Japan <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Michelle <br />
| Thorne <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Lee <br />
| Tom <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Abdulkadir <br />
| Topal <br />
| Germany <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Jorge <br />
| Villalobos <br />
| Costa Rica <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Erik <br />
| Vold <br />
| Canada <br />
| <br> <br />
| erikvvold@gmail.com <br />
| @erikvold<br />
|-<br />
| Philip <br />
| von Weitershausen <br />
| Netherlands <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Andrew <br />
| Williamson <br />
| UK <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Arzhel <br />
| Younsi <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Matthew <br />
| Zeier <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Rachel <br />
| Zhang <br />
| China <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Malolepszy <br />
| Stas <br />
| Poland <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Tim <br />
| Taubert <br />
| Germany <br />
| Firefox <br />
| ttaubert@mozilla.com <br />
| @ttaubert<br />
|-<br />
| Stephanie <br />
| Schipper <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Susan <br />
| Chen <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Bret <br />
| Reckard <br />
| USA <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Mike <br />
| Hommey <br />
| France <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Axel<br />
| Grude <br />
| Ireland <br />
| AMO-Editor, MDN, Extensions (QuickFolders, QuickPasswords, Zombie Keys) <br />
| ([mailto:&#97;&#120;&#101;l.grude@gmail.com Gmail]) <br />
| <br><br />
|-<br />
| Ken <br />
| Barbalace <br />
| USA <br />
| AMO Editor <br />
| ken@EnvironmentalChemistry.com<br />
| http://EnvironmentalChemistry.com<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2011-11-01&diff=363115
SeaMonkey/StatusMeetings/2011-11-01
2011-11-01T15:17:42Z
<p>Mnyromyr: /* Mnyromyr */</p>
<hr />
<div><small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small><br />
<br />
'''SeaMonkey Meeting Details'''<br />
<br />
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=11&year=2011&hour=13&min=0&sec=0&p1=0 1 November, 2011, 13:00 UTC]<br />
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]<br />
<br />
== Agenda ==<br />
* Who's taking minutes? -> '''Ratty'''<br />
* Nominees for Friends of the Fish Tank?<br />
** Tony Mechelynck for organising the bug event.<br />
** Px and Mnyromyr for lots of bug triaging during the bug event.<br />
** Callek and the Mozilla RelEng team for services above and beyond the call of duty in getting SeaMonkey builds working again.<br />
** Please note ''A person or entity can't be nominated twice in a row''.<br />
<br />
=== Action Items ===<br />
(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.<br />
<br />
'''NEW'''<br />
<br />
'''OPEN'''<br />
* '''IanN''' to write the "Friends of the Fish Tank" F.A.Q.<br />
<br />
'''CLOSED'''<br />
<br />
=== Status of the SeaMonkey Buildbot Master and Tree ===<br />
Previously on Buffy the Vampire Slayer, Callek said:<br />
* "What Happened?"<br />
** One XServe that hosts "Parallels" in Mozilla died, taking down with it all the data it housed. (There were two problems to appear here)<br />
<br />
* "What VM's does that translate to?"<br />
** Parallels can only reliably (for us anyway) run 7 total VM's; Which are: 1 "Linux32 CentOS5.0 Buildbot Master", 2 "Linux32 Centos5.0 Buildbot Slaves", 1 "Linux64 Centos5.0 Buildbot Slave", 3 "Win32 w2k3 Buildbot Slaves"<br />
<br />
* "Don't you have refimages?"<br />
** Sadly we don't have anything current. I had just updated both our masters software heavily and our Linux32 slaves.<br />
<br />
* "What can I do to help?"<br />
** Not sure there is too much build/releng related that you, in general can do. I suspect it will be more work in the end to get many of you into the loop after thinking about it. Primarily because it would mean me handholding a bit, getting you access to the machines with <secret-password> and meaning I'll want to verify that nothing is out of whack....<br />
<br />
* "What does this mean for our Release"<br />
** We missed one planned beta because of this, and at the rate things are going, we'll miss the next beta date too. We might likely be delaying the Gecko 8 ship date at that, I'm trying hard to make that not the case though.<br />
<br />
* "Where do we stand with the machine right now?"<br />
** Mozilla IT gave me rough ETA of Wednesday 26th before Host OS is installed setup, VM software is installed (parallels or maybe even VMWare Fusion, not sure), and we get the base image/OS's installed for the now-lost VM's. I'll start work on the buildmaster as _SOON_ as I get confirmation the system is ready.<br />
<br />
* "Can you get help from other Mozilla Departments?"<br />
** Maybe, I have sent a request to Mozilla Releng to see if they can spare a few machines, and give me access to them to do my release-work at the least. So I can have a beta/release out with relatively little delay. I don't really expect an answer until after their weekly meeting on Monday 24th, if even that early. Beyond that there really is no easy path to getting additional help.<br />
<br />
* "When can I land my patches?"<br />
** I'll make the confirmation now, that any patches slated to land on aurora/beta and any [simple] regression fixes, and any bustage fixes, can land with explicit approval. And all must have been tested locally. Where possible also test other OS's as well. If in doubt, ask yourself if the risk of it landing with no builds is worse than the trouble the bug causes. (since at this point, I'm unsure if any beta patches will be able to have coverage before my next/final beta build)<br />
<br />
'''Current Situation'''<br />
(To be updated)<br />
* Callek has a temporary buildbot master up and running and we have been able to get some builds out. Some nightlies are available from the 30th onwards.<br />
* We still don't have all machines up (about half of the Linux and Windows machines and the Linux64 machine are still missing), but we have some coverage on the major platforms. Windows will just take longer than usual to build due to only having 2 of 5 machines up.<br />
* Tree is still closed unless you have tested things up, down, and sideways.<br />
** Callek says we can open the tree to METERED.<br />
** What's METERED? Approval required and try to not get too many pushes in short order.<br />
<br />
=== Release Train ===<br />
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).<br />
** Patch updated. Awaiting review. Although it looks like Corey has taken over the bug from Callek.<br />
* 2.5b3 shipped 14th October.<br />
* Target date for 2.5 is around 8th November. (Note: This sounds unlikely given the tree closure. Update/new ETA needed.)<br />
* We expect at least 1 more beta, perhaps two. The buildbot master being down (went down two weeks ago) may cause a delay and we will probably miss one beta. buildbot down is {{Bug|695278}}). A brief chat with IT indicates it may require a colo-trip. Unfortunately only one person really knows how to administer the machine those VM's are on.<br />
* '''Update:''' Callek is on the East Coast so he's probably been hit by storm related power cuts. We will need to discuss VM administration when Callek is back online.<br />
<br />
=== Extensions Compatibility Tracking ===<br />
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] created and maintained by InvisibleSmiley, with help from some community members like DERoss.<br />
** Recent changes can be found [[SeaMonkey/AddonCompat#Recent_Changes_to_This_Page|here]].<br />
** <nowiki>[InvisibleSmiley:]</nowiki> The External Sources part is still TODO, help appreciated.<br />
* Enigmail provides versions for release (AMO) and all branches ([http://enigmail.mozdev.org/download/nightly.php.html Enigmail nightly page])<br />
* Lightning currently provides versions for the current stable release (AMO), Aurora and trunk (both [http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/ FTP]) and Beta ([https://developer.mozilla.org/en/Calendar/Calendar_Versions Calendar Versions page]).<br />
* The latest Firebug is now fully compatible but still not flagged as such on AMO (which seems to depend on automatic tests being set up and run on the Firebug side, see [http://code.google.com/p/fbug/issues/detail?id=4430 Issue 4430])<br />
** <nowiki>[InvisibleSmiley]</nowiki> Use Firebug 1.9 pre-releases for 2.4 and later (maybe even earlier SM versions; haven't checked)<br />
* Besides the above, we should also take a look at other add-ons that are important for our users when they switch to 2.x.<br />
** Useful query: [https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular]<br />
* InvisibleSmiley '''still needs help''' updating and maintaining the [[SeaMonkey/FAQ|FAQ]] Wiki page. Everybody please help update it, so it stays current. '''mcsmurf''' says he'll help.<br />
* KaiRo created a [[SeaMonkey/Features|SeaMonkey Features]] page and sub-pages for all those that are in development.<br />
* We need to get the Addon Compatibility page finished and better communicate how to keep Lightning and Enigmail updated since unfortunately the only versions provided on AMO are for the current stable release. People keep coming back reporting that e.g. Lightning stopped working on trunk, Aurora or Beta. But since it contains binary components, Lightning easily breaks if you don't retrieve the matching install file yourself.<br />
** <nowiki>[InvisibleSmiley]</nowiki> AMO currently has a Lightning version compatible with SM Beta (1.0rc2)<br />
<br />
We should also add some information on this to the release notes of future betas.<br />
<br />
=== 2.x (Last, Current, Next) ===<br />
<br />
==== 2.x Follow-ups and Issues ====<br />
Moved to [[SeaMonkey:2.x-followup|a separate page]].<br />
<br />
==== 2.4 ====<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%2B open tracking] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%3F tracking requests] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.4 targeted] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_seamonkey23&type0-1-0=substring&value0-4-0=fixed&list_id=1409055&field0-1-0=cf_status_seamonkey24&field0-0-0=target_milestone&type0-4-0=notsubstring&resolution=FIXED&value0-3-0=fixed&query_format=advanced&value0-2-0=seamonkey2.3%20seamonkey2.2%20seamonkey2.1%20seamonkey2.0&value0-1-0=fixed&type0-3-0=notsubstring&field0-2-0=target_milestone&field0-4-0=cf_status_seamonkey22&type0-0-0=anywordssubstr&value0-0-0=seamonkey2.4%20seamonkey2.5%20seamonkey2.6&type0-2-0=nowordssubstr fixed] (26)<br><br />
<br />
* The [[SeaMonkey/Features/2.4|New 2.4 Features]] page has a comprehensive list of features.<br />
* 2.4.x had ~64500 ADU yesterday and 2.4.1 has had ~217,100 downloads so far.<br />
** vs. 5644 on 2.3, 3792 on 2.2, 1247 on 2.1 and 18788 on 2.0. So, in the last two weeks, ~?k have migrated to 2.3 and above.<br />
<br />
==== 2.Next ====<br />
* Please make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when we to do a release we can be sure that we don't miss anything.<br />
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.<br />
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.<br />
* Remember to help update the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go along.<br />
<br />
=== Feature List, Planning ===<br />
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 12 fixed, 102 triaged.<br />
* Very good triage effort during the Seamonkey Halloween Bug Event.<br />
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!<br />
<br />
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 32 review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 14 super-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 7 feedback]<br />
<br />
Major wanted/needed features:<br />
<br />
==== Active ====<br />
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN].<br />
** Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.<br />
** IanN will need to poke some people about reviews not happening quickly enough.<br />
** There is still a patch that needs checking in but both the patches there are for SM (even though it is a TB bug :P).<br />
** IanN is still wading through the unpicking of Composer/Mail Compose code in the dependent bugs. After that he will be reworking his customising patches.<br />
* de-RDF {{bug|654864}} has been finished and landed on all development branches, including 2.3. Still to do:<br />
** Neil wanted to follow up on some listener issues. This is being addressed in {{bug|669203}.<br />
** for the selection issue, see what the TB guys come up with in {{bug|669203}}.<br />
* {{bug|477845}} Build a standalone (Comm-central) Composer. [kaze]<br />
** ''kaze'' has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.<br />
** ''IanN'' was supposed to help get builds working with <tt>--enable-tests</tt>.<br />
*** Will look into this once he gets his customization patches reworked.<br />
<br />
==== Needing help, Unowned, Stalled ====<br />
* Kill-RDF:<br />
** {{Bug|657607}} Port jminta's kill-rdf to SeaMonkey where applicable Part 2 ['''meta'''].<br />
** {{Bug|657604}} Remove the RDF global object. [''serge'']<br />
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.<br />
** SM UI needed, unowned, helpwanted.<br />
* {{bug|449728}} Drag tabs between windows.<br />
* {{bug|477840}} Backport KompoZer to Composer (Depends on {{bug|477845}}).<br />
** kaze has done a ton of work there. We still need to work out some organizational issues. At the moment there is no active interest from MoMo for bringing standalone composer into comm-central. That's something we (KaiRo and kaze) will have to negotiate with the Thunderbird team (Standard8).<br />
* {{Bug|507841}} Port Bug 422814 - Make account configuration quick, easy, and more secure (autoconfig, Quick Account Setup).<br />
* {{Bug|533908}} SeaMonkey Mail: tabs not restored [misak].<br />
* {{Bug|523274}} Complete new default theme icon set.<br />
** A [https://bugzilla.mozilla.org/show_bug.cgi?id=523274#c0 list of TODO icons] is up in the bug.<br />
* {{Bug|526210}} Update the icon set for the SeaMonkey Modern Theme.<br />
** {{Bug|548778}} New communicator icons (based on Strata theme) for SeaMonkey. Some proposed icons got posted, we should take a look how to get that contribution into the product.<br />
** The rest is unowned so far.<br />
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.<br />
** Note: Our location bar history doesn't and can't use autocomplete at all.<br />
* {{Bug|677484}} Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.<br />
* {{Bug|654009}} Reply to list: automatically determine From: address<br />
** Note: The actual task here is to port {{Bug|45715}} "Reply to List" [button/(context) menu item]<br />
* {{Bug|664309}} Make the built-in ChatZilla display a cZ icon in SeaMonkey (now ''helpwanted'')<br />
<br />
=== Roundtable - Personal Status Updates ===<br />
<br />
Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status). <br />
<br />
==== Aqualon ====<br />
==== asrail ====<br />
==== Callek ====<br />
==== ewong ====<br />
<br />
*'''Fixed''':<br />
** {{bug|513900}} - executable permissions for data files (port bug 461322 to SeaMonkey) <br />
<br />
*'''Checkin-needed''':<br />
** {{bug|678979}} - Remove README.txt from release packages<br />
<br />
*'''Needs Review''':<br />
** {{bug|102275}} - Number untitled pages. (sr)<br />
** {{bug|682537}} - Don't remove jemalloc lib when building with MOZ_MEMORY<br />
<br />
*'''Working On''':<br />
** {{bug|78357}} - Account wizard doesn't have place to enter port info<br />
** {{bug|608103}} - Message Display panel clipped on Windows 7 <br />
** {{bug|670561}} - show profile path in profile manager.<br />
** {{bug|675589}} - Group all session restore menu items together. <br />
<br />
*'''To Do''':<br />
** {{bug|633937}} - Port {{bug|562048}} to suite.<br />
<br />
*'''BackBurner''':<br />
** {{bug|649952}} - Port |Bug 609824 - Re-add Bloglines to the feed reader options| to SeaMonkey<br />
<br />
==== IanN ====<br />
* Usual testing, reviewing and commenting.<br />
* Bug triaging during bug event.<br />
* Fixed:<br />
** {{Bug|682580}} Remove suite's dependency on nsTryToClose.js (non-editor part)<br />
** {{Bug|680805}} Share edit menus between Composer, Plain Text Editor and Messenger Compose<br />
** {{Bug|688765}} Move file menu from editorOverlay to editingOverlay<br />
** {{Bug|690145}} Move CharsetPopupMenu code from editorOverlay to editingOverlay<br />
* Waiting for review on:<br />
** {{Bug|638643}} Remove obsolete EditorToggleParagraphMarks from editor.js<br />
* Waiting for additional review on:<br />
** {{Bug|694027}} Move Editor toolbar buttons from editorOverlay to editingOverlay<br />
* Reviewed and waiting for feedback from mobile peer:<br />
** {{Bug|689253}} Update en-GB for Mobile 8.0 (comm-aurora)<br />
* Working on:<br />
** {{Bug|695842}} Move Editor startup/shutdown functions to editingOverlay<br />
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition<br />
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay<br />
** {{Bug|657234}} Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay<br />
** File/Folder selection in windows.<br />
* To Do:<br />
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.<br />
** Prefs-in-a-tab.<br />
<br />
==== InvisibleSmiley ====<br />
* Fixed:<br />
** {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** {{bug|694144}} Port syncAddDevice fixes from {{bug|690532}} and {{bug|689428}}<br />
** {{bug|696633}} Port |Bug 678586 - Trigger a delayed sync after pairing a new device|<br />
** reviewed {{bug|684537}} Port {{bug|626949}} |Sync UI: Style generic change dialogs like the setup and Add a Device wizards| to suite<br />
<br />
* Working On:<br />
** check in once tree reopens:<br />
*** {{bug|695523}} Port |Bug 564560 - Sync dialogs should persist position|<br />
*** {{bug|693210}} Add support for some keys to Advanced Search<br />
*** {{bug|696731}} Properties context menu option in Bookmarks Manager does nothing when the embedded properties pane is already open<br />
*** {{bug|696598}} Add default value for extensions.autoDisableScopes<br />
** address post-landing comment on {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** look into {{bug|698038}} Update Preferences help for the new section to control crash report submission.<br />
** {{bug|688953}} Create/Update 2.5 Release Notes<br />
** track {{bug|687316}} (Remaining) Sync changes to port to Suite<br />
<br />
* Needs Coordination:<br />
** investigate whether we need to adapt our Places code for the FF/Toolkit changes from {{bug|696159}} and/or {{bug|692120}}<br />
<br />
==== KaiRo ====<br />
==== mcsmurf ====<br />
==== Misak ====<br />
Working on keeping Session Restore in sync with FF:<br />
* {{Bug|698267}} Port {{Bug|694378}} [session restore fails when selectedWindow > number of windows]<br />
* {{Bug|698274}} {{Bug|665260}} [Store start time in sessionstore data]<br />
* {{Bug|698276}} Port {{Bug|686065}} [Don't clear nsSessionStartup::sessionType after the session startup phase finished]<br />
* {{Bug|698557}} Port {{Bug|665702}} [expose session information in getBrowserState]<br />
<br />
==== Mnyromyr ====<br />
<br />
Current:<br />
* {{Bug|356742}} [cocoa] Sheets are offscreen if opened when all windows closed<br />
* {{Bug|610509}} Make fullscreen mode really fullscreen.<br />
* Sidebar planning<br />
<br />
==== MReimer ====<br />
Working on implementing Opera API for adding sidebars from websites ({{Bug|697799}}).<br />
<br />
==== Neil ====<br />
==== Ratty ====<br />
Done:<br />
* {{Bug|696400}} Close Places containers after use (Sync Suite with changes from {{Bug|641531}}).<br />
* {{Bug|696542}} Remove obsolete preference places.database.cache_to_memory_percentage (q.v. {{Bug|674210}}).<br />
* {{Bug|697124}} Update the Context menu video items.<br />
* {{Bug|697453}} Allow setting report submission preference via XPCOM.<br />
<br />
Working on:<br />
* {{Bug|698187}} Sync pluginCrashedUI with changes from Firefox ({{Bug|665196}} and {{Bug|688083}}).<br />
<br />
ToDo:<br />
* {{Bug|694786}} Remove hard coded dependency on xpinstallItemGeneric.png from notification.xml<br />
* Remove modern dependency on winstripe images, copy them into the comm-central tree instead.<br />
<br />
Other:<br />
* Bug triage and Bug discussions.<br />
* End user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].<br />
<br />
==== Ricardo ====<br />
==== sgautherie ====<br />
*Fixed (<i>or in-progress</i>) MailNews Core bugs:<br />
**<i>{{bug|694371}} [c-c] "Warning: package error or possible missing or unnecessary file:" : 4 "VC80" files</i><br />
<br />
==== Stanimir ====<br />
Done:<br />
* {{Bug|576402}} Add small icons for Address Book toolbar to Classic theme.<br />
Investigating:<br />
* {{Bug|489067}} Allow inline background color in Message Compose.<br />
<br />
==== stefanh ====<br />
==== tonymec ====<br />
* Organized and ran a very successful SeaMonkey Halloween Bug Event (like a testday) on #bugday on the 30th of October.<br />
** Special thanks to Px and Mnyromyr for lots of bug triaging during the bug event.<br />
<br />
=== Any other business? ===<br />
* Need to review [http://www.seamonkey-project.org/dev/project-areas project areas]<br />
** '''IanN''' has put out a final draft of the project areas list, and will then confirm that anyone who is not in the loop already has been consulted.<br />
* Extended Support Releases (ESR)<br />
** At the moment looks like that will be based off either Gecko 8 or 9 so potentially that will be either 2.5 or 2.6 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.5/2.6.<br />
** Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.<br />
** A ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer both what Gecko it will be based on, and what MoCo's general plans for their marketing/target/ support-levels etc are.<br />
* '''Geolocation'''.<br />
** <s>We can probably start working on this. Callek hasn't verified all the minutia there yet, but if someone wants to begin work, he can devote slightly more of his time to it.</s><br />
** Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central. For comm-beta all we need to do is to add <tt>pref("geo.wifi.uri", "https://www.google.com/loc/json");</tt> to browser-prefs.js.<br />
* The '''Halloween Bug Event''' happened at the end of last week.<br />
** tonymec will be producing some stats from the event.<br />
* Who is going to MozCamp Europe 2011? (sgautherie, KaiRo, mcsmurf, Mnyromyr and stefanh)<br />
**Anything planned w.r.t. SeaMonkey?<br />
* Who is going to MozCamp Asia 2011? (Ratty).<br />
** Nothing planned w.r.t. SeaMonkey, but Ratty might give a lightning talk.</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2011-11-01&diff=363059
SeaMonkey/StatusMeetings/2011-11-01
2011-11-01T13:47:52Z
<p>Mnyromyr: /* Mnyromyr */</p>
<hr />
<div><small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small><br />
<br />
'''SeaMonkey Meeting Details'''<br />
<br />
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=11&year=2011&hour=13&min=0&sec=0&p1=0 1 November, 2011, 13:00 UTC]<br />
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]<br />
<br />
== Agenda ==<br />
* Who's taking minutes? -> '''Ratty'''<br />
* Nominees for Friends of the Fish Tank?<br />
** Tony Mechelynck for organising the bug event.<br />
** Px and Mnyromyr for lots of bug triaging during the bug event.<br />
** Callek and the Mozilla RelEng team for services above and beyond the call of duty in getting SeaMonkey builds working again.<br />
** Please note ''A person or entity can't be nominated twice in a row''.<br />
<br />
=== Action Items ===<br />
(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.<br />
<br />
'''NEW'''<br />
<br />
'''OPEN'''<br />
* '''IanN''' to write the "Friends of the Fish Tank" F.A.Q.<br />
<br />
'''CLOSED'''<br />
<br />
=== Status of the SeaMonkey Buildbot Master and Tree ===<br />
Previously on Buffy the Vampire Slayer, Callek said:<br />
* "What Happened?"<br />
** One XServe that hosts "Parallels" in Mozilla died, taking down with it all the data it housed. (There were two problems to appear here)<br />
<br />
* "What VM's does that translate to?"<br />
** Parallels can only reliably (for us anyway) run 7 total VM's; Which are: 1 "Linux32 CentOS5.0 Buildbot Master", 2 "Linux32 Centos5.0 Buildbot Slaves", 1 "Linux64 Centos5.0 Buildbot Slave", 3 "Win32 w2k3 Buildbot Slaves"<br />
<br />
* "Don't you have refimages?"<br />
** Sadly we don't have anything current. I had just updated both our masters software heavily and our Linux32 slaves.<br />
<br />
* "What can I do to help?"<br />
** Not sure there is too much build/releng related that you, in general can do. I suspect it will be more work in the end to get many of you into the loop after thinking about it. Primarily because it would mean me handholding a bit, getting you access to the machines with <secret-password> and meaning I'll want to verify that nothing is out of whack....<br />
<br />
* "What does this mean for our Release"<br />
** We missed one planned beta because of this, and at the rate things are going, we'll miss the next beta date too. We might likely be delaying the Gecko 8 ship date at that, I'm trying hard to make that not the case though.<br />
<br />
* "Where do we stand with the machine right now?"<br />
** Mozilla IT gave me rough ETA of Wednesday 26th before Host OS is installed setup, VM software is installed (parallels or maybe even VMWare Fusion, not sure), and we get the base image/OS's installed for the now-lost VM's. I'll start work on the buildmaster as _SOON_ as I get confirmation the system is ready.<br />
<br />
* "Can you get help from other Mozilla Departments?"<br />
** Maybe, I have sent a request to Mozilla Releng to see if they can spare a few machines, and give me access to them to do my release-work at the least. So I can have a beta/release out with relatively little delay. I don't really expect an answer until after their weekly meeting on Monday 24th, if even that early. Beyond that there really is no easy path to getting additional help.<br />
<br />
* "When can I land my patches?"<br />
** I'll make the confirmation now, that any patches slated to land on aurora/beta and any [simple] regression fixes, and any bustage fixes, can land with explicit approval. And all must have been tested locally. Where possible also test other OS's as well. If in doubt, ask yourself if the risk of it landing with no builds is worse than the trouble the bug causes. (since at this point, I'm unsure if any beta patches will be able to have coverage before my next/final beta build)<br />
<br />
'''Current Situation'''<br />
(To be updated)<br />
* Callek has a temporary buildbot master up and running and we have been able to get some builds out.<br />
* We have nightlies available from the 30th onwards. Monday/Tuesday is the earliest for linux64 builds.<br />
* Tree is still closed unless you have tested things up, down, and sideways.<br />
<br />
=== Release Train ===<br />
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).<br />
** Patch updated. Awaiting review. Although it looks like Corey has taken over the bug from Callek.<br />
* 2.5b3 shipped 14th October.<br />
* Target date for 2.5 is around 8th November. (Note: This sounds unlikely given the tree closure. Update/new ETA needed.)<br />
* We expect at least 1 more beta, perhaps two. The buildbot master being down (went down two weeks ago) may cause a delay or even make us miss one beta. buildbot down is {{Bug|695278}}). A brief chat with IT indicates it may require a colo-trip. Unfortunately only one person really knows how to administer the machine those VM's are on. (Update?)<br />
<br />
=== Extensions Compatibility Tracking ===<br />
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] created and maintained by InvisibleSmiley, with help from some community members like DERoss.<br />
** Recent changes can be found [[SeaMonkey/AddonCompat#Recent_Changes_to_This_Page|here]].<br />
** <nowiki>[InvisibleSmiley:]</nowiki> The External Sources part is still TODO, help appreciated.<br />
* Enigmail provides versions for release (AMO) and all branches ([http://enigmail.mozdev.org/download/nightly.php.html Enigmail nightly page])<br />
* Lightning currently provides versions for the current stable release (AMO), Aurora and trunk (both [http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/ FTP]) and Beta ([https://developer.mozilla.org/en/Calendar/Calendar_Versions Calendar Versions page]).<br />
* The latest Firebug is now fully compatible but still not flagged as such on AMO (which seems to depend on automatic tests being set up and run on the Firebug side, see [http://code.google.com/p/fbug/issues/detail?id=4430 Issue 4430])<br />
** <nowiki>[InvisibleSmiley]</nowiki> Use Firebug 1.9 pre-releases for 2.4 and later (maybe even earlier SM versions; haven't checked)<br />
* Besides the above, we should also take a look at other add-ons that are important for our users when they switch to 2.x.<br />
** Useful query: [https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular]<br />
* InvisibleSmiley '''still needs help''' updating and maintaining the [[SeaMonkey/FAQ|FAQ]] Wiki page. Everybody please help update it, so it stays current. '''mcsmurf''' says he'll help.<br />
* KaiRo created a [[SeaMonkey/Features|SeaMonkey Features]] page and sub-pages for all those that are in development.<br />
* We need to get the Addon Compatibility page finished and better communicate how to keep Lightning and Enigmail updated since unfortunately the only versions provided on AMO are for the current stable release. People keep coming back reporting that e.g. Lightning stopped working on trunk, Aurora or Beta. But since it contains binary components, Lightning easily breaks if you don't retrieve the matching install file yourself.<br />
** <nowiki>[InvisibleSmiley]</nowiki> AMO currently has a Lightning version compatible with SM Beta (1.0rc2)<br />
<br />
We should also add some information on this to the release notes of future betas.<br />
<br />
=== 2.x (Last, Current, Next) ===<br />
<br />
==== 2.x Follow-ups and Issues ====<br />
Moved to [[SeaMonkey:2.x-followup|a separate page]].<br />
<br />
==== 2.4 ====<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%2B open tracking] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%3F tracking requests] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.4 targeted] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_seamonkey23&type0-1-0=substring&value0-4-0=fixed&list_id=1409055&field0-1-0=cf_status_seamonkey24&field0-0-0=target_milestone&type0-4-0=notsubstring&resolution=FIXED&value0-3-0=fixed&query_format=advanced&value0-2-0=seamonkey2.3%20seamonkey2.2%20seamonkey2.1%20seamonkey2.0&value0-1-0=fixed&type0-3-0=notsubstring&field0-2-0=target_milestone&field0-4-0=cf_status_seamonkey22&type0-0-0=anywordssubstr&value0-0-0=seamonkey2.4%20seamonkey2.5%20seamonkey2.6&type0-2-0=nowordssubstr fixed] (26)<br><br />
<br />
* The [[SeaMonkey/Features/2.4|New 2.4 Features]] page has a comprehensive list of features.<br />
* 2.4.x had ~64500 ADU yesterday and 2.4.1 has had ~217,100 downloads so far.<br />
** vs. 5644 on 2.3, 3792 on 2.2, 1247 on 2.1 and 18788 on 2.0. So, in the last two weeks, ~?k have migrated to 2.3 and above.<br />
<br />
==== 2.Next ====<br />
* Please make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when we to do a release we can be sure that we don't miss anything.<br />
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.<br />
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.<br />
* Please help updating the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go.<br />
<br />
=== Feature List, Planning ===<br />
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 12 fixed, 102 triaged.<br />
* Very good triage effort over the Seamonkey Halloween Bug Event.<br />
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!<br />
<br />
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 32 review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 14 super-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 7 feedback]<br />
<br />
Major wanted/needed features:<br />
<br />
==== Active ====<br />
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN].<br />
** Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.<br />
** IanN will need to poke some people about reviews not happening quickly enough.<br />
** IanN has done as much unpicking of Composer/Mail Compose code as possible in the dependent bugs, so will be reworking his customising patches.<br />
* de-RDF {{bug|654864}} has been finished and landed on all development branches, including 2.3. Still to do:<br />
** Neil wanted to follow up on some listener issues<br />
** for the selection issue, see what the TB guys come up with in {{bug|669203}}<br />
* {{bug|477845}} Build a standalone (Comm-central) Composer. [kaze]<br />
** ''kaze'' has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.<br />
** ''IanN'' was supposed to help get builds working with <tt>--enable-tests</tt>.<br />
*** Will look into this once he gets his customization patches reworked.<br />
<br />
==== Needing help, Unowned, Stalled ====<br />
* Kill-RDF:<br />
** {{Bug|657607}} Port jminta's kill-rdf to SeaMonkey where applicable Part 2 ['''meta'''].<br />
** {{Bug|657604}} Remove the RDF global object. [''serge'']<br />
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.<br />
** SM UI needed, unowned, helpwanted.<br />
* {{bug|449728}} Drag tabs between windows.<br />
* {{bug|477840}} Backport KompoZer to Composer (Depends on {{bug|477845}}).<br />
** kaze has done a ton of work there. We still need to work out some organizational issues. At the moment there is no active interest from MoMo for bringing standalone composer into comm-central. That's something we (KaiRo and kaze) will have to negotiate with the Thunderbird team (Standard8).<br />
* {{Bug|507841}} Port Bug 422814 - Make account configuration quick, easy, and more secure (autoconfig, Quick Account Setup).<br />
* {{Bug|533908}} SeaMonkey Mail: tabs not restored [misak].<br />
* {{Bug|523274}} Complete new default theme icon set.<br />
** A [https://bugzilla.mozilla.org/show_bug.cgi?id=523274#c0 list of TODO icons] is up in the bug.<br />
* {{Bug|526210}} Update the icon set for the SeaMonkey Modern Theme.<br />
** {{Bug|548778}} New communicator icons (based on Strata theme) for SeaMonkey. Some proposed icons got posted, we should take a look how to get that contribution into the product.<br />
** The rest is unowned so far.<br />
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.<br />
** Note: Our location bar history doesn't and can't use autocomplete at all.<br />
* {{Bug|677484}} Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.<br />
* {{Bug|654009}} Reply to list: automatically determine From: address<br />
** Note: The actual task here is to port {{Bug|45715}} "Reply to List" [button/(context) menu item]<br />
* {{Bug|664309}} Make the built-in ChatZilla display a cZ icon in SeaMonkey (now ''helpwanted'')<br />
<br />
=== Roundtable - Personal Status Updates ===<br />
<br />
Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status). <br />
<br />
==== Aqualon ====<br />
==== asrail ====<br />
==== Callek ====<br />
==== ewong ====<br />
<br />
*'''Fixed''':<br />
** {{bug|513900}} - executable permissions for data files (port bug 461322 to SeaMonkey) <br />
<br />
*'''Checkin-needed''':<br />
** {{bug|678979}} - Remove README.txt from release packages<br />
<br />
*'''Needs Review''':<br />
** {{bug|102275}} - Number untitled pages. (sr)<br />
** {{bug|682537}} - Don't remove jemalloc lib when building with MOZ_MEMORY<br />
<br />
*'''Working On''':<br />
** {{bug|78357}} - Account wizard doesn't have place to enter port info<br />
** {{bug|608103}} - Message Display panel clipped on Windows 7 <br />
** {{bug|670561}} - show profile path in profile manager.<br />
** {{bug|675589}} - Group all session restore menu items together. <br />
<br />
*'''To Do''':<br />
** {{bug|633937}} - Port {{bug|562048}} to suite.<br />
<br />
*'''BackBurner''':<br />
** {{bug|649952}} - Port |Bug 609824 - Re-add Bloglines to the feed reader options| to SeaMonkey<br />
<br />
==== IanN ====<br />
* Usual testing, reviewing and commenting.<br />
* Bug triaging during bug event.<br />
* Fixed:<br />
** {{Bug|682580}} Remove suite's dependency on nsTryToClose.js (non-editor part)<br />
** {{Bug|680805}} Share edit menus between Composer, Plain Text Editor and Messenger Compose<br />
** {{Bug|688765}} Move file menu from editorOverlay to editingOverlay<br />
** {{Bug|690145}} Move CharsetPopupMenu code from editorOverlay to editingOverlay<br />
* Waiting for review on:<br />
** {{Bug|638643}} Remove obsolete EditorToggleParagraphMarks from editor.js<br />
* Waiting for additional review on:<br />
** {{Bug|694027}} Move Editor toolbar buttons from editorOverlay to editingOverlay<br />
* Reviewed and waiting for feedback from mobile peer:<br />
** {{Bug|689253}} Update en-GB for Mobile 8.0 (comm-aurora)<br />
* Working on:<br />
** {{Bug|695842}} Move Editor startup/shutdown functions to editingOverlay<br />
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition<br />
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay<br />
** {{Bug|657234}} Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay<br />
** File/Folder selection in windows.<br />
* To Do:<br />
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.<br />
** Prefs-in-a-tab.<br />
<br />
==== InvisibleSmiley ====<br />
* Fixed:<br />
** {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** {{bug|694144}} Port syncAddDevice fixes from {{bug|690532}} and {{bug|689428}}<br />
** {{bug|696633}} Port |Bug 678586 - Trigger a delayed sync after pairing a new device|<br />
** reviewed {{bug|684537}} Port {{bug|626949}} |Sync UI: Style generic change dialogs like the setup and Add a Device wizards| to suite<br />
<br />
* Working On:<br />
** check in once tree reopens:<br />
*** {{bug|695523}} Port |Bug 564560 - Sync dialogs should persist position|<br />
*** {{bug|693210}} Add support for some keys to Advanced Search<br />
*** {{bug|696731}} Properties context menu option in Bookmarks Manager does nothing when the embedded properties pane is already open<br />
*** {{bug|696598}} Add default value for extensions.autoDisableScopes<br />
** address post-landing comment on {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** look into {{bug|698038}} Update Preferences help for the new section to control crash report submission.<br />
** {{bug|688953}} Create/Update 2.5 Release Notes<br />
** track {{bug|687316}} (Remaining) Sync changes to port to Suite<br />
<br />
* Needs Coordination:<br />
** investigate whether we need to adapt our Places code for the FF/Toolkit changes from {{bug|696159}} and/or {{bug|692120}}<br />
<br />
==== KaiRo ====<br />
==== mcsmurf ====<br />
==== Misak ====<br />
Working on keeping Session Restore in sync with FF:<br />
* {{Bug|698267}} Port {{Bug|694378}} [session restore fails when selectedWindow > number of windows]<br />
* {{Bug|698274}} {{Bug|665260}} [Store start time in sessionstore data]<br />
* {{Bug|698276}} Port {{Bug|686065}} [Don't clear nsSessionStartup::sessionType after the session startup phase finished]<br />
* {{Bug|698557}} Port {{Bug|665702}} [expose session information in getBrowserState]<br />
<br />
==== Mnyromyr ====<br />
<br />
Current:<br />
* {{Bug|356742}} [cocoa] Sheets are offscreen if opened when all windows closed<br />
* {{Bug|610509}} Make fullscreen mode really fullscreen.<br />
* Sidebar planning<br />
* other<br />
<br />
==== MReimer ====<br />
Working on implementing Opera API for adding sidebars from websites ({{Bug|697799}}).<br />
<br />
==== Neil ====<br />
==== Ratty ====<br />
Done:<br />
* {{Bug|696400}} Close Places containers after use (Sync Suite with changes from {{Bug|641531}}).<br />
* {{Bug|696542}} Remove obsolete preference places.database.cache_to_memory_percentage (q.v. {{Bug|674210}}).<br />
* {{Bug|697124}} Update the Context menu video items.<br />
* {{Bug|697453}} Allow setting report submission preference via XPCOM.<br />
<br />
Working on:<br />
* {{Bug|698187}} Sync pluginCrashedUI with changes from Firefox ({{Bug|665196}} and {{Bug|688083}}).<br />
<br />
ToDo:<br />
* {{Bug|694786}} Remove hard coded dependency on xpinstallItemGeneric.png from notification.xml<br />
* Remove modern dependency on winstripe images, copy them into the comm-central tree instead.<br />
<br />
Other:<br />
* Bug triage and Bug discussions.<br />
* End user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].<br />
<br />
==== Ricardo ====<br />
==== sgautherie ====<br />
*Fixed (<i>or in-progress</i>) MailNews Core bugs:<br />
**<i>{{bug|694371}} [c-c] "Warning: package error or possible missing or unnecessary file:" : 4 "VC80" files</i><br />
<br />
==== Stanimir ====<br />
Done:<br />
* {{Bug|576402}} Add small icons for Address Book toolbar to Classic theme.<br />
Investigating:<br />
* {{Bug|489067}} Allow inline background color in Message Compose.<br />
<br />
==== stefanh ====<br />
==== tonymec ====<br />
* Organized and ran a very successful SeaMonkey Halloween Bug Event (like a testday) on #bugday on the 30th of October.<br />
** Special thanks to Px and Mnyromyr for lots of bug triaging during the bug event.<br />
<br />
=== Any other business? ===<br />
* Need to review [http://www.seamonkey-project.org/dev/project-areas project areas]<br />
** '''IanN''' will put out a final draft of the project areas list this week, and then confirm that anyone who is not in the loop already has been consulted.<br />
* Extended Support Releases (ESR)<br />
** At the moment looks like that will be based off either Gecko 8 or 9 so potentially that will be either 2.5 or 2.6 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.5/2.6.<br />
** Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.<br />
** A ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer both what Gecko it will be based on, and what MoCo's general plans for their marketing/target/ support-levels etc are.<br />
* We can probably start working on Geolocation. Callek hasn't verified all the minutia there yet, but if someone wants to begin work, he can devote slightly more of his time to it.<br />
* Another bug event happened at the end of last week.<br />
*Who is going to MozCamp Europe 2011? (sgautherie, ...)<br />
**Anything planned w.r.t. SeaMonkey?</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2011-11-01&diff=363033
SeaMonkey/StatusMeetings/2011-11-01
2011-11-01T13:18:17Z
<p>Mnyromyr: /* Mnyromyr */</p>
<hr />
<div><small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small><br />
<br />
'''SeaMonkey Meeting Details'''<br />
<br />
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=01&month=11&year=2011&hour=13&min=0&sec=0&p1=0 1 November, 2011, 13:00 UTC]<br />
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]<br />
<br />
== Agenda ==<br />
* Who's taking minutes? -> '''TBD'''<br />
* Nominees for Friends of the Fish Tank?<br />
** Tony Mechelynck for organising the bug event.<br />
** Px and Mnyromyr for lots of bug triaging during the bug event.<br />
** Callek for services above and beyond the call of duty in getting builds working again.<br />
** Please note ''A person or entity can't be nominated twice in a row''.<br />
<br />
=== Action Items ===<br />
(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.<br />
<br />
'''NEW'''<br />
<br />
'''OPEN'''<br />
* '''IanN''' to write the "Friends of the Fish Tank" F.A.Q.<br />
<br />
'''CLOSED'''<br />
<br />
=== Status of the SeaMonkey Buildbot Master and Tree ===<br />
Previously on Buffy the Vampire Slayer, Callek said:<br />
* "What Happened?"<br />
** One XServe that hosts "Parallels" in Mozilla died, taking down with it all the data it housed. (There were two problems to appear here)<br />
<br />
* "What VM's does that translate to?"<br />
** Parallels can only reliably (for us anyway) run 7 total VM's; Which are: 1 "Linux32 CentOS5.0 Buildbot Master", 2 "Linux32 Centos5.0 Buildbot Slaves", 1 "Linux64 Centos5.0 Buildbot Slave", 3 "Win32 w2k3 Buildbot Slaves"<br />
<br />
* "Don't you have refimages?"<br />
** Sadly we don't have anything current. I had just updated both our masters software heavily and our Linux32 slaves.<br />
<br />
* "What can I do to help?"<br />
** Not sure there is too much build/releng related that you, in general can do. I suspect it will be more work in the end to get many of you into the loop after thinking about it. Primarily because it would mean me handholding a bit, getting you access to the machines with <secret-password> and meaning I'll want to verify that nothing is out of whack....<br />
<br />
* "What does this mean for our Release"<br />
** We missed one planned beta because of this, and at the rate things are going, we'll miss the next beta date too. We might likely be delaying the Gecko 8 ship date at that, I'm trying hard to make that not the case though.<br />
<br />
* "Where do we stand with the machine right now?"<br />
** Mozilla IT gave me rough ETA of Wednesday 26th before Host OS is installed setup, VM software is installed (parallels or maybe even VMWare Fusion, not sure), and we get the base image/OS's installed for the now-lost VM's. I'll start work on the buildmaster as _SOON_ as I get confirmation the system is ready.<br />
<br />
* "Can you get help from other Mozilla Departments?"<br />
** Maybe, I have sent a request to Mozilla Releng to see if they can spare a few machines, and give me access to them to do my release-work at the least. So I can have a beta/release out with relatively little delay. I don't really expect an answer until after their weekly meeting on Monday 24th, if even that early. Beyond that there really is no easy path to getting additional help.<br />
<br />
* "When can I land my patches?"<br />
** I'll make the confirmation now, that any patches slated to land on aurora/beta and any [simple] regression fixes, and any bustage fixes, can land with explicit approval. And all must have been tested locally. Where possible also test other OS's as well. If in doubt, ask yourself if the risk of it landing with no builds is worse than the trouble the bug causes. (since at this point, I'm unsure if any beta patches will be able to have coverage before my next/final beta build)<br />
<br />
=== Release Train ===<br />
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).<br />
** Patch updated. Awaiting review. Although it looks like Corey has taken over the bug from Callek.<br />
* 2.5b3 shipped 14th October.<br />
* Target date for 2.5 is around 8th November. (Note: This sounds unlikely given the tree closure. Update/new ETA needed.)<br />
* We expect at least 1 more beta, perhaps two. The buildbot master being down (went down two weeks ago) may cause a delay or even make us miss one beta. buildbot down is {{Bug|695278}}). A brief chat with IT indicates it may require a colo-trip. Unfortunately only one person really knows how to administer the machine those VM's are on. (Update?)<br />
<br />
=== Extensions Compatibility Tracking ===<br />
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] created and maintained by InvisibleSmiley, with help from some community members like DERoss.<br />
** Recent changes can be found [[SeaMonkey/AddonCompat#Recent_Changes_to_This_Page|here]].<br />
** <nowiki>[InvisibleSmiley:]</nowiki> The External Sources part is still TODO, help appreciated.<br />
* Enigmail provides versions for release (AMO) and all branches ([http://enigmail.mozdev.org/download/nightly.php.html Enigmail nightly page])<br />
* Lightning currently provides versions for the current stable release (AMO), Aurora and trunk (both [http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/ FTP]) and Beta ([https://developer.mozilla.org/en/Calendar/Calendar_Versions Calendar Versions page]).<br />
* The latest Firebug is now fully compatible but still not flagged as such on AMO (which seems to depend on automatic tests being set up and run on the Firebug side, see [http://code.google.com/p/fbug/issues/detail?id=4430 Issue 4430])<br />
** <nowiki>[InvisibleSmiley]</nowiki> Use Firebug 1.9 pre-releases for 2.4 and later (maybe even earlier SM versions; haven't checked)<br />
* Besides the above, we should also take a look at other add-ons that are important for our users when they switch to 2.x.<br />
** Useful query: [https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=popular]<br />
* InvisibleSmiley '''still needs help''' updating and maintaining the [[SeaMonkey/FAQ|FAQ]] Wiki page. Everybody please help update it, so it stays current. '''mcsmurf''' says he'll help.<br />
* KaiRo created a [[SeaMonkey/Features|SeaMonkey Features]] page and sub-pages for all those that are in development.<br />
* We need to get the Addon Compatibility page finished and better communicate how to keep Lightning and Enigmail updated since unfortunately the only versions provided on AMO are for the current stable release. People keep coming back reporting that e.g. Lightning stopped working on trunk, Aurora or Beta. But since it contains binary components, Lightning easily breaks if you don't retrieve the matching install file yourself.<br />
** <nowiki>[InvisibleSmiley]</nowiki> AMO currently has a Lightning version compatible with SM Beta (1.0rc2)<br />
<br />
We should also add some information on this to the release notes of future betas.<br />
<br />
=== 2.x (Last, Current, Next) ===<br />
<br />
==== 2.x Follow-ups and Issues ====<br />
Moved to [[SeaMonkey:2.x-followup|a separate page]].<br />
<br />
==== 2.4 ====<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%2B open tracking] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey24&type0-0-0=equals&value0-0-0=%3F tracking requests] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.4 targeted] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_seamonkey23&type0-1-0=substring&value0-4-0=fixed&list_id=1409055&field0-1-0=cf_status_seamonkey24&field0-0-0=target_milestone&type0-4-0=notsubstring&resolution=FIXED&value0-3-0=fixed&query_format=advanced&value0-2-0=seamonkey2.3%20seamonkey2.2%20seamonkey2.1%20seamonkey2.0&value0-1-0=fixed&type0-3-0=notsubstring&field0-2-0=target_milestone&field0-4-0=cf_status_seamonkey22&type0-0-0=anywordssubstr&value0-0-0=seamonkey2.4%20seamonkey2.5%20seamonkey2.6&type0-2-0=nowordssubstr fixed] (26)<br><br />
<br />
* The [[SeaMonkey/Features/2.4|New 2.4 Features]] page has a comprehensive list of features.<br />
* 2.4.x had ~64500 ADU yesterday and 2.4.1 has had ~217,100 downloads so far.<br />
** vs. 5644 on 2.3, 3792 on 2.2, 1247 on 2.1 and 18788 on 2.0. So, in the last two weeks, ~?k have migrated to 2.3 and above.<br />
<br />
==== 2.Next ====<br />
* Please make sure that anything that landed on comm-beta (for TB) or mozilla-beta (for FF) which affected non-shared code and which fixed regressions will be fixed on our side, too. Please mark bugs we feel *need* to land on a particular train tracking+ or tracking? so that when we to do a release we can be sure that we don't miss anything.<br />
** Priority should be given to fixing regressions ASAP. Also keep an eye on and prioritize bugs to be ported from FF/TB that land on branches (Aurora, Beta). We need to keep an eye especially on Session Restore, Sync, Tabbrowser and Address Book.<br />
** Be careful not to break code shared with Thunderbird, otherwise patches might have to be backed out of string frozen repositories.<br />
* Please help updating the [[SeaMonkey/Features/2.5|New 2.5 Features]] page as we go.<br />
<br />
=== Feature List, Planning ===<br />
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 36 new, 12 fixed, 102 triaged.<br />
* Very good triage effort over the Seamonkey Halloween Bug Event.<br />
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!<br />
<br />
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 32 review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 14 super-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 7 feedback]<br />
<br />
Major wanted/needed features:<br />
<br />
==== Active ====<br />
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN].<br />
** Progressing slowly, still waiting on reviews from TB side. Full customization has to go to 2.next (currently 2.6 but could be pushed back further) as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.<br />
** IanN will need to poke some people about reviews not happening quickly enough.<br />
** IanN has done as much unpicking of Composer/Mail Compose code as possible in the dependent bugs, so will be reworking his customising patches.<br />
* de-RDF {{bug|654864}} has been finished and landed on all development branches, including 2.3. Still to do:<br />
** Neil wanted to follow up on some listener issues<br />
** for the selection issue, see what the TB guys come up with in {{bug|669203}}<br />
* {{bug|477845}} Build a standalone (Comm-central) Composer. [kaze]<br />
** ''kaze'' has done a bit of work in this bug recently. Building on Windows works. Now supports debug builds on Linux if tests are disabled (--disable-tests). Still a lot to do.<br />
** ''IanN'' was supposed to help get builds working with <tt>--enable-tests</tt>.<br />
*** Will look into this once he gets his customization patches reworked.<br />
<br />
==== Needing help, Unowned, Stalled ====<br />
* Kill-RDF:<br />
** {{Bug|657607}} Port jminta's kill-rdf to SeaMonkey where applicable Part 2 ['''meta'''].<br />
** {{Bug|657604}} Remove the RDF global object. [''serge'']<br />
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.<br />
** SM UI needed, unowned, helpwanted.<br />
* {{bug|449728}} Drag tabs between windows.<br />
* {{bug|477840}} Backport KompoZer to Composer (Depends on {{bug|477845}}).<br />
** kaze has done a ton of work there. We still need to work out some organizational issues. At the moment there is no active interest from MoMo for bringing standalone composer into comm-central. That's something we (KaiRo and kaze) will have to negotiate with the Thunderbird team (Standard8).<br />
* {{Bug|507841}} Port Bug 422814 - Make account configuration quick, easy, and more secure (autoconfig, Quick Account Setup).<br />
* {{Bug|533908}} SeaMonkey Mail: tabs not restored [misak].<br />
* {{Bug|523274}} Complete new default theme icon set.<br />
** A [https://bugzilla.mozilla.org/show_bug.cgi?id=523274#c0 list of TODO icons] is up in the bug.<br />
* {{Bug|526210}} Update the icon set for the SeaMonkey Modern Theme.<br />
** {{Bug|548778}} New communicator icons (based on Strata theme) for SeaMonkey. Some proposed icons got posted, we should take a look how to get that contribution into the product.<br />
** The rest is unowned so far.<br />
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.<br />
** Note: Our location bar history doesn't and can't use autocomplete at all.<br />
* {{Bug|677484}} Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.<br />
* {{Bug|654009}} Reply to list: automatically determine From: address<br />
** Note: The actual task here is to port {{Bug|45715}} "Reply to List" [button/(context) menu item]<br />
* {{Bug|664309}} Make the built-in ChatZilla display a cZ icon in SeaMonkey (now ''helpwanted'')<br />
<br />
=== Roundtable - Personal Status Updates ===<br />
<br />
Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status). <br />
<br />
==== Aqualon ====<br />
==== asrail ====<br />
==== Callek ====<br />
==== ewong ====<br />
<br />
*'''Fixed''':<br />
** {{bug|513900}} - executable permissions for data files (port bug 461322 to SeaMonkey) <br />
<br />
*'''Checkin-needed''':<br />
** {{bug|678979}} - Remove README.txt from release packages<br />
<br />
*'''Needs Review''':<br />
** {{bug|102275}} - Number untitled pages. (sr)<br />
** {{bug|682537}} - Don't remove jemalloc lib when building with MOZ_MEMORY<br />
<br />
*'''Working On''':<br />
** {{bug|78357}} - Account wizard doesn't have place to enter port info<br />
** {{bug|608103}} - Message Display panel clipped on Windows 7 <br />
** {{bug|670561}} - show profile path in profile manager.<br />
** {{bug|675589}} - Group all session restore menu items together. <br />
<br />
*'''To Do''':<br />
** {{bug|633937}} - Port {{bug|562048}} to suite.<br />
<br />
*'''BackBurner''':<br />
** {{bug|649952}} - Port |Bug 609824 - Re-add Bloglines to the feed reader options| to SeaMonkey<br />
<br />
==== IanN ====<br />
* Usual testing, reviewing and commenting.<br />
* Bug triaging during bug event.<br />
* Fixed:<br />
** {{Bug|682580}} Remove suite's dependency on nsTryToClose.js (non-editor part)<br />
** {{Bug|680805}} Share edit menus between Composer, Plain Text Editor and Messenger Compose<br />
** {{Bug|688765}} Move file menu from editorOverlay to editingOverlay<br />
** {{Bug|690145}} Move CharsetPopupMenu code from editorOverlay to editingOverlay<br />
* Waiting for review on:<br />
** {{Bug|638643}} Remove obsolete EditorToggleParagraphMarks from editor.js<br />
* Waiting for additional review on:<br />
** {{Bug|694027}} Move Editor toolbar buttons from editorOverlay to editingOverlay<br />
* Reviewed and waiting for feedback from mobile peer:<br />
** {{Bug|689253}} Update en-GB for Mobile 8.0 (comm-aurora)<br />
* Working on:<br />
** {{Bug|695842}} Move Editor startup/shutdown functions to editingOverlay<br />
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition<br />
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay<br />
** {{Bug|657234}} Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay<br />
** File/Folder selection in windows.<br />
* To Do:<br />
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.<br />
** Prefs-in-a-tab.<br />
<br />
==== InvisibleSmiley ====<br />
* Fixed:<br />
** {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** {{bug|694144}} Port syncAddDevice fixes from {{bug|690532}} and {{bug|689428}}<br />
** {{bug|696633}} Port |Bug 678586 - Trigger a delayed sync after pairing a new device|<br />
** reviewed {{bug|684537}} Port {{bug|626949}} |Sync UI: Style generic change dialogs like the setup and Add a Device wizards| to suite<br />
<br />
* Working On:<br />
** check in once tree reopens:<br />
*** {{bug|695523}} Port |Bug 564560 - Sync dialogs should persist position|<br />
*** {{bug|693210}} Add support for some keys to Advanced Search<br />
*** {{bug|696731}} Properties context menu option in Bookmarks Manager does nothing when the embedded properties pane is already open<br />
*** {{bug|696598}} Add default value for extensions.autoDisableScopes<br />
** address post-landing comment on {{bug|674208}} Add a Properties context menu option to open the embedded properties pane in Bookmarks Manager<br />
** look into {{bug|698038}} Update Preferences help for the new section to control crash report submission.<br />
** {{bug|688953}} Create/Update 2.5 Release Notes<br />
** track {{bug|687316}} (Remaining) Sync changes to port to Suite<br />
<br />
* Needs Coordination:<br />
** investigate whether we need to adapt our Places code for the FF/Toolkit changes from {{bug|696159}} and/or {{bug|692120}}<br />
<br />
==== KaiRo ====<br />
==== mcsmurf ====<br />
==== Misak ====<br />
Working on keeping Session Restore in sync with FF:<br />
* {{Bug|698267}} Port {{Bug|694378}} [session restore fails when selectedWindow > number of windows]<br />
* {{Bug|698274}} {{Bug|665260}} [Store start time in sessionstore data]<br />
* {{Bug|698276}} Port {{Bug|686065}} [Don't clear nsSessionStartup::sessionType after the session startup phase finished]<br />
* {{Bug|698557}} Port {{Bug|665702}} [expose session information in getBrowserState]<br />
<br />
==== Mnyromyr ====<br />
<br />
Current:<br />
* {{Bug|356742}} [cocoa] Sheets are offscreen if opened when all windows closed<br />
* {{Bug|610509}} Make fullscreen mode really fullscreen.<br />
* Sidebar planning<br />
<br />
==== MReimer ====<br />
Working on implementing Opera API for adding sidebars from websites ({{Bug|697799}}).<br />
<br />
==== Neil ====<br />
==== Ratty ====<br />
Done:<br />
* {{Bug|696400}} Close Places containers after use (Sync Suite with changes from {{Bug|641531}}).<br />
* {{Bug|696542}} Remove obsolete preference places.database.cache_to_memory_percentage (q.v. {{Bug|674210}}).<br />
* {{Bug|697124}} Update the Context menu video items.<br />
* {{Bug|697453}} Allow setting report submission preference via XPCOM.<br />
<br />
Working on:<br />
* {{Bug|698187}} Sync pluginCrashedUI with changes from Firefox ({{Bug|665196}} and {{Bug|688083}}).<br />
<br />
ToDo:<br />
* {{Bug|694786}} Remove hard coded dependency on xpinstallItemGeneric.png from notification.xml<br />
* Remove modern dependency on winstripe images, copy them into the comm-central tree instead.<br />
<br />
Other:<br />
* Bug triage and Bug discussions.<br />
* End user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].<br />
<br />
==== Ricardo ====<br />
==== sgautherie ====<br />
*Fixed (<i>or in-progress</i>) MailNews Core bugs:<br />
**<i>{{bug|694371}} [c-c] "Warning: package error or possible missing or unnecessary file:" : 4 "VC80" files</i><br />
<br />
==== Stanimir ====<br />
Done:<br />
* {{Bug|576402}} Add small icons for Address Book toolbar to Classic theme.<br />
Investigating:<br />
* {{Bug|489067}} Allow inline background color in Message Compose.<br />
<br />
==== stefanh ====<br />
==== tonymec ====<br />
* Organized and ran a very successful SeaMonkey Halloween Bug Event (like a testday) on #bugday on the 30th of October.<br />
** Special thanks to Px and Mnyromyr for lots of bug triaging during the bug event.<br />
<br />
=== Any other business? ===<br />
* Need to review [http://www.seamonkey-project.org/dev/project-areas project areas]<br />
** '''IanN''' will put out a final draft of the project areas list this week, and then confirm that anyone who is not in the loop already has been consulted.<br />
* Extended Support Releases (ESR)<br />
** At the moment looks like that will be based off either Gecko 8 or 9 so potentially that will be either 2.5 or 2.6 for us. Assuming we have the machines, we will also have an ESR which might help move some of those still on 2.0 up to 2.5/2.6.<br />
** Our ESR should use the same branch as Firefox ESR so any Security and Stability "extended" fixes for Gecko will be picked up by the SeaMonkey ESR.<br />
** A ESR (Extended Security Release) may not be a given for us out of the gate. Callek thinks we should revisit that, separately, once it is clearer both what Gecko it will be based on, and what MoCo's general plans for their marketing/target/ support-levels etc are.<br />
* We can probably start working on Geolocation. Callek hasn't verified all the minutia there yet, but if someone wants to begin work, he can devote slightly more of his time to it.<br />
* Another bug event happened at the end of last week.<br />
*Who is going to MozCamp Europe 2011? (sgautherie, ...)<br />
**Anything planned w.r.t. SeaMonkey?</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Modules/MailNews_Core&diff=362257
Modules/MailNews Core
2011-10-29T14:19:56Z
<p>Mnyromyr: wrong Bugzilla name shortcut</p>
<hr />
<div>{{Module<br />
|name=Mail and News Backend<br />
|description=<br />
|owner=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu), [mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8)<br />
|peers= [mailto:mnyromyr@tprac.de Karsten Düsterloh] (mnyromyr), [mailto:kaie@kuix.de Kai Engert] (:kaie), [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:bugmail@asutherland.org Andrew Sutherland] (:asuth)<br />
|group=dev-apps-thunderbird<br />
|source_dirs=mailnews/<br />
|url=http://www.mozilla.org/mailnews/<br />
https://developer.mozilla.org/en/Mailnews_and_Mail_code_review_requirements<br />
|components=MailNews Core::Backend, Thunderbird::Account Manager, Thunderbird::Migration, MailNews Core::Account Manager, MailNews Core::Composition, MailNews Core::Filters, MailNews Core::Internationalization, MailNews Core::Networking, MailNews Core::Networking: POP, MailNews Core::Networking: SMTP, MailNews Core::Printing, MailNews Core::Profile Migration, MailNews Core::Search, MailNews Core::Security, MailNews Core::Simple MAPI<br />
}}<br />
<br />
===Sub Modules===<br />
<br />
{{Module<br />
|name=Addressbook<br />
|description=<br />
|owner=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8)<br />
|peers=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|source_dirs=mailnews/addressbook<br />
|components=MailNews Core::Address Book<br />
}}<br />
<br />
{{Module<br />
|name=Feeds<br />
|description=<br />
|owner=(Unowned - ask a MailNews Core owner or peer for review)<br />
|peers=[mailto:myk@mozilla.org Myk Melez]<br />
|source_dirs=mailnews/extensions/newsblog<br />
|components=MailNews Core::Feed Reader<br />
}}<br />
<br />
{{Module<br />
|name=IMAP handling code<br />
|description=<br />
|owner=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|peers=<br />
|source_dirs=mailnews/imap<br />
|components=MailNews Core::Networking: IMAP<br />
}}<br />
<br />
{{Module<br />
|name=GloDa <br />
|description=Global message database<br />
|owner=[mailto:bugmail@asutherland.org Andrew Sutherland] (:asuth)<br />
|peers=[mailto:jonathan.protzenko@gmail.com Jonathan Protzenko] (:protz)<br />
|source_dirs=mailnews/db/gloda, sqlite-backport, storage-backport<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=LDAP XPCOM SDK<br />
|description=<br />
|owner=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8)<br />
|peers=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|source_dirs=ldap/xpcom<br />
|components=MailNews Core::LDAP Integration<br />
}}<br />
<br />
{{Module<br />
|name=Message Database <br />
|description=MSF files<br />
|owner=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|peers=<br />
|source_dirs=mailnews/db<br />
|components=MailNews Core::Database<br />
}}<br />
<br />
{{Module<br />
|name=MIME Parser<br />
|description=RFC822 MIME Parser<br />
|owner=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|peers=[mailto:kaie@kuix.de Kai Engert] (:kaie), [mailto:bugmail@asutherland.org Andrew Sutherland] (:asuth)<br />
|source_dirs=mailnews/mime<br />
|components=MailNews Core::MIME<br />
}}<br />
<br />
{{Module<br />
|name=Movemail<br />
|description=<br />
|owner=(Unowned - ask a MailNews Core owner or peer for review)<br />
|peers=<br />
|source_dirs=mailnews/movemail<br />
|components=MailNews Core::Movemail<br />
}}<br />
<br />
{{Module<br />
|name=News<br />
|description=<br />
|owner=[mailto:Pidgeot18@gmail.com Joshua Cranmer] (:jcranmer)<br />
|peers=[mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|source_dirs=mailnews/news<br />
|components=MailNews Core::Networking: NNTP<br />
}}<br />
<br />
{{Module<br />
|name=Unit Testing Infrastructure<br />
|description=<br />
|owner=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8)<br />
|peers=<br />
|source_dirs=mailnews/test, mailnews/base/test<br />
|components=MailNews Core::Testing Infrastructure<br />
}}<br />
<br />
{{Module<br />
|name=Build Config: comm-central<br />
|description=Build & configuration for the comm-central repository<br />
|owner=[mailto:kairo@kairo.at Robert Kaiser]<br />
|peers=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8), [mailto:callek@gmail.com Justin Wood] (:callek), [mailto:gozer@mozillamessaging.com Philippe Chiasson] (:gozer)<br />
|group=dev-builds<br />
|source_dirs=build/, config/<br />
|url=https://wiki.mozilla.org/Comm-central_Build_System<br />
|components=MailNews Core::Build Config, Calendar::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=Import<br />
|description=<br />
|owner=(Unowned - ask a peer for review)<br />
|peers=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8), [mailto:bienvenu@nventure.com David Bienvenu] (:bienvenu)<br />
|group=<br />
|source_dirs=mailnews/import<br />
|url=<br />
|components=MailNews Core::Import <br />
}}<br />
<br />
{{Module<br />
|name=Attachments<br />
|description=Attachment handling and libmime<br />
|owner=(Unowned - ask a MailNews Core owner or peer for review)<br />
|peers=<br />
|group=<br />
|source_dirs=mailnews/mime<br />
|url=<br />
|components=MailNews Core::Attachments<br />
}}<br />
<br />
{{Module<br />
|name=Localization<br />
|description=<br />
|owner=(Unowned - ask a MailNews Core owner or peer for review)<br />
|peers=[mailto:bugzilla@standard8.plus.com Mark Banner] (:standard8)<br />
|group=<br />
|source_dirs=<br />
|url=<br />
|components=MailNews Core::Localization<br />
}}<br />
<br />
{{Module<br />
|name=S/MIME<br />
|description=Secure Multipurpose Internet Mail Extensions<br />
|owner=(Unowned - ask a peer for review)<br />
|peers=[mailto:kaie@kuix.de Kai Engert] (:kaie)<br />
|group=<br />
|source_dirs=mailnews/extensions/smime<br />
|url=<br />
|components=MailNews Core::Security: S/MIME<br />
}}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2011-04-19&diff=301644
SeaMonkey/StatusMeetings/2011-04-19
2011-04-21T22:04:13Z
<p>Mnyromyr: /* Mnyromyr */</p>
<hr />
<div><small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting &raquo;]]</small><br />
<br />
'''SeaMonkey Meeting Details'''<br />
<br />
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=19&month=4&year=2011&hour=12&min=0&sec=0&p1=0 April 19, 2011, 12:00 UTC]<br />
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]<br />
<br />
== Agenda ==<br />
* Who's taking minutes? -> '''Ratty'''<br />
* Nominees for Friends of the Fish Tank?<br />
** werwolf<br />
* Is there a step after nomination? a vote? a blackball?<br />
** How about we use whatever rules they are using for Friends of the Tree [http://weblogs.mozillazine.org/asa/archives/2007/08/friends_of_the.html]?<br />
** If we do it like "Friends of the Tree" in Mozilla, it's just the notion that it's there.<br />
** MoMo has been sending T-shirts to those people, but we can't afford that at this moment.<br />
<br />
=== Action Items ===<br />
(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.<br />
<br />
'''NEW'''<br />
* '''IanN''' to email Fallen to get some cooperation for getting a version of Lightning that is compatible with SeaMonkey 2.1 out on AMO.<br />
<br />
'''OPEN'''<br />
* Mnyromyr to coordinate the SeaMonkey response to this years Google Summer of Code.<br />
<br />
'''CLOSED'''<br />
<br />
'''K.I.V.'''<br />
* Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. We can still only wait on the Google front right now. Didn't hear anything about open Geolocation service yet. No easy solution in sight.<br />
** At the "State of the Map - Europe" OpenStreetMap conference, KaiRo will try to get people to team up and create an open service.<br />
<br />
=== SeaMonkey 2.0.14 ===<br />
<br />
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&keywords=fixed-seamonkey2.0.14&field0-0-0=cf_status_191&type0-0-0=nowords&value0-0-0=.19-fixed&field0-1-0=flagtypes.name&type0-1-0=equals&value0-1-0=blocking-seamonkey2.0.14%2B open blockers] (1)<br />
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&keywords=fixed-seamonkey2.0.14&field0-0-0=cf_status_191&type0-0-0=nowords&value0-0-0=.19-fixed&field0-1-0=flagtypes.name&type0-1-0=equals&value0-1-0=blocking-seamonkey2.0.14%3F blocker requests] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Toolkit&product=MailNews+Core&product=SeaMonkey&product=Other+Applications&field0-0-0=keywords&type0-0-0=anywords&value0-0-0=fixed-seamonkey2.0.14&field0-0-1=cf_status_191&type0-0-1=anywords&value0-0-1=.19-fixed fixed] (27)<br />
<br />
* Based on Gecko 1.9.1.19, target April 26, see [[Releases]], in sync with Firefox 3.5.19.<br />
* Pushed to "beta" overnight, no announcement for testers sent yet, any Council free to do it for me --[[User:Callek|Justin Wood (Callek)]]<br />
* We are dependent on Fx 3.5.19 so if they respin due to {{Bug|650522}} so must we.<br />
<br />
=== SeaMonkey 2.1 Beta 3 ===<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.1b3 targeted] (0)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&target_milestone=seamonkey2.1b3 fixed] (119)<br />
<br />
* Has been '''SHIPPED''' on 08 April, ~3660 downloads and ~940 ADU so far,<br />
<br />
=== SeaMonkey 2.1 ===<br />
<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=final%2B open blockers] (6)<br />
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_blocking_seamonkey21&type0-0-0=equals&value0-0-0=%3F blocker requests] (2)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.1final targeted] (2)<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&target_milestone=seamonkey2.1final fixed] (9)<br />
<br />
* Firefox 4.0 was released on 22nd March.<br />
* Don't fear being aggressive with blocker triage, If it isn't needed it doesn't block. By that same token, if you are able to fix a blocker please try and work on them before tackling any other bugs.<br />
* Help patches can go in at anytime.<br />
<br />
Further 2.1 scheduling:<br />
<br />
* Please help updating the [[SeaMonkey:Features:2.1|New 2.1 Features]] page as we go.<br />
* 2.1pre should be followed by our release (candidate), which most likely will be based on Gecko 2.0.1 (which is now available).<br />
* '''Callek''' has been working on getting comm-2.0 branch in place and live which will be used for SM2.1.<br />
** Branch process for comm-20 started on 18 April.<br />
* We should release within 6 weeks from FF4.<br />
** We're still on schedule for early May release.<br />
* There might not be any more official security updates to the 1.9.1 branch after the upcoming one, so we should get a stable release based on Mozilla 2.0 out as soon as we can.<br />
<br />
=== Feature List, Planning ===<br />
<br />
[http://dev.seamonkey.at/#bugstats Bug statistics] for last two (full) weeks: 44 new, 24 fixed, 24 triaged.<br />
* Good further triage targets could come out of looking at the [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- component bug counts], pick yours!<br />
<br />
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 33 review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 11 super-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 0 ui-review]<br />
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 6 feedback]<br />
<br />
Major wanted/needed features:<br />
<br />
==== 2.1 ====<br />
===== Active =====<br />
* {{Bug|570004}} Popup/"doorhanger" notifications [Neil].<br />
** Implementation moved to {{Bug|595810}}.<br />
** Only lwthemes doorhangers are left to do.<br />
** '''''NO''' l10n-impact''<br />
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN].<br />
** Moved to 2.next.<br />
<br />
We also should take a look at the other items on [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&&field0-0-0=cf_status_seamonkey21&type0-0-0=equals&value0-0-0=wanted 2.1-wanted]<br />
Also the [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_status_seamonkey21&type0-0-0=equals&value0-0-0=%3F nominations] need triaging.<br />
<br />
* We will need to take a close look at Lightning, which is mainly targeting Thunderbird.<br />
** Lightning 1.0b4 seems to be targeted to be Gecko 2.0-based.<br />
** Due to recent Lightning patches/fixes, Lightning nightlies are now working again on SM trunk.<br />
** '''IanN''' to email Fallen to get some cooperation for getting a version of Lightning that is compatible with SeaMonkey 2.1 out on AMO.<br />
<br />
==== 2.next ====<br />
<br />
===== Needing help, Unowned, Stalled =====<br />
* {{bug|460953}} kill-rdf port.<br />
* {{bug|436794}} Enable Mac OS X system address book per default and add UI.<br />
** SM UI needed, unowned, helpwanted.<br />
* {{bug|449728}} Drag tabs between windows.<br />
* {{bug|477845}} Build a standalone (Gecko 2.0) Composer. [kaze]<br />
** kaze is currently busy with his new job so doesn't have much time to spend on this.<br />
** {{bug|477840}} Backport KompoZer to Composer (Depends on {{bug|477845}}).<br />
** kaze has done a ton of work there. We still need to work out some organizational issues. At the moment there is no active interest from MoMo for bringing standalone composer into comm-central. That's something we (KaiRo and kaze) will have to negotiate with the Thunderbird team (dmose).<br />
* {{Bug|507841}} Port Bug 422814 - Make account configuration quick, easy, and more secure (autoconfig, Quick Account Setup).<br />
* {{Bug|533908}} SeaMonkey Mail: tabs not restored [misak].<br />
* {{Bug|523274}} Complete new default theme icon set.<br />
** A [https://bugzilla.mozilla.org/show_bug.cgi?id=523274#c0 list of TODO icons] is up in the bug.<br />
** MattATobin and MReimer <s>are</s>were looking into this.<br />
* {{Bug|526210}} Update the icon set for the SeaMonkey Modern Theme.<br />
** {{Bug|548778}} New communicator icons (based on Strata theme) for SeaMonkey. Some proposed icons got posted, we should take a look how to get that contribution into the product.<br />
** The rest is unowned so far.<br />
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.<br />
** No l10n impact<br />
** (InvisibleSmiley: ) Neil said "Actually our location bar history doesn't and can't use autocomplete at all.", moving to 2.next.<br />
<br />
For now only a drop zone for those that surely will not make 2.1 any more.<br />
<br />
===== Active =====<br />
<br />
* {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition [IanN].<br />
** A lot of untangling needs to go on between the 3 editors that we have. We can expect a bit of code cleanup for 2.1 but full customization has to go to 2.next as it needs work on TB too which is taking a while to get reviews on, plus feedback from kaze.<br />
<br />
=== Roundtable - Personal Status Updates ===<br />
<br />
Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status). <br />
<br />
==== Aqualon ====<br />
==== asrail ====<br />
==== Callek ====<br />
'''Release Engineering'''<br />
* '''Released: SeaMonkey 2.1 Beta 3 ({{Bug|647928}})'''.<br />
** {{Bug|648474}} Send out 2.1b3 announcement.<br />
* Fixed:<br />
** {{Bug|648202}} Fix the polling for comm-2.0, to poll against mozilla-2.0 release branch.<br />
** {{Bug|649280}} cb-sea-miniosx64-*: upgrade Yasm to v1.1 from v1.0.<br />
** {{Bug|649798}} change surf warning from nagios that results when hg is down.<br />
** {{Bug|650552}} Switch SeaMonkey 2.1 to build out of comm-2.0 and mozilla2.0.<br />
** {{Bug|650724}} Update the tree-closure hook for c-c based apps for comm-2.0.<br />
** {{Bug|650725}} Update comm-2.0 client.py to pull from mozilla-2.0 by default.<br />
** {{Bug|650727}} Disallow building on comm-2.0 without mozilla-2.0[ish] clone.<br />
** {{Bug|650729}} Update (and deploy) cctbpl changes for SeaMonkey2.1 (comm-2.0) branching.<br />
** {{Bug|650731}} Update repo location for nagios script for comm-2.0 nightly checks.<br />
* Working on:<br />
** {{Bug|631864}} Investigate why [or fix] mac (trunk) repacks being uploaded to mac/ rather than mac64/.<br />
** {{Bug|643324}} Enable the shared checkouts from CCMercurialBuildFactory.<br />
** {{Bug|646723}} Install kypM-ssh on windows slaves.<br />
** '''Build and release of SeaMonkey 2.0.14 ({{Bug|650598}}'''.<br />
''Other stuff''<br />
* Working on:<br />
** {{Bug|640464}} Develop a way for tests in mozilla-central to be overridden in a suite build.<br />
<br />
==== ewong ====<br />
<br />
*'''Fixed''':<br />
** {{bug|85655}} - paste into TO: line ignores email addresses after CR in compose window.<br />
** {{bug|451960}} - s/observes=/command=/g in /editor/ui/*<br />
** {{bug|479647}} - remove intl.charset.default from navigator.properties<br />
** {{Bug|601562}} - Update Modern theme from missingPlugin.css to PluginProblem.css<br />
** {{bug|647322}} - Port |Bug 640649 - Remove unused cmd_file| to SeaMonkey<br />
** {{bug|647685}} - mailNavigatorOverlay.xul is 60% script.<br />
<br />
*'''Checkin-needed''':<br />
** {{bug|366774}} - Remove unused preference bidi.characterset<br />
<br />
*'''Needs Review''':<br />
** {{bug|480696}} - Add ifdef MOZ_UPDATER for the app update preferences UI and help menu.<br />
<br />
*'''Working On''':<br />
** {{bug|56365}} - mailOverlay.xul abuses <script>...</script><br />
** {{bug|566440}} - APP Update dialog is to wide with modern<br />
<br />
*'''To Do''':<br />
** {{bug|633937}} - Port {{bug|562048}} to suite.<br />
<br />
*'''Investigating''':<br />
** {{bug|112356}} - No option to leave email messages on server when creating new account<br />
<br />
==== IanN ====<br />
* Usual testing, reviewing and commenting.<br />
* Fixed:<br />
** {{Bug|647481}} Remove nsInt64, nsUint64 and nsTime from comm-central<br />
** {{Bug|647000}} Remove use of nsAutoLock from comm-central (addressbook part)<br />
** {{Bug|647003}} Remove use of nsAutoLock from LDAP SDK code<br />
** {{Bug|638964}} Allow customization of formatting toolbar in Mail Composition [TB]<br />
** {{Bug|648720}} Build failure in ../mailnews/base/src/nsMsgRDFDataSource.cpp<br />
* Waiting for review on:<br />
** {{Bug|638643}} Remove obsolete EditorToggleParagraphMarks from editor.js<br />
** {{Bug|650885}} Make better use of menuitem and command elements relating to editing already in utilityOverlay<br />
* Waiting for comm-central to open:<br />
** {{Bug|643788}} Move cmd_exportToText, cmd_preview and cmd_editSendPage out of editorOverlay<br />
* Working on:<br />
** {{Bug|335375}} changing accesskey on a <broadcaster> via an overlay doesn't propagate to its <toolbarbutton><br />
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition<br />
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay.<br />
* To Do:<br />
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.<br />
** Prefs-in-a-tab.<br />
<br />
==== InvisibleSmiley ====<br />
* Fixed:<br />
** {{bug|647898}} Links from SeaMonkey Nightly Builds page are broken<br />
** {{bug|559891}} Update README for 2.1<br />
** {{bug|648723}} SeaMonkey "New for 2.1" links do nothing, maybe should be "Features/2.1"<br />
** {{bug|647937}} Create 2.1 Beta 3 Release Notes<br />
** {{bug|612172}} Update Modern for Sync UI<br />
** {{bug|647936}} Update SeaMonkey website for 2.1b3 release<br />
** {{bug|648781}} Add support for Firefox's -search command line option<br />
* Working On:<br />
** {{bug|615950}} Port FF4 Sync UI changes after initial set included in bug 576970<br />
<br />
==== KaiRo ====<br />
* Talked through some crash analysis workflows in a CrashKill team meeting to be able to explain those to the Socorro team on the all-hands.<br />
* Refined my thoughts on prioritizing work somewhat.<br />
* Regularly generated "explosiveness" reports locally and uploaded them, looked at signatures it brought up, filed bugs where needed, commented on others, tried to point some to the right people to get them fixed.<br />
* Attended the Mozilla all-hands and discussed a lot of status and planning with a number of people in the CrashKill and Socorro teams as well as other Mozilla employees.<br />
* Created wiki pages and filed bugs for some outcomes from all-hands discussions.<br />
* Helped the SeaMonkey 2.0.13 release by getting the announcements out the door ({{bug|644287}}).<br />
* Got the new SeaMonkey 2.1b3 and 2.1pre versions up on crash-stats ({{bug|647935}}).<br />
* Landed the SeaMonkey patch for installing built-in extensions into the profile ({{bug|627240}}).<br />
* Did some reviews for SeaMonkey build and release infrastructure.<br />
* Got the train rolling again on new build machines for SeaMonkey ({{bug|572395}}).<br />
* Had some discussions at the all-hands with Standard8, khuey, ted and others on how to go forward on the comm-central build system.<br />
* Did some more updates to EarlyBlue and LCARStrek for SeaMonkey 2.1 and, for the latter, some more work to get it to run on Firefox 4.<br />
* Cared that L10n dashboard works for SeaMonkey with both the 2.1-targeted "branch" and the development trunk going forward.<br />
* Signed off locales for the SeaMonkey 2.1 Beta 3 release ({{bug|647637}}).<br />
* Did a number of updates of the German localization to catch up with all the changes leading up to the L10n freeze for SeaMonkey 2.1, and completed those in time for the Beta 3 release.<br />
*As usual, [http://home.kairo.at/blog/ my blog] has more detailed status about my work, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps.<br />
<br />
==== mcsmurf ====<br />
==== Misak ====<br />
==== Mnyromyr ====<br />
* Did some reviews.<br />
* Working on Venkman {{Bug|452288}} Allow ignoring NS_ERROR_NO_INTERFACE errors.<br />
* This year's gSoC proposals for Mozilla as such are very weak in toto, ideas for mail/news related stuff are very scarce — some remotely related seek to improve instant messsaging in Instandbird. SeaMonkey received no student applications. :-(<br />
<br />
==== MReimer ====<br />
==== Neil ====<br />
Did some reviews.<br />
<br />
Fixed:<br />
* {{Bug|639338}} Unable to specify XBL modifiers for all possible mouse events. [Core]<br />
* {{Bug|641330}} maxrows="10" doesn't work.<br />
* {{Bug|642404}} <autocomplete disablehistory="false"> does not display correctly on Linux.<br />
* {{Bug|647877}} [SeaMonkey] mochitest-browser-chrome: browser_library_infoBox.js fails since 2011.04.02.<br />
* {{Bug|648101}} browser.tabs.insertRelatedAfterCurrent misses links opened in foreground.<br />
* {{Bug|648844}} localized text in extension download tooltip doesn't fit.<br />
Working on:<br />
* {{Bug|595810}} Centralise notifications for ease of conversion to doorhangers.<br />
* {{Bug|611503}} Constructing an nsTDependentString from an nsTAString makes no sense. [Core]<br />
* {{Bug|614479}} [trunk] Send To Mail Recipient not working, MAPI broken.<br />
* {{Bug|626716}} Remove VC7.1 support code. [Core]<br />
* {{Bug|650950}} Simplify DOMMouseScroll event handler [Firefox].<br />
<br />
==== Ratty ====<br />
Bugs fixed:<br />
* {{Bug|648738}} [Modern 2.1] mozapps/places/defaultFavicon.png.<br />
* {{Bug|648760}} [Modern 2.1] Implement aboutCache.css and aboutCacheEntry.css.<br />
Working on:<br />
* Updating the global styles in Modern.<br />
** {{Bug|650511}} [Modern 2.1] global fixes: autocomplete.css to menulist.css.<br />
Other:<br />
* Bug triage and Bug discussions.<br />
* End user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].<br />
<br />
==== Ricardo ====<br />
==== sgautherie ====<br />
*Fixed SeaMonkey (related) bugs:<br />
**{{bug|644433}} Bump SeaMonkey version on trunk for post-2.1 development<br />
*Fixed MailNews Core bugs:<br />
**{{bug|650852}} Add a COMM_2_0_BASE tag to comm-central (and comm-2.0)<br />
*Fixed (<i>or in-progress</i>) Core bugs:<br />
**{{bug|605701}} Make WIN32_REDIST_DIR support stricter and more explicit<br />
**{{bug|607544}} Remove DDRAW junk from configure, missed part<br />
**{{bug|647404}} automation.py: fix extractZip() and installExtension() issues from bug 573263, affecting bug 647394<br />
**{{bug|647414}} Distributed extensions should be automatically installed into temporary testing profile<br />
**<i>{{bug|228448}} Remove '=='/'!=' 'PR_FALSE'/'PR_TRUE'</i><br />
**<i>{{bug|508760}} Remove MSVC6 support from the tree</i><br />
**<i>{{bug|599748}} Remove custom |def check_call()|, now that Python 2.4 is unsupported</i><br />
<br />
==== stefanh ====<br />
* Did some reviews.<br />
* Working on:<br />
** {{Bug|621546}} [Mac Classic] Missing visual keyboard focus in MailNews filter edit dialog.<br />
** {{Bug|643323}} [Mac Default] Need disabled icon for 'Subscribe to This Page' in Bookmarks toolbar menu.<br />
** {{Bug|649136}} [Mac Default] directory.css shouldn't use old-style icons.<br />
** {{Bug|650642}} [Pinstripe] Make the filterdialog and the advanced search dialogs look better [TB].<br />
<br />
=== Any other business? ===<br />
* Another Triage Day or Triage Week.<br />
** A week was too long the last time. We don't have the resources to tie up for a week.<br />
** We should limit it to two or three days mid-week. Contiguous days would be better so as not to lose momentum.<br />
** Any Triage event is probably feasible only after the Easter Holidays.<br />
** '''tonymec''' says that around mid-May preferably Wednesday thru Friday would be doable for him. So we have provisionally blocked off 18th-20th May, but we will need to confirm this at next status meeting in a fortnight.<br />
** Tentative suggestion: European evenings (20h-24h CEST) three days in a row but we need Aqualon's feedback as he led the last Triage Event.</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode11:Brainstorming&diff=291226
Community:SummerOfCode11:Brainstorming
2011-03-15T20:34:50Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality. <br />
<br />
<b>Students: ideas approved by the SoC admins are [[Community:SummerOfCode11|here]].</b> You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) <b>You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.</b><br />
<br />
==How To Make Good Suggestions==<br />
<br />
Before adding an idea to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Links to ideas lists from previous years]].<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Camino==<br />
<br />
See the [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects Camino Summer of Code page] for project suggestions.<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Score-based filtering<br />
|You can filter on quite some terms, but you can't weigh them. A scoring system will allow a much finer control, eg. it would be just a property score with a range of maybe 1..1000, along with some new conditions <br />
[is ]<br />
[isn't ]<br />
Score [is lower than ][\/] [<value in range>]<br />
[is lower than or equal to ]<br />
[is greater than ]<br />
[is greater than or equal to]<br />
and actions<br />
[Increment score by]<br />
[Decrement score by][\/] [<value in range>]<br />
[Set score to ]<br />
Each message would start with a score of 500 before filters get applied.<br />
<br />
This feature will require MailNews Core C++ hacking.<br />
<br />
Related:<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=151622 Bug 151622] "filters that score messages"<br />
|Karsten "Mnyromyr" Düsterloh<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|}<br />
<br />
==Instantbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|JavaScript Implementation of IM protocols<br />
|Goal: Implement new protocols in JavaScript, or create more stable implementations of existing ones.<br />
<br />
Instantbird 0.3 will support protocol plugins implemented in JavaScript in addition to the C libpurple plugins used before. The student will either add support for new protocols in Instantbird (if so, explain why this protocol matters) or reimplement in JavaScript protocols that are currently poorly supported by libpurple (if so, explain what will be better supported in the new implementation, or why the current implementation is broken). All new protocol plugins will go through a strict code review to ensure high code quality. The student working on new protocols should take every opportunity to improve the code and APIs shared by all JS protocol plugins.<br />
|Florian Quèze<br />
|Florian Quèze or Patrick Cloke<br />
| IRC and Twitter protocols have been (or are in the process of) being implemented and should not be considered.<br />
|-<br />
|Account import wizard<br />
|Goal: Ease the pain of switching to Instantbird<br />
<br />
Lots of users don't try a new IM client only because they don't want to spend time reconfiguring all their IM accounts. Being able to import accounts from other clients installed on the system would help Instantbird adoption. The student should focus on the dominant IM clients (Windows Live Messenger, AIM, ...) and on the other multi network IM clients (Digsby, Pidgin, Trillian, Miranda, ...). The student will need to study the way other IM clients store their profile data (reverse engineering may be required), think of an architecture to share as much code as possible between the various import modules, and implement import modules for some clients<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Indexed Logs<br />
|Goal: Create an easily search-able and sync-able storage for IM logs.<br />
<br />
A student working on this project will implement a new log storage back-end in Instantbird using SQLite. The format should allow efficient search (reuse code from Gloda in Thunderbird) and prevent dataloss. The student will also have to think about the user interface of the log viewer. Things to keep in mind when working on this project: it should be easy to import logs from other IM applications into this system; it should be easy to export logs; it should be easy to store logs on a remote server.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Voice and Video<br />
|Goal: Support voice and video communication.<br />
<br />
This project intends to explore the possibilities for Voice and Video communication using the Mozilla platform. The student will need to experiment both with usage of the microphone and webcam and with codecs available in the system on the three supported OSes. Compatible implementations of the various IM protocols that support these features is out of the scope of this project, but the student will at least need to prove that s/he has seriously investigated using the various open source projects that have started some work on this. A (mostly) working proof of concept is expected. UI mockups for what a well-thought user interface for voice and video could be would be appreciated.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Rhino ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Explore and implement JDK7 InvokeDynamic<br />
| JDK7 (currently in beta and due for general release this summer) contains new features for [http://openjdk.java.net/projects/mlvm/ dynamically typed languages] on top of the Java VM. One significant feature brought by [http://jcp.org/en/jsr/detail?id=292 JSR 292 features] is the new invokedynamic bytecode instruction and supporting libraries, which has the potential to make Rhino bytecode both simpler and faster. The goal of this project would be to make Rhino generate bytecode that uses JSR 292 InvokeDynamic and compare its performance characteristics with the current code. There is an [http://kenai.com/projects/davincimonkey/pages/Home initial implementation] by Oracle's John Rose which can serve as a starting point.<br />
| Hannes Wallnoefer<br />
| Hannes Wallnoefer<br />
|<br />
|-<br />
| Implement ECMAScript 5 strict mode <br />
| Rhino has pretty solid ECMAScript 5 support, with [https://developer.mozilla.org/en/JavaScript/Strict_mode strict mode] being the major exception. Implementation involves adding detection of the strict mode directive to the parser and then adding checks for the various strict mode rules. Some of the restraints are already detected by Rhino which should make it easy to get started.<br />
| Hannes Wallnoefer <br />
| Hannes Wallnoefer<br />
| <br />
|}<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Mozilla Services (Sync, Identity, etc) ==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Drumbeat/Batucada==<br />
<br />
Any hacking projects connected to a [http://www.drumbeat.org/ Drumbeat] project or [https://wiki.mozilla.org/Drumbeat/Batucada Batucada].<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode11:Brainstorming&diff=291224
Community:SummerOfCode11:Brainstorming
2011-03-15T20:30:17Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality. <br />
<br />
<b>Students: ideas approved by the SoC admins are [[Community:SummerOfCode11|here]].</b> You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) <b>You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.</b><br />
<br />
==How To Make Good Suggestions==<br />
<br />
Before adding an idea to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Links to ideas lists from previous years]].<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Camino==<br />
<br />
See the [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects Camino Summer of Code page] for project suggestions.<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Score-based filtering<br />
|You can filter on quite some terms, but you can't weigh them. A scoring system will allow a much finer control, eg. it would be just a property score with a range of maybe 1..1000, along with some new conditions <br />
Score [is|isn't|is lower than|is lower than or equal to|is greater than|is greater than or equal to][\/] [<value in range>]<br />
and actions<br />
[Increment score by|Decrement score by|Set score to][\/] [<value in range>]<br />
Each message would start with a score of 500 before filters get applied.<br />
<br />
This feature will require MailNews Core C++ hacking.<br />
<br />
Related:<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=151622 Bug 151622] "filters that score messages"<br />
|Karsten "Mnyromyr" Düsterloh<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|}<br />
<br />
==Instantbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|JavaScript Implementation of IM protocols<br />
|Goal: Implement new protocols in JavaScript, or create more stable implementations of existing ones.<br />
<br />
Instantbird 0.3 will support protocol plugins implemented in JavaScript in addition to the C libpurple plugins used before. The student will either add support for new protocols in Instantbird (if so, explain why this protocol matters) or reimplement in JavaScript protocols that are currently poorly supported by libpurple (if so, explain what will be better supported in the new implementation, or why the current implementation is broken). All new protocol plugins will go through a strict code review to ensure high code quality. The student working on new protocols should take every opportunity to improve the code and APIs shared by all JS protocol plugins.<br />
|Florian Quèze<br />
|Florian Quèze or Patrick Cloke<br />
| IRC and Twitter protocols have been (or are in the process of) being implemented and should not be considered.<br />
|-<br />
|Account import wizard<br />
|Goal: Ease the pain of switching to Instantbird<br />
<br />
Lots of users don't try a new IM client only because they don't want to spend time reconfiguring all their IM accounts. Being able to import accounts from other clients installed on the system would help Instantbird adoption. The student should focus on the dominant IM clients (Windows Live Messenger, AIM, ...) and on the other multi network IM clients (Digsby, Pidgin, Trillian, Miranda, ...). The student will need to study the way other IM clients store their profile data (reverse engineering may be required), think of an architecture to share as much code as possible between the various import modules, and implement import modules for some clients<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Indexed Logs<br />
|Goal: Create an easily search-able and sync-able storage for IM logs.<br />
<br />
A student working on this project will implement a new log storage back-end in Instantbird using SQLite. The format should allow efficient search (reuse code from Gloda in Thunderbird) and prevent dataloss. The student will also have to think about the user interface of the log viewer. Things to keep in mind when working on this project: it should be easy to import logs from other IM applications into this system; it should be easy to export logs; it should be easy to store logs on a remote server.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|-<br />
|Voice and Video<br />
|Goal: Support voice and video communication.<br />
<br />
This project intends to explore the possibilities for Voice and Video communication using the Mozilla platform. The student will need to experiment both with usage of the microphone and webcam and with codecs available in the system on the three supported OSes. Compatible implementations of the various IM protocols that support these features is out of the scope of this project, but the student will at least need to prove that s/he has seriously investigated using the various open source projects that have started some work on this. A (mostly) working proof of concept is expected. UI mockups for what a well-thought user interface for voice and video could be would be appreciated.<br />
|Florian Quèze<br />
|Florian Quèze<br />
|<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Rhino ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|-<br />
| Explore and implement JDK7 InvokeDynamic<br />
| JDK7 (currently in beta and due for general release this summer) contains new features for [http://openjdk.java.net/projects/mlvm/ dynamically typed languages] on top of the Java VM. One significant feature brought by [http://jcp.org/en/jsr/detail?id=292 JSR 292 features] is the new invokedynamic bytecode instruction and supporting libraries, which has the potential to make Rhino bytecode both simpler and faster. The goal of this project would be to make Rhino generate bytecode that uses JSR 292 InvokeDynamic and compare its performance characteristics with the current code. There is an [http://kenai.com/projects/davincimonkey/pages/Home initial implementation] by Oracle's John Rose which can serve as a starting point.<br />
| Hannes Wallnoefer<br />
| Hannes Wallnoefer<br />
|<br />
|-<br />
| Implement ECMAScript 5 strict mode <br />
| Rhino has pretty solid ECMAScript 5 support, with [https://developer.mozilla.org/en/JavaScript/Strict_mode strict mode] being the major exception. Implementation involves adding detection of the strict mode directive to the parser and then adding checks for the various strict mode rules. Some of the restraints are already detected by Rhino which should make it easy to get started.<br />
| Hannes Wallnoefer <br />
| Hannes Wallnoefer<br />
| <br />
|}<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Mozilla Services (Sync, Identity, etc) ==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Drumbeat/Batucada==<br />
<br />
Any hacking projects connected to a [http://www.drumbeat.org/ Drumbeat] project or [https://wiki.mozilla.org/Drumbeat/Batucada Batucada].<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode11:Brainstorming&diff=289104
Community:SummerOfCode11:Brainstorming
2011-03-06T20:14:53Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality. <br />
<br />
<b>Students: ideas approved by the SoC admins are [[Community:SummerOfCode11|here]].</b> You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) <b>You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.</b><br />
<br />
==How To Make Good Suggestions==<br />
<br />
Before adding an idea to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Links to ideas lists from previous years]].<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Camino==<br />
<br />
See the [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects Camino Summer of Code page] for project suggestions.<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Messenger Bookmarks<br />
|SM Mailnews provides access not only to mail, but also to NNTP news and even to RSS feeds, and maybe others in future as well. It would be quite useful to be able to bookmark specific news items for later use, e.g. specific postings of a discussion, etc. <br />
This should include full usual bookmark handling for those URLs, including sidebar support.<br />
<br />
Relevant bugs:<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=14988 Bug 14988] - Allow bookmarking of e-mail/Usenet messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77186 Bug 77186] - allow drag and drop bookmarking of mail / news messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77195 Bug 77195] - support news, imap, mailbox message urls from the browser<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=178003 Bug 178003] - Restore access to Sidebar from Mail/News, Compose and Addressbook<br />
|Karsten "Mnyromyr" Düsterloh<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|-<br />
|OpenSearch results in Sidebar<br />
|When we implemented OpenSearch, we lost the result listing in the sidebar. But OpenSearch responses can be RSS/Atom and we should use this to bring back short results to the sidebar.<br />
<br />
This feature is likely to need Core/Toolkit fixes.<br />
<br />
Related:<br><br />
[http://www.opensearch.org/Specifications/OpenSearch/1.1/Draft_4#OpenSearch_response_elements OpenSearch spec]<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments <br />
|}<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Mozilla Services (Sync, Identity, etc) ==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Drumbeat/Batucada==<br />
<br />
Any hacking projects connected to a [http://www.drumbeat.org/ Drumbeat] project or [https://wiki.mozilla.org/Drumbeat/Batucada Batucada].<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode11:Brainstorming&diff=289103
Community:SummerOfCode11:Brainstorming
2011-03-06T20:09:33Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality. <br />
<br />
<b>Students: ideas approved by the SoC admins are [[Community:SummerOfCode11|here]].</b> You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) <b>You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.</b><br />
<br />
==How To Make Good Suggestions==<br />
<br />
Before adding an idea to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Links to ideas lists from previous years]].<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Camino==<br />
<br />
See the [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects Camino Summer of Code page] for project suggestions.<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Messenger Bookmarks<br />
|SM Mailnews provides access not only to mail, but also to NNTP news and even to RSS feeds, and maybe others in future as well. It would be quite useful to be able to bookmark specific news items for later use, e.g. specific postings of a discussion, etc. <br />
This should include full usual bookmark handling for those URLs, including sidebar support.<br />
<br />
Relevant bugs:<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=14988 Bug 14988] - Allow bookmarking of e-mail/Usenet messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77186 Bug 77186] - allow drag and drop bookmarking of mail / news messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77195 Bug 77195] - support news, imap, mailbox message urls from the browser<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=178003 Bug 178003] - Restore access to Sidebar from Mail/News, Compose and Addressbook<br />
|Karsten "Mnyromyr" Düsterloh<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|-<br />
|OpenSearch results in Sidebar<br />
|When we implemented OpenSearch, we lost the result listing in the sidebar. But OpenSearch responses can be RSS/Atom and we should use this to bring back short results to the sidebar.<br />
<br />
This feature is likely to need Core/Toolkit fixes.<br />
|Karsten "Mnyromyr" Düsterloh<br />
|<br />
|<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments <br />
|}<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Mozilla Services (Sync, Identity, etc) ==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Drumbeat/Batucada==<br />
<br />
Any hacking projects connected to a [http://www.drumbeat.org/ Drumbeat] project or [https://wiki.mozilla.org/Drumbeat/Batucada Batucada].<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode11:Brainstorming&diff=289102
Community:SummerOfCode11:Brainstorming
2011-03-06T19:40:32Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div> <br />
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality. <br />
<br />
<b>Students: ideas approved by the SoC admins are [[Community:SummerOfCode11|here]].</b> You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) <b>You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.</b><br />
<br />
==How To Make Good Suggestions==<br />
<br />
Before adding an idea to this list, please consider the following:<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.<br />
<br />
==Suggestion List==<br />
<br />
[[SummerOfCode|Links to ideas lists from previous years]].<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Calendar ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Camino==<br />
<br />
See the [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects Camino Summer of Code page] for project suggestions.<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Messenger Bookmarks<br />
|SM Mailnews provides access not only to mail, but also to NNTP news and even to RSS feeds, and maybe others in future as well. It would be quite useful to be able to bookmark specific news items for later use, e.g. specific postings of a discussion, etc. <br />
This should include full usual bookmark handling for those URLs, including sidebar support.<br />
<br />
Relevant bugs:<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=14988 Bug 14988] - Allow bookmarking of e-mail/Usenet messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77186 Bug 77186] - allow drag and drop bookmarking of mail / news messages<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=77195 Bug 77195] - support news, imap, mailbox message urls from the browser<br><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=178003 Bug 178003] - Restore access to Sidebar from Mail/News, Compose and Addressbook<br />
|Karsten "Mnyromyr" Düsterloh<br />
|Karsten "Mnyromyr" Düsterloh<br />
|}<br />
<br />
==NSS (Network Security Services)==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
== Bugzilla ==<br />
<br />
{| class="standard-table"<br />
|-<br />
! Title <br />
! Details - with links as appropriate <br />
! Reporter <br />
! Mentor(s) <br />
! Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments <br />
|}<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
== Mozilla Services (Sync, Identity, etc) ==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Drumbeat/Batucada==<br />
<br />
Any hacking projects connected to a [http://www.drumbeat.org/ Drumbeat] project or [https://wiki.mozilla.org/Drumbeat/Batucada Batucada].<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Details - with links as appropriate<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Fosdem:2011/Dinner_sign_up&diff=278259
Fosdem:2011/Dinner sign up
2011-01-18T21:41:29Z
<p>Mnyromyr: /* Crosly Bowling (8:00pm) */</p>
<hr />
<div>Please make sure to sign-up for the Saturday dinner. <br><br />
'''NB: people who have not signed-up will not be allowed entry - Mozilla bouncers at the door will see to that :)'''<br />
<br />
=[http://www.crosly.be/ Crosly Bowling] (8:00pm)=<br />
{| class="fullwidth-table"<br />
|-<br />
| width="50%" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Name''' <br />
| width="50%" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Name'''<br />
|-<br />
| 1. Milos Dinic <br />
| 26. <br />
|-<br />
| 2. William Quiviger<br />
| 27. <br />
|-<br />
| 3. Christian Biesinger<br />
| 28. <br />
|-<br />
| 4. Benjamin Biesinger<br />
| 29. <br />
|-<br />
| 5. Sonny Piers<br />
| 30. <br />
|-<br />
| 6. Emmanuel Gil Peyrot<br />
| 31. <br />
|-<br />
| 7. Marien Zwart<br />
| 32. <br />
|-<br />
| 8. Cédric Corazza<br />
| 33. <br />
|-<br />
| 9. Tarek Ziadé<br />
| 34. <br />
|-<br />
| 10. Karsten Düsterloh<br />
| 35. <br />
|-<br />
| 11. Martin Creutziger<br />
| 36. <br />
|-<br />
| 12. Cédric Menge<br />
| 37. <br />
|-<br />
| 13. Thomas Ruecker<br />
| 38. <br />
|-<br />
| 14. <br />
| 39. <br />
|-<br />
| 15. <br />
| 40. <br />
|-<br />
| 16. <br />
| 41. <br />
|-<br />
| 17. <br />
| 42. <br />
|-<br />
| 18. <br />
| 43. <br />
|-<br />
| 19. <br />
| 44. <br />
|-<br />
| 20. <br />
| 45. <br />
|-<br />
| 21. <br />
| 46. <br />
|-<br />
| 22. <br />
| 47. <br />
|-<br />
| 23. <br />
| 48. <br />
|-<br />
| 24. <br />
| 49. <br />
|-<br />
| 25. <br />
| 50. <br />
| <br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=277969
SeaMonkey:MailNews:CodingStyle
2011-01-17T19:51:07Z
<p>Mnyromyr: </p>
<hr />
<div>Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the [https://developer.mozilla.org/en/JavaScript_style_guide Mozilla JavaScript rules], but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
Empty blocks, e.g. when implementing interfaces or <tt>try</tt>ing to <tt>catch</tt> exceptions, should really be empty and can go at the end of the line if needed:<br />
// implement nsIFolderListener<br />
var folderListener =<br />
{<br />
OnItemAdded: function(parentItem, item) {},<br />
OnItemRemoved: function(parentItem, item) <br />
{<br />
try<br />
{<br />
SomethingWhichThrows();<br />
}<br />
catch (ex) {}<br />
}<br />
};<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div><br />
[[category:SeaMonkey|P]]</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=260442
SeaMonkey/Developer Meeting:2010/Proposals
2010-10-12T19:23:00Z
<p>Mnyromyr: doc links added</p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| Aqualon<br />
| Presentation<br />
|-<br />
| Messenger Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| (Short mock-up presentation, but mainly) Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey Keysigning Event<br />
| [http://www.gnupg.org/faq/GnuPG-FAQ.html GPG key signing] and [http://wiki.cacert.org/ CACert assurance]<br />
| Mnyromyr<br />
| Please add your GPG key to the [http://biglumber.com/x/web?keyring=6313 event keyring] to ease participation! See the [http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html Keysigning Party HOWTO] for details.<br> CACert assurers should tell me they're coming so that I know I'm not the only one. ;-)<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=257914
SeaMonkey/Developer Meeting:2010/Proposals
2010-10-03T19:07:00Z
<p>Mnyromyr: </p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley (?)<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| Aqualon<br />
| Presentation<br />
|-<br />
| Messenger Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| (Short mock-up presentation, but mainly) Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey Keysigning Event<br />
| GPG key signing and CACert assurance<br />
| Mnyromyr<br />
| Please add your GPG key to the [http://biglumber.com/x/web?keyring=6313 event keyring] if you like to participate! See the [http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html Keysigning Party HOWTO] for details. CACert assurers should tell me they're coming so that I know I'm not the only one. ;-)<br />
|}<br />
<br />
<br />
http://biglumber.com/x/web?keyring=6313</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=255824
SeaMonkey/Developer Meeting:2010/Proposals
2010-09-25T20:38:04Z
<p>Mnyromyr: </p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley (?)<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| sgautherie (?)<br />
| Presentation<br />
|-<br />
| Messenger Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| (Short mock-up presentation, but mainly) Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=255823
SeaMonkey/Developer Meeting:2010/Proposals
2010-09-25T20:31:29Z
<p>Mnyromyr: </p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley (?)<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| sgautherie (?)<br />
| Presentation<br />
|-<br />
| Messenger Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| Presentation / Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=255822
SeaMonkey/Developer Meeting:2010/Proposals
2010-09-25T20:31:09Z
<p>Mnyromyr: </p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley (?)<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| sgautherie (?)<br />
| Presentation<br />
|-<br />
| Messnger Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| Presentation / Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/Developer_Meeting:2010/Proposals&diff=255821
SeaMonkey/Developer Meeting:2010/Proposals
2010-09-25T20:23:39Z
<p>Mnyromyr: </p>
<hr />
<div>Please add your proposals in similar style to those that are already in the list. A question mark next to the Speaker/Leader of a session means having him do it is requested but not confirmed by himself.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Topic'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Description'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Speaker/Lead'''<br />
| style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''Type'''<br />
|-<br />
| Reviews<br />
| How to improve review rules, how to get queues down, how to improve satisfation on both sides<br />
| ?<br />
| Discussion<br />
|-<br />
| Organization<br />
| Creating an organization to support the project with resources<br />
| BenB (?)<br />
| Presentation<br />
|-<br />
| Project Areas<br />
| Revamp the project area and bugzilla component lists, re-think owners and peers<br />
| ?<br />
| Discussion<br />
|-<br />
| Mac UI<br />
| How does SeaMonkey look on the Mac, where are the differences, difficulties, and what developers need to be careful with<br />
| stefanh (?)<br />
| Presentation, Demo<br />
|-<br />
| Sync<br />
| How "Firefox" Sync integrates on our end and how (well) it works for us<br />
| InvisibleSmiley (?)<br />
| Presentation<br />
|-<br />
| Automated tests<br />
| Increasing our automated test coverage, what suites do we have, how to write tests<br />
| sgautherie (?)<br />
| ?<br />
|-<br />
| Product vision<br />
| Where is SeaMonkey's future, how do we get there?<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Marketing<br />
| How can we get the message out? What message? Who can lead that effort?<br />
| ?<br />
| Discussion<br />
|-<br />
| UX / UI Design<br />
| Guidelines for SeaMonkey UX and UI design, what to improve and how<br />
| ?<br />
| Discussion<br />
|-<br />
| Infrastructure<br />
| How does it work that we get builds, tests, and releases done? How does this compare to Firefox and Thunderbird? What's changing/moving there?<br />
| Callek (?)<br />
| Presentation<br />
|-<br />
| Web editing<br />
| How can we get both Composer and KompoZer into the modern world? How can we work together to help both products?<br />
| kaze (?)<br />
| Discussion<br />
|-<br />
| SeaMonkey Council<br />
| New members, responsibilities, processes, in the Council<br />
| KaiRo<br />
| Discussion<br />
|-<br />
| Mercurial Queues<br />
| Understanding and using hg queues<br />
| sgautherie (?)<br />
| Presentation<br />
|-<br />
| MailNews Future<br />
| Planning the direction of the development of our Mail/News component.<br />
| Mnyromyr<br />
| Presentation / Discussion<br />
|-<br />
| Preferences Reorganization<br />
| How can we organize our UI prefs more logically?<br />
| IanN (?)<br />
| Discussion<br />
|-<br />
| Code Porting<br />
| How to port code from/to SeaMonkey most efficiently<br />
| ?<br />
| Discussion<br />
|-<br />
| SeaMonkey.next<br />
| Where to go after 2.1, in features, version numbers, etc.<br />
| ?<br />
| Discussion<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=De:Meeting:2010/travel_data&diff=243803
De:Meeting:2010/travel data
2010-08-08T21:26:45Z
<p>Mnyromyr: /* Departures */</p>
<hr />
<div>Bitte füllt die Ankunfts- und Abfahrtsdaten ein, damit wir den Beginn und das Ende des Treffens besser abstimmen können.<br />
<br />
= Arrivals =<br />
<br />
{| border="1"<br />
|-<br />
| Name <br />
| Trans.Type <br />
| Arr.Date <br />
| Arr.Time <br />
|-<br />
| Wawuschel<br />
| Bahn<br />
| 18.09.2010<br />
| 11:05 Uhr<br />
|-<br />
| Road-Runner<br />
| Bahn<br />
| 18.09.2010<br />
| 11:42 Uhr<br />
|-<br />
| Elchi3<br />
| Bahn<br />
| 18.09.2010 <br />
| 11:46 Uhr<br />
|-<br />
| Mnyromyr<br />
| Bahn<br />
| 18.09.2010 <br />
| when needed (local trains arrive regularly)<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
= Departures =<br />
<br />
{| border="1"<br />
|-<br />
| Name <br />
| Trans.Type <br />
| Dep.Date <br />
| Dep.Time <br />
|-<br />
| Fux<br />
| Bahn<br />
| 19.09.2010<br />
| 16:55 Uhr<br />
|-<br />
| Wawuschel<br />
| Bahn<br />
| 19.09.2010<br />
| 17:20 Uhr<br />
|-<br />
| Road-Runner<br />
| Bahn<br />
| 19.09.2010<br />
| 18:18 Uhr<br />
|-<br />
| Elchi3<br />
| Bahn<br />
| 19.09.2010 <br />
| 17:26 Uhr<br />
|-<br />
| Mnyromyr<br />
| Bahn<br />
| 19.09.2010 <br />
| when needed (local trains depart regularly)<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=De:Meeting:2010/travel_data&diff=243802
De:Meeting:2010/travel data
2010-08-08T21:26:07Z
<p>Mnyromyr: /* Arrivals */</p>
<hr />
<div>Bitte füllt die Ankunfts- und Abfahrtsdaten ein, damit wir den Beginn und das Ende des Treffens besser abstimmen können.<br />
<br />
= Arrivals =<br />
<br />
{| border="1"<br />
|-<br />
| Name <br />
| Trans.Type <br />
| Arr.Date <br />
| Arr.Time <br />
|-<br />
| Wawuschel<br />
| Bahn<br />
| 18.09.2010<br />
| 11:05 Uhr<br />
|-<br />
| Road-Runner<br />
| Bahn<br />
| 18.09.2010<br />
| 11:42 Uhr<br />
|-<br />
| Elchi3<br />
| Bahn<br />
| 18.09.2010 <br />
| 11:46 Uhr<br />
|-<br />
| Mnyromyr<br />
| Bahn<br />
| 18.09.2010 <br />
| when needed (local trains arrive regularly)<br />
|-<br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
= Departures =<br />
<br />
{| border="1"<br />
|-<br />
| Name <br />
| Trans.Type <br />
| Dep.Date <br />
| Dep.Time <br />
|-<br />
| Fux<br />
| Bahn<br />
| 19.09.2010<br />
| 16:55 Uhr<br />
|-<br />
| Wawuschel<br />
| Bahn<br />
| 19.09.2010<br />
| 17:20 Uhr<br />
|-<br />
| Road-Runner<br />
| Bahn<br />
| 19.09.2010<br />
| 18:18 Uhr<br />
|-<br />
| Elchi3<br />
| Bahn<br />
| 19.09.2010 <br />
| 17:26 Uhr<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Summit2010/Meetings&diff=235960
Summit2010/Meetings
2010-07-01T21:54:04Z
<p>Mnyromyr: /* CAcert Signing Party */</p>
<hr />
<div>Additional meetings<br />
<br />
This page shall help us to coordinate additional meetings at the Summit.<br />
<br />
Maybe you'd like to meet with a group of people to sit down and discuss a topic, and none of the other talks seem to cover it?<br />
<br />
Which meetings will happen? Who is interested? Where to go? When?<br />
<br />
= Developer Meetings =<br />
<br />
== Security code, PSM, NSS, padlock ==<br />
<br />
* We want to talk about the open issues in PSM and answer questions<br />
* brainstorm on future code changes, such as improving the "https padlock tracking" mechanisms<br />
<br />
Proposed time and place:<br />
* After the "security trends" talk (B081), in the same room.<br />
<br />
Want to come (add yourself):<br />
* Honza Bambas<br />
* Kai Engert<br />
* Sid Stamm<br />
<br />
== Secure Authentication ==<br />
<br />
* We want to talk about PKI based user authentication, SSL client auth<br />
* brainstorm on user interfaces and implementation<br />
<br />
Proposed time and place:<br />
* After the "Account Manager & Online Identity" talk (B027), in the same room.<br />
<br />
Want to come (add yourself):<br />
* Kai Engert<br />
* Sid Stamm<br />
<br />
= Contributor Meetings =<br />
== SuMoMo Non English Meeting ==<br />
[http://support.mozillamessaging.com/en-US/kb/ SuMoMo] is the knowledge base for Thunderbird! <br />
all SuMoMo contributors welcome but emphasis on non English SuMoMo. Would like especially like anybody who can/will contribute to SuMoMo from these languages DE, JP, IT, FR, CZ, NL, etc - <br />
host:rolandtanglao on irc ping him on #moz10, cell:+16047297924, roland AT mozillamessaging.com, Mozilla Messaging Technical Suport Lead <br />
<br />
== QA && Support working hand in hand ==<br />
[http://etherpad.mozilla.com:9000/CV7WkIdVsx Organizing Thunderbird QA/Support Communities] - [[User:Tsk|Ludovic Hirlimann]] and Roland Tanglao (see SuMoMo above for contact info) will present ideas to organize support better to make support more effective worldwide as well as make support and QA work better together<br />
<br />
= Engineering Meetings =<br />
<br />
= Engagement Meetings =<br />
<br />
== PGP Signing party ==<br />
Idea is that mozilla contributors from all over the world are meeting. Some of us are using PGP on a daily basis - would be nice to sign / cross sign our keys.<br />
<br />
[[User:Tsk]] created a keyring on [http://biglumber.com/x/web?keyring=4739 biglumber], please add your key there , this will facilitate - the meeting and signing process, as printing the keyring will allow an easy, I've check this signature.<br />
<br />
If you have a pgp key consider joigning.<br />
<br />
I'll update for the time and date of meeting and will probably post a tweet and a message on the #moz10 channel.<br />
<br />
== CAcert Signing Party ==<br />
<br />
Assurers (please add your name if you want to assure) :<br />
* Bogomil Shopov<br />
* Iacopo Benesperi<br />
* Ludovic Hirlimann<br />
* Wolfgang Rosenauer<br />
* Karsten Düsterloh<br />
<br />
Date/place/Time TBA when the complete schedule is ready.</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Fosdem:2010/Saturday_dinner/lasertag_signup&diff=199897
Fosdem:2010/Saturday dinner/lasertag signup
2010-02-04T21:50:16Z
<p>Mnyromyr: </p>
<hr />
<div>All attendees of the Mozilla dinner are encouraged to let their competitive team spirit loose and show their shooting skills to fellow Mozillians. <br />
<br />
Each game lasts 30 minutes and up to 30 players (15 per team) can play in a game. Basically, laser-tag consists of having two teams shooting and neutralizing each other to capture the other team's base. A player who fires his laser into his opponents receiver "neutralises" him for 6 seconds and earns points for his team. <br />
<br />
The team with the most points at the end of a match will earn a special "Mozilla prize" :)<br />
<br />
To learn more about the fun game of laser tag, check this out: http://en.wikipedia.org/wiki/Laser_tag<br />
<br />
'''NB: if you're waiting for your turn to play laser tag, you can have a drink on the 3rd floor while you wait or play a game of [[Fosdem:2010/Saturday_dinner/bowling_signup|bowling]]'''.<br />
<br />
== Match #1 (21:30 - 22:00) ==<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| width="33%" style="background: none repeat scroll 0% 0% rgb(0, 0, 255); -moz-background-inline-policy: continuous;" | '''BLUE TEAM''' (Thunderbird) <br />
| width="33%" style="background: none repeat scroll 0% 0% rgb(255, 0, 0); -moz-background-inline-policy: continuous;" | '''RED TEAM''' (Firefox)<br />
|-<br />
| 1. Ludovic H.<br />
| 1. Markus M.<br />
|-<br />
| 2. Iacopo B.<br />
| 2. William D<br />
|-<br />
| 3. Gerv <br />
| 3.<br />
|-<br />
| 4.<br />
| 4.<br />
|-<br />
| 5. <br />
| 5.<br />
|-<br />
| 6. <br />
| 6.<br />
|-<br />
| 7. <br />
| 7.<br />
|-<br />
| 8. <br />
| 8.<br />
|-<br />
| 9. <br />
| 9.<br />
|-<br />
| 10. <br />
| 10.<br />
|-<br />
| 11. <br />
| 11.<br />
|-<br />
| 12. <br />
| 12.<br />
|-<br />
| 13. <br />
| 13.<br />
|-<br />
| 14. <br />
| 14.<br />
|-<br />
| 15. <br />
| 15.<br />
|}<br />
<br />
==Match #2 (22:00 - 22:30)== <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| width="33%" style="background: rgb(0, 0, 255) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''BLUE TEAM''' (SeaMonkey)<br />
| width="33%" style="background: rgb(255, 0, 0) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''RED TEAM''' (Firefox)<br />
|-<br />
| 1. chewey<br />
| 1. Tomcat <br />
|-<br />
| 2. Mnyromyr <br />
| 2.<br />
|-<br />
| 3. <br />
| 3.<br />
|-<br />
| 4. <br />
| 4.<br />
|-<br />
| 5. <br />
| 5.<br />
|-<br />
| 6. <br />
| 6.<br />
|-<br />
| 7. <br />
| 7.<br />
|-<br />
| 8. <br />
| 8.<br />
|-<br />
| 9. <br />
| 9.<br />
|-<br />
| 10. <br />
| 10.<br />
|-<br />
| 11. <br />
| 11.<br />
|-<br />
| 12. <br />
| 12.<br />
|-<br />
| 13. <br />
| 13.<br />
|-<br />
| 14. <br />
| 14.<br />
|-<br />
| 15. <br />
| 15.<br />
|}<br />
<br />
==Match #3 (22:30 - 23:00)== <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| width="33%" style="background: rgb(0, 0, 255) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''BLUE TEAM'''<br />
| width="33%" style="background: rgb(255, 0, 0) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''RED TEAM'''<br />
|-<br />
| 1. <br />
| 1.<br />
|-<br />
| 2. <br />
| 2.<br />
|-<br />
| 3. <br />
| 3.<br />
|-<br />
| 4. <br />
| 4.<br />
|-<br />
| 5. <br />
| 5.<br />
|-<br />
| 6. <br />
| 6.<br />
|-<br />
| 7. <br />
| 7.<br />
|-<br />
| 8. <br />
| 8.<br />
|-<br />
| 9. <br />
| 9.<br />
|-<br />
| 10. <br />
| 10.<br />
|-<br />
| 11. <br />
| 11.<br />
|-<br />
| 12. <br />
| 12.<br />
|-<br />
| 13. <br />
| 13.<br />
|-<br />
| 14. <br />
| 14.<br />
|-<br />
| 15. <br />
| 15.<br />
|}<br />
<br />
==Match #4 (23:00 - 23:30)== <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
| width="33%" style="background: rgb(0, 0, 255) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''BLUE TEAM''' <br />
| width="33%" style="background: rgb(255, 0, 0) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | '''RED TEAM'''<br />
|-<br />
| 1. <br />
| 1.<br />
|-<br />
| 2. <br />
| 2.<br />
|-<br />
| 3. <br />
| 3.<br />
|-<br />
| 4. <br />
| 4.<br />
|-<br />
| 5. <br />
| 5.<br />
|-<br />
| 6. <br />
| 6.<br />
|-<br />
| 7. <br />
| 7.<br />
|-<br />
| 8. <br />
| 8.<br />
|-<br />
| 9. <br />
| 9.<br />
|-<br />
| 10. <br />
| 10.<br />
|-<br />
| 11. <br />
| 11.<br />
|-<br />
| 12. <br />
| 12.<br />
|-<br />
| 13. <br />
| 13.<br />
|-<br />
| 14. <br />
| 14.<br />
|-<br />
| 15. <br />
| 15.<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=File:Mnyromyr_20091113.png&diff=183040
File:Mnyromyr 20091113.png
2009-11-13T20:21:35Z
<p>Mnyromyr: </p>
<hr />
<div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=176649
SeaMonkey:MailNews:CodingStyle
2009-10-19T20:44:12Z
<p>Mnyromyr: </p>
<hr />
<div>Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the [https://developer.mozilla.org/en/JavaScript_style_guide Mozilla JavaScript rules], but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
Empty blocks, e.g. when implementing interfaces or <tt>try</tt>ing to <tt>catch</tt> exceptions, should really be empty and can go at the end of the line if needed:<br />
// implement nsIFolderListener<br />
var folderListener =<br />
{<br />
OnItemAdded: function(parentItem, item) {},<br />
OnItemRemoved: function(parentItem, item) <br />
{<br />
try<br />
{<br />
SomethingWhichThrows();<br />
}<br />
catch (ex) {}<br />
}<br />
};<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=EU_MozCamp_2009/Participants&diff=170981
EU MozCamp 2009/Participants
2009-09-25T17:37:29Z
<p>Mnyromyr: </p>
<hr />
<div>Participants list <br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Name <br />
! Country <br />
! I work on<br />
|-<br />
| [[User:Alfredkayser|Alfred Kayser]] <br />
| The Netherlands <br />
| Core development &amp; Themes<br />
|-<br />
| Aliiev Rail <br />
| <br />
| <br />
|-<br />
| Babych Timothy <br />
| <br />
| <br />
|-<br />
| Ballesteros Eva <br />
| Spain<br />
| <br />
|-<br />
| Bambas Honza <br />
| <br />
| <br />
|-<br />
| Bassetto Thomas <br />
| France <br />
| Geckozone.org<br />
|-<br />
| Beltzner Mike <br />
| <br />
| <br />
|-<br />
| Beddoes Jonathan <br />
| <br />
| <br />
|-<br />
| Benes Wim <br />
| The Netherlands <br />
| Frisian localizer<br />
|-<br />
| [[User:Iacchi|Benesperi Iacopo]] <br />
| Italy <br />
| Calendar l10n, QA on l10n, community support<br />
|-<br />
| Bengoa David <br />
| <br />
| <br />
|-<br />
| Biesinger Christian <br />
| Switzerland <br />
| Gecko developer<br />
|-<br />
| Bindernagel Seth <br />
| <br />
| <br />
|-<br />
| [[User:Azurams|Blanc Dit Jolicoeur William]]<br />
| France<br />
| Firefox Ukulele Rock&Roll Singer<br />
|-<br />
| Brablc Ondrej <br />
| <br />
| <br />
|-<br />
| Braniecki Zbigniew <br />
| <br />
| <br />
|-<br />
| Brunschwig Patrick <br />
| Switzerland <br />
| Enigmail<br />
|-<br />
| Buchner Julia <br />
| France <br />
| Frenchmozilla / WoMoz<br />
|-<br />
| Cazenave Fabien <br />
| France <br />
| KompoZer<br />
|-<br />
| Chateaux Frédéric <br />
| France<br />
| Frenchmozilla / Websites Localization / KompoZer QA<br />
|-<br />
| Chevrel Pascal <br />
| <br />
| <br />
|-<br />
| Colmard Bastien <br />
| France<br />
| Extension developer, from MMTC<br />
|-<br />
| Colvig Mary <br />
| <br />
| <br />
|-<br />
| Corazza Cédric <br />
| France <br />
| Frenchmozilla / KompoZer l10n lead<br />
|-<br />
| Coustenoble Gregoire <br />
| France <br />
| <br />
|-<br />
| D'Hont Rene-Luc <br />
| France<br />
| Geolocation<br />
|-<br />
| [[User:ottodv|de Voogd, Otto]] <br />
| Estonia &amp; The Netherlands<br />
| Firefox marketing, SpreadThunderbird admin, AccessFirefox admin.<br />
|-<br />
| Dejus Raivis <br />
| Latvia<br />
| Firefox latvian l10n<br />
|-<br />
| Desré Fabrice <br />
| France<br />
| Fennec & extensions<br />
|-<br />
| Dessante Philippe <br />
| France <br />
| Frenchmozilla <br />
|-<br />
| [[User:Milos|Dinic Milos]] <br />
| Serbia <br />
| QA WebDev &amp; SUMO<br />
|-<br />
| Dominikowski Tomasz <br />
| <br />
| <br />
|-<br />
| Düllmann Thomas <br />
| <br />
| <br />
|-<br />
| [[User:Mnyromyr|Düsterloh, Karsten]] (Mnyromyr)<br />
| Germany<br />
| SeaMonkey, Mnenhy<br />
|-<br />
| Duyck William <br />
| <br />
| <br />
|-<br />
| England Steve <br />
| UK<br />
| Nightly Tester, Bugzilla Triage, Range Finder & Mozillaziner<br />
|-<br />
| Finch Patrick <br />
| <br />
| <br />
|-<br />
| Fraisse Laurent <br />
| France<br />
| Video marketing<br />
|-<br />
| Franc Pavel <br />
| <br />
| <br />
|-<br />
| Frinolli Carlo <br />
| <br />
| <br />
|-<br />
| Fritze Alexander <br />
| <br />
| <br />
|-<br />
| [[User:Hubert|Gajewski Hubert]] <br />
| Poland<br />
| Aviary.pl<br />
|-<br />
| Gambier Olivier <br />
| <br />
| <br />
|-<br />
| Gamonal Capdevila Edu <br />
| Catalonia <br />
| Localisation and community<br />
|-<br />
| García Gómez Fernando <br />
| Spain <br />
| Web developer (client and server side) Mozilla Hispano, Proyecto Nave<br />
|-<br />
| Garcia Rodriguez Pedro <br />
| <br />
| <br />
|-<br />
| Gautherie Serge <br />
| <br />
| <br />
|-<br />
| Gaztelumendi Patxi <br />
| <br />
| <br />
|-<br />
| [[User:Gemal|Gemal Henrik ]]<br />
| Denmark<br />
| Extension Developer / Guerilla Marketing<br />
|-<br />
| Gertner Matthew <br />
| <br />
| <br />
|-<br />
| Gladkov Alexey <br />
| Russia<br />
| Mozilla.Россия Team<br />
|-<br />
| Glogowski Grzegorz <br />
| <br />
| <br />
|-<br />
| Gorjan Jovanovski <br />
| Republic of Macedonia <br />
| Mozilla Macedonia<br />
|-<br />
| [http://rfobic.wordpress.com/ Gozalishvili Irakli]<br />
| Netherlands<br />
| TomTom International<br />
|-<br />
| Greco Luca <br />
| <br />
| <br />
|-<br />
| Habali Svitlana <br />
| <br />
| <br />
|-<br />
| [[User:Met|Hassman Martin]] <br />
| Czech Republic <br />
| <br />
|-<br />
| [[User:AxelHecht|Hecht Axel]] <br />
| Germany<br />
| l10n coordination, infrastructure<br />
|-<br />
| Heikkinen Ilmari <br />
| Finland<br />
| [http://code.google.com/p/cakejs/ Canvas animation]<br />
|-<br />
| Hermes Stefan <br />
| <br />
| <br />
|-<br />
| [[User:Toniher|Hermoso Pulido Toni]] <br />
| Catalonia <br />
| Localisation and community<br />
|-<br />
| Hiatt Jeremy <br />
| <br />
| <br />
|-<br />
| Hirlimann Ludovic <br />
| The Netherlands/France <br />
| QA lead for Mozillamessaging<br />
|-<br />
| Hofmann Chris <br />
| <br />
| <br />
|-<br />
| Horvat Matjaz <br />
| Slovenia <br />
| Localisation and community<br />
|-<br />
| Hueppe Barbara <br />
| <br />
| <br />
|-<br />
| Ian Neal <br />
| <br />
| <br />
|-<br />
| Iyer Anusha <br />
| <br />
| <br />
|-<br />
| Izquierdo Daniel <br />
| <br />
| <br />
|-<br />
| Jesper Kristensen<br />
| Denmark<br />
| Localization<br />
|-<br />
| Jouanneau Laurent <br />
| France<br />
| Tech Evangelism, Core development, and development of Xulrunner applications<br />
|-<br />
| Jovanovski Gorjan <br />
| <br />
| <br />
|-<br />
| Kadem Nadir <br />
| France <br />
| Dailymotion Openvideo<br />
|-<br />
| [[User:KaiRo|Kaiser Robert]]<br />
| Austria<br />
| SeaMonkey, L10n<br />
|-<br />
| Kalamujic Kerim <br />
| <br />
| <br />
|-<br />
| Kalla Adrian <br />
| Germany <br />
| Aviary.pl, L10n, Koala<br />
|-<br />
| Kéménczy Kálmán <br />
| Hungary<br />
| l10n<br />
|-<br />
| Kewisch Philipp <br />
| Germany <br />
| Mozilla Calendar Project<br />
|-<br />
| King Brian <br />
| <br />
| <br />
|-<br />
| Kirsch Daniel <br />
| <br />
| <br />
|-<br />
| Kliehm Martin <br />
| Germany <br />
| HTML 5 Accessibility<br />
|-<br />
| Knous Marcia <br />
| USA <br />
| Firefox QA<br />
|-<br />
| Koehler Michael <br />
| Germany <br />
| Website localization<br />
|-<br />
| Kristensen Jesper <br />
| <br />
| <br />
|-<br />
| Kristoffersen Mike <br />
| Denmark <br />
| Fennec<br />
|-<br />
| Kulev Ognyan <br />
| <br />
| <br />
|-<br />
| Lach Kamil <br />
| <br />
| <br />
|-<br />
| Lando Simone <br />
| Italy <br />
| SUMO IT localization / l10n QA / community support<br />
|-<br />
| [[User:Stevel|Lau Stephen]] <br />
| USA <br />
| Songbird<br />
|-<br />
| Lebédel Delphine <br />
| France <br />
| Communities &amp; Website Localization / WoMoz<br />
|-<br />
| Leingruber Tobias <br />
| <br />
| <br />
|-<br />
| Lepikhov Konstantin <br />
| Russia<br />
| Mozilla.Россия Team<br />
|-<br />
| Leseul Benoit <br />
| Belgium<br />
| Frenchmozilla, Geckozone.org<br />
|-<br />
| Lodolo Francesco <br />
| Italy<br />
| Web and software localization, community<br />
|-<br />
| Looney Caitlin<br />
|<br />
|<br />
|-<br />
| López Guillermo <br />
| <br />
| <br />
|-<br />
| Magnini Giacomo <br />
| Italy <br />
| SeaMonkey, L10n, community support<br />
|-<br />
| Małolepszy Stanisław <br />
| <br />
| <br />
|-<br />
| Marcon Jean-Bernard <br />
| <br />
| <br />
|-<br />
| Markham Gervase <br />
| <br />
| <br />
|-<br />
| Markus Tobias <br />
| Germany <br />
| SUMO, sometimes Tech Evangelism<br />
|-<br />
| Marteau David <br />
| <br />
| <br />
|-<br />
| [[User:Nukeador|Martín Rubén]]<br />
| Spain<br />
| Mozilla Hispano, Proyecto NAVE (es-ES)<br />
|-<br />
| Mazgaj Joanna <br />
| Poland<br />
| Aviary.pl<br />
|-<br />
| McNamara David <br />
| <br />
| <br />
|-<br />
| Menge Cédric <br />
| <br />
| <br />
|-<br />
| Mierluș Alina <br />
| Catalonia <br />
| community marketing, advocacy - RO/CAT<br />
|-<br />
| [[User:Hyperstruct|Mirra Massimiliano]] <br />
| The Netherlands/Italy <br />
| instant messaging, development tools, development community<br />
|-<br />
| Moody Glyn <br />
| <br />
| <br />
|-<br />
| Mous Fabrice <br />
| <br />
| <br />
|-<br />
| Munk Skrøder Søren <br />
| Denmark<br />
| Localization (MozillaDanmark)<br />
|-<br />
| Narayanan Anant <br />
| <br />
| <br />
|-<br />
| Neves Miguel Joao <br />
| <br />
| <br />
|-<br />
| Nicolas Vivien <br />
| <br />
| <br />
|-<br />
| Ninove Thibaut <br />
| <br />
| <br />
|-<br />
| Nitot Tristan <br />
| France <br />
| Mozilla Europe President<br />
|-<br />
| Novak Chelsea <br />
| <br />
| <br />
|-<br />
| Nyman Robert<br />
| Sweden<br />
| Front end web developer - has done a number of Mozilla talks <br />
|-<br />
| Odvarko Jan <br />
| <br />
| <br />
|-<br />
| Paquet Simon <br />
| Germany <br />
| Calendar Project, Thunderbird &amp; Calendar l10n coordination<br />
|-<br />
| Pasche Sylvain <br />
| Switzerland<br />
| Firefox/Gecko developer<br />
|-<br />
| Peev Pavel <br />
| <br />
| <br />
|-<br />
| Picolini Francisco <br />
| <br />
| <br />
|-<br />
| Piers Sonny <br />
| <br />
| <br />
|-<br />
| Plewako Stefan <br />
| <br />
| <br />
|-<br />
| Quèze Florian <br />
| France<br />
| Instantbird<br />
|-<br />
| Quiviger William <br />
| France <br />
| EU Marketing<br />
|-<br />
| Raskin Aza <br />
| <br />
| <br />
|-<br />
| Rehbein Benedict <br />
| <br />
| <br />
|-<br />
| [http://hanblog.info Ricaud Anthony]<br />
| France<br />
| Skyrock.com & Web Inspector in WebKit<br />
|-<br />
| Rodaro Michele <br />
| Italy<br />
| SUMO IT localization / community support<br />
|-<br />
| Romera Teo <br />
| <br />
| <br />
|-<br />
| Rouget Paul <br />
| France <br />
| Tech Evangelist<br />
|-<br />
| Rozbora Branislav <br />
| Slovakia<br />
| Localization<br />
|-<br />
| Ruiz Miriam <br />
| Spain<br />
| Gecko newbie developer<br />
|-<br />
| Ruiz Aizpuru Julen <br />
| Basque Country <br />
| Localisation, [http://librezale.org Librezale.org]<br />
|-<br />
| Sandu Irina <br />
| <br />
| <br />
|-<br />
| [[User:FlorianS|Schloegl Florian]] <br />
| Germany <br />
| [http://koala.mozdev.org Koala]<br />
|-<br />
| Schröder Martin <br />
| Germany <br />
| Mozilla Calendar Project<br />
|-<br />
| Schwecherl Thomas <br />
| Austria <br />
| SUMO, Website localization<br />
|-<br />
| Seghers Jeroen <br />
| <br />
| <br />
|-<br />
| Sell Merike <br />
| <br />
| <br />
|-<br />
| Sharp Remy<br />
| United Kingdom<br />
| HTML5 & JavaScript<br />
|-<br />
| [[User:Bogomil|Shopov Bogomil]] <br />
| Bulgaria <br />
| <br />
|-<br />
| Skupin Henrik <br />
| Germany <br />
| Mozilla QA, Mozmill automation<br />
|-<br />
| Slovesnik Alexander <br />
| Russia <br />
| Localisation<br />
|-<br />
| Soref Josh <br />
| <br />
| <br />
|-<br />
| Sorensen Finn <br />
| <br />
| <br />
|-<br />
| Stawarz Katarzyna <br />
| Poland<br />
| L10n / Aviary.pl <br />
|-<br />
| [[User:Marcoos|Stępień Marek]]<br />
| Poland<br />
| Firefox localization, evangelism<br />
|-<br />
| [http://commonspace.wordpress.com/about/ Surman Mark] <br />
| Canada<br />
| Mozilla mission, community support, [https://wiki.mozilla.org/Drumbeat Drumbeat]<br />
|-<br />
| Szasz Alexandru <br />
| Romania<br />
| Localization, Localization tools<br />
|-<br />
| Tenser David <br />
| <br />
| <br />
|-<br />
| Tímár András <br />
| Hungary<br />
| l10n<br />
|-<br />
| Topal Abdulkadir <br />
| <br />
| <br />
|-<br />
| Turbureanu Tiberiu <br />
| <br />
| <br />
|-<br />
| Valaštiak Vlado <br />
| Slovakia<br />
| Localization<br />
|-<br />
| van der Woude Peter <br />
| <br />
| <br />
|-<br />
| Vukicevic Vlado <br />
| <br />
| <br />
|-<br />
| Wargers Martijn <br />
| Netherlands <br />
| QA<br />
|-<br />
| Wilcoxon Drew <br />
| <br />
| <br />
|-<br />
| Yen Mark <br />
| USA <br />
| Songbird<br />
|-<br />
| Younsi Arzhel <br />
| France<br />
| IT & MECT<br />
|-<br />
| Zwart Marien <br />
| Netherlands <br />
| SUMO, addons<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=164252
SeaMonkey:MailNews:CodingStyle
2009-08-25T19:20:53Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is still a draft and may change slightly!<br>Comments welcome!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
Empty blocks, e.g. when implementing interfaces or <tt>try</tt>ing to <tt>catch</tt> exceptions, should really be empty and can go at the end of the line if needed:<br />
// implement nsIFolderListener<br />
var folderListener =<br />
{<br />
OnItemAdded: function(parentItem, item) {},<br />
OnItemRemoved: function(parentItem, item) <br />
{<br />
try<br />
{<br />
SomethingWhichThrows();<br />
}<br />
catch (ex) {}<br />
}<br />
};<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=164135
SeaMonkey:MailNews:CodingStyle
2009-08-25T16:46:43Z
<p>Mnyromyr: /* Default bracing style is "curly braces go on their own line" */</p>
<hr />
<div><div style="color:red">This is still a draft and may change slightly!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
Empty blocks, e.g. when implementing interfaces or <tt>try</tt>ing to <tt>catch</tt> exceptions, should really be empty and can go at the end of the line if needed:<br />
// implement nsIFolderListener<br />
var folderListener =<br />
{<br />
OnItemAdded: function(parentItem, item) {},<br />
OnItemRemoved: function(parentItem, item) <br />
{<br />
try<br />
{<br />
SomethingWhichThrows();<br />
}<br />
catch (ex) {}<br />
}<br />
};<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=164089
SeaMonkey:MailNews:CodingStyle
2009-08-25T15:51:30Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is still a draft and may change slightly!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=164087
SeaMonkey:MailNews:CodingStyle
2009-08-25T15:50:59Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is still a draft and may slightly change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163956
SeaMonkey:MailNews:CodingStyle
2009-08-24T22:18:23Z
<p>Mnyromyr: wrong link</p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/Indent_style Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163936
SeaMonkey:MailNews:CodingStyle
2009-08-24T21:10:30Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
([http://en.wikipedia.org/wiki/1TBS Wikipedia] has an interesting comparison of the most common quoting style religions.)<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163536
SeaMonkey:MailNews:CodingStyle
2009-08-21T21:43:00Z
<p>Mnyromyr: /* One attribute per line when folding */</p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
=== CSS ===<br />
No divergent rules currently.<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163534
SeaMonkey:MailNews:CodingStyle
2009-08-21T21:37:33Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
The following rules describe our current practice.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163533
SeaMonkey:MailNews:CodingStyle
2009-08-21T21:35:43Z
<p>Mnyromyr: /* JavaScript */</p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, follow the C++ rules, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163532
SeaMonkey:MailNews:CodingStyle
2009-08-21T21:33:12Z
<p>Mnyromyr: </p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
=== General ===<br />
==== No whitespace crusades ====<br />
Yes, many MailNews code is misaligned, uses tabs instead of spaces for indentation, has trailing whitespace and what not. If doing stuff in the vincinity, fine, do the clean up. But don't touch it just for arbitrary whitespace correction, this just messes up the "whodunnit" history in our repository (and you don't want to look responsible for <strike>Blake's</strike> someone else's code, do you?).<br />
<br />
=== JavaScript ===<br />
In general, use the C++ rules above, but take care of these exceptions:<br />
<br />
==== Capitalize function names ====<br />
All names should use CamelCase, not under_score_delimiters. But while variable names should begin with lowercase characters, functions (incl. member functions) should begin with an uppercase letter:<br />
function CallSomething(ax)<br />
{<br />
var conspiracy = ax;<br />
return conspiracy;<br />
}<br />
<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163526
SeaMonkey:MailNews:CodingStyle
2009-08-21T21:15:08Z
<p>Mnyromyr: /* Use let for sub-scope variables */</p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
=== JavaScript ===<br />
In general, use the C++ rules above, but take care of these exceptions:<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
=== XML/XUL ===<br />
==== Indent is two spaces per nesting level ====<br />
&lt;element><br />
&lt;element><br />
&lt;element/><br />
&lt;/element><br />
&lt;/element><br />
<br />
==== Sort XUL attributes ====<br />
XUL attributes should come in this rough order:<br />
&lt;element id="menu_showMessagePane"<br />
label="&showMessagePaneCmd.label;"<br />
accesskey="&showMessagePaneCmd.accesskey;"<br />
key="key_toggleMessagePane"<br />
random_other_attributes="put 'em here!"<br />
oncommand="MsgToggleMessagePane(true);"/><br />
Especially, id should be first, label/accesskey/key should go together and handlers should be last.<br />
<br />
==== One attribute per line when folding ====<br />
If the XML element definition (vastly) exceeds the 80 columns limit, it should be wrapped. In this case, put each attribute onto its own line and align them vertically:<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" type="checkbox"/><br />
<br />
&lt;!-- Bad! Don't do this! --><br />
&lt;element id="menu_showMessagePane" type="checkbox" random_other_attribute1="1" random_other_attribute2="1" random_other_attribute3="1"/><br />
<br />
&lt;!-- Fine! --><br />
&lt;element id="menu_showMessagePane" <br />
type="checkbox" <br />
random_other_attribute1="1"<br />
random_other_attribute2="1"<br />
random_other_attribute3="1"/><br />
<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey:MailNews:CodingStyle&diff=163515
SeaMonkey:MailNews:CodingStyle
2009-08-21T20:56:16Z
<p>Mnyromyr: Created page with '<div style="color:red">This is just a draft and may change!</div> Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide r…'</p>
<hr />
<div><div style="color:red">This is just a draft and may change!</div><br />
<br />
<br />
Basically, the [https://developer.mozilla.org/En/Developer_Guide/Coding_Style Mozilla C++ coding style guide rules] apply. But our MailNews code has <strike>grown</strike> evolved over the years and can be rather <strike>twisted</strike> complex, thus we favour '''readability''' over brevity.<br />
<br />
=== JavaScript ===<br />
In general, use the C++ rules above, but take care of these exceptions:<br />
==== Default bracing style is "curly braces go on their own line" ====<br />
To enhance readability, curly braces should be aligned vertically:<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
{<br />
CallSomethingElse();<br />
}<br />
There are quite some (old) files in our codebase which entirely adhere to the "opening curly braces go at the end of a line" style. If you do changes there, please keep the file's coding style consistent. Mixed coding styles only makes things worse.<br />
<br />
==== If one <tt>if</tt> branch needs braces, the other should have braces as well ====<br />
// Fine!<br />
if (condition)<br />
CallSomething(23);<br />
else<br />
CallSomethingElse();<br />
<br />
// Bad! Don't do this!<br />
if (condition)<br />
{<br />
let x = 23;<br />
CallSomething(x);<br />
}<br />
else<br />
CallSomethingElse();<br />
<br />
==== No one-line <tt>if</tt> contructs ====<br />
Almost all contemporary debuggers are line debuggers and can't break amidst a line of code:<br />
// Fine!<br />
if (condition)<br />
return 42;<br />
<br />
// Bad! Don't do this!<br />
if (condition) return 42;<br />
<br />
==== Use let for sub-scope variables ====<br />
The scope of variables should as small as possible. Using the <tt>let</tt> keyword, the visibility can be restricted to the current block:<br />
function CallSomething(ax)<br />
{<br />
var x = 23; // global to CallSomething!<br />
if (x < ax)<br />
{<br />
var y = 42; // global to CallSomething!<br />
let z = 666; // local to this <tt>if</tt><br />
for (let i = 0; i < ax; ++i) // i is local to the for loop<br />
CallSomethingElse(i);<br />
}<br />
}<br />
<br />
<br />
<br />
<div style="text-align: right">''This page is maintained by [mailto:mnyromyr@tprac.de Karsten "Mnyromyr" Düsterloh].''</div></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=User:Mnyromyr&diff=163511
User:Mnyromyr
2009-08-21T20:11:46Z
<p>Mnyromyr: </p>
<hr />
<div>Some unordered thoughts about SeaMonkey and things I'd like to see hacked, maybe even by myself. '''<tt>;-)</tt>'''<br />
<ul><br />
<li>[https://bugzilla.mozilla.org/show_bug.cgi?id=360488 Stuff we (may) want to port over from Thunderbird into SeaMonkey MailNews (bug 360488)]</li><br />
<li>'''[[SeaMonkey:MailNews:CodingStyle|Guide on approved SeaMonkey MailNews coding style]]'''</li><br />
<li>[[User:Mnyromyr:MailFilters|Improvements for SeaMonkey MailNews filters]]</li><br />
<li>[[User:Mnyromyr:MessageViews|Fixing Message Views]]</li><br />
<li>[[User:Mnyromyr:BayesFacts|Technical Notes on the Bayesian Junk Filter]]</li><br />
<li>[[User:Mnyromyr:SeaMonkeyXPFE2toolkit_widget_transition|SeaMonkey /xpfe to /toolkit widget transition]] (historic)</li><br />
</ul></div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Venkman&diff=136814
Venkman
2009-03-29T18:02:35Z
<p>Mnyromyr: link to hg repository</p>
<hr />
<div>== Introduction ==<br />
Venkman is Mozilla's cross platform JavaScript Debugger, visit devmo for a [http://developer.mozilla.org/En/Venkman comprehensive overview]. Alas, it's currently in a sad state of hibernation - its [http://www.hacksrus.com/~ginda/venkman/ homepage] is out of sync with reality since 2005! The current version on [https://addons.mozilla.org/en-US/firefox/addon/216 amo] is 0.9.87.4, though.<br />
<br />
Despite efforts for a web-related debugger for Firefox (named [https://addons.mozilla.org/en-US/firefox/addon/1843 Firebug]), Venkman still has its place as a '''cross-platform''', '''cross-application''' (Firefox, SeaMonkey, Thunderbird, Netscape, etc.) debugging tool for both '''web and Mozilla chrome''' development.<br />
<br />
Unfortunately, Venkman's codebase hasn't kept pace with current development of the Mozilla ecosystem, so action is badly required to keep Venkman alive. This page aims at helping in coordinating this.<br />
<br />
== Tasks ==<br />
The stuff to be done can be splitted in three major groups:<br />
''<br/>Todo: add more bug numbers!''<br />
=== Architecture ===<br />
General changes have been made to make Venkman work with current development, to ease maintenance and attracting developers. It now lives in HG ([http://hg.mozilla.org/venkman/ hg.mozilla.org/venkman/]). Work on the build system is still progressing.<br />
<br />
The meta {{bug|141097}} ("Release Venkman 1.0") is still valid, but needs to be changed to reflect the current state of affairs.<br />
<br />
=== Important Bugs ===<br />
Bugs which break Venkman or make it hard to use.<br />
* {{Bug|342590}} – Make --enable-extensions=venkman work for XULRunner<br />
* {{Bug|424493}} - Copying native code stack frames generates errors<br />
* {{Bug|446120}} - Watches crash when expanding 2 levels and the values change<br />
* {{Bug|449766}} - Variable Value remains "undefined" when stopped in a debugger before initialization of the variable (JSD bug, seen in both Vnk and Firebug).<br />
* {{Bug|452288}} - Allow ignoring NS_ERROR_NO_INTERFACE errors<br />
* Venkman doesn't recognise <code>let</code> statements<br />
* ...<br />
<br />
=== Enhancements ===<br />
* Better keyboard experience, eg. shortcut keys for (un)setting breakpoints, etc. pp.<br />
* Source code tooltips with variable values.<br />
* ...<br />
<br />
== Related Links ==<br />
* Alex Vincent started a [http://groups.google.com/group/mozilla.dev.apps.js-debugger/browse_frm/thread/422b6ee58abc0701/061a3a638846405f?tvc=1&q=+Venkman+planning+for+Gecko+1.9#061a3a638846405f thread about Venkman's future] with focus on Gecko 1.9 in the Mozilla newsgroup mozilla.dev.apps.js-debugger in 2007, but it didn't really take off.<br />
* Alex Vincent made a fresh attempt with his blog post on [http://weblogs.mozillazine.org/weirdal/archives/019539.html Gecko 1.9.1, TraceMonkey and Venkman?] recently.<br />
<br />
<br />
<small>''Page maintained by [mailto:mnyromyr@tprac.de Karsten Düsterloh]''</small>.</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode09:Brainstorming&diff=135627
Community:SummerOfCode09:Brainstorming
2009-03-23T20:26:03Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div>This page is for submitting ideas for Summer of Code projects for 2009. Therefore, it will inevitably contain suggestions of wildly variable quality. Ideas approved by the SoC admins are [[Community:SummerOfCode09|here]].<br />
<br />
==How To Make Good Suggestions==<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. Potential mentors [[Community:SummerOfCode09:Mentors|sign up here]].<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
<br />
([http://weblogs.mozillazine.org/gerv/archives/2006/05/making_a_soc_project_list.html More thoughts on making a good list])<br />
<br />
==Suggestion List==<br />
<br />
Last year's ideas: [[Community:SummerOfCode08|Confirmed]], [[Community:SummerOfCode08:Brainstorming|Brainstorming]]<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Metalink support<br />
| Native support for the [[Metalink]] Download Description (XML) format ({{bug|331979}}) which lists mirrors and checksums, along with other useful metadata such as mirror location. Listing multiple URLs for a file increases availability while the checksums guarantee integrity and let downloads be repaired automatically. You can also filter downloads by location and other things. Metalink is currently supported by most download managers including DownThemAll!<br />
It would also be great to have Mozilla people involved with Metalink as well.<br />
|Ant Bryan<br />
|<br />
|Comments in the bug suggest that this would not be particularly well received by the network team. Sorry... -- Gerv<br />
|-<br />
|<strike>Support system spellcheck services on Mac and/or Linux/GTK</strike><br />
|<strike>Currently Firefox and other Mozilla products bundle the Hunspell spell-checking engine. It would be great if we could (perhaps optionally at build time and/or run-time) use the system dictionary. For example, that would let people use an existing "user dictionary" of words they've added in other applications. On Mac, there's [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSpellChecker_Class/Reference/Reference.html NSSpellChecker] and GTK applications seem to use [http://www.abisource.com/projects/enchant/ Enchant]. The simplest approach would probably be to add a build-time option to use Enchant or NSSpellChecker instead of Hunspell, with code #ifdefs to call those other APIs instead of Hunspell.</strike><br />
|<strike>Robert O'Callahan</strike><br />
|<br />
|The Mac code already exists, and all Moz apps used to use it on the trunk prior to 2008. However, there was much rancor, and osxspell was turned off for all applications other than Camino. Before someone invests time in this again, it's probably a good idea to get everyone on the same page as to whether it's really wanted or not (and/or if the complaints can be addressed). See {{bug|422760}}, {{bug|419959}}, and {{bug|343535}} (particularly comments 5 and 10) for the backstory and known issues. —[[User:Sardisson|sardisson]]<br />
Oh dear. Thanks for the heads-up! [[User:Roc|roc]]<br />
|-<br />
|Windows 7 Jump List<br />
|Jump List will be one of the major interface changes in Windows 7, which provides shortcuts for software features right in Windows Taskbar. If there is an XPCOM component for Windows 7 Jump List, user experience in Windows 7 will be improved a lot. ({{bug|473045}})<br />
|[[User:Littlebtc|Littlebtc]]<br />
|<br />
| To me, the major problem is that implementation/example of Jump List COM API does not work for me in Windows 7 Public Beta Build 7000. Is there any workaround? --[[User:Littlebtc|Littlebtc]] 21:57, 22 March 2009 (UTC)<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Printable CSS repository<br />
|The other day I [http://robert.accettura.com/blog/2009/02/05/printable-stylesheets-to-save-the-environment/ mentioned how cool printable stylesheets were]. I figured I'd write up an idea for a Firefox addon (or perhaps a future feature). It would make a pretty cool summer of code project (or two depending on if you split it up). The idea is not all that different from [http://userstyles.org/userstyles Userstyles] or [https://addons.mozilla.org/en-US/firefox/addon/748 GreaseMonkey] though intends to be easier to use.<br />
<br />
On the client side when attempting to print a page the addon would inject a printable stylesheet to make the printable output waste less paper, be more readable and just ascetically superior to raw printing. Since each site is unique if it didn't have a stylesheet for the site already it would query a central repository for stylesheets that match that url. If one or more is found it would be offered to the user as a stylesheet that could be installed and then printed with. Installing leaves a copy on the clients computer so that it could be used even in offline mode and if the repository were unavailable.<br />
<br />
On the server side of things there would obviously need to be a repository of stylesheets and a way to review and rate them. For privacy purposes I think there should be no remote loading content in the stylesheet that doesn't originate on the server which the stylesheet is for (for example a sites logo would be ok if served from the site's server). Ratings and reviews would let the better ones gravitate to the top and the poorer ones fall to the bottom.<br />
<br />
This approach is better than the more popular "select what you want to print" since it allows for not just printing a block of text, but printing web pages in a more meaningful and readable way.<br />
|[[User:Raccettura|Raccettura]]<br />
|<br />
|<br />
|-<br />
|Back- and Frontend for storing web pages<br />
|[[User:Archaeopteryx/Concept:Personal_web|Personal web]]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=287066 bug 287066] [https://bugzilla.mozilla.org/show_bug.cgi?id=342916 bug 342916]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=342917 bug 342917]<br />
Today the internet is an essential part of work and life, people have personal browsing habits and some things what they see and read they want to remember later or give to someone else. These pages define very good what the user wants, so they should be used for customization. Furthermore, addresses aren't available for infinity.<br />
Goals<br />
* Integration into bookmarks<br />
* Weave integration<br />
* Backend support for fulltext address bar search<br />
* Backend for extensions which detected updated webpages by source code comparing<br />
* Making documents and files offline available, but be still able to update them via Firefox<br />
* Save multiple captures of a web page<br />
|Archaeopteryx<br />
|Someone from the Places team?<br />
|<br />
|-<br />
|Support [http://en.wikipedia.org/wiki/Ed2k_URI_scheme ed2k:// hyperlinks] (ed2k/Kad network)<br />
|Create an extension that facilitates getting content from the (already existing) distributed serverless [http://en.wikipedia.org/wiki/Kad_network Kad network] and thus allows HTML/CSS constructs like the following:<br />
<br />
* <code>&lt;img src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;object src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;video src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;audio src="ed2k://..."&gt;</code><br />
<br />
* <span style="white-space: nowrap;"><code>@font-face { ... src: url(ed2k://...); ... }</code></span><br />
<br />
* <code>background-image: url(ed2k://...);</code><br />
<br />
The idea is that '''''content does not need centralized Web hosting if it has enough readers willing to participate in file exchange.'''''<br />
<br />
----<br />
<br />
The student is not expected to create a brand new Kad [http://en.wikipedia.org/wiki/Servent servent] software from the scratch. The extension should (instead) be able to install (if not installed previously) and then use an existing ed2k/Kad software on the user's machine (free software such as [http://www.emule-project.net/ eMule] or [http://en.wikipedia.org/wiki/MLDonkey MLDonkey], probably both should be known); the extension should just be able to determine (using ed2k and AICH hashes and file size given in the URL) whether the designated object exists in servent's cache; thus the extension's algorithm for serving content to Firefox is like the following:<br />
<br />
* If the ed2k://... URL designates an object that exists in servent's cache, grab it.<br />
<br />
* If the ed2k://... URL designates an object that does not exist in servent's cache, launch the servent (if not already running) and feed the URL into the servent.<br />
** If the object is not popular enough to be downloaded within a reasonable amount of time (e.g. half a minute), the extension signals to Firefox that request failed (similar to <code>504 Gateway Timeout</code> of HTTP), but servent continues getting the object and thus the subsequent requests for the same object (e.g. when the page is reloaded) are more likely to be successful.<br />
<br />
----<br />
<br />
'''Note:''' if the «ed2k://» URL has <span style="white-space: nowrap;">«s=<nowiki>http://</nowiki>...»</span> optional part (see «The ed2k link format» section in [http://web.archive.org/web/20050623081914/http://www.edonkey2000.com/documentation/distro.html the Internet Archive page of Overnet]), the extension should try the given Web URL first, and only if it fails (or if the given response does not match URL's filesize/ed2k hash/AICH hash) use the local servent.<br />
<br />
|[[User:Mithgol the Webmaster|Mithgol the Webmaster]]<br />
|<br />
|Previous efforts to add Bittorrent support to Firefox have fizzled. A compelling case would need to be made for a) adding P2P support at all, and b) choosing ed2k rather than bittorrent, particularly as bittorrent has libraries which could be integrated directly rather than the fairly hacky external program solution proposed here. -- Gerv<br />
|-<br />
|OpenSearch: Support resultURLs and descriptions from search suggestions<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=386591 resultURLs]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=481423 descriptions]<br />
resultURLs are very helpful for catalog searches (i. e. Wikipedia, shops, libraries, ...), descriptions for uncommon or very specific suggestions<br />
|Archaeopteryx<br />
|Gavin? (see bug)<br />
|This doesn't look to me like it's big enough, or that Gavin is interested in mentoring it... :-( -- Gerv<br />
|-<br />
|Provide Firefox MSI package<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=231062 bug 231062]<br />
MSI packages of Firefox are a long desired feature and would help enterprise users. Maybe Thunderbird could also benefit from this work.<br />
[http://msdn.microsoft.com/en-us/library/cc185688(VS.85).aspx More info from Microsoft]<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Implement more of pop3, imap and smtp fakeserver<br />
| Would be nice if [[MailNews:Fakeserver]] would implement more of the protocols. Would also be nice to be able to have a UI on top of Fakeserver to be able to add emails in mailboxes.<br />
| Ludovic Hirlimann<br />
|}<br />
<br />
==Calendar==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Sync Lightning code to Sunbird (1.0-post Sunbird support)<br />
|[http://weblogs.mozillazine.org/calendar/2009/02/calendar_project_at_a_critical.html Calendar blog post]<br />
Lightning's Calendar and Task mode should be ported to Sunbird, also the Today sidebar, either by modifying existing code or setting up a repacking script which integrates Lightning into Thunderbird, hides the mail UI and brands the build as Sunbird (including Sunbird UI)<br />
|Archaeopteryx<br />
|Fallen?<br />
|<br />
|-<br />
|Enhanced task management<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=194863 Nested tasks]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=357502 All day tasks]<br />
Current task support is very basic. All day tasks (which don't calendar pane stuff like today's tasks) and nested task supported would advance the user experience<br />
|Archaeopteryx<br />
|Mailed Fred, no response yet<br />
|<br />
|}<br />
<br />
==Camino==<br />
'''''N.B.''' Camino brainstorming is taking place [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects on the Camino wiki]. Mike Pinkerton or Stuart Morgan will add vetted project ideas with mentors.''<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Folder Views<br />
| We provide the ability to create and use message views for pre-filtering which messages to show in the thread pane. We don't have a comparable feature yet in the folder pane...<br />
While this would basically mean to port Thunderbird's {{bug|251296}}, the UI should be more in sync with the SeaMonkey look and feel, e.g. columns for unread count, size, etc; a drop down menu for switching views; allow custom folder views; ...<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| <br />
|}<br />
<br />
==Bugzilla==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Refactor Bugzilla::Bugmail into real objects<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=301447 bug 301447]<br />
Enhancing the the module for sending bugmails would allow further enhancements like HTML-based stuff<br />
|Archaeopteryx<br />
|<br />
|mkanat suggests both of these ideas are the wrong size for GSoC, and unfortunately the Bugzilla project doesn't have any mentors anyway :-( -- Gerv<br />
|-<br />
|tag-based email preferences<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=482207 bug 482207]<br />
If a user adds a tag to a bug, he should be able to specify email preferences for this tag. This would be helpful because votes, ccs and watches can happen for different reasons, even of the same event class, i. e. bug triage, getting notified when bug gets resolved or reopened, discussion in the component your are a peer of etc. I. e. I would like to get rid of some bugs which change the status from unconfirmed to new (and already know that when I get cc-ed). Existing bug dependencies should also be changed to tags which would i.e. allow to get of bugmails for bugs you filed.<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==L10n==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Labs==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools Lab / Bespin==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Thunderhead: Cross browser JavaScript UI toolkit<br />
|Work with us to implement a cross browser UI toolkit experiment, code named "Thunderhead"<br />
|Dion Almaer & Ben Galbraith<br />
|<br />
|<br />
|-<br />
|Bespin: Pluggable Syntax Highlighting<br />
|Build a syntax highlighter that groks emacs, vim, and Textmate highlighter files<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Offline editing<br />
|Create an offline Bespin editing experience<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Server Side JavaScript<br />
|Create a server side JavaScript Bespin server implementation<br />
|Kevin Dangoor<br />
|<br />
|<br />
|-<br />
|Bespin: Heuristic analysis<br />
|Build server side rules analysis to check project code for errors and hints<br />
|Dion Almaer<br />
|<br />
|<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode09:Brainstorming&diff=135626
Community:SummerOfCode09:Brainstorming
2009-03-23T20:24:14Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div>This page is for submitting ideas for Summer of Code projects for 2009. Therefore, it will inevitably contain suggestions of wildly variable quality. Ideas approved by the SoC admins are [[Community:SummerOfCode09|here]].<br />
<br />
==How To Make Good Suggestions==<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. Potential mentors [[Community:SummerOfCode09:Mentors|sign up here]].<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
<br />
([http://weblogs.mozillazine.org/gerv/archives/2006/05/making_a_soc_project_list.html More thoughts on making a good list])<br />
<br />
==Suggestion List==<br />
<br />
Last year's ideas: [[Community:SummerOfCode08|Confirmed]], [[Community:SummerOfCode08:Brainstorming|Brainstorming]]<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Metalink support<br />
| Native support for the [[Metalink]] Download Description (XML) format ({{bug|331979}}) which lists mirrors and checksums, along with other useful metadata such as mirror location. Listing multiple URLs for a file increases availability while the checksums guarantee integrity and let downloads be repaired automatically. You can also filter downloads by location and other things. Metalink is currently supported by most download managers including DownThemAll!<br />
It would also be great to have Mozilla people involved with Metalink as well.<br />
|Ant Bryan<br />
|<br />
|Comments in the bug suggest that this would not be particularly well received by the network team. Sorry... -- Gerv<br />
|-<br />
|<strike>Support system spellcheck services on Mac and/or Linux/GTK</strike><br />
|<strike>Currently Firefox and other Mozilla products bundle the Hunspell spell-checking engine. It would be great if we could (perhaps optionally at build time and/or run-time) use the system dictionary. For example, that would let people use an existing "user dictionary" of words they've added in other applications. On Mac, there's [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSpellChecker_Class/Reference/Reference.html NSSpellChecker] and GTK applications seem to use [http://www.abisource.com/projects/enchant/ Enchant]. The simplest approach would probably be to add a build-time option to use Enchant or NSSpellChecker instead of Hunspell, with code #ifdefs to call those other APIs instead of Hunspell.</strike><br />
|<strike>Robert O'Callahan</strike><br />
|<br />
|The Mac code already exists, and all Moz apps used to use it on the trunk prior to 2008. However, there was much rancor, and osxspell was turned off for all applications other than Camino. Before someone invests time in this again, it's probably a good idea to get everyone on the same page as to whether it's really wanted or not (and/or if the complaints can be addressed). See {{bug|422760}}, {{bug|419959}}, and {{bug|343535}} (particularly comments 5 and 10) for the backstory and known issues. —[[User:Sardisson|sardisson]]<br />
Oh dear. Thanks for the heads-up! [[User:Roc|roc]]<br />
|-<br />
|Windows 7 Jump List<br />
|Jump List will be one of the major interface changes in Windows 7, which provides shortcuts for software features right in Windows Taskbar. If there is an XPCOM component for Windows 7 Jump List, user experience in Windows 7 will be improved a lot. ({{bug|473045}})<br />
|[[User:Littlebtc|Littlebtc]]<br />
|<br />
| To me, the major problem is that implementation/example of Jump List COM API does not work for me in Windows 7 Public Beta Build 7000. Is there any workaround? --[[User:Littlebtc|Littlebtc]] 21:57, 22 March 2009 (UTC)<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Printable CSS repository<br />
|The other day I [http://robert.accettura.com/blog/2009/02/05/printable-stylesheets-to-save-the-environment/ mentioned how cool printable stylesheets were]. I figured I'd write up an idea for a Firefox addon (or perhaps a future feature). It would make a pretty cool summer of code project (or two depending on if you split it up). The idea is not all that different from [http://userstyles.org/userstyles Userstyles] or [https://addons.mozilla.org/en-US/firefox/addon/748 GreaseMonkey] though intends to be easier to use.<br />
<br />
On the client side when attempting to print a page the addon would inject a printable stylesheet to make the printable output waste less paper, be more readable and just ascetically superior to raw printing. Since each site is unique if it didn't have a stylesheet for the site already it would query a central repository for stylesheets that match that url. If one or more is found it would be offered to the user as a stylesheet that could be installed and then printed with. Installing leaves a copy on the clients computer so that it could be used even in offline mode and if the repository were unavailable.<br />
<br />
On the server side of things there would obviously need to be a repository of stylesheets and a way to review and rate them. For privacy purposes I think there should be no remote loading content in the stylesheet that doesn't originate on the server which the stylesheet is for (for example a sites logo would be ok if served from the site's server). Ratings and reviews would let the better ones gravitate to the top and the poorer ones fall to the bottom.<br />
<br />
This approach is better than the more popular "select what you want to print" since it allows for not just printing a block of text, but printing web pages in a more meaningful and readable way.<br />
|[[User:Raccettura|Raccettura]]<br />
|<br />
|<br />
|-<br />
|Back- and Frontend for storing web pages<br />
|[[User:Archaeopteryx/Concept:Personal_web|Personal web]]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=287066 bug 287066] [https://bugzilla.mozilla.org/show_bug.cgi?id=342916 bug 342916]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=342917 bug 342917]<br />
Today the internet is an essential part of work and life, people have personal browsing habits and some things what they see and read they want to remember later or give to someone else. These pages define very good what the user wants, so they should be used for customization. Furthermore, addresses aren't available for infinity.<br />
Goals<br />
* Integration into bookmarks<br />
* Weave integration<br />
* Backend support for fulltext address bar search<br />
* Backend for extensions which detected updated webpages by source code comparing<br />
* Making documents and files offline available, but be still able to update them via Firefox<br />
* Save multiple captures of a web page<br />
|Archaeopteryx<br />
|Someone from the Places team?<br />
|<br />
|-<br />
|Support [http://en.wikipedia.org/wiki/Ed2k_URI_scheme ed2k:// hyperlinks] (ed2k/Kad network)<br />
|Create an extension that facilitates getting content from the (already existing) distributed serverless [http://en.wikipedia.org/wiki/Kad_network Kad network] and thus allows HTML/CSS constructs like the following:<br />
<br />
* <code>&lt;img src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;object src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;video src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;audio src="ed2k://..."&gt;</code><br />
<br />
* <span style="white-space: nowrap;"><code>@font-face { ... src: url(ed2k://...); ... }</code></span><br />
<br />
* <code>background-image: url(ed2k://...);</code><br />
<br />
The idea is that '''''content does not need centralized Web hosting if it has enough readers willing to participate in file exchange.'''''<br />
<br />
----<br />
<br />
The student is not expected to create a brand new Kad [http://en.wikipedia.org/wiki/Servent servent] software from the scratch. The extension should (instead) be able to install (if not installed previously) and then use an existing ed2k/Kad software on the user's machine (free software such as [http://www.emule-project.net/ eMule] or [http://en.wikipedia.org/wiki/MLDonkey MLDonkey], probably both should be known); the extension should just be able to determine (using ed2k and AICH hashes and file size given in the URL) whether the designated object exists in servent's cache; thus the extension's algorithm for serving content to Firefox is like the following:<br />
<br />
* If the ed2k://... URL designates an object that exists in servent's cache, grab it.<br />
<br />
* If the ed2k://... URL designates an object that does not exist in servent's cache, launch the servent (if not already running) and feed the URL into the servent.<br />
** If the object is not popular enough to be downloaded within a reasonable amount of time (e.g. half a minute), the extension signals to Firefox that request failed (similar to <code>504 Gateway Timeout</code> of HTTP), but servent continues getting the object and thus the subsequent requests for the same object (e.g. when the page is reloaded) are more likely to be successful.<br />
<br />
----<br />
<br />
'''Note:''' if the «ed2k://» URL has <span style="white-space: nowrap;">«s=<nowiki>http://</nowiki>...»</span> optional part (see «The ed2k link format» section in [http://web.archive.org/web/20050623081914/http://www.edonkey2000.com/documentation/distro.html the Internet Archive page of Overnet]), the extension should try the given Web URL first, and only if it fails (or if the given response does not match URL's filesize/ed2k hash/AICH hash) use the local servent.<br />
<br />
|[[User:Mithgol the Webmaster|Mithgol the Webmaster]]<br />
|<br />
|Previous efforts to add Bittorrent support to Firefox have fizzled. A compelling case would need to be made for a) adding P2P support at all, and b) choosing ed2k rather than bittorrent, particularly as bittorrent has libraries which could be integrated directly rather than the fairly hacky external program solution proposed here. -- Gerv<br />
|-<br />
|OpenSearch: Support resultURLs and descriptions from search suggestions<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=386591 resultURLs]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=481423 descriptions]<br />
resultURLs are very helpful for catalog searches (i. e. Wikipedia, shops, libraries, ...), descriptions for uncommon or very specific suggestions<br />
|Archaeopteryx<br />
|Gavin? (see bug)<br />
|This doesn't look to me like it's big enough, or that Gavin is interested in mentoring it... :-( -- Gerv<br />
|-<br />
|Provide Firefox MSI package<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=231062 bug 231062]<br />
MSI packages of Firefox are a long desired feature and would help enterprise users. Maybe Thunderbird could also benefit from this work.<br />
[http://msdn.microsoft.com/en-us/library/cc185688(VS.85).aspx More info from Microsoft]<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Implement more of pop3, imap and smtp fakeserver<br />
| Would be nice if [[MailNews:Fakeserver]] would implement more of the protocols. Would also be nice to be able to have a UI on top of Fakeserver to be able to add emails in mailboxes.<br />
| Ludovic Hirlimann<br />
|}<br />
<br />
==Calendar==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Sync Lightning code to Sunbird (1.0-post Sunbird support)<br />
|[http://weblogs.mozillazine.org/calendar/2009/02/calendar_project_at_a_critical.html Calendar blog post]<br />
Lightning's Calendar and Task mode should be ported to Sunbird, also the Today sidebar, either by modifying existing code or setting up a repacking script which integrates Lightning into Thunderbird, hides the mail UI and brands the build as Sunbird (including Sunbird UI)<br />
|Archaeopteryx<br />
|Fallen?<br />
|<br />
|-<br />
|Enhanced task management<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=194863 Nested tasks]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=357502 All day tasks]<br />
Current task support is very basic. All day tasks (which don't calendar pane stuff like today's tasks) and nested task supported would advance the user experience<br />
|Archaeopteryx<br />
|Mailed Fred, no response yet<br />
|<br />
|}<br />
<br />
==Camino==<br />
'''''N.B.''' Camino brainstorming is taking place [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects on the Camino wiki]. Mike Pinkerton or Stuart Morgan will add vetted project ideas with mentors.''<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Folder Views<br />
| We provide the ability to create and use message views for pre-filtering which messages to show in the thread pane. We don't have a comparable feature yet in the folder pane...<br />
While this would basically mean to port Thunderbird's {bug|251296}, the UI should be more in sync with the SeaMonkey look and feel, e.g. columns for unread count, size, etc; a drop down menu for switching views; allow custom folder views; ...<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| <br />
|}<br />
<br />
==Bugzilla==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Refactor Bugzilla::Bugmail into real objects<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=301447 bug 301447]<br />
Enhancing the the module for sending bugmails would allow further enhancements like HTML-based stuff<br />
|Archaeopteryx<br />
|<br />
|mkanat suggests both of these ideas are the wrong size for GSoC, and unfortunately the Bugzilla project doesn't have any mentors anyway :-( -- Gerv<br />
|-<br />
|tag-based email preferences<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=482207 bug 482207]<br />
If a user adds a tag to a bug, he should be able to specify email preferences for this tag. This would be helpful because votes, ccs and watches can happen for different reasons, even of the same event class, i. e. bug triage, getting notified when bug gets resolved or reopened, discussion in the component your are a peer of etc. I. e. I would like to get rid of some bugs which change the status from unconfirmed to new (and already know that when I get cc-ed). Existing bug dependencies should also be changed to tags which would i.e. allow to get of bugmails for bugs you filed.<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==L10n==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Labs==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools Lab / Bespin==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Thunderhead: Cross browser JavaScript UI toolkit<br />
|Work with us to implement a cross browser UI toolkit experiment, code named "Thunderhead"<br />
|Dion Almaer & Ben Galbraith<br />
|<br />
|<br />
|-<br />
|Bespin: Pluggable Syntax Highlighting<br />
|Build a syntax highlighter that groks emacs, vim, and Textmate highlighter files<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Offline editing<br />
|Create an offline Bespin editing experience<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Server Side JavaScript<br />
|Create a server side JavaScript Bespin server implementation<br />
|Kevin Dangoor<br />
|<br />
|<br />
|-<br />
|Bespin: Heuristic analysis<br />
|Build server side rules analysis to check project code for errors and hints<br />
|Dion Almaer<br />
|<br />
|<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=Community:SummerOfCode09:Brainstorming&diff=135257
Community:SummerOfCode09:Brainstorming
2009-03-21T14:02:05Z
<p>Mnyromyr: /* SeaMonkey */</p>
<hr />
<div>This page is for submitting ideas for Summer of Code projects for 2009. Therefore, it will inevitably contain suggestions of wildly variable quality. Ideas approved by the SoC admins are [[Community:SummerOfCode09|here]].<br />
<br />
==How To Make Good Suggestions==<br />
<br />
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.<br />
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.<br />
* '''Do your research'''. Support the idea with well-researched links.<br />
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment. <br />
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. Potential mentors [[Community:SummerOfCode09:Mentors|sign up here]].<br />
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.<br />
<br />
([http://weblogs.mozillazine.org/gerv/archives/2006/05/making_a_soc_project_list.html More thoughts on making a good list])<br />
<br />
==Suggestion List==<br />
<br />
Last year's ideas: [[Community:SummerOfCode08|Confirmed]], [[Community:SummerOfCode08:Brainstorming|Brainstorming]]<br />
<br />
==Mozilla IT Infrastructure==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Platform==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Metalink support<br />
| Native support for the [[Metalink]] Download Description (XML) format ({{bug|331979}}) which lists mirrors and checksums, along with other useful metadata such as mirror location. Listing multiple URLs for a file increases availability while the checksums guarantee integrity and let downloads be repaired automatically. You can also filter downloads by location and other things. Metalink is currently supported by most download managers including DownThemAll!<br />
It would also be great to have Mozilla people involved with Metalink as well.<br />
|Ant Bryan<br />
|<br />
|Comments in the bug suggest that this would not be particularly well received by the network team. :-| -- Gerv<br />
|-<br />
|<strike>Support system spellcheck services on Mac and/or Linux/GTK</strike><br />
|<strike>Currently Firefox and other Mozilla products bundle the Hunspell spell-checking engine. It would be great if we could (perhaps optionally at build time and/or run-time) use the system dictionary. For example, that would let people use an existing "user dictionary" of words they've added in other applications. On Mac, there's [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSSpellChecker_Class/Reference/Reference.html NSSpellChecker] and GTK applications seem to use [http://www.abisource.com/projects/enchant/ Enchant]. The simplest approach would probably be to add a build-time option to use Enchant or NSSpellChecker instead of Hunspell, with code #ifdefs to call those other APIs instead of Hunspell.</strike><br />
|<strike>Robert O'Callahan</strike><br />
|<br />
|The Mac code already exists, and all Moz apps used to use it on the trunk prior to 2008. However, there was much rancor, and osxspell was turned off for all applications other than Camino. Before someone invests time in this again, it's probably a good idea to get everyone on the same page as to whether it's really wanted or not (and/or if the complaints can be addressed). See {{bug|422760}}, {{bug|419959}}, and {{bug|343535}} (particularly comments 5 and 10) for the backstory and known issues. —[[User:Sardisson|sardisson]]<br />
Oh dear. Thanks for the heads-up! [[User:Roc|roc]]<br />
|}<br />
<br />
==Firefox==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Printable CSS repository<br />
|The other day I [http://robert.accettura.com/blog/2009/02/05/printable-stylesheets-to-save-the-environment/ mentioned how cool printable stylesheets were]. I figured I'd write up an idea for a Firefox addon (or perhaps a future feature). It would make a pretty cool summer of code project (or two depending on if you split it up). The idea is not all that different from [http://userstyles.org/userstyles Userstyles] or [https://addons.mozilla.org/en-US/firefox/addon/748 GreaseMonkey] though intends to be easier to use.<br />
<br />
On the client side when attempting to print a page the addon would inject a printable stylesheet to make the printable output waste less paper, be more readable and just ascetically superior to raw printing. Since each site is unique if it didn't have a stylesheet for the site already it would query a central repository for stylesheets that match that url. If one or more is found it would be offered to the user as a stylesheet that could be installed and then printed with. Installing leaves a copy on the clients computer so that it could be used even in offline mode and if the repository were unavailable.<br />
<br />
On the server side of things there would obviously need to be a repository of stylesheets and a way to review and rate them. For privacy purposes I think there should be no remote loading content in the stylesheet that doesn't originate on the server which the stylesheet is for (for example a sites logo would be ok if served from the site's server). Ratings and reviews would let the better ones gravitate to the top and the poorer ones fall to the bottom.<br />
<br />
This approach is better than the more popular "select what you want to print" since it allows for not just printing a block of text, but printing web pages in a more meaningful and readable way.<br />
|[[User:Raccettura|Raccettura]]<br />
|<br />
|<br />
|-<br />
|Back- and Frontend for storing web pages<br />
|[[User:Archaeopteryx/Concept:Personal_web|Personal web]]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=287066 bug 287066] [https://bugzilla.mozilla.org/show_bug.cgi?id=342916 bug 342916]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=342917 bug 342917]<br />
Today the internet is an essential part of work and life, people have personal browsing habits and some things what they see and read they want to remember later or give to someone else. These pages define very good what the user wants, so they should be used for customization. Furthermore, addresses aren't available for infinity.<br />
Goals<br />
* Integration into bookmarks<br />
* Weave integration<br />
* Backend support for fulltext address bar search<br />
* Backend for extensions which detected updated webpages by source code comparing<br />
* Making documents and files offline available, but be still able to update them via Firefox<br />
* Save multiple captures of a web page<br />
|Archaeopteryx<br />
|Someone from the Places team?<br />
|<br />
|-<br />
|Support [http://en.wikipedia.org/wiki/Ed2k_URI_scheme ed2k:// hyperlinks] (ed2k/Kad network)<br />
|Create an extension that facilitates getting content from the (already existing) distributed serverless [http://en.wikipedia.org/wiki/Kad_network Kad network] and thus allows HTML/CSS constructs like the following:<br />
<br />
* <code>&lt;img src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;object src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;video src="ed2k://..."&gt;</code><br />
<br />
* <code>&lt;audio src="ed2k://..."&gt;</code><br />
<br />
* <span style="white-space: nowrap;"><code>@font-face { ... src: url(ed2k://...); ... }</code></span><br />
<br />
* <code>background-image: url(ed2k://...);</code><br />
<br />
The idea is that '''''content does not need centralized Web hosting if it has enough readers willing to participate in file exchange.'''''<br />
<br />
----<br />
<br />
The student is not expected to create a brand new Kad [http://en.wikipedia.org/wiki/Servent servent] software from the scratch. The extension should (instead) be able to install (if not installed previously) and then use an existing ed2k/Kad software on the user's machine (free software such as [http://www.emule-project.net/ eMule] or [http://en.wikipedia.org/wiki/MLDonkey MLDonkey], probably both should be known); the extension should just be able to determine (using ed2k and AICH hashes and file size given in the URL) whether the designated object exists in servent's cache; thus the extension's algorithm for serving content to Firefox is like the following:<br />
<br />
* If the ed2k://... URL designates an object that exists in servent's cache, grab it.<br />
<br />
* If the ed2k://... URL designates an object that does not exist in servent's cache, launch the servent (if not already running) and feed the URL into the servent.<br />
** If the object is not popular enough to be downloaded within a reasonable amount of time (e.g. half a minute), the extension signals to Firefox that request failed (similar to <code>504 Gateway Timeout</code> of HTTP), but servent continues getting the object and thus the subsequent requests for the same object (e.g. when the page is reloaded) are more likely to be successful.<br />
<br />
----<br />
<br />
'''Note:''' if the «ed2k://» URL has <span style="white-space: nowrap;">«s=<nowiki>http://</nowiki>...»</span> optional part (see «The ed2k link format» section in [http://web.archive.org/web/20050623081914/http://www.edonkey2000.com/documentation/distro.html the Internet Archive page of Overnet]), the extension should try the given Web URL first, and only if it fails (or if the given response does not match URL's filesize/ed2k hash/AICH hash) use the local servent.<br />
<br />
|[[User:Mithgol the Webmaster|Mithgol the Webmaster]]<br />
|<br />
|Previous efforts to add Bittorrent support to Firefox have fizzled. A compelling case would need to be made for a) adding P2P support at all, and b) choosing ed2k rather than bittorrent, particularly as bittorrent has libraries which could be integrated directly rather than the fairly hacky external program solution proposed here. -- Gerv<br />
|-<br />
|OpenSearch: Support resultURLs and descriptions from search suggestions<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=386591 resultURLs]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=481423 descriptions]<br />
resultURLs are very helpful for catalog searches (i. e. Wikipedia, shops, libraries, ...), descriptions for uncommon or very specific suggestions<br />
|Archaeopteryx<br />
|Gavin? (see bug)<br />
|This doesn't look to me like it's big enough, or that Gavin is interested in mentoring it... :-( -- Gerv<br />
|-<br />
|Provide Firefox MSI package<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=231062 bug 231062]<br />
MSI packages of Firefox are a long desired feature and would help enterprise users. Maybe Thunderbird could also benefit from this work.<br />
[http://msdn.microsoft.com/en-us/library/cc185688(VS.85).aspx More info from Microsoft]<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==Thunderbird==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Implement more of pop3, imap and smtp fakeserver<br />
| Would be nice if [[MailNews:Fakeserver]] would implement more of the protocols. Would also be nice to be able to have a UI on top of Fakeserver to be able to add emails in mailboxes.<br />
| Ludovic Hirlimann<br />
|}<br />
<br />
==Calendar==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Sync Lightning code to Sunbird (1.0-post Sunbird support)<br />
|[http://weblogs.mozillazine.org/calendar/2009/02/calendar_project_at_a_critical.html Calendar blog post]<br />
Lightning's Calendar and Task mode should be ported to Sunbird, also the Today sidebar, either by modifying existing code or setting up a repacking script which integrates Lightning into Thunderbird, hides the mail UI and brands the build as Sunbird (including Sunbird UI)<br />
|Archaeopteryx<br />
|Fallen?<br />
|<br />
|-<br />
|Enhanced task management<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=194863 Nested tasks]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=357502 All day tasks]<br />
Current task support is very basic. All day tasks (which don't calendar pane stuff like today's tasks) and nested task supported would advance the user experience<br />
|Archaeopteryx<br />
|Mailed Fred, no response yet<br />
|<br />
|}<br />
<br />
==Camino==<br />
'''''N.B.''' Camino brainstorming is taking place [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects on the Camino wiki]. Mike Pinkerton or Stuart Morgan will add vetted project ideas with mentors.''<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==SeaMonkey==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
| Message Filter UI Overhaul<br />
| The current message filter UI is rather hard to work with and doesn't even provide the complexity the backend would allow. I propose to:<br />
* integrate the account hierarchy into the rule list<br />
* integrate the actual rules into the rule list, allowing "inline editing" (this may mean a bigger dialog window and twisties to collapse accounts/rules)<br />
* allow nested rules (and/or)<br />
* improve overall usability by allowing to copy rules, defining drag'n'drop and context menus, etc.<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| [[User:Mnyromyr|Karsten Düsterloh]]<br />
| FilterListDialog.xul is almost identical in both SeaMonkey and Thunderbird, so it shouldn't be too hard to fix both or derive a TB version easily.<br />
|}<br />
<br />
==Bugzilla==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Refactor Bugzilla::Bugmail into real objects<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=301447 bug 301447]<br />
Enhancing the the module for sending bugmails would allow further enhancements like HTML-based stuff<br />
|Archaeopteryx<br />
|<br />
|<br />
|-<br />
|tag-based email preferences<br />
|[https://bugzilla.mozilla.org/show_bug.cgi?id=482207 bug 482207]<br />
If a user adds a tag to a bug, he should be able to specify email preferences for this tag. This would be helpful because votes, ccs and watches can happen for different reasons, even of the same event class, i. e. bug triage, getting notified when bug gets resolved or reopened, discussion in the component your are a peer of etc. I. e. I would like to get rid of some bugs which change the status from unconfirmed to new (and already know that when I get cc-ed). Existing bug dependencies should also be changed to tags which would i.e. allow to get of bugmails for bugs you filed.<br />
|Archaeopteryx<br />
|<br />
|<br />
|}<br />
<br />
==L10n==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Firefox Support (Sumo)==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Rhino==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mobile/Fennec==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Mozilla Labs==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|}<br />
<br />
==Developer Tools Lab / Bespin==<br />
<br />
{| class="standard-table"<br />
|-<br />
!Title<br />
!Abstract - links to details/bugs/etc<br />
!Reporter<br />
!Mentor(s)<br />
!Comments<br />
|-<br />
|Thunderhead: Cross browser JavaScript UI toolkit<br />
|Work with us to implement a cross browser UI toolkit experiment, code named "Thunderhead"<br />
|Dion Almaer & Ben Galbraith<br />
|<br />
|<br />
|-<br />
|Bespin: Pluggable Syntax Highlighting<br />
|Build a syntax highlighter that groks emacs, vim, and Textmate highlighter files<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Offline editing<br />
|Create an offline Bespin editing experience<br />
|Dion Almaer<br />
|<br />
|<br />
|-<br />
|Bespin: Server Side JavaScript<br />
|Create a server side JavaScript Bespin server implementation<br />
|Kevin Dangoor<br />
|<br />
|<br />
|-<br />
|Bespin: Heuristic analysis<br />
|Build server side rules analysis to check project code for errors and hints<br />
|Dion Almaer<br />
|<br />
|<br />
|}</div>
Mnyromyr
https://wiki.mozilla.org/index.php?title=SeaMonkey/StatusMeetings/2009-02-24&diff=130849
SeaMonkey/StatusMeetings/2009-02-24
2009-02-26T19:59:39Z
<p>Mnyromyr: /* Mnyromyr */</p>
<hr />
<div><small>[[SeaMonkey:StatusMeetings:2009-02-10|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]]</small><br />
<br />
'''SeaMonkey Meeting Details'''<br />
<br />
* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=24&month=02&year=2009&hour=13&min=0&sec=0&p1=0 February 24, 2009, 13:00 UTC]<br />
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]<br />
<br />
== Agenda ==<br />
* Who's taking minutes? -> '''Ratty'''<br />
<br />
=== Action Items ===<br />
(who needs to do what that hasn't been recorded in a bug)<br />
* Find a volunteer to drive the Modern theme updates into the tree.<br />
* Make sure a bug is filed to create the UI for the mail archiving function available in the backend.<br />
* SeaMonkey developers will need to nominate bugs for Beta 1.<br />
* Create new bugzilla components: session store, Tabs and Toolbars (to match Firefox and Thunderbird).<br />
* The fishcam webpage needs to replace the "Get Firefox" button with a "Get SeaMonkey" button or at least add a SeaMonkey one. '''Assigned to KaiRo'''.<br />
<br />
=== SeaMonkey 2 Alpha 3 ===<br />
<br />
Bug Queries<br />
<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B open blockers]<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B all blockers]<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%3F blocker requests]<br />
<br />
* Relbranched, tagged, and build a first build: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a3-candidates/build1/<br />
* Built a second release candidate, see: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0a3-candidates/build2/<br />
** Crash {{Bug|479206}} included in this build.<br />
* Only one blocker left which is to [https://bugzilla.mozilla.org/show_bug.cgi?id=479175 Create the 2.0a3 release notes].<br />
* We're also watching closely what Thunderbird is doing. If they respin again, we would probably have to do the same.<br />
<br />
=== SeaMonkey 2 Beta 1 ===<br />
<br />
Bug Queries<br />
<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0b1%2B open blockers]<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0b1%2B all blockers]<br />
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0b1%3F blocker requests]<br />
<br />
* This will be the next milestone, but there are no firm plans yet.<br />
* The target is probably about 6-8 weeks from now.<br />
<br />
=== Longer-Term SeaMonkey 2 Planning ===<br />
<br />
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%2B open wanted]<br />
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%3F wanted requests]<br />
<br />
Major wanted/needed features:<br />
<br />
* {{bug|381157}} Download manager backend.<br />
** status/progress?<br />
*{{bug|472001}} UI for download manager.<br />
** Review done as far as possible with the code only. Waiting on backend.<br />
* {{bug|36810}} Session restore.<br />
** '''landed in time for 2.0a3!'''<br />
** Misak is working on followup bugs such as:<br />
*** {{Bug|478707}} (SeaMonkey sessionstore saves, but doesn't restore closed tabs list).<br />
* Toolbar customization:<br />
** {{bug|394288}} (Navigator): Fixed. All dependencies fixed.<br />
*** Someone can work on legacy bugs that depend on this e.g. optional toolbar buttons for Find in Page, Zoom and so forth.<br />
*** TODO Polish: {{Bug|475921}} (tidy up CSS) {{Bug|464653 }} (Fine Tune the toolbar context menu).<br />
** Toolkit {{Bug|476814}} (Unfork/Unify customizeToolbar.* and customizeToolbarSheet.*) has been checked in on trunk; and it needs to land on 1.9.1 subsequently as well. However this isn't urgent since currently we are using a forked copy.<br />
** {{bug|413385}} (MailNews): It would be preferable to have small icons for the MailNews window first. And turning customization on may break some of the more complicated and XBLfied button widgets. However I think it's best to start on this and catch regressions early.<br />
** The Council will have to decide on which other windows to turn on toolbar customization. The procedure is essentially:<br />
*** 1. Make suitable small icons.<br />
*** 2. Turn on the customize code (just call the code already in utilityOverlay.*).<br />
*** 3. Catch regressions.<br />
* {{bug|456757}} Modern theme update<br />
** The next step is to file bugs/patches for each sub-module under mozapps/ in order to get reviewed. Ideally a graphically oriented person should to drive this - '''helpwanted'''.<br />
** '''If someone (who is reading this) understands our review process and can drive the existing stuff into the tree, please help us there!'''<br />
* {{bug|460699}} Make the default theme look better on mac.<br />
** No progress at the moment but stefanh says he will look into this soon.<br />
* {{bug|454847}} Fishcam update.<br />
** '''landed in time for 2.0a3'''<br />
** Pointing to http://www.fishcam.com/ now, which has a nice new camera up.<br />
** The webcam page needs to replace the "Get Firefox" button with a '''"Get SeaMonkey" button''' or at least add a SeaMonkey one.<br />
* {{bug|410613}} OpenSearch.<br />
** '''helpwanted'''<br />
* {{bug|460953}} Port jminta's kill-rdf to SeaMonkey where applicable.<br />
** mcsmurf has a large patch ready for one particular area but it needs review and isn't a priority at the moment.<br />
* {{bug|415372}} Implement Feed Preview.<br />
** No progress since the last report.<br />
** {{Bug|471346}} (Port GetDefaultFeedReader to SeaMonkey shell service).<br />
*** Need to update the patch to use the Windows API directly, not via nsIWindowsRegKey.<br />
* {{bug|460960}} Port Thunderbird tabbed interface to MailNews.<br />
** Mnyromyr was successful in the distanglement of the UI so we can now separate tabmail from Thunderbird.<br />
* {{Bug|449728}} Write front-end code to handle Drag & Drop tabs between browser windows back end introduced in {{Bug|113934}}.<br />
<br />
=== Roundtable ===<br />
<br />
Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).<br />
<br />
==== ajschult ====<br />
==== asrail ====<br />
* Almost no time for coding this week. See: <br />
https://wiki.mozilla.org/SeaMonkey:StatusMeetings:2009-02-10#asrail<br />
<br />
==== biesi ====<br />
==== Callek ====<br />
==== IanN ====<br />
* {{bug|471932}} Do some tidy up/fixing of feed subscription and related code - fixes lots of issues with the new shared code - new patch with updated folderDeleted tests is '''STILL''' waiting for review.<br />
* Usual reviewing and commenting.<br />
* Hopefully will have time next week to do some more coding.<br />
<br />
==== KaiRo ====<br />
* Away this week for being one of four representatives of Mozilla at [http://liftconference.com/lift09/ Lift09 in Geneva].<br />
* As always, [http://home.kairo.at/blog/ my blog] has more detailed status about my work.<br />
<br />
==== mcsmurf ====<br />
* Looked into {{bug|466994}} (New FAYT implementation prevents entering any text in text input boxes while search is active) Collected some ideas for fixing this, implemented a patch locally, currently only works for text input boxen in the same tab; does not work for other tabs or text input in chrome.<br />
* {{bug|476988}} SeaMonkey crashes just after profile selection panel display, when Sm is invoked via internet shortcut. Attached a patch to this bug, still need to request review.<br />
* {{bug|467249}} Modify folderWidgets.xml to be able to XBLify the Go menu in MailNews. Got review for the patch, need to check this in. When this is checked in, quite some code in the MailNews UI can be replaced with XBL bindings.<br />
* Did some reviewing of installer patches.<br />
<br />
==== Misak ====<br />
* Session restore landing and followup patches.<br />
* {{bug|425480}} (non-ASCII characters should be decoded in the urlbar) and followups.<br />
<br />
==== Mnyromyr ====<br />
* finally finished sifting through mailnews ui chaos, resulting in a first patch for {{bug|390262}} <br />
* tabmail progress stalled until next week<br />
<br />
==== MReimer ====<br />
==== Neil ====<br />
==== Ratty ====<br />
* Bug triage, especially concentrating on the fallout from the [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2009-02-18+20%3A00&chfieldto=2009-02-19&chfield=resolution&chfieldvalue=EXPIRED&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 182 bugs mass closed without review].<br />
* Keeping the Mozillazine forum readers informed with the latest SeaMonkey developments and general SeaMonkey evangelism (unfortunately all these new features just makes them even more impatient for 2.0 final).<br />
* Tracking requirements for Calendar integration in both SeaMonkey and Thunderbird.<br />
<br />
==== sgautherie ====<br />
*Fixed (<i>or in-progress</i>) SeaMonkey bugs:<br />
** {{bug|477355}} nsWindowsShellService::SetDefaultClientVista is not used and can be removed<br />
** <i>{{bug|467015}} "warning C4005: 'FILE_ILLEGAL_CHARACTERS' : macro redefinition"</i><br />
*<i>And working on other areas... like</i><br />
** infrastructure to run tests<br />
** filing bugs for leaks in (TUnit and Reftest) tests<br />
** doing an (experimental) Windows mozilla-central SeaMonkey build, reporting to {{bug|470184}} issue tracking; hoping for {{bug|464325}} new tinderboxes.<br />
<br />
==== Standard8 ====<br />
* See [[Thunderbird/StatusMeetings/2009-02-24#Standard8]]<br />
<br />
==== stefanh ====<br />
==== wladow ====<br />
<br />
=== Any other business? ===<br />
* SeaMonkey now has an "OS Integration" component in Bugzilla. Should be used for bugs in the shell service (and possibly other areas of code in the future).</div>
Mnyromyr