https://wiki.mozilla.org/api.php?action=feedcontributions&feedformat=atom&user=Mhoye 2026-08-08T16:47:54Z User contributions MediaWiki 1.39.10 https://wiki.mozilla.org/index.php?title=Modules/Activities&diff=1246804 2023-06-19T15:57:48Z

<p>Mhoye: Moving mhoye to emeritus.</p> <hr /> <div>&lt;noinclude&gt;<br /> '''Only module owners may edit this page.''' <br /> <br /> They may:<br /> <br /> * update any information about their module except the name of the owner<br /> * add or remove sub-modules<br /> * change the owner of a sub-module <br /> * add emeritus owners or peers<br /> <br /> Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br /> &lt;/noinclude&gt;<br /> {{Module<br /> |name=Governance<br /> |description=Policies and process for how we distribute authority and govern ourselves; including:<br /> * Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br /> * Management of the source tree<br /> * Balancing different constituencies of the Mozilla project<br /> * Maintaining the Mozilla identity as we take on new activities<br /> <br /> [http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=governance<br /> |url=https://wiki.mozilla.org/GovernanceIssues<br /> |components=mozilla.org::Governance<br /> }}<br /> <br /> ===Governance Sub Modules===<br /> <br /> {{Module<br /> |name=Module Ownership System<br /> |description=Healthy operation of the module ownership system, including topics such as:<br /> * Filling vacant roles where appropriate<br /> * Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br /> * Creating and staffing new modules where new parts of the project evolve.<br /> * Figuring out what to do if a module isn't getting enough attention<br /> * Resolving conflicts among module owners <br /> |owner= [mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker], Guillermo Movia (as 'observer'. This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br /> |ownersemeritus=Brendan Eich<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Commit Access Management<br /> |description= Governance structure for the work of implementing, managing and enforcing Mozilla's commit access systems and policies.<br /> |owner=[mailto:glob@mozilla.com glob]<br /> |peers=[mailto:mconnor@mozilla.com Mike Connor], [mailto:jlin@mozilla.com Jonathan Lin], [mailto:mhristova@mozilla.com Mira Hristova], [mailto:jdirks@mozilla.com James Dirks]<br /> |ownersemeritus=Mitchell Baker, Josh Matthews<br /> |peersemeritus=Marcia Knous<br /> |group=<br /> |url=http://www.mozilla.org/hacking/committer/<br /> |components=mozilla.org::Repository Account Requests<br /> }}<br /> <br /> {{Module<br /> |name=Security Policy<br /> |description=Policies for handling security issues in Mozilla code<br /> |owner=[mailto:dveditz@mozilla.com Dan Veditz]<br /> |peers=[mailto:security@mozilla.org Tom Ritter]<br /> |peersemeritus= Al Billings<br /> |group=dev-security<br /> |url=http://www.mozilla.org/security/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla CA Certificate Policy<br /> |description=Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies.<br /> |owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |peers=[mailto:bwilson@mozilla.com Ben Wilson]<br /> |ownersemeritus=Frank Hecker, Wayne Thayer<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer<br /> |group=dev-security-policy<br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Code Review Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=<br /> |url=http://www.mozilla.org/hacking/reviewers.html<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Performance Regression Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |group=<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Planet Mozilla<br /> |description=Content and policy for planet.mozilla.org, including topics such as:<br /> * which blogs are syndicated to planet.mozilla.org<br /> * which content from syndicated blogs is included<br /> * other planet.mozilla.org policy issues <br /> |owner=<br /> |peers=[mailto:asa@mozilla.org Asa Dotzler]<br /> |group=<br /> |url=<br /> |components=Websites::planet.mozilla.org<br /> |ownersemeritus=Robert Accettura, Mike Hoye<br /> |peersemeritus=Reed Loden<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla Public License<br /> |description=Maintenance and development of the MPL<br /> * changes in the legal landscape which could /should be reflected<br /> * changes in FLOSS development practices which could / should be reflected <br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br /> |peersemeritus=Gervase Markham<br /> |group=governance-mpl-update<br /> |url=<br /> |components=mozilla.org::Licensing<br /> }}<br /> <br /> {{Module<br /> |name=CA Certificates<br /> |description=Determine which root certificates should be included in Mozilla software products, which trust bits should be set on them, and which of them should be enabled for EV treatment. Evaluate requests from Certification Authorities (CAs) for inclusion or removal of root certificates, and for updating trust bit settings or enabling EV treatment for already included root certificates.<br /> |owner=[mailto:bwilson@mozilla.com Ben Wilson]<br /> |peers=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |ownersemeritus=Frank Hecker, Kathleen Wilson<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Ryan Sleevi<br /> |group=dev-security-policy <br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=mozilla.org::CA Certificates<br /> }}<br /> <br /> {{Module<br /> |name=Participation Metrics<br /> |description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br /> * determining which questions are most important to ask (how many people do X?)<br /> * determining what data is relevant to answer these questions<br /> * designing and operating a system to generate the requested data<br /> * analyzing the resulting metrics<br /> * notifying appropriate people when participation starts to change significantly<br /> * assisting various groups to understand and use the metrics to strengthen participation<br /> * produce periodic report/analysis of participation metrics <br /> |owner=[mailto:ppapadeas@mozilla.com Pierros Papadeas]<br /> |peers=[mailto:dboswell@mozilla.com David Boswell], [mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]<br /> |group=<br /> |url=https://wiki.mozilla.org/Contribute/Dashboards<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Internet Public Policy<br /> |description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: &quot;courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives.&quot; <br /> This includes topics such as:<br /> *determining if Mozilla should take an official position on a particular public policy issue<br /> *determining what that position is <br /> *determining how mozilla communicates our position <br /> **global, multi-regional, regional or local action<br /> **direct action, or support of action by other aligned groups<br /> **public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD<br /> *strengthening local community capabilities to address public policy issues <br /> |owner=[mailto:handerson@mozilla.com Harvey Anderson]<br /> |peers=[mailto:mitchell@mozilla.org Mitchell Baker], [mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman]<br /> |url=https://wiki.mozilla.org/Netpolicy<br /> |group=https://mail.mozilla.org/listinfo/netpolicy<br /> |components=<br /> |notes=Area Expert Advisors: Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos<br /> }}<br /> Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not. <br /> <br /> <br /> {{Module<br /> |name=Weekly Project All Hands Meeting<br /> |description=Responsibility for the weekly meetings, including:<br /> * determining and implementing the best organization and structure for the meeting<br /> * Determining and implementing the most useful content<br /> * Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br /> |owner=[mailto:asa@mozilla.org Asa Dotzler]<br /> |peers=MoCo Desktop IT services<br /> |ownersemeritus=[mailto:potch@mozilla.com Matt Claypotch]<br /> |group=mozilla.governance<br /> |url=https://wiki.mozilla.org/WeeklyUpdates<br /> |components=<br /> }}<br /> <br /> (It's a new thing to have a group such as &quot;MoCo Desktop IT services&quot; as a<br /> &quot;peer.&quot; We're trying this based on the idea that anyone in the Desktop IT group<br /> should be able to resolve problems and make fixes to the systems.)<br /> <br /> ===Other===<br /> <br /> {{Module<br /> |name=Tree Sheriffs<br /> |description=Tree Sheriffs aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. <br /> |owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen] (:RyanVM)<br /> |peers=[mailto:shengst@mozilla.com Sebastian Hengst] (:Aryx)<br /> |ownersemeritus=Ed Morley<br /> |peersemeritus=Carsten Book, Wes Kocher<br /> |group=https://mail.mozilla.org/listinfo/sheriffs<br /> |url=https://wiki.mozilla.org/Sheriffing<br /> }}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Planet_Mozilla&diff=1246803 2023-06-19T15:55:56Z

<p>Mhoye: Removing mhoye as a contact.</p> <hr /> <div>Everything you ever wanted to know about [http://planet.mozilla.org/ Planet Mozilla], and then some.<br /> <br /> Planet Mozilla is a long-standing and incredibly valuable resource for the Mozilla Community. As our community has grown and number of projects increased, we (the Planet peers) have decided codify some of our previously-unwritten-but-generally-understood policies, and clarify the reasoning behind them. <br /> <br /> This document was last updated in November, 2017.<br /> <br /> == Being added to Planet Mozilla ==<br /> If you would like your blog syndicated on Planet Mozilla, please [http://bit.ly/planetmobug file a bug] requesting that we do so. The bug three things:<br /> <br /> # Your blog's URL.<br /> # A URL for a tagged feed you want included. Though not all feeds have tags, a tag is required for newly-added feeds. Please see the [https://wiki.mozilla.org/Planet_Mozilla#Tagged_Feeds Tagged Feeds] section for more information.<br /> # A short bio that we can use to announce your addition on the Planet Mozilla weblog <br /> # Some assurance that you meet the requirements below.<br /> <br /> === Approvals ===<br /> You must have some demonstrated, current involvement with the Mozilla project or community in order to be included on Planet Mozilla. This will be evaluated per-addition by members of the Planet team; Module owner approval is not required, but may of course be sought in the event of disagreement.<br /> <br /> Planet is a community of people, not products, services or bits. Each blog must be the work of an individual community member, and syndicated articles should (generally) be tagged for Planet inclusion. Participants are obviously free to blog about what they are working on, but we want to keep planet for the people, though exceptions will be made by the Planet team (Mozilla Blog, Planet blog, Mozilla team blogs, for example).<br /> <br /> If there are any questions that need to be answered prior to approval, they will be posted in the bug -- please remember to check your bug sporadically until it is closed and resolved.<br /> <br /> === Requesting feed changes ===<br /> If you move your blog or the feed URL changes for whatever reason, you can request that be updated on Planet without a second round of approvals. You simply need to [http://bit.ly/planetmobug file a bug] requesting the change.<br /> <br /> == Being removed from Planet Mozilla ==<br /> There are a number of reasons that a feed can be removed from Planet Mozilla:<br /> <br /> # It may be removed if the Planet team determines it violates the spirit of the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines] or [https://www.mozilla.org/en-US/about/legal/acceptable-use/ Conditions of Use.]<br /> # The person who owns the feed [http://bit.ly/planetmobug files a bug] to request its removal. Please note that unless there are clearly unusual circumstances no one else can request a blog be removed. Any requests for removal must come from or be confirmed by the blog owner.<br /> # The Planet team may remove feeds at their discretion (temporarily or permanently) for various reasons, including spam or illegal activities. <br /> # Blogs may be pulled from Planet for poor availability; The blog owner will be notified by a [http://bit.ly/planetmobug bug being filed], email, IRC, IM, or other communication means identifying the feed so that they can either fix their issue and be re-included or choose to be removed from Planet permanently. When removing a blog if a bug isn't filed, a commit message will indicate the action taken (notified on IRC, Twitter, etc.).<br /> <br /> == Having a blog post removed from Planet ==<br /> Individual posts can be removed from Planet if absolutely necessary, such as in rare instances when something private has been accidentally posted. The original poster must [http://bit.ly/planetmobug file a bug] to request the removal, and should contact a peer directly in cases of emergency. ''Posts will only be removed if the original post has also been removed from the source blog'', and due to the nature of syndicated feeds any private information such as passwords should be assumed to have been circulated regardless of how quickly the Planet team responds.<br /> <br /> == Tagged Feeds ==<br /> Because of its large, diverse and global audience, Planet is a powerful tool to amplify the voices of its participants. With that in mind, a tagged feed is intended to act as a trigger guard, indicating that an article's inclusion on Planet is deliberate. This should not be interpreted as a promise that the article in question is Mozilla-related, only that it is intended for the Planet audience. <br /> <br /> As a courtesy to that audience, we ask (but do not mandate) that articles on challenging, non-Mozilla topics have a brief summary at the beginning, outlining the contents. <br /> <br /> Some blog hosts - most notably Medium - do not support tagged feeds; if you are in the process of deciding where to host your blog, please keep this requirement in mind. On Medium, the workaround for this is to [https://help.medium.com/hc/en-us/articles/214874118-RSS-Feeds-of-publications-and-profiles create a publication dedicated to yourself] and ask Planet to syndicate tagged articles from that publication. Note that the standard syndication on Medium includes all your Medium activity, not just your written articles, which is almost certainly not what you - or the larger Planet audience - want.<br /> <br /> == Planet Mozilla Team ==<br /> * Module owner:<br /> ** [empty]<br /> * Peers:<br /> ** Asa Dotzler (&quot;asa&quot;, asa-AT-mozilla.org)<br /> &lt;i&gt;(please use planet-AT-mozilla.org to contact the entire team)&lt;/i&gt;<br /> <br /> == Working docs ==<br /> * [[Planet Mozilla/Channels]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Travel_Guide&diff=1243349 2022-07-11T20:38:05Z

<p>Mhoye: /* Staying healthy */</p> <hr /> <div><br /> = Travel doesn’t have to be terrible. =<br /> <br /> In fact, there may be no other part of your life where a handful of modest optimizations can make such an enormous difference. How different would travelling become, if:<br /> <br /> * You never lost your luggage.<br /> * You could get from the airport entrance to your flight's gate in minutes.<br /> * You had lounge access at the airport, upgraded flights, maybe even nicer rooms in hotels.<br /> * You knew you didn't have to eat junk on the road, but could discover great local restaurants instead.<br /> <br /> We have secrets. We have millions of miles travelled between us, and we'd like to show you how it's done.<br /> <br /> First, here are the 3 simplest things you can do to make travel a lot better:<br /> # Never, ever check your luggage.<br /> # Check in online as early as possible.<br /> # Pick a Frequent Flyer program<br /> <br /> Do these every time, and you’re already in the 80th percentile for travel success. What follows below is travel brilliance.<br /> <br /> = Planning =<br /> <br /> == Quick Tips ==<br /> * Scan a copy of your passport and any other travel documents and put them somewhere web accessible but password protected (like Dropbox or Google Drive). This is helpful for getting replacements, and for getting consular help in the meantime.<br /> * Print a copy of those scans - particularly your passport, covid test and vaccination status - and keep them in your carry-on. Do this regardless of the current policies of the countries you're travelling to or through - if policies change while you're on the road, you might have a problem.<br /> * Let your credit card company know that you travel. Anti-fraud measures might lock your card the first time you use it on foreign soil, but they can flag your account so that doesn’t happen. This is no fun to discover after the fact.<br /> * Different airlines have different size restrictions for carryon luggage; know your limits for the whole trip and stay inside them.<br /> * Wear a mask.<br /> <br /> == Pick a Frequent Flyer Program ==<br /> <br /> Prices are generally going to be competitive, so figure out your most common trip(s) and figure out which airline/alliance is best for those. Use that group for everything. You can easily sign up for FF programs online, and add it to your travel agency profile (Egencia for Mozilla employees).<br /> <br /> Even if you travel rarely, you'll eventually accrue enough mileage for free travel, and having a FF number makes online check-in easier.<br /> <br /> If you travel often enough, though, (25k+/year on most airlines) you start earning preferred status. This is the difference between &quot;scum&quot; and &quot;How can I help you?&quot; You have shorter lines for agents, shorter lines for security, you board first. You get access to elite lounges while you wait, and free upgrades to business class to make the trip more pleasant. These are little niceties, but they add up, and make travel much nicer. You can often share status with someone less privileged, which means your spouse likes traveling with you more, too.<br /> <br /> == Check In Online ==<br /> <br /> Every airline will let you check in online, usually 24 hours before your flight leaves. I know this will feel weird the first time, but it is an absolute necessity. With online check-in and no checked luggage, you can skip all the lines at the airport except security (and possibly customs/immigration).<br /> <br /> Checking in early may put you into a lower &quot;group&quot; for boarding (or at least not the suckiest, all-the-overhead-bins-are-full group). Check in as early as possible, even if you don't know how many bags you will check (correct answer: 0). You can always add (and pay for) checked bags when you get to the airport.<br /> <br /> The one '''exception''' to this guideline is that if you think your flight might be delayed or cancelled due to weather, ''don't'' check in online ahead of time. If you have to re-book, and you are already checked-in, the agent will have to &quot;uncheck&quot; you, which may slow down the re-booking process and cause you to miss out on alternate flight options. Keep in mind that weather problems cause ripple effects even in locations where weather is good. For example, your flight out of sunny Phoenix might be cancelled because the aircraft is grounded by a snowstorm in Chicago. (See this Egencia blog post for [http://info.egencia.com/wintertraveltips2014.html tips for avoiding weather delays].)<br /> <br /> Online check-in also lets you choose your seats, which brings us to...<br /> <br /> == Choose Your Seats ==<br /> <br /> * Take a window seat for very short flights or very long flights. Window seats have more shoulder room, less hassle from other passengers, and a window. The only downside is bladder management, but on short flights you can stick it out and on long ones you can get up when your fellow passengers do.<br /> * ''Every'' plane has some seats that suck. No recline, noisy, cold, lack of floor storage or slightly narrower than most, [http://www.seatguru.com SeatGuru] will tell you what to avoid. It'll also tell you which seats are great (extra legroom, etc) that you should take given half a chance. Usually, exit-row seats have extra legroom (good for tall people), and the last row and the row in front of the exit row do not recline (bad in general). The first row in a section (where you have a bulkhead in front of you instead of another seat) typically does not have under-seat storage, so everything must go in overhead bins, but it typically does have more legroom. (Seatguru will tell you whether or not this is the case on a particular plane.)<br /> * ''The Middle Seat Gambit'' - If you’re traveling with someone else, check in online together and look for an empty 3-person row. Take the aisle and window. Middle seats fill up last, there’s a decent chance the seat stays empty. If so, you have a lot more space to dump things during the flight, and more legroom since you can use that space instead of putting things under the seat in front of you.<br /> * If you’re traveling alone, you can still use the middle seat gambit by checking in online and looking at the seat map for someone acting as a de facto accomplice.<br /> * If there is only one (worst possible) seat left when you go to select seats, ''don't take it''. It will be claimed by someone else, and the gate agent will assign you a different seat. A flight that full might mean that someone gets bumped, but lack of a seat assignment doesn't guarantee it will be you.<br /> <br /> == Manage Layovers ==<br /> <br /> Flying nonstop to your destination is always easiest, but if that’s not a possibility for whatever reason, here are some other things to keep in mind:<br /> <br /> * Major metropolitan centers are often served by multiple airports, and each airline will have a preference. If you can’t get the flight you want with the airline you like, look to see whether you’re just pointing at the wrong airport.<br /> * If you can’t fly nonstop, you probably at least have your choice of connection airports, and the choice matters there. What’s more, a given airline will have certain preferred connection cities, so a couple trips should get you a reasonably complete list. (For example, connecting from Toronto to San Francisco on Star Alliance, it is much preferable to connect in Denver or Vancouver than it is to connect in Chicago O’Hare.) Consider the immigration/customs procedures of the country you're connecting in if it's separate from the origin or destination (e.g., prefer Vancouver over a US airport for connecting between Toronto and Auckland, since the US requires internationally-connecting passengers to go through immigration and customs).<br /> * If you have to have a connection, you might also have the opportunity to fly to a better airport (e.g., if you have to connect to Washington, DC, you are likely to be able to fly to DCA instead of IAD).<br /> * Take the season and likely weather into account when picking connecting airports; avoid snowy airports in winter, thunderstorm-y airports in summer.<br /> * If you have to layover overnight, prefer airports that have on-site hotels (and for god’s sake prefer Munich over Frankfurt).<br /> * If you’re crossing a border during your flight, it’s often preferable to layover in-country before crossing over. It means your first flight is domestic, so you can arrive later at the airport since there’s no immigration headache there. <br /> * Another reason not to check a bag is that when you have a connection after arriving in some countries (e.g., the USA, but not EU countries), you have to claim your bag, take it through customs (even though they rarely look at it), and then check it again for your connecting flight. More time and hassle.<br /> * Remember to account for boarding time when calculating layovers. If flight A arrives at 12:00 and flight B leaves at 1:00, you do not have an hour, you have about 20 minutes (because you need to get OFF of flight A once it arrives, transit to whichever gate/terminal flight B is in, and then be there for flight B '''boarding''', not flight B '''departure''').<br /> <br /> = Immigration and Customs =<br /> <br /> == General advice ==<br /> * Make sure you know what the requirements are for crossing all immigration and customs barriers before you do so. If you don't know what those requirements are, embassy or consulate websites are often useful, as are the US government's [http://travel.state.gov/content/passports/english/country.html country specific information] (though somewhat tending towards information useful to Americans).<br /> ** This includes vaccination status and testing, which varies on a country by country basis and will continue to do so for the foreseeable future.<br /> * Make sure you have any documentation needed in your carry-on luggage. When entering a country where you're not a citizen or resident, you should carry proof of onward travel, particularly if the reservation on which you're flying doesn't return you to your home country (e.g., because you're traveling on separate reservations).<br /> * If you're ''transferring'' in a country (or multi-country immigration zone) that's different from your origin or destination, figure out whether you'll need to deal with immigration there, and if so, what the rules are. This might vary depending on the airport, or in some cases even on which terminal you arrive at and depart from. (In the latter case, airport websites are often helpful.)<br /> * Don't carry any non-commercially-packaged food through customs, not even the apple you got in the airport. Many places have strict agricultural control policies that prohibit doing so; it's not worth the trouble.<br /> * Always carry a pen (blue or black) somewhere in your checked luggage for filling out the immigration and customs forms.<br /> <br /> = Packing =<br /> <br /> '''Quick Tips'''<br /> * Have a toiletry bag that you keep stocked, rather than trying to remember to pack toothbrushes &amp;c the day of. It doesn’t cost much to buy the duplicates once, and saves hassle/forgetting.<br /> * Put your favourite head, stomach, and sleep meds in the toiletry bag. You can buy most things on the road, but meds are sometimes an exception.<br /> * Throw a couple of large ziploc bags in there, too. They are immensely useful for storing wet clothing or leaking bottles or, by contrast, for putting things like passports in when you need them to stay dry. They weigh nothing and disappear into a pocket until needed.<br /> * Layers. You can adapt to a wide range of climates, even multi-city travel, by packing layers. Shirt, Sweater, Hoodie, Jacket is plenty warm, packs much more compactly than a parka, and gives you middle ground for an overwarm restaurant or an overcool office.<br /> * While you're packing, make a text list on your phone of everything you pack. Towards the end of your trip (such as waiting for your flight home), put a '+' next to every item you actually used. Next time, don't pack the things you didn't use. Also, if your bag goes missing, you have a list of what was in it.<br /> <br /> == Don’t Check Luggage ==<br /> <br /> :: Repeat after me: Checked luggage is for chumps.<br /> <br /> :: Again. Checked luggage is for chumps.<br /> <br /> :: -- George Clooney, ''Up in the Air''<br /> <br /> Every time you give your bag to the airlines, you're inviting them to lose it, abuse it, leave it in your departure city, forget about it on the tarmac during a rain delay, etc. North American airlines will allow you one carry on suitcase and one “personal bag” which usually means a purse or laptop. This is easily enough for a week of travel, and can be extended indefinitely with laundry service. Invest in a good carry-on and bring it with you.<br /> <br /> Put everything you need during the flight in your laptop bag, in case you have to gate-check your carry-on suitcase (common on short flights with smaller planes).<br /> <br /> == Choose the Right Luggage ==<br /> Checked luggage will inevitably be destroyed over time, regardless of quality. If you stick to carry on, though, good luggage will last forever; be willing to pay once for something that gets it right. Your happiness while traveling is worth it.<br /> <br /> His bias for non-rolling luggage notwithstanding, [http://www.onebag.com/bags.html this is the single best guide out there] for evaluating luggage. The highlights:<br /> <br /> * Lighter is better<br /> * Curvy designs rob you of packing volume, prefer right angles<br /> * Chain zippers are stronger than coil zippers (look for YKK as the brand of zipper)<br /> * Pocket design and positioning matters<br /> * So do tie-downs<br /> <br /> In truth, the best way to maximize quality while minimizing weight is to let go of the dependence on rolling bags. Soft-sided, non-wheeled bags are exceptionally light and versatile. [http://www.tombihn.com Tom Bihn] and [http://www.redoxx.com/ Red Oxx] are your best plays. Tom Bihn’s Aeronaut is is a full-sized carry-on that converts to a backpack for long walks across cobblestones/sprints to catch a connection/etc. The Red Oxx Air Boss was designed by the same guy who wrote the luggage-choosing guide above.<br /> <br /> If you're not ready to let go of wheeled bags, any manufacturer with a lifetime warranty is probably worth considering. These include:<br /> <br /> * [http://www.briggs-riley.com/ Briggs &amp; Riley]<br /> * [http://www.travelpro.com Travelpro] (&quot;the best&quot; carry-on according to [http://thewirecutter.com/reviews/best-carry-on-luggage/ The Wirecutter])<br /> * Certain models of [http://shop.eaglecreek.com/lightweight-carry-on/l/111 Eagle Creek] (not all models have a lifetime warranty)<br /> <br /> Pay attention to the bag’s extensible arm: is it well constructed? What does it do to your interior space? 2 segments of extension or 3? Moving parts make everything more fragile -- if you are choosing moving parts in your luggage, they need to be brilliant.<br /> <br /> == Buy It There (BIT) ==<br /> <br /> Don’t try to anticipate every contingency and pack for it. You will bog yourself down with unnecessary cruft. Pack for what you ''know'' you’ll need, or at most what you reasonably expect to need the majority of the time. You can find contact solution, toothpaste, aspirin, and dental floss at almost any convenience store. For the rest, shove an extra $50 into a pocket somewhere and buy whatever you need there, if it comes up. <br /> <br /> (Good news: It comes up less often than you’d think.)<br /> <br /> BIT exceptions: <br /> There are some things you don't want to source while traveling - if you only use one specific brand of shampoo, conditioner, etc, transfer it to a small, travel-friendly bottle. Depending on where you're traveling BIT can be tough if you don't speak the language and are looking for something very specific (like Cipro in India or a flat iron in China). Goes without saying, but BIT does *not* apply to medications (remember that what requires a prescription varies by country, but you can apply it if you know that something can be bought without a prescription at your destination).<br /> <br /> === Corollary: Wash It There ===<br /> If you’re gone for longer than a carry-on can reasonably contain (which is longer than you think), don’t fail over to multiple suitcases; just get things laundered partway through. Your hotel will offer laundry service, though it will be overpriced. Most of the time you’ll find a wash and fold place within walking distance or a service that does pick up and next day drop off.<br /> <br /> Also keep in mind that at most Mozilla or other geek events, you will probably acquire at least one or two t-shirts. You can bring one or two fewer shirts; if this guideline fails, wash one of the ones you brought.<br /> <br /> If you bring quick-drying underwear and socks, you can wash them in the sink or bathtub and dry them overnight on the towel rack (except in humid climates). You can skip bringing detergent by using the hotel's shampoo (as long as you don't mind your underwear smelling like &quot;ginger lemongrass&quot; or whatever); shampoo is just mild detergent. Check the plumbing before you fill the sink; some hotels don't install the lever for raising the plug. Before hanging items to dry, roll them in a towel and squeeze out excess moisture.<br /> <br /> == Counterpoint: The case for checking a suitcase ==<br /> A few heavy-traveling Mozillians are in the &quot;checked bag&quot; camp. Add your reasons for using this strategy here:<br /> * Problems with checked luggage are actually quite rare.<br /> * You don't have to schlep a roll-aboard through the airport with you, including squeezing it into tiny toilet stalls.<br /> * You can pack a few extra things that help you be more comfortable on an extended trip.<br /> * At least one airline (American) gives early boarding privileges (after Elite and Priority but before Zone 1) to passengers with no overhead baggage.<br /> * You aren't limited to 100ml bottles of liquid/gel/cream, and can bring home ''properly packed'' wine, booze, perfume, etc. (Wrap the bottle in at least two plastic bags and nestle it in the groove left by the extending handle, surrounded tightly by clothes.)<br /> * Having airline status often helps your bag appear on the belt faster. Also, if the final segment of your trip is an international arrival in the United States, you're unlikely to have to wait long for your bag, since all baggage goes to the same belt, so it gets there quickly.<br /> * TIP: Get a suitcase with four wheels. Baggage handlers can slide it across the floor of the cargo hold instead of tossing it, subjecting the suitcase and its contents to much less abuse. Anything that protrudes, like carry straps or zipper pulls, can get snagged and chewed up in baggage-handling equipment; go for streamlined.<br /> * TIP: Ask for your checked luggage to be marked &quot;Fragile&quot;. It will be loaded on top of other bags, and usually be unloaded first.<br /> * TIP: If you check luggage, don't let your eyes off the bag until there's a tag on it, and if you can, check that the tag is correct (with your name and correct destination airport on it). One of the common reasons for lost/delayed luggage is getting the wrong tag on it right at the check-in desk.<br /> * TIP: Things to make sure are '''not''' in your checked bag: everything you need to get through customs and immigration and get to your final destination. Any electronics that might be stolen. Lithium-ion batteries (prohibited).<br /> <br /> Some airlines (particularly non-North American or discount airlines) have much lower limits for what you're allowed to carry on, so you'll have to check luggage anyway.<br /> <br /> Some airlines (e.g., Air France, KLM) will even want to weigh your carry-on bag (often although not reliably), and want it to be a weight that's lower than what it is with your laptop in it (e.g., 6kg, 8kg). Remember that your laptop often counts as a separate personal item and you can take it out of the bag before weighing.<br /> <br /> ==Packing Techniques and Tools==<br /> Your strategy for how to put your stuff in your suitcase is very much a matter of personal preference, along with the type of travel you're doing (destination vs. touring) and the type of clothes you bring. Here are some ideas that may be helpful.<br /> <br /> * The [http://www.onebag.com/pack.html bundle method] is great for avoiding wrinkles, but it tends to require that you unbundle ''everything'' to get out any single thing.<br /> * It's extremely helpful to have some kind of containers to organize your stuff. Purpose-made packing &quot;cubes&quot; are great, but are absurdly expensive. You can get by with zip-top plastic bags if you don't travel often, or while you're waiting to find ready-made cubes on sale. <br /> * If you buy only one packing accessory, consider getting a [http://www.amazon.com/Eagle-Creek-Travel-Pack-It-Folder/dp/B002YIRC3O/ packing folder], which helps you fold larger items (shirts, pants, skirts) to a uniform footprint, and then encloses them like an envelope.<br /> * Compression bags, which let you squeeze all the air out of your clothes, are good only for clothes that don't easily wrinkle. However, a compression bag can be great as a laundry bag to minimize the volume of dirty clothes on your way home. Either way, have a cloth or plastic bag you can use to keep used laundry separate. <br /> <br /> = Airport Hacking =<br /> '''Quick Tips'''<br /> * ABC: Always Be Charging. Wherever you come to rest, be charging. Maybe your flight has power plugs, that's swell, but maybe they stop working, or your seatmate gets to it first, or you need it to charge your phone. If you're at rest for more than 10 minutes, find a plug. If you bring a power strip so others can plug in, too, you can make friends anywhere :-)<br /> * Watch where uniformed crew members go. They know the best eateries in any given airport, and even where to stand on the tram platform in order to get off quickly at the other end.<br /> * The internet knows about delays before your gate agents do. Bookmark [http://flightaware.com/live/ flightaware] right now, and use it from your phone at the airport to keep tabs. Caveat: Flightaware may show your flight as delayed because the inbound plane you're getting on is delayed; if the airline substitutes another aircraft, your flight could be on time or only a little delayed.<br /> * If you do see signs of a significant delay, particularly at night when it's likely you'll be put off until morning, act swiftly before the lines form. Talk to gate agents about rebooking onto other flights and if the line there is long, be on the phone with your airline as well. First to rebook means first to call hotels and taxis and all the rest. Being last to rebook means sleeping in the airport. If you have elite status, call the customer service number for elite members, not the general customer service number.<br /> * When you get off the plane, the restroom closest to your gate will be crowded with other people from your flight. Keep going to the next one further away.<br /> * No one wants to sleep in an airport, but flight delays or cancellations, or just poor planning, may require it. There is actually a whole website devoted to [http://www.sleepinginairports.net/tips.htm sleeping in airports].<br /> <br /> <br /> == Being prepared for security ==<br /> * Veteran move: if you have a digital boarding pass, set a screenshot of that boarding pass as the background of your lock screen, so you can see the QR code without unlocking the phone.<br /> * Bring identification. [http://www.tsa.gov/traveler-information/acceptable-ids Here's a list of acceptable IDs] in the US. If you forget your ID, all is not lost. It's possible, with some extra hassle, to travel within the US even if you don't have your identification. [http://blog.tsa.gov/2013/04/tsa-travel-tips-tuesday-can-you-fly.html Here's what the TSA says to do if you don't have ID.]<br /> * Have photocopies - paper copies - of your passport and one other piece of ID (and where necessary, vaccination status or test results.)<br /> * Avoid getting into a screening line behind people who look like they don't travel often (families with kids, retirement-age folks, large groups).<br /> * Wear slip-on shoes and socks. Do not go barefoot in airports (And, for the love of God, Do Not Sit Or Lie Down On The Floors. Airport floors are disgusting, you have no idea.)<br /> * Consider not wearing a belt, or wear one with no metal, so you don't have to take it off.<br /> * Avoid clothes with extra pockets, like cargo pants. They can be flagged by the body scanner, and cause you to get a pat-down. Same for &quot;travel&quot; clothes with hidden pockets; these can be handy while touring, but not while flying. Even a hoodie can win you a pat-down for the hood and kangaroo pocket. <br /> * On the other hand, a jacket with lots of pockets is like an extra carry-on; you have to remove it for security anyway, and you can keep your in-flight necessities (gadgets, etc.) close to hand during your flight.<br /> * Know the drill with liquids, gels, and creams: containers at most 100ml/3oz, in a clear zip-top bag, 1 liter/1 quart size. Have this in an external pocket of your carry-on, ready to pull out and put in a bin. (If you travel often, you might want to get a sturdier bag than the grocery store kind. It must still be clear and zip-top.)<br /> ** Don't pack little bottles of booze. Yes, it's under the limit, yes you're technically allowed to carry it through security. Don't.<br /> * Avoid large metal jewelry.<br /> * Take everything, but especially metal (keys, coins, etc.), out of your pockets.<br /> * '''Leave your pocket knives and multitools at home.'''<br /> * If you're wearing an activity monitor, such as a FitBit, take it off for screening.<br /> * You should hang onto your ID and boarding pass as you go through the line, but you can't carry them through screening; put them in your bin.<br /> * Put the bin with your shoes, jacket, and liquids onto the conveyor belt first. You can be getting dressed while the rest of your stuff comes through.<br /> * Take your laptop out of your bag and put it in a separate bin. You can usually leave it in a sleeve, as long as there's nothing else in the sleeve. <br /> * Consider getting a checkpoint-friendly laptop bag, with a laptop-only section that folds out without taking out the computer. The less you handle your laptop, the less likely you are to drop it. (US TSA allows you leave the computer in this type of bag; other countries often do not.)<br /> * Don't start going through the screening machine or metal detectors before you can see your stuff moving down the conveyor belt.<br /> <br /> == US Trusted Traveler Programs ==<br /> If you frequently cross US borders, you can save time and hassle in the long run by enrolling in one of the programs that provide expedited entry for pre-approved travelers. Enrolling involves an application fee and form, and an in-person interview at an entry point, so there is a start-up cost in time and money. Which program you should enroll in depends on the type of crossing you do most; you can enroll in more than one. <br /> <br /> * When entering the US, if you're not in a &quot;trusted traveler&quot; program, try to get into the immigration queue that is ''next to'' the Global Entry lane. If no one is in the Global Entry lane, the officer there will often take people from the nearby queue, making it move faster. Do likewise for NEXUS when entering Canada.<br /> * Wear Firefox gear when going through immigration, anywhere. It creates goodwill and starts pleasant conversations.<br /> <br /> ===Automated Passport Control===<br /> Automated Passport Control kiosks are available to citizens of the US, Canada, and [http://www.cbp.gov/travel/international-visitors/frequently-asked-questions-about-visa-waiver-program-vwp-and-electronic-system-travel Visa Waiver Program] countries, for entry into the US, in an expanding number of North American cities. Unlike Global Entry or Nexus, these kiosks require no pre-registration. You swipe your passport, let the kiosk take a photo, answer some questions, and then get a receipt that you show to a Customs and Border Patrol officer. The kiosk replaces filling out a customs card by hand.<br /> <br /> See the [http://www.cbp.gov/travel/us-citizens/Automated%20Passport%20Control Automated Passport Control] webpage for a list of cities with APC kiosks.<br /> <br /> === Global Entry ===<br /> [http://globalentry.gov/about.html Global Entry] provides expedited screening for entry ''into'' the US at certain airports. Once in the program, you can go to an automated kiosk instead of an immigration agent (skipping the enormous lines that result from multiple international flights arriving at about the same time), and you can answer the customs questions at the kiosk instead of filling out a paper form. Unless there is an issue with your kiosk interaction (such as it couldn't read your fingerprints), you don't need to talk to a CBP agent. Global Entry is open to U.S. citizens, lawful permanent residents of the U.S., Dutch citizens, South Korean citizens and Mexican nationals.<br /> <br /> === NEXUS ===<br /> [http://www.globalentry.gov/nexus.html NEXUS] provides expedited screening for crossing the US-Canada border in both directions. It can be used at land and sea entry points as well as at airports. You can use the NEXUS-only lanes at land crossings only if every person in the vehicle (including children) has a NEXUS card. Using NEXUS at an airport requires scanning your irises. If you wear contact lenses, you must remove them for the initial iris scan that is taken after your enrollment interview.<br /> <br /> === Other US programs ===<br /> * [http://www.globalentry.gov/netherlands.html FLUX] expedites passage between the US and '''the Netherlands''', and is open to US and Dutch citizens.<br /> * Global Entry members can receive expedited entry into '''[http://www.globalentry.gov/newzealand.html New Zealand]'''.<br /> * [http://www.globalentry.gov/sentri.html SENTRI] provides expedited entry into the US from '''Mexico''' at specific land crossings.<br /> * [http://www.globalentry.gov/korea.html Smart Entry Service] provides expedited entry into the Republic of '''Korea'''. It is open to US and Korean citizens.<br /> * [http://www.globalentry.gov/smartgate.html SmartGate] provides streamlined entry into '''Australia''' for US Global Entry members. Visa requirements still apply.<br /> * [http://www.globalentry.gov/tsa.html TSA PreCheck] enables US Global Entry and Canadian NEXUS members to use designated TSA airport screening lanes, without removing liquids, laptops, shoes, jackets, or belts. You must provide your membership number when booking flights with participating airlines. TSA is expanding the PreCheck program to include more people, including US military members and those invited by their airline's frequent flyer program. You must still apply, pay a fee, and go through an interview. See the [http://www.tsa.gov/tsa-precheck TSA PreCheck] website for details.<br /> <br /> == Other countries' traveler programs ==<br /> * The UK's [https://www.gov.uk/registered-traveller Registered Traveller service] enables certain citizens of Australia, Canada, Japan, New Zealand and the USA to get faster entry to the UK, without filling out a landing card. <br /> <br /> <br /> == Country-specific notes ==<br /> <br /> '''Note: Much of the per-country information is pre-covid, and needs to be verified or updated.'''<br /> <br /> === USA ===<br /> * visitors under the [https://travel.state.gov/content/travel/en/us-visas/tourism-visit/visa-waiver-program.html visa waiver program] (those who don't need a visa) must apply online for an [http://www.cbp.gov/travel/international-visitors/esta ESTA].<br /> <br /> === Canada ===<br /> * visitors who do not need a visa, are entering Canada by air, and are not US citizens or Canadian citizens or Canadian permanent residents, must apply online for an [http://www.cic.gc.ca/english/visit/eta.asp eTA].<br /> <br /> === Schengen Area (Europe) ===<br /> * The [http://en.wikipedia.org/wiki/Schengen_Area Schengen Area] is an immigration-barrier-free zone covering most of the European Union and some additional non-EU countries, but not the UK or Ireland.<br /> * If you need a visa to visit the Schengen Area, it is easier to get such a visa if your point of arrival in the Schengen Area is the same country as your destination. (For example, if you're traveling to Spain, it is easier to arrive in Madrid after connecting in the UK or US than connecting via Amsterdam, since in the latter case getting the visa requires dealing with both the Spanish and Dutch authorities.)<br /> * If your nationality requires a visa to visit the Schengen Area and your trip does not terminate in Schengen, avoid making more than one connection in Schengen; in such a case you must get a Schengen visa, even though that's not your destination. Schengen immigration authorities look at your ''next'' point of travel (not your final one) to decide whether you need a visa; if it is Schengen, they will ask for one.<br /> <br /> === New Zealand ===<br /> * Make sure to declare any shoes in your checked luggage. The authorities just want to look at them and maybe clean the dirt off for you, but they'll be upset if you don't declare them.<br /> * Don't even think about [http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&amp;objectid=11404025 bringing fresh fruit] into New Zealand or you will get an instant fine.<br /> <br /> === Australia ===<br /> * Visitors who can can enter without a visa must apply online for an [https://www.eta.immi.gov.au/ ETA].<br /> <br /> = Flying =<br /> <br /> '''Quick Tips'''<br /> * Hydrate, hydrate, hydrate. Air in an airplane at altitude is incredibly dry and dries you out. Drink water whenever you can. Bring an empty water bottle (even better: collapsible) and fill it from a water fountain inside security. (Some airports, like SFO, have water bottle filling spots that make this a little easier.) Don't drink the water that comes out of the water tanks onboard an airplane, including coffee and tea; you don't want to know how disgusting those tanks are. If you get water in the beverage service, ask for fizzy water (club soda) to ensure it came out of a bottle or can. If you need to brush your teeth in-flight, use water from your water bottle, not the tap in the toilet.<br /> * Request an alternate meal (kosher, indian, vegan, whatever) - they tend to be tastier, and often come first. (However, the downside to the meal coming first is that the tray is going to be in your way substantially longer.)<br /> * If you're in an aisle seat, you’ll find that the aisle-side armrest won’t lift. This is annoying, because it is much easier to deplane with that thing out of the way. Reach back to where the armrest joins the back of the chair -- there may be a release latch or button. (This works on some Boeing 777s; most smaller craft do not have this feature. See [http://brokensecrets.com/2011/01/17/raising-the-airplane-aisle-armrest/ this article] for a photo.)<br /> * Always wear shoes before going to the airplane lavatories; never go barefoot or wearing socks only. <br /> * Wear a mask, n95 or better.<br /> <br /> == Headphones ==<br /> Enjoying music or movies during travel is much better with headphones designed for travel use. You need to consider three types: <br /> * active noise-cancelling headphones<br /> * those without noise-cancellation<br /> * in-ear monitors. <br /> Generally speaking, on airplanes, active noise-cancellation will be better on the plane but worse when you're not on the plane (in the hotel room, for instance.) A quality headphone without noise cancellation will almost always sound better when not on an airplane. In-ear monitors allow for excellent sound quality and also allow one to rest your head on a pillow without the headphone pushing against one's ear, but some are uncomfortable with putting anything in one's ear. In-ear monitors are also much more compact. For those who want the sound quality of in-ear monitors and the compactness, but find that fit is a problem, consider Comply foam tip replacements which can be selected to fit your ear size.<br /> <br /> * For active noise cancellation headphones, the Bose Quiet Comfort 15 is the most popular model sold and for good reason. However if you want the headphone to be good when the noise-cancellation is turned off, you may want to consider the [http://www.psbspeakers.com/products/headphones/M4U-2-Headphones Psb m4u 2], which is more expensive but also more versatile.<br /> * For headphones without active noise cancellation, consider rugged models that have reputations burnished by decades of use by audio professionals such as the Sennheiser HD-25 1-ii. Another popular option is the V-Moda M-80 which has similar sound quality, has a good reputation for build quality, and also comes with a nice travel case.<br /> * For in ear monitors, there are too many to list but one line that is very popular is the Shure SE series which have models from $99 on up. These are very rugged models which allow for replaceable cables, replaceable tips and have very good sound quality.<br /> Additional resources for headphones include [http://www.innerfidelity.com/content/innerfidelitys-wall-fame Innerfidelity's Wall of Fame] and Head-fi.org's [http://www.head-fi.org/t/618255/check-out-the-head-fi-summer-2012-buying-guide 2012 Summer Buying Guide].<br /> <br /> == Make friends with TSA and your flight crew ==<br /> <br /> Airplanes are a sea of grumpy, tired, unhappy people. A little friendliness goes a long way -- especially if you're regularly flying the same route with the same flight crew.<br /> <br /> == Seat etiquette ==<br /> The following tips are about showing consideration to your fellow passengers, who unfortunately may not even notice it. But violating these norms is likely to cause annoyance. You don't want to be &quot;that guy&quot;, do you?<br /> <br /> * The person in the middle seats gets to use both armrests. The people in the window and aisle seats get a little extra space, so yielding one armrest each is the least they can do. In any case, try to keep your elbows in your own space.<br /> * Consider the person behind you before reclining your seat into their space, especially if they are trying to eat or use a laptop. Avoid reclining abruptly (though it's not always possible to control this). Raise your seat back during meals.<br /> * If you need to leave your seat during the flight, try to avoid hoisting yourself up by yanking on the seat in front of you. This may be difficult to avoid if the seat is reclined (see above).<br /> * If you have an individual touchscreen in the seat back in front of you, jabbing it forcefully doesn't make the touchscreen work any better. If it's really not responding to touch input, try controlling it from the armrest controls.<br /> * [http://www.independenttraveler.com/travel-tips/travelers-ed/the-etiquette-of-seat-backs-and-elbow-room The Independent Traveler: The etiquette of seat backs and elbow room]<br /> <br /> = Tips for specific airports =<br /> As a general rule of thumb, in any airport, the terminal or concourse that serves international flights has nicer shops and restaurants than the areas for domestic flights. So, if you're traveling domestically, have time to kill, and can get into the international terminal without going through passport control, you might want to go hang out there.<br /> <br /> == AMS Amsterdam ==<br /> * in the international section (only?), there are nice quiet places to sit on the upper level outside the lounges (even if you don't have lounge access)<br /> * if you want to take the train to/from the airport, hoard coins (€4 to Amsterdam-Centraal, less to Amsterdam-Lelylaan or Amsterdam Zuid), since the ticket machines don't take bills or American credit cards. (The city trams/buses in Amsterdam do take bills, but this is a national train.)<br /> * note that the entirety of the outside-[https://en.wikipedia.org/wiki/Schengen_Area Schengen]-immigration part of the airport does security at the gate, per flight<br /> <br /> == AUS Austin, Texas ==<br /> The food available in the airport is actually pretty good, since most of the food concessions offer menus from local restaurants. Get to the airport early enough to have a last plate of barbecue or breakfast tacos. <br /> <br /> Another reason to get to the airport early is the &quot;Knot Anymore&quot; chair massages available near gates 13 and 7. Austin is awash in good massage therapists, so the ones working in the airport are far better than most airport massage services.<br /> <br /> == CDG Paris / Charles de Gaulle ==<br /> * CDG airport has multiple airport hotels on premises (on the around-the-airport CDGVal shuttle train); typically at least one of the fancy ones has good prices because it isn't hosting a conference that week, but there's also an Ibis. <br /> * CDG airport has four disconnected parts:<br /> ** Terminal 1 (the cylinder with pods) (United is here)<br /> ** Terminal 3 (the discount airlines)<br /> ** Terminal 2A-2B-2C-2D-2E-2F (the bulk of the airport) (Air France is here)<br /> *** note that there are two satellite piers attached by train (outside immigration but not inside security) attached to Terminal 2E (the attached part of terminal 2E is called K, the satellites are called L and M)<br /> ** Terminal 2G<br /> * transport<br /> ** there's a train (CDGVal) connecting Terminal 1, Terminal 3 / Roissypole (where most but not all of the hotels are), and Terminal 2 (the station is between 2C/2D/2E/2F)<br /> ** high speed trains stop only at the terminal 2 station (between 2C/2D/2E/2F)<br /> ** RER trains (Paris's suburban rail network) stop at Terminal 2 (same station, again) and at &quot;Terminal 1&quot; (which is actually the Terminal 3 / Roissypole station for CDGVal)<br /> ** Terminal 2G is reachable only by shuttle (I think, never done it)<br /> ** If you want to take the RER to/from the airport, hoard coins in advance to pay the €9.50, since foreign cards don't work, and the machines don't take bills. <br /> ** The RoissyBus is only €10.50 and runs nonstop between CDG and the Paris Opera, only a few blocks from the Mozilla Paris office. Look for signs for &quot;RoissyBus&quot; or &quot;Paris by bus&quot; within each terminal to find the bus stop.<br /> <br /> == JFK New York ==<br /> * The wifi password of the British Airways' lounge is &quot;London&quot; (according to Reddit). You can usually get in range of the wifi hotspot without going inside the lounge.<br /> <br /> == LHR London Heathrow ==<br /> * Terminal 5 (international) <br /> ** If you need to take the train to concourse B or C, go to the far end of the platform. You'll bypass the crowds at the near end, and be closest to the escalators when you exit.<br /> ** If you need to backtrack from concourses B or C to concourse A, ''don't'' take the train; you'll be routed through security again. There's a pedestrian tunnel that parallels the train, and comes out next to elevators that let out inside security in concourse A. The tunnel doors are marked &quot;Emergency Exit&quot;, but do not have alarms, and in fact open automatically, to accommodate mobility-assistance carts. Stay to the left (remember: you're in England) to keep from being run over by them.<br /> ** If you're going to the Mozilla London office, [[London#From_Heathrow_by_traincheck the directions]] and don't bother with Heathrow Express.<br /> <br /> == NCE Nice, France ==<br /> * if you have a really early flight, there are multiple decent airport hotels nearby. But do '''not''', under any circumstances, stay at the Etap.<br /> * if you want to avoid a really early flight, consider as an alternative doing an overnight layover at CDG, which has multiple airport hotels walking distance from Terminal 1 (but poorly signed). Make sure your layover is long enough, though.<br /> * if you're traveling to west of the airport (e.g., towards W3C's European offices near Antibes) and want to take public transit, it's possible to walk to the Nice - St. Augustin train station ('''not''' the main Nice - Ville train station) in about 15-20 minutes, but there's basically no signage. But definitely look at the train schedules before trying this. Buses from the bus station (gare routière) at the airport may be better.<br /> * there's a free shuttle between Terminals 1 and 2. Don't try walking between terminals.<br /> * There are bus stations at both terminals, but some bus routes stop at both terminal and some stop only at Terminal 1. You need to buy a ticket at the station before boarding.<br /> * the airport does not have water fountains behind security. But restaurants will probably be willing to fill up a water bottle for you, especially if you've bought something there.<br /> <br /> == NRT Tokyo/Narita ==<br /> * If you can do so just as easily, fly to Haneda Airport (HND) instead, which is closer to the city.<br /> * Don't even ''think'' of taking a taxi. It will take hours, and cost multiple hundreds of US dollars.<br /> * Two companies (JR and Keisei) run trains to Tokyo, and both have express and local services at different prices. Choices depend on where in Tokyo you're going. Google Maps might be helpful, or just figure it out when you get there.<br /> * Consider taking a [http://www.limousinebus.co.jp/en/ Limousine Bus] to somewhere close to your destination, and take a taxi from there.<br /> <br /> == ORD Chicago O'Hare ==<br /> * In Terminal 3, at the beginning of concourse G, there is a &quot;Chicago Urban Garden&quot; on the second floor, with aeroponic herbs and vegetables. This is a nice quiet place to wait if you don't have access to an airline lounge. <br /> <br /> == SFO San Francisco ==<br /> * if you're through security and looking for food, realize that some pairs of terminals are connected behind security. In particular, there are four separated behind-security zones at SFO right now: International-G/Terminal3-F/Terminal3-E, Terminal2-D/Terminal1-C, Terminal1-B, and International-A. In particular, if you're in C, you can probably find better food and better places to sit in D, and at some hours there's not much open in G, but you can head over to F.<br /> * The recently renovated terminal areas are the International Terminal (2000), Terminal 2 (gates D) (2011), and Terminal 3 gates E only (2014)<br /> * If you're taking BART to the airport, you can take the airtrain or walk to get around the airport from the airport BART station. You should definitely walk to International (G or A, which share a large central checkin hall but have separate gate areas), maybe walk to Terminal 3 (at least if you're ready to go straight to the security line), and you can walk to the other terminal if you like.<br /> <br /> == SJC San Jose CA ==<br /> <br /> == TPE Taipei Taoyuan ==<br /> * if you're coming from within Asia to Taipei, fly to Songshan Airport (TSA) instead<br /> * if you have Star Alliance gold, there are multiple EVA lounges to choose from. The main one, with all the good food, is on the same side of the open (to the floor below) space as the tropical bar one, with entrance across the hallway from it (not across the open space)<br /> <br /> == YVR Vancouver ==<br /> * As airports go this one is a pretty beautiful. If you're departing to the US from Vancouver note that you will go through US customs and immigration at YVR, so arrive 2 hours before your scheduled departure time. <br /> <br /> = Trains =<br /> <br /> * for booking long-distance trains within Europe, https://www.trainline.eu/ is often better than the national train company sites, because they tend to be clearer about both giving you the better options for ticket retrieval and explaining those options to you<br /> <br /> = Hotels =<br /> <br /> '''Quick Tips'''<br /> * Ask for upgrades. I know, this sounds trite, but it works. If you don’t know how that works, just remember, when checking in, to ask “Is there a better room available?” If they say yes, you’re set. If they say no, that’s fine. If they say “yes, for a price” then you can consider that price and make the call. We’ve gotten $2000/night rooms on a $180/night booking just by asking. This tends to work well when the hotel has a lot of open inventory (particularly effective in LAS, less effective near Moscone during a conference).<br /> * When checking in, adjust your interactions with the clerk based on whether they smile when you approach. Chit-chat with a smiling clerk, but not with an unsmiling clerk. The latter is just as much a form of establishing rapport as chit-chat, because you're not wasting the time of a transaction-oriented person. And establishing rapport can make the marginal difference in whether they decide to give you an upgrade.<br /> * Expensive hotels tend to have sensors in the minibars, but most of the rest still just have housekeeping track what’s missing each visit and bill you. If you do get the munchies, just head out to a convenience store the next day before housekeeping and buy matching replacements at the saner price. <br /> * You can avoid the minibar entirely by grabbing a granola bar or two from a Mozilla kitchen before departing. They are bound to be healthier than anything you find in the minibar late night. <br /> * Every hotel has a bucket of standard toiletry items (toothbrush, razor, &amp;c). You should have a toiletry bag stocked and ready to go (see above) but if you find yourself missing something, just call the front desk.<br /> * Likewise, every hotel has a bucket of left-behind chargers/power cables.<br /> * Set your climate controls when you first get into the room. Forgetting until you come back after dinner ready for sleep and finding the room is hot and stale is no fun.<br /> * Some hotels won’t let the climate controls work unless your room keycard is stuck into a switch by the door. This isn’t a magstripe reader, it’s just a physical switch - use a business card or a folded up piece of paper (or your library card) and have your room the way you want it.<br /> * If the drapes that don't quite meet, and therefore let in unwanted sunlight or street light, use one or two big binder clips to keep the drapes closed.<br /> * You can usually get a later check-out time just by asking. This doesn't work indefinitely, but they can't clean every room at once, so asking for 1pm instead of 11am just means they move your room to the bottom of the list for cleaning that day.<br /> * Repack for departure before you go to sleep, except for the clothes and toiletries you'll need in the morning. That way, if you oversleep for whatever reason, you can throw on your clothes, grab those last items, and go without wasting any more time.<br /> * To avoid leaving things behind:<br /> ** Bring your original packing checklist, and use it to repack.<br /> ** Pull all the linens off the bed and throw all used towels into the shower, so you're sure nothing's hidden, and check every wall socket for chargers.<br /> ** If you unpack into drawers, check every drawer before you leave.<br /> <br /> == Pick a hotel, get into the frequent guest program ==<br /> <br /> Same deal as airlines. At the least, it eventually adds up to free stays, but getting to status means room upgrades, easier check-in, more flexibility on check-in/check-out times, and extra points for each stay. Some hotel loyalty points can also be transferred to airline loyalty programs.<br /> <br /> It can be harder to consistently stay with the same hotel group than to consistently fly the same airline (they're sold out or not convenient, the conference hotel is elsewhere, etc.). However, it's good to join the loyalty program for any hotel you stay at, before you make your reservation. You may get a better rate or a better room. Hotel staff seem to give an extra measure of courtesy and consideration when you're in the loyalty program. (When booking by phone, I've had a &quot;sold out&quot; group rate suddenly become available when I gave my membership number.) If you haven't joined by the time you check in, ask the clerk to sign you up; they'll get credit for signing you up, and will be even more inclined to treat you nicely.<br /> <br /> Linked below are the programs associated with the hotels that are typically used for visiting Mozilla in Mountain View.<br /> <br /> {|<br /> |-<br /> |Holiday Inn Express<br /> |[http://www.priorityclub.com/ Priority Club]<br /> |<br /> |-<br /> |Avante/Wild Palms<br /> |[http://www.joyoflifeclub.com/ Joy of Life Club]<br /> |(Does not give points for stays that are paid through corporate billing.)<br /> |}<br /> <br /> == Choose Your Room ==<br /> <br /> It's a good practice to indicate that you have any preference on your room at all. Put this into your loyalty program profile and your travel agency profile (Egencia, for Mozilla employees), so it's transmitted with your reservation. If you have no preference, they will put you in the room for people who do not indicate a preference. You know, the one in the basement. With the leaky faucet and carpet from 1973. <br /> <br /> If you have a choice between one or two beds, choose two, even though you'll only use one for sleeping. The other one makes a great surface for spreading out your stuff. Often, hotel beds are on casters, so you can shove the extra bed against the wall, to prevent stuff falling between the bed and the wall.<br /> <br /> Generally, you'll do well to ask for a high floor and a room away from the elevator. Many hotels do renovations by floor starting from the top and working their way down. So high floors have a better chance of being recently renovated. They are also further away from street noise or the bar in the atrium. A room away from the elevator means less foot traffic and not waking up at 5am to repeated &quot;ding!&quot; of the elevator door opening. For motels, you want upstairs (less foot traffic) and outside (away from the courtyard with the pool).<br /> <br /> If the room is awful, don't be afraid to walk back downstairs and see if they have anything a bit more updated. If the whole hotel is awful, check your luggage at the desk and walk in a square block radius around the hotel to see if there's something less frightening. <br /> <br /> Never pick a hotel based on a picture of the lobby. Lobbies are always the first thing to get renovated.<br /> <br /> == Tipping Hotel Staff ==<br /> If you believe in tipping (which varies across cultures):<br /> * If you take a hotel shuttle from the airport, be sure to tip the shuttle driver. Don't just hand it to them and walk away; look them in the eye and express genuine appreciation for their service while you give them the tip. This is your first contact with the hotel staff, and if you make a good impression, word will spread to the other staff, and you'll get great service throughout your stay. This driver may also be the person who gets you to your outbound flight, through heavy traffic, just in the nick of time.<br /> * Similarly, leave a tip for housekeeping after the first night. This paves the way for good service when you make special requests, such as extra towels or toiletries, or to come back later because you're still in the room. Leave the money on top of a note that says at least &quot;Thanks!&quot; so the housekeeper knows it's for them.<br /> <br /> = Money =<br /> <br /> * Exchange: Do not change money at the airport. The rates are higher there than anywhere else. If you have a local bureau de change, use that, or order currency online for pickup at the airport. If you can find a company that does that (Travelex in the UK, at least) the rates will be much better than those posted on the wall that they charge you when you are a captive customer. The best rates are likely to be had by using an ATM. <br /> * Debit: Using an ATM card can be an easy and inexpensive way to secure some local currency. Make sure your card will work abroad before you travel. Common ATM networks that are broadly available include Pulse and Plus. Consider getting a debit card with no foreign transaction fees (Charles Schwab offers one).<br /> * Stay organized: It's helpful to keep your currency separate from your home currency, particularly if you're going to cycle through multiple currencies during your trip (usd &gt; euro &gt; pounds). Don't underestimate the power of a ziploc baggie if you're American and unaccustomed to coinage-heavy currencies.<br /> <br /> == Credit cards ==<br /> The US has historically had a different system (magnetic strips) for credit card security from the rest of the world (which uses the chip-and-pin system). This can cause headaches for both Americans traveling abroad, and others traveling to the US, as the systems are incompatible. Most US stores now support chip-and-signature cards, but you might run into smaller ones that don't have chip-reading equipment (e.g., a food truck using Square). <br /> <br /> * A very few US banks offer true chip-and-pin cards, including Citibank and [https://www.andrewsfcu.org/credit_cards_and_loans/credit_cards/globetrek_rewards.html Andrews Federal Credit Union]. The latter also has no annual fee and no international transaction fees. See this extensive but not exhaustive [http://thepointsguy.com/2013/05/us-credit-cards-with-smart-chips/ list of US-based chip-and-pin cards]. <br /> * You can get a pre-paid, reloadable chip-and-pin card called [http://www.cashpassport.com/1/travelex/ &quot;Cash Passport&quot;] from Travelex. You can buy it and reload it online or at Travelex locations in the US. You can load it in multiple currencies: GBP, EUR, CAD, AUD and JPY. The security seems a bit crappy (you can't change the PIN, and their only security question is mother's maiden name), but since it's pre-paid, you can limit your financial exposure, and reload online as needed.<br /> <br /> Another issue for travelers is transaction fees when making purchases in currencies other than your home currency; these can range from 1% up to as much as 7%. US-based credit cards that don't charge international transaction fees include CapitalOne and Andrews FCU.<br /> <br /> More and more US retailers have card readers that accept chip-based cards, so the situation is improving for visitors to the US. However, they probably don't understand the PIN system, so you will still need to sign (either on the reader, or on paper).<br /> <br /> = Preparing to be less-online than normal =<br /> <br /> If your cellphone plan doesn't have reasonable data roaming, or if you might be in areas with poor cell coverage, you should be prepared to survive without your usual data connection. This might include things like:<br /> * downloading offline maps in advance. ([http://maps.me/ maps.me] for Android and iOS lets you download offline OpenStreetMap maps by country or part-of-country.)<br /> * knowing where you're going to need to be (hotels, meeting locations) before you leave<br /> <br /> = On Foreign Soil =<br /> <br /> * Data/Voice rates<br /> ** You can use Skype to call US 1-800 numbers toll free from anywhere in the world.<br /> ** Before you leave your home country, add $20-40 of SkypeOut credits to your account. While Skype to Skype calls are free, SkypeOut credits will let you call any number internationally for about $.02 per minute.<br /> ** International text messages are typically NOT covered under your mobile plan. For US cell plans, it's usually about $.50 per SMS. If you have a good international rate, think long and hard about when you use SMS and why. A conversation about when you landed and where to meet and what time to get there on SMS may be more than a 2 minute call that covers the same details.<br /> ** [http://readwrite.com/2014/06/17/5-secrets-avoiding-hefty-international-data-roaming-charges-fees 5 secrets to avoiding hefty international data roaming fees] <br /> * Finding wifi<br /> ** In airports, airlines' priority lounges often have no wifi password, and you can access their hotspots from outside the lounge. (See note above for JFK airport.)<br /> ** Starbucks, McDonalds, and Burger King are sadly ubiquitous, and often have free wifi.<br /> ** You can sometimes find the password for a business's wifi in the comments for that business on FourSquare.<br /> * Language barriers<br /> ** Grab some business cards or stationery with your hotel's address on them before you head out. You can hand one to a cabbie whose language you do not speak, to get yourself back to home base. <br /> <br /> Still to write/update:<br /> * Language barriers<br /> ** Add Line2 details...<br /> <br /> ==Coping with jet lag==<br /> * Do not go to sleep. Do not nap. Stay up as long as you possibly can. Eat meals at local times and get into bed when it's dark outside. It will hurt on day one but by day three, you'll be glad you did. <br /> * If you absolutely must sleep, do a 20 minute powernap and then get up, walk around, and do not fall back to sleep. (Powernapping pro tip: [https://www.vox.com/2014/8/28/6074177/coffee-naps-caffeine-science take a &quot;coffee nap&quot;]: quickly drink a cup of coffee, and ''then'' take a nap; the coffee will wake you up in a short while, and you'll be more alert than with a nap or a coffee alone.) <br /> * In a pinch, Benedryl (dipenhydramine) can help you reset your internal clock and it's substantially gentler on your system than the prescription sleep aids. (It's also good for nausea if you get motion sickness, and of course, allergic reactions.)<br /> * If you find yourself awake when you should be sleeping (by local time), avoid bright screens (computers, phones, e-readers), because they activate wakefulness in your brain. Try reading a paper book or magazine (radical, I know). If you must use a screen, set it to white text on a black background, to reduce the overall brightness; or get an app (such as [https://justgetflux.com/ f.lux] for Mac/iOS or [https://play.google.com/store/apps/details?id=com.urbandroid.lux Twilight] for Android) that reduces the amount of blue light emitted by your device at night.<br /> * If possible, follow the [http://www.wikihow.com/Prevent-Jet-Lag-with-a-Modified-Diet Anti-Jet Lag Diet]; this is easier to do at home than while traveling, but IME even an approximation helps. <br /> ** As an abbreviated version: eat as little as possible on your day of travel, avoiding caffeine and alcohol; eat a high-protein breakfast at breakfast time in your new time zone.<br /> ** Bring protein bars with you to ensure that you can get protein at the right time.<br /> <br /> <br /> = Eating =<br /> <br /> Eat like a local.<br /> <br /> Never ask the front desk at your hotel for a dinner recommendation. If possible, ask anyone else to weigh in. The bellhop, your taxi driver, the barista at Starbucks, Yelp, Chowhound, etc. The best recommendations come from people who are actually living and working in the area. (TripAdvisor tells you what people who ''don't'' live there think.) The concierge at the hotel will always orient toward broad, tourist-pacifying tastes. The food will be edible, but forgettable. They'll never tell you about the super tasty hole-in-the-wall joint three blocks away.<br /> <br /> = Staying healthy =<br /> * Wear a mask, N95 or better, as close to all the time as you can manage.<br /> * Wash hands frequently! <br /> * Carry and use hand-sanitizer wipes. (A bottle of hand-sanitizer gel takes up valuable room in your liquids bag.) Sanitize your hands in-flight before you eat or drink, and after washing your hands in the lavatory (on-board water, again). Also use them to wipe off [http://www.travelmath.com/feature/airline-hygiene-exposed/ tray tables, seatbelt buckles, and air vents], where germs lurk on airplanes.<br /> * Set the fan above your seat on the plane to low or medium, and position it to blow into your lap, just in front of your face. This will help knock airborne pathogens out of the air, so you'll be less likely to breathe them in. ([http://www.npr.org/blogs/goatsandsoda/2014/07/14/319194689/pathogens-on-a-plane-how-to-stay-healthy-in-flight?ft=1 (NPR) Pathogens on a plane: how to stay healthy in flight])<br /> * Keep your exercise routine as much as possible. Exercise burns calories, relieves stress, and helps reset your body clock, if you're in a different time zone.<br /> ** Pick a hotel that has a fitness center. If you must use a hotel that doesn't have one (or you need specific equipment, like a stationary bike) call and ask; they may have an arrangement with a nearby gym.<br /> ** If you're out of luck on the fitness center, bring an exercise DVD, and/or small lightweight equipment like a jump rope or tension bands. Or do a [http://well.blogs.nytimes.com/2013/05/09/the-scientific-7-minute-workout/ body-weight-only exercise routine].<br /> ** Bring quick-drying workout clothes. Rinse them in the shower, and dry them over the shower rod, so they're ready for tomorrow.<br /> ** Bring athletic shoes that double as casual street shoes, so you don't need to take up luggage space with extra shoes.<br /> ** See the Quartz [http://qz.com/287800/the-complete-guide-to-staying-in-shape-on-the-road/ Complete guide to staying in shape on the road].<br /> <br /> = Redux =<br /> <br /> '''Most people travel infrequently, and aren’t very skilled at it...'''<br /> * and there are a lot of people, so despite the infrequency of their travel, the Don’t Know path is very crowded<br /> * Businesses on the Don’t Know path have no loyalty to you (since infrequent travellers have no meaningful loyalty to them) so their main goal is to extract money from you immediately, even at the cost of the relationship<br /> * People on the Don’t Know path have to deal with the same Don’t Know problems every single day, which is exhausting and saps their empathy<br /> <br /> '''BUT - If you know what you’re doing...'''<br /> * You can shortcut around the Don’t Know path everywhere. Airports, Hotels, Restaurants<br /> * The businesses you deal with will view you as a regular, and want to keep you happy<br /> * The people you deal with will view you as a breath of fresh air, and feel understood, and be grateful and human in the ways that travel never is for others.<br /> <br /> = More advice =<br /> * [http://christianheilmann.com/2014/02/16/how-i-save-money-when-traveling-for-work-san-franciscovalleyus/ How I save money when traveling for work] by Christian Heilmann<br /> <br /> These podcasts have some excellent advice on business travel:<br /> * [http://www.manager-tools.com/2009/07/airline-travel-basics-1-part-1 Airline Travel Basics, part 1]<br /> * [http://www.manager-tools.com/2009/08/airline-travel-basics-1-part-2 Airline Travel Basics, part 2]<br /> * [http://www.manager-tools.com/2008/08/business-travel-packing Business Travel Packing]<br /> * [http://www.manager-tools.com/2009/07/travel-airline-seats Travel - Airline Seats]<br /> <br /> The what and how of packing only a carry-on: [http://www.onebag.com/ Onebag.com]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Travel_Guide&diff=1243348 2022-07-11T20:37:02Z

<p>Mhoye: Updates for modernity.</p> <hr /> <div><br /> = Travel doesn’t have to be terrible. =<br /> <br /> In fact, there may be no other part of your life where a handful of modest optimizations can make such an enormous difference. How different would travelling become, if:<br /> <br /> * You never lost your luggage.<br /> * You could get from the airport entrance to your flight's gate in minutes.<br /> * You had lounge access at the airport, upgraded flights, maybe even nicer rooms in hotels.<br /> * You knew you didn't have to eat junk on the road, but could discover great local restaurants instead.<br /> <br /> We have secrets. We have millions of miles travelled between us, and we'd like to show you how it's done.<br /> <br /> First, here are the 3 simplest things you can do to make travel a lot better:<br /> # Never, ever check your luggage.<br /> # Check in online as early as possible.<br /> # Pick a Frequent Flyer program<br /> <br /> Do these every time, and you’re already in the 80th percentile for travel success. What follows below is travel brilliance.<br /> <br /> = Planning =<br /> <br /> == Quick Tips ==<br /> * Scan a copy of your passport and any other travel documents and put them somewhere web accessible but password protected (like Dropbox or Google Drive). This is helpful for getting replacements, and for getting consular help in the meantime.<br /> * Print a copy of those scans - particularly your passport, covid test and vaccination status - and keep them in your carry-on. Do this regardless of the current policies of the countries you're travelling to or through - if policies change while you're on the road, you might have a problem.<br /> * Let your credit card company know that you travel. Anti-fraud measures might lock your card the first time you use it on foreign soil, but they can flag your account so that doesn’t happen. This is no fun to discover after the fact.<br /> * Different airlines have different size restrictions for carryon luggage; know your limits for the whole trip and stay inside them.<br /> * Wear a mask.<br /> <br /> == Pick a Frequent Flyer Program ==<br /> <br /> Prices are generally going to be competitive, so figure out your most common trip(s) and figure out which airline/alliance is best for those. Use that group for everything. You can easily sign up for FF programs online, and add it to your travel agency profile (Egencia for Mozilla employees).<br /> <br /> Even if you travel rarely, you'll eventually accrue enough mileage for free travel, and having a FF number makes online check-in easier.<br /> <br /> If you travel often enough, though, (25k+/year on most airlines) you start earning preferred status. This is the difference between &quot;scum&quot; and &quot;How can I help you?&quot; You have shorter lines for agents, shorter lines for security, you board first. You get access to elite lounges while you wait, and free upgrades to business class to make the trip more pleasant. These are little niceties, but they add up, and make travel much nicer. You can often share status with someone less privileged, which means your spouse likes traveling with you more, too.<br /> <br /> == Check In Online ==<br /> <br /> Every airline will let you check in online, usually 24 hours before your flight leaves. I know this will feel weird the first time, but it is an absolute necessity. With online check-in and no checked luggage, you can skip all the lines at the airport except security (and possibly customs/immigration).<br /> <br /> Checking in early may put you into a lower &quot;group&quot; for boarding (or at least not the suckiest, all-the-overhead-bins-are-full group). Check in as early as possible, even if you don't know how many bags you will check (correct answer: 0). You can always add (and pay for) checked bags when you get to the airport.<br /> <br /> The one '''exception''' to this guideline is that if you think your flight might be delayed or cancelled due to weather, ''don't'' check in online ahead of time. If you have to re-book, and you are already checked-in, the agent will have to &quot;uncheck&quot; you, which may slow down the re-booking process and cause you to miss out on alternate flight options. Keep in mind that weather problems cause ripple effects even in locations where weather is good. For example, your flight out of sunny Phoenix might be cancelled because the aircraft is grounded by a snowstorm in Chicago. (See this Egencia blog post for [http://info.egencia.com/wintertraveltips2014.html tips for avoiding weather delays].)<br /> <br /> Online check-in also lets you choose your seats, which brings us to...<br /> <br /> == Choose Your Seats ==<br /> <br /> * Take a window seat for very short flights or very long flights. Window seats have more shoulder room, less hassle from other passengers, and a window. The only downside is bladder management, but on short flights you can stick it out and on long ones you can get up when your fellow passengers do.<br /> * ''Every'' plane has some seats that suck. No recline, noisy, cold, lack of floor storage or slightly narrower than most, [http://www.seatguru.com SeatGuru] will tell you what to avoid. It'll also tell you which seats are great (extra legroom, etc) that you should take given half a chance. Usually, exit-row seats have extra legroom (good for tall people), and the last row and the row in front of the exit row do not recline (bad in general). The first row in a section (where you have a bulkhead in front of you instead of another seat) typically does not have under-seat storage, so everything must go in overhead bins, but it typically does have more legroom. (Seatguru will tell you whether or not this is the case on a particular plane.)<br /> * ''The Middle Seat Gambit'' - If you’re traveling with someone else, check in online together and look for an empty 3-person row. Take the aisle and window. Middle seats fill up last, there’s a decent chance the seat stays empty. If so, you have a lot more space to dump things during the flight, and more legroom since you can use that space instead of putting things under the seat in front of you.<br /> * If you’re traveling alone, you can still use the middle seat gambit by checking in online and looking at the seat map for someone acting as a de facto accomplice.<br /> * If there is only one (worst possible) seat left when you go to select seats, ''don't take it''. It will be claimed by someone else, and the gate agent will assign you a different seat. A flight that full might mean that someone gets bumped, but lack of a seat assignment doesn't guarantee it will be you.<br /> <br /> == Manage Layovers ==<br /> <br /> Flying nonstop to your destination is always easiest, but if that’s not a possibility for whatever reason, here are some other things to keep in mind:<br /> <br /> * Major metropolitan centers are often served by multiple airports, and each airline will have a preference. If you can’t get the flight you want with the airline you like, look to see whether you’re just pointing at the wrong airport.<br /> * If you can’t fly nonstop, you probably at least have your choice of connection airports, and the choice matters there. What’s more, a given airline will have certain preferred connection cities, so a couple trips should get you a reasonably complete list. (For example, connecting from Toronto to San Francisco on Star Alliance, it is much preferable to connect in Denver or Vancouver than it is to connect in Chicago O’Hare.) Consider the immigration/customs procedures of the country you're connecting in if it's separate from the origin or destination (e.g., prefer Vancouver over a US airport for connecting between Toronto and Auckland, since the US requires internationally-connecting passengers to go through immigration and customs).<br /> * If you have to have a connection, you might also have the opportunity to fly to a better airport (e.g., if you have to connect to Washington, DC, you are likely to be able to fly to DCA instead of IAD).<br /> * Take the season and likely weather into account when picking connecting airports; avoid snowy airports in winter, thunderstorm-y airports in summer.<br /> * If you have to layover overnight, prefer airports that have on-site hotels (and for god’s sake prefer Munich over Frankfurt).<br /> * If you’re crossing a border during your flight, it’s often preferable to layover in-country before crossing over. It means your first flight is domestic, so you can arrive later at the airport since there’s no immigration headache there. <br /> * Another reason not to check a bag is that when you have a connection after arriving in some countries (e.g., the USA, but not EU countries), you have to claim your bag, take it through customs (even though they rarely look at it), and then check it again for your connecting flight. More time and hassle.<br /> * Remember to account for boarding time when calculating layovers. If flight A arrives at 12:00 and flight B leaves at 1:00, you do not have an hour, you have about 20 minutes (because you need to get OFF of flight A once it arrives, transit to whichever gate/terminal flight B is in, and then be there for flight B '''boarding''', not flight B '''departure''').<br /> <br /> = Immigration and Customs =<br /> <br /> == General advice ==<br /> * Make sure you know what the requirements are for crossing all immigration and customs barriers before you do so. If you don't know what those requirements are, embassy or consulate websites are often useful, as are the US government's [http://travel.state.gov/content/passports/english/country.html country specific information] (though somewhat tending towards information useful to Americans).<br /> ** This includes vaccination status and testing, which varies on a country by country basis and will continue to do so for the foreseeable future.<br /> * Make sure you have any documentation needed in your carry-on luggage. When entering a country where you're not a citizen or resident, you should carry proof of onward travel, particularly if the reservation on which you're flying doesn't return you to your home country (e.g., because you're traveling on separate reservations).<br /> * If you're ''transferring'' in a country (or multi-country immigration zone) that's different from your origin or destination, figure out whether you'll need to deal with immigration there, and if so, what the rules are. This might vary depending on the airport, or in some cases even on which terminal you arrive at and depart from. (In the latter case, airport websites are often helpful.)<br /> * Don't carry any non-commercially-packaged food through customs, not even the apple you got in the airport. Many places have strict agricultural control policies that prohibit doing so; it's not worth the trouble.<br /> * Always carry a pen (blue or black) somewhere in your checked luggage for filling out the immigration and customs forms.<br /> <br /> = Packing =<br /> <br /> '''Quick Tips'''<br /> * Have a toiletry bag that you keep stocked, rather than trying to remember to pack toothbrushes &amp;c the day of. It doesn’t cost much to buy the duplicates once, and saves hassle/forgetting.<br /> * Put your favourite head, stomach, and sleep meds in the toiletry bag. You can buy most things on the road, but meds are sometimes an exception.<br /> * Throw a couple of large ziploc bags in there, too. They are immensely useful for storing wet clothing or leaking bottles or, by contrast, for putting things like passports in when you need them to stay dry. They weigh nothing and disappear into a pocket until needed.<br /> * Layers. You can adapt to a wide range of climates, even multi-city travel, by packing layers. Shirt, Sweater, Hoodie, Jacket is plenty warm, packs much more compactly than a parka, and gives you middle ground for an overwarm restaurant or an overcool office.<br /> * While you're packing, make a text list on your phone of everything you pack. Towards the end of your trip (such as waiting for your flight home), put a '+' next to every item you actually used. Next time, don't pack the things you didn't use. Also, if your bag goes missing, you have a list of what was in it.<br /> <br /> == Don’t Check Luggage ==<br /> <br /> :: Repeat after me: Checked luggage is for chumps.<br /> <br /> :: Again. Checked luggage is for chumps.<br /> <br /> :: -- George Clooney, ''Up in the Air''<br /> <br /> Every time you give your bag to the airlines, you're inviting them to lose it, abuse it, leave it in your departure city, forget about it on the tarmac during a rain delay, etc. North American airlines will allow you one carry on suitcase and one “personal bag” which usually means a purse or laptop. This is easily enough for a week of travel, and can be extended indefinitely with laundry service. Invest in a good carry-on and bring it with you.<br /> <br /> Put everything you need during the flight in your laptop bag, in case you have to gate-check your carry-on suitcase (common on short flights with smaller planes).<br /> <br /> == Choose the Right Luggage ==<br /> Checked luggage will inevitably be destroyed over time, regardless of quality. If you stick to carry on, though, good luggage will last forever; be willing to pay once for something that gets it right. Your happiness while traveling is worth it.<br /> <br /> His bias for non-rolling luggage notwithstanding, [http://www.onebag.com/bags.html this is the single best guide out there] for evaluating luggage. The highlights:<br /> <br /> * Lighter is better<br /> * Curvy designs rob you of packing volume, prefer right angles<br /> * Chain zippers are stronger than coil zippers (look for YKK as the brand of zipper)<br /> * Pocket design and positioning matters<br /> * So do tie-downs<br /> <br /> In truth, the best way to maximize quality while minimizing weight is to let go of the dependence on rolling bags. Soft-sided, non-wheeled bags are exceptionally light and versatile. [http://www.tombihn.com Tom Bihn] and [http://www.redoxx.com/ Red Oxx] are your best plays. Tom Bihn’s Aeronaut is is a full-sized carry-on that converts to a backpack for long walks across cobblestones/sprints to catch a connection/etc. The Red Oxx Air Boss was designed by the same guy who wrote the luggage-choosing guide above.<br /> <br /> If you're not ready to let go of wheeled bags, any manufacturer with a lifetime warranty is probably worth considering. These include:<br /> <br /> * [http://www.briggs-riley.com/ Briggs &amp; Riley]<br /> * [http://www.travelpro.com Travelpro] (&quot;the best&quot; carry-on according to [http://thewirecutter.com/reviews/best-carry-on-luggage/ The Wirecutter])<br /> * Certain models of [http://shop.eaglecreek.com/lightweight-carry-on/l/111 Eagle Creek] (not all models have a lifetime warranty)<br /> <br /> Pay attention to the bag’s extensible arm: is it well constructed? What does it do to your interior space? 2 segments of extension or 3? Moving parts make everything more fragile -- if you are choosing moving parts in your luggage, they need to be brilliant.<br /> <br /> == Buy It There (BIT) ==<br /> <br /> Don’t try to anticipate every contingency and pack for it. You will bog yourself down with unnecessary cruft. Pack for what you ''know'' you’ll need, or at most what you reasonably expect to need the majority of the time. You can find contact solution, toothpaste, aspirin, and dental floss at almost any convenience store. For the rest, shove an extra $50 into a pocket somewhere and buy whatever you need there, if it comes up. <br /> <br /> (Good news: It comes up less often than you’d think.)<br /> <br /> BIT exceptions: <br /> There are some things you don't want to source while traveling - if you only use one specific brand of shampoo, conditioner, etc, transfer it to a small, travel-friendly bottle. Depending on where you're traveling BIT can be tough if you don't speak the language and are looking for something very specific (like Cipro in India or a flat iron in China). Goes without saying, but BIT does *not* apply to medications (remember that what requires a prescription varies by country, but you can apply it if you know that something can be bought without a prescription at your destination).<br /> <br /> === Corollary: Wash It There ===<br /> If you’re gone for longer than a carry-on can reasonably contain (which is longer than you think), don’t fail over to multiple suitcases; just get things laundered partway through. Your hotel will offer laundry service, though it will be overpriced. Most of the time you’ll find a wash and fold place within walking distance or a service that does pick up and next day drop off.<br /> <br /> Also keep in mind that at most Mozilla or other geek events, you will probably acquire at least one or two t-shirts. You can bring one or two fewer shirts; if this guideline fails, wash one of the ones you brought.<br /> <br /> If you bring quick-drying underwear and socks, you can wash them in the sink or bathtub and dry them overnight on the towel rack (except in humid climates). You can skip bringing detergent by using the hotel's shampoo (as long as you don't mind your underwear smelling like &quot;ginger lemongrass&quot; or whatever); shampoo is just mild detergent. Check the plumbing before you fill the sink; some hotels don't install the lever for raising the plug. Before hanging items to dry, roll them in a towel and squeeze out excess moisture.<br /> <br /> == Counterpoint: The case for checking a suitcase ==<br /> A few heavy-traveling Mozillians are in the &quot;checked bag&quot; camp. Add your reasons for using this strategy here:<br /> * Problems with checked luggage are actually quite rare.<br /> * You don't have to schlep a roll-aboard through the airport with you, including squeezing it into tiny toilet stalls.<br /> * You can pack a few extra things that help you be more comfortable on an extended trip.<br /> * At least one airline (American) gives early boarding privileges (after Elite and Priority but before Zone 1) to passengers with no overhead baggage.<br /> * You aren't limited to 100ml bottles of liquid/gel/cream, and can bring home ''properly packed'' wine, booze, perfume, etc. (Wrap the bottle in at least two plastic bags and nestle it in the groove left by the extending handle, surrounded tightly by clothes.)<br /> * Having airline status often helps your bag appear on the belt faster. Also, if the final segment of your trip is an international arrival in the United States, you're unlikely to have to wait long for your bag, since all baggage goes to the same belt, so it gets there quickly.<br /> * TIP: Get a suitcase with four wheels. Baggage handlers can slide it across the floor of the cargo hold instead of tossing it, subjecting the suitcase and its contents to much less abuse. Anything that protrudes, like carry straps or zipper pulls, can get snagged and chewed up in baggage-handling equipment; go for streamlined.<br /> * TIP: Ask for your checked luggage to be marked &quot;Fragile&quot;. It will be loaded on top of other bags, and usually be unloaded first.<br /> * TIP: If you check luggage, don't let your eyes off the bag until there's a tag on it, and if you can, check that the tag is correct (with your name and correct destination airport on it). One of the common reasons for lost/delayed luggage is getting the wrong tag on it right at the check-in desk.<br /> * TIP: Things to make sure are '''not''' in your checked bag: everything you need to get through customs and immigration and get to your final destination. Any electronics that might be stolen. Lithium-ion batteries (prohibited).<br /> <br /> Some airlines (particularly non-North American or discount airlines) have much lower limits for what you're allowed to carry on, so you'll have to check luggage anyway.<br /> <br /> Some airlines (e.g., Air France, KLM) will even want to weigh your carry-on bag (often although not reliably), and want it to be a weight that's lower than what it is with your laptop in it (e.g., 6kg, 8kg). Remember that your laptop often counts as a separate personal item and you can take it out of the bag before weighing.<br /> <br /> ==Packing Techniques and Tools==<br /> Your strategy for how to put your stuff in your suitcase is very much a matter of personal preference, along with the type of travel you're doing (destination vs. touring) and the type of clothes you bring. Here are some ideas that may be helpful.<br /> <br /> * The [http://www.onebag.com/pack.html bundle method] is great for avoiding wrinkles, but it tends to require that you unbundle ''everything'' to get out any single thing.<br /> * It's extremely helpful to have some kind of containers to organize your stuff. Purpose-made packing &quot;cubes&quot; are great, but are absurdly expensive. You can get by with zip-top plastic bags if you don't travel often, or while you're waiting to find ready-made cubes on sale. <br /> * If you buy only one packing accessory, consider getting a [http://www.amazon.com/Eagle-Creek-Travel-Pack-It-Folder/dp/B002YIRC3O/ packing folder], which helps you fold larger items (shirts, pants, skirts) to a uniform footprint, and then encloses them like an envelope.<br /> * Compression bags, which let you squeeze all the air out of your clothes, are good only for clothes that don't easily wrinkle. However, a compression bag can be great as a laundry bag to minimize the volume of dirty clothes on your way home. Either way, have a cloth or plastic bag you can use to keep used laundry separate. <br /> <br /> = Airport Hacking =<br /> '''Quick Tips'''<br /> * ABC: Always Be Charging. Wherever you come to rest, be charging. Maybe your flight has power plugs, that's swell, but maybe they stop working, or your seatmate gets to it first, or you need it to charge your phone. If you're at rest for more than 10 minutes, find a plug. If you bring a power strip so others can plug in, too, you can make friends anywhere :-)<br /> * Watch where uniformed crew members go. They know the best eateries in any given airport, and even where to stand on the tram platform in order to get off quickly at the other end.<br /> * The internet knows about delays before your gate agents do. Bookmark [http://flightaware.com/live/ flightaware] right now, and use it from your phone at the airport to keep tabs. Caveat: Flightaware may show your flight as delayed because the inbound plane you're getting on is delayed; if the airline substitutes another aircraft, your flight could be on time or only a little delayed.<br /> * If you do see signs of a significant delay, particularly at night when it's likely you'll be put off until morning, act swiftly before the lines form. Talk to gate agents about rebooking onto other flights and if the line there is long, be on the phone with your airline as well. First to rebook means first to call hotels and taxis and all the rest. Being last to rebook means sleeping in the airport. If you have elite status, call the customer service number for elite members, not the general customer service number.<br /> * When you get off the plane, the restroom closest to your gate will be crowded with other people from your flight. Keep going to the next one further away.<br /> * No one wants to sleep in an airport, but flight delays or cancellations, or just poor planning, may require it. There is actually a whole website devoted to [http://www.sleepinginairports.net/tips.htm sleeping in airports].<br /> <br /> <br /> == Being prepared for security ==<br /> * Veteran move: if you have a digital boarding pass, set a screenshot of that boarding pass as the background of your lock screen, so you can see the QR code without unlocking the phone.<br /> * Bring identification. [http://www.tsa.gov/traveler-information/acceptable-ids Here's a list of acceptable IDs] in the US. If you forget your ID, all is not lost. It's possible, with some extra hassle, to travel within the US even if you don't have your identification. [http://blog.tsa.gov/2013/04/tsa-travel-tips-tuesday-can-you-fly.html Here's what the TSA says to do if you don't have ID.]<br /> * Have photocopies - paper copies - of your passport and one other piece of ID (and where necessary, vaccination status or test results.)<br /> * Avoid getting into a screening line behind people who look like they don't travel often (families with kids, retirement-age folks, large groups).<br /> * Wear slip-on shoes and socks. Do not go barefoot in airports (And, for the love of God, Do Not Sit Or Lie Down On The Floors. Airport floors are disgusting, you have no idea.)<br /> * Consider not wearing a belt, or wear one with no metal, so you don't have to take it off.<br /> * Avoid clothes with extra pockets, like cargo pants. They can be flagged by the body scanner, and cause you to get a pat-down. Same for &quot;travel&quot; clothes with hidden pockets; these can be handy while touring, but not while flying. Even a hoodie can win you a pat-down for the hood and kangaroo pocket. <br /> * On the other hand, a jacket with lots of pockets is like an extra carry-on; you have to remove it for security anyway, and you can keep your in-flight necessities (gadgets, etc.) close to hand during your flight.<br /> * Know the drill with liquids, gels, and creams: containers at most 100ml/3oz, in a clear zip-top bag, 1 liter/1 quart size. Have this in an external pocket of your carry-on, ready to pull out and put in a bin. (If you travel often, you might want to get a sturdier bag than the grocery store kind. It must still be clear and zip-top.)<br /> ** Don't pack little bottles of booze. Yes, it's under the limit, yes you're technically allowed to carry it through security. Don't.<br /> * Avoid large metal jewelry.<br /> * Take everything, but especially metal (keys, coins, etc.), out of your pockets.<br /> * '''Leave your pocket knives and multitools at home.'''<br /> * If you're wearing an activity monitor, such as a FitBit, take it off for screening.<br /> * You should hang onto your ID and boarding pass as you go through the line, but you can't carry them through screening; put them in your bin.<br /> * Put the bin with your shoes, jacket, and liquids onto the conveyor belt first. You can be getting dressed while the rest of your stuff comes through.<br /> * Take your laptop out of your bag and put it in a separate bin. You can usually leave it in a sleeve, as long as there's nothing else in the sleeve. <br /> * Consider getting a checkpoint-friendly laptop bag, with a laptop-only section that folds out without taking out the computer. The less you handle your laptop, the less likely you are to drop it. (US TSA allows you leave the computer in this type of bag; other countries often do not.)<br /> * Don't start going through the screening machine or metal detectors before you can see your stuff moving down the conveyor belt.<br /> <br /> == US Trusted Traveler Programs ==<br /> If you frequently cross US borders, you can save time and hassle in the long run by enrolling in one of the programs that provide expedited entry for pre-approved travelers. Enrolling involves an application fee and form, and an in-person interview at an entry point, so there is a start-up cost in time and money. Which program you should enroll in depends on the type of crossing you do most; you can enroll in more than one. <br /> <br /> * When entering the US, if you're not in a &quot;trusted traveler&quot; program, try to get into the immigration queue that is ''next to'' the Global Entry lane. If no one is in the Global Entry lane, the officer there will often take people from the nearby queue, making it move faster. Do likewise for NEXUS when entering Canada.<br /> * Wear Firefox gear when going through immigration, anywhere. It creates goodwill and starts pleasant conversations.<br /> <br /> ===Automated Passport Control===<br /> Automated Passport Control kiosks are available to citizens of the US, Canada, and [http://www.cbp.gov/travel/international-visitors/frequently-asked-questions-about-visa-waiver-program-vwp-and-electronic-system-travel Visa Waiver Program] countries, for entry into the US, in an expanding number of North American cities. Unlike Global Entry or Nexus, these kiosks require no pre-registration. You swipe your passport, let the kiosk take a photo, answer some questions, and then get a receipt that you show to a Customs and Border Patrol officer. The kiosk replaces filling out a customs card by hand.<br /> <br /> See the [http://www.cbp.gov/travel/us-citizens/Automated%20Passport%20Control Automated Passport Control] webpage for a list of cities with APC kiosks.<br /> <br /> === Global Entry ===<br /> [http://globalentry.gov/about.html Global Entry] provides expedited screening for entry ''into'' the US at certain airports. Once in the program, you can go to an automated kiosk instead of an immigration agent (skipping the enormous lines that result from multiple international flights arriving at about the same time), and you can answer the customs questions at the kiosk instead of filling out a paper form. Unless there is an issue with your kiosk interaction (such as it couldn't read your fingerprints), you don't need to talk to a CBP agent. Global Entry is open to U.S. citizens, lawful permanent residents of the U.S., Dutch citizens, South Korean citizens and Mexican nationals.<br /> <br /> === NEXUS ===<br /> [http://www.globalentry.gov/nexus.html NEXUS] provides expedited screening for crossing the US-Canada border in both directions. It can be used at land and sea entry points as well as at airports. You can use the NEXUS-only lanes at land crossings only if every person in the vehicle (including children) has a NEXUS card. Using NEXUS at an airport requires scanning your irises. If you wear contact lenses, you must remove them for the initial iris scan that is taken after your enrollment interview.<br /> <br /> === Other US programs ===<br /> * [http://www.globalentry.gov/netherlands.html FLUX] expedites passage between the US and '''the Netherlands''', and is open to US and Dutch citizens.<br /> * Global Entry members can receive expedited entry into '''[http://www.globalentry.gov/newzealand.html New Zealand]'''.<br /> * [http://www.globalentry.gov/sentri.html SENTRI] provides expedited entry into the US from '''Mexico''' at specific land crossings.<br /> * [http://www.globalentry.gov/korea.html Smart Entry Service] provides expedited entry into the Republic of '''Korea'''. It is open to US and Korean citizens.<br /> * [http://www.globalentry.gov/smartgate.html SmartGate] provides streamlined entry into '''Australia''' for US Global Entry members. Visa requirements still apply.<br /> * [http://www.globalentry.gov/tsa.html TSA PreCheck] enables US Global Entry and Canadian NEXUS members to use designated TSA airport screening lanes, without removing liquids, laptops, shoes, jackets, or belts. You must provide your membership number when booking flights with participating airlines. TSA is expanding the PreCheck program to include more people, including US military members and those invited by their airline's frequent flyer program. You must still apply, pay a fee, and go through an interview. See the [http://www.tsa.gov/tsa-precheck TSA PreCheck] website for details.<br /> <br /> == Other countries' traveler programs ==<br /> * The UK's [https://www.gov.uk/registered-traveller Registered Traveller service] enables certain citizens of Australia, Canada, Japan, New Zealand and the USA to get faster entry to the UK, without filling out a landing card. <br /> <br /> <br /> == Country-specific notes ==<br /> <br /> '''Note: Much of the per-country information is pre-covid, and needs to be verified or updated.'''<br /> <br /> === USA ===<br /> * visitors under the [https://travel.state.gov/content/travel/en/us-visas/tourism-visit/visa-waiver-program.html visa waiver program] (those who don't need a visa) must apply online for an [http://www.cbp.gov/travel/international-visitors/esta ESTA].<br /> <br /> === Canada ===<br /> * visitors who do not need a visa, are entering Canada by air, and are not US citizens or Canadian citizens or Canadian permanent residents, must apply online for an [http://www.cic.gc.ca/english/visit/eta.asp eTA].<br /> <br /> === Schengen Area (Europe) ===<br /> * The [http://en.wikipedia.org/wiki/Schengen_Area Schengen Area] is an immigration-barrier-free zone covering most of the European Union and some additional non-EU countries, but not the UK or Ireland.<br /> * If you need a visa to visit the Schengen Area, it is easier to get such a visa if your point of arrival in the Schengen Area is the same country as your destination. (For example, if you're traveling to Spain, it is easier to arrive in Madrid after connecting in the UK or US than connecting via Amsterdam, since in the latter case getting the visa requires dealing with both the Spanish and Dutch authorities.)<br /> * If your nationality requires a visa to visit the Schengen Area and your trip does not terminate in Schengen, avoid making more than one connection in Schengen; in such a case you must get a Schengen visa, even though that's not your destination. Schengen immigration authorities look at your ''next'' point of travel (not your final one) to decide whether you need a visa; if it is Schengen, they will ask for one.<br /> <br /> === New Zealand ===<br /> * Make sure to declare any shoes in your checked luggage. The authorities just want to look at them and maybe clean the dirt off for you, but they'll be upset if you don't declare them.<br /> * Don't even think about [http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&amp;objectid=11404025 bringing fresh fruit] into New Zealand or you will get an instant fine.<br /> <br /> === Australia ===<br /> * Visitors who can can enter without a visa must apply online for an [https://www.eta.immi.gov.au/ ETA].<br /> <br /> = Flying =<br /> <br /> '''Quick Tips'''<br /> * Hydrate, hydrate, hydrate. Air in an airplane at altitude is incredibly dry and dries you out. Drink water whenever you can. Bring an empty water bottle (even better: collapsible) and fill it from a water fountain inside security. (Some airports, like SFO, have water bottle filling spots that make this a little easier.) Don't drink the water that comes out of the water tanks onboard an airplane, including coffee and tea; you don't want to know how disgusting those tanks are. If you get water in the beverage service, ask for fizzy water (club soda) to ensure it came out of a bottle or can. If you need to brush your teeth in-flight, use water from your water bottle, not the tap in the toilet.<br /> * Request an alternate meal (kosher, indian, vegan, whatever) - they tend to be tastier, and often come first. (However, the downside to the meal coming first is that the tray is going to be in your way substantially longer.)<br /> * If you're in an aisle seat, you’ll find that the aisle-side armrest won’t lift. This is annoying, because it is much easier to deplane with that thing out of the way. Reach back to where the armrest joins the back of the chair -- there may be a release latch or button. (This works on some Boeing 777s; most smaller craft do not have this feature. See [http://brokensecrets.com/2011/01/17/raising-the-airplane-aisle-armrest/ this article] for a photo.)<br /> * Always wear shoes before going to the airplane lavatories; never go barefoot or wearing socks only. <br /> * Wear a mask, n95 or better.<br /> <br /> == Headphones ==<br /> Enjoying music or movies during travel is much better with headphones designed for travel use. You need to consider three types: <br /> * active noise-cancelling headphones<br /> * those without noise-cancellation<br /> * in-ear monitors. <br /> Generally speaking, on airplanes, active noise-cancellation will be better on the plane but worse when you're not on the plane (in the hotel room, for instance.) A quality headphone without noise cancellation will almost always sound better when not on an airplane. In-ear monitors allow for excellent sound quality and also allow one to rest your head on a pillow without the headphone pushing against one's ear, but some are uncomfortable with putting anything in one's ear. In-ear monitors are also much more compact. For those who want the sound quality of in-ear monitors and the compactness, but find that fit is a problem, consider Comply foam tip replacements which can be selected to fit your ear size.<br /> <br /> * For active noise cancellation headphones, the Bose Quiet Comfort 15 is the most popular model sold and for good reason. However if you want the headphone to be good when the noise-cancellation is turned off, you may want to consider the [http://www.psbspeakers.com/products/headphones/M4U-2-Headphones Psb m4u 2], which is more expensive but also more versatile.<br /> * For headphones without active noise cancellation, consider rugged models that have reputations burnished by decades of use by audio professionals such as the Sennheiser HD-25 1-ii. Another popular option is the V-Moda M-80 which has similar sound quality, has a good reputation for build quality, and also comes with a nice travel case.<br /> * For in ear monitors, there are too many to list but one line that is very popular is the Shure SE series which have models from $99 on up. These are very rugged models which allow for replaceable cables, replaceable tips and have very good sound quality.<br /> Additional resources for headphones include [http://www.innerfidelity.com/content/innerfidelitys-wall-fame Innerfidelity's Wall of Fame] and Head-fi.org's [http://www.head-fi.org/t/618255/check-out-the-head-fi-summer-2012-buying-guide 2012 Summer Buying Guide].<br /> <br /> == Make friends with TSA and your flight crew ==<br /> <br /> Airplanes are a sea of grumpy, tired, unhappy people. A little friendliness goes a long way -- especially if you're regularly flying the same route with the same flight crew.<br /> <br /> == Seat etiquette ==<br /> The following tips are about showing consideration to your fellow passengers, who unfortunately may not even notice it. But violating these norms is likely to cause annoyance. You don't want to be &quot;that guy&quot;, do you?<br /> <br /> * The person in the middle seats gets to use both armrests. The people in the window and aisle seats get a little extra space, so yielding one armrest each is the least they can do. In any case, try to keep your elbows in your own space.<br /> * Consider the person behind you before reclining your seat into their space, especially if they are trying to eat or use a laptop. Avoid reclining abruptly (though it's not always possible to control this). Raise your seat back during meals.<br /> * If you need to leave your seat during the flight, try to avoid hoisting yourself up by yanking on the seat in front of you. This may be difficult to avoid if the seat is reclined (see above).<br /> * If you have an individual touchscreen in the seat back in front of you, jabbing it forcefully doesn't make the touchscreen work any better. If it's really not responding to touch input, try controlling it from the armrest controls.<br /> * [http://www.independenttraveler.com/travel-tips/travelers-ed/the-etiquette-of-seat-backs-and-elbow-room The Independent Traveler: The etiquette of seat backs and elbow room]<br /> <br /> = Tips for specific airports =<br /> As a general rule of thumb, in any airport, the terminal or concourse that serves international flights has nicer shops and restaurants than the areas for domestic flights. So, if you're traveling domestically, have time to kill, and can get into the international terminal without going through passport control, you might want to go hang out there.<br /> <br /> == AMS Amsterdam ==<br /> * in the international section (only?), there are nice quiet places to sit on the upper level outside the lounges (even if you don't have lounge access)<br /> * if you want to take the train to/from the airport, hoard coins (€4 to Amsterdam-Centraal, less to Amsterdam-Lelylaan or Amsterdam Zuid), since the ticket machines don't take bills or American credit cards. (The city trams/buses in Amsterdam do take bills, but this is a national train.)<br /> * note that the entirety of the outside-[https://en.wikipedia.org/wiki/Schengen_Area Schengen]-immigration part of the airport does security at the gate, per flight<br /> <br /> == AUS Austin, Texas ==<br /> The food available in the airport is actually pretty good, since most of the food concessions offer menus from local restaurants. Get to the airport early enough to have a last plate of barbecue or breakfast tacos. <br /> <br /> Another reason to get to the airport early is the &quot;Knot Anymore&quot; chair massages available near gates 13 and 7. Austin is awash in good massage therapists, so the ones working in the airport are far better than most airport massage services.<br /> <br /> == CDG Paris / Charles de Gaulle ==<br /> * CDG airport has multiple airport hotels on premises (on the around-the-airport CDGVal shuttle train); typically at least one of the fancy ones has good prices because it isn't hosting a conference that week, but there's also an Ibis. <br /> * CDG airport has four disconnected parts:<br /> ** Terminal 1 (the cylinder with pods) (United is here)<br /> ** Terminal 3 (the discount airlines)<br /> ** Terminal 2A-2B-2C-2D-2E-2F (the bulk of the airport) (Air France is here)<br /> *** note that there are two satellite piers attached by train (outside immigration but not inside security) attached to Terminal 2E (the attached part of terminal 2E is called K, the satellites are called L and M)<br /> ** Terminal 2G<br /> * transport<br /> ** there's a train (CDGVal) connecting Terminal 1, Terminal 3 / Roissypole (where most but not all of the hotels are), and Terminal 2 (the station is between 2C/2D/2E/2F)<br /> ** high speed trains stop only at the terminal 2 station (between 2C/2D/2E/2F)<br /> ** RER trains (Paris's suburban rail network) stop at Terminal 2 (same station, again) and at &quot;Terminal 1&quot; (which is actually the Terminal 3 / Roissypole station for CDGVal)<br /> ** Terminal 2G is reachable only by shuttle (I think, never done it)<br /> ** If you want to take the RER to/from the airport, hoard coins in advance to pay the €9.50, since foreign cards don't work, and the machines don't take bills. <br /> ** The RoissyBus is only €10.50 and runs nonstop between CDG and the Paris Opera, only a few blocks from the Mozilla Paris office. Look for signs for &quot;RoissyBus&quot; or &quot;Paris by bus&quot; within each terminal to find the bus stop.<br /> <br /> == JFK New York ==<br /> * The wifi password of the British Airways' lounge is &quot;London&quot; (according to Reddit). You can usually get in range of the wifi hotspot without going inside the lounge.<br /> <br /> == LHR London Heathrow ==<br /> * Terminal 5 (international) <br /> ** If you need to take the train to concourse B or C, go to the far end of the platform. You'll bypass the crowds at the near end, and be closest to the escalators when you exit.<br /> ** If you need to backtrack from concourses B or C to concourse A, ''don't'' take the train; you'll be routed through security again. There's a pedestrian tunnel that parallels the train, and comes out next to elevators that let out inside security in concourse A. The tunnel doors are marked &quot;Emergency Exit&quot;, but do not have alarms, and in fact open automatically, to accommodate mobility-assistance carts. Stay to the left (remember: you're in England) to keep from being run over by them.<br /> ** If you're going to the Mozilla London office, [[London#From_Heathrow_by_traincheck the directions]] and don't bother with Heathrow Express.<br /> <br /> == NCE Nice, France ==<br /> * if you have a really early flight, there are multiple decent airport hotels nearby. But do '''not''', under any circumstances, stay at the Etap.<br /> * if you want to avoid a really early flight, consider as an alternative doing an overnight layover at CDG, which has multiple airport hotels walking distance from Terminal 1 (but poorly signed). Make sure your layover is long enough, though.<br /> * if you're traveling to west of the airport (e.g., towards W3C's European offices near Antibes) and want to take public transit, it's possible to walk to the Nice - St. Augustin train station ('''not''' the main Nice - Ville train station) in about 15-20 minutes, but there's basically no signage. But definitely look at the train schedules before trying this. Buses from the bus station (gare routière) at the airport may be better.<br /> * there's a free shuttle between Terminals 1 and 2. Don't try walking between terminals.<br /> * There are bus stations at both terminals, but some bus routes stop at both terminal and some stop only at Terminal 1. You need to buy a ticket at the station before boarding.<br /> * the airport does not have water fountains behind security. But restaurants will probably be willing to fill up a water bottle for you, especially if you've bought something there.<br /> <br /> == NRT Tokyo/Narita ==<br /> * If you can do so just as easily, fly to Haneda Airport (HND) instead, which is closer to the city.<br /> * Don't even ''think'' of taking a taxi. It will take hours, and cost multiple hundreds of US dollars.<br /> * Two companies (JR and Keisei) run trains to Tokyo, and both have express and local services at different prices. Choices depend on where in Tokyo you're going. Google Maps might be helpful, or just figure it out when you get there.<br /> * Consider taking a [http://www.limousinebus.co.jp/en/ Limousine Bus] to somewhere close to your destination, and take a taxi from there.<br /> <br /> == ORD Chicago O'Hare ==<br /> * In Terminal 3, at the beginning of concourse G, there is a &quot;Chicago Urban Garden&quot; on the second floor, with aeroponic herbs and vegetables. This is a nice quiet place to wait if you don't have access to an airline lounge. <br /> <br /> == SFO San Francisco ==<br /> * if you're through security and looking for food, realize that some pairs of terminals are connected behind security. In particular, there are four separated behind-security zones at SFO right now: International-G/Terminal3-F/Terminal3-E, Terminal2-D/Terminal1-C, Terminal1-B, and International-A. In particular, if you're in C, you can probably find better food and better places to sit in D, and at some hours there's not much open in G, but you can head over to F.<br /> * The recently renovated terminal areas are the International Terminal (2000), Terminal 2 (gates D) (2011), and Terminal 3 gates E only (2014)<br /> * If you're taking BART to the airport, you can take the airtrain or walk to get around the airport from the airport BART station. You should definitely walk to International (G or A, which share a large central checkin hall but have separate gate areas), maybe walk to Terminal 3 (at least if you're ready to go straight to the security line), and you can walk to the other terminal if you like.<br /> <br /> == SJC San Jose CA ==<br /> <br /> == TPE Taipei Taoyuan ==<br /> * if you're coming from within Asia to Taipei, fly to Songshan Airport (TSA) instead<br /> * if you have Star Alliance gold, there are multiple EVA lounges to choose from. The main one, with all the good food, is on the same side of the open (to the floor below) space as the tropical bar one, with entrance across the hallway from it (not across the open space)<br /> <br /> == YVR Vancouver ==<br /> * As airports go this one is a pretty beautiful. If you're departing to the US from Vancouver note that you will go through US customs and immigration at YVR, so arrive 2 hours before your scheduled departure time. <br /> <br /> = Trains =<br /> <br /> * for booking long-distance trains within Europe, https://www.trainline.eu/ is often better than the national train company sites, because they tend to be clearer about both giving you the better options for ticket retrieval and explaining those options to you<br /> <br /> = Hotels =<br /> <br /> '''Quick Tips'''<br /> * Ask for upgrades. I know, this sounds trite, but it works. If you don’t know how that works, just remember, when checking in, to ask “Is there a better room available?” If they say yes, you’re set. If they say no, that’s fine. If they say “yes, for a price” then you can consider that price and make the call. We’ve gotten $2000/night rooms on a $180/night booking just by asking. This tends to work well when the hotel has a lot of open inventory (particularly effective in LAS, less effective near Moscone during a conference).<br /> * When checking in, adjust your interactions with the clerk based on whether they smile when you approach. Chit-chat with a smiling clerk, but not with an unsmiling clerk. The latter is just as much a form of establishing rapport as chit-chat, because you're not wasting the time of a transaction-oriented person. And establishing rapport can make the marginal difference in whether they decide to give you an upgrade.<br /> * Expensive hotels tend to have sensors in the minibars, but most of the rest still just have housekeeping track what’s missing each visit and bill you. If you do get the munchies, just head out to a convenience store the next day before housekeeping and buy matching replacements at the saner price. <br /> * You can avoid the minibar entirely by grabbing a granola bar or two from a Mozilla kitchen before departing. They are bound to be healthier than anything you find in the minibar late night. <br /> * Every hotel has a bucket of standard toiletry items (toothbrush, razor, &amp;c). You should have a toiletry bag stocked and ready to go (see above) but if you find yourself missing something, just call the front desk.<br /> * Likewise, every hotel has a bucket of left-behind chargers/power cables.<br /> * Set your climate controls when you first get into the room. Forgetting until you come back after dinner ready for sleep and finding the room is hot and stale is no fun.<br /> * Some hotels won’t let the climate controls work unless your room keycard is stuck into a switch by the door. This isn’t a magstripe reader, it’s just a physical switch - use a business card or a folded up piece of paper (or your library card) and have your room the way you want it.<br /> * If the drapes that don't quite meet, and therefore let in unwanted sunlight or street light, use one or two big binder clips to keep the drapes closed.<br /> * You can usually get a later check-out time just by asking. This doesn't work indefinitely, but they can't clean every room at once, so asking for 1pm instead of 11am just means they move your room to the bottom of the list for cleaning that day.<br /> * Repack for departure before you go to sleep, except for the clothes and toiletries you'll need in the morning. That way, if you oversleep for whatever reason, you can throw on your clothes, grab those last items, and go without wasting any more time.<br /> * To avoid leaving things behind:<br /> ** Bring your original packing checklist, and use it to repack.<br /> ** Pull all the linens off the bed and throw all used towels into the shower, so you're sure nothing's hidden, and check every wall socket for chargers.<br /> ** If you unpack into drawers, check every drawer before you leave.<br /> <br /> == Pick a hotel, get into the frequent guest program ==<br /> <br /> Same deal as airlines. At the least, it eventually adds up to free stays, but getting to status means room upgrades, easier check-in, more flexibility on check-in/check-out times, and extra points for each stay. Some hotel loyalty points can also be transferred to airline loyalty programs.<br /> <br /> It can be harder to consistently stay with the same hotel group than to consistently fly the same airline (they're sold out or not convenient, the conference hotel is elsewhere, etc.). However, it's good to join the loyalty program for any hotel you stay at, before you make your reservation. You may get a better rate or a better room. Hotel staff seem to give an extra measure of courtesy and consideration when you're in the loyalty program. (When booking by phone, I've had a &quot;sold out&quot; group rate suddenly become available when I gave my membership number.) If you haven't joined by the time you check in, ask the clerk to sign you up; they'll get credit for signing you up, and will be even more inclined to treat you nicely.<br /> <br /> Linked below are the programs associated with the hotels that are typically used for visiting Mozilla in Mountain View.<br /> <br /> {|<br /> |-<br /> |Holiday Inn Express<br /> |[http://www.priorityclub.com/ Priority Club]<br /> |<br /> |-<br /> |Avante/Wild Palms<br /> |[http://www.joyoflifeclub.com/ Joy of Life Club]<br /> |(Does not give points for stays that are paid through corporate billing.)<br /> |}<br /> <br /> == Choose Your Room ==<br /> <br /> It's a good practice to indicate that you have any preference on your room at all. Put this into your loyalty program profile and your travel agency profile (Egencia, for Mozilla employees), so it's transmitted with your reservation. If you have no preference, they will put you in the room for people who do not indicate a preference. You know, the one in the basement. With the leaky faucet and carpet from 1973. <br /> <br /> If you have a choice between one or two beds, choose two, even though you'll only use one for sleeping. The other one makes a great surface for spreading out your stuff. Often, hotel beds are on casters, so you can shove the extra bed against the wall, to prevent stuff falling between the bed and the wall.<br /> <br /> Generally, you'll do well to ask for a high floor and a room away from the elevator. Many hotels do renovations by floor starting from the top and working their way down. So high floors have a better chance of being recently renovated. They are also further away from street noise or the bar in the atrium. A room away from the elevator means less foot traffic and not waking up at 5am to repeated &quot;ding!&quot; of the elevator door opening. For motels, you want upstairs (less foot traffic) and outside (away from the courtyard with the pool).<br /> <br /> If the room is awful, don't be afraid to walk back downstairs and see if they have anything a bit more updated. If the whole hotel is awful, check your luggage at the desk and walk in a square block radius around the hotel to see if there's something less frightening. <br /> <br /> Never pick a hotel based on a picture of the lobby. Lobbies are always the first thing to get renovated.<br /> <br /> == Tipping Hotel Staff ==<br /> If you believe in tipping (which varies across cultures):<br /> * If you take a hotel shuttle from the airport, be sure to tip the shuttle driver. Don't just hand it to them and walk away; look them in the eye and express genuine appreciation for their service while you give them the tip. This is your first contact with the hotel staff, and if you make a good impression, word will spread to the other staff, and you'll get great service throughout your stay. This driver may also be the person who gets you to your outbound flight, through heavy traffic, just in the nick of time.<br /> * Similarly, leave a tip for housekeeping after the first night. This paves the way for good service when you make special requests, such as extra towels or toiletries, or to come back later because you're still in the room. Leave the money on top of a note that says at least &quot;Thanks!&quot; so the housekeeper knows it's for them.<br /> <br /> = Money =<br /> <br /> * Exchange: Do not change money at the airport. The rates are higher there than anywhere else. If you have a local bureau de change, use that, or order currency online for pickup at the airport. If you can find a company that does that (Travelex in the UK, at least) the rates will be much better than those posted on the wall that they charge you when you are a captive customer. The best rates are likely to be had by using an ATM. <br /> * Debit: Using an ATM card can be an easy and inexpensive way to secure some local currency. Make sure your card will work abroad before you travel. Common ATM networks that are broadly available include Pulse and Plus. Consider getting a debit card with no foreign transaction fees (Charles Schwab offers one).<br /> * Stay organized: It's helpful to keep your currency separate from your home currency, particularly if you're going to cycle through multiple currencies during your trip (usd &gt; euro &gt; pounds). Don't underestimate the power of a ziploc baggie if you're American and unaccustomed to coinage-heavy currencies.<br /> <br /> == Credit cards ==<br /> The US has historically had a different system (magnetic strips) for credit card security from the rest of the world (which uses the chip-and-pin system). This can cause headaches for both Americans traveling abroad, and others traveling to the US, as the systems are incompatible. Most US stores now support chip-and-signature cards, but you might run into smaller ones that don't have chip-reading equipment (e.g., a food truck using Square). <br /> <br /> * A very few US banks offer true chip-and-pin cards, including Citibank and [https://www.andrewsfcu.org/credit_cards_and_loans/credit_cards/globetrek_rewards.html Andrews Federal Credit Union]. The latter also has no annual fee and no international transaction fees. See this extensive but not exhaustive [http://thepointsguy.com/2013/05/us-credit-cards-with-smart-chips/ list of US-based chip-and-pin cards]. <br /> * You can get a pre-paid, reloadable chip-and-pin card called [http://www.cashpassport.com/1/travelex/ &quot;Cash Passport&quot;] from Travelex. You can buy it and reload it online or at Travelex locations in the US. You can load it in multiple currencies: GBP, EUR, CAD, AUD and JPY. The security seems a bit crappy (you can't change the PIN, and their only security question is mother's maiden name), but since it's pre-paid, you can limit your financial exposure, and reload online as needed.<br /> <br /> Another issue for travelers is transaction fees when making purchases in currencies other than your home currency; these can range from 1% up to as much as 7%. US-based credit cards that don't charge international transaction fees include CapitalOne and Andrews FCU.<br /> <br /> More and more US retailers have card readers that accept chip-based cards, so the situation is improving for visitors to the US. However, they probably don't understand the PIN system, so you will still need to sign (either on the reader, or on paper).<br /> <br /> = Preparing to be less-online than normal =<br /> <br /> If your cellphone plan doesn't have reasonable data roaming, or if you might be in areas with poor cell coverage, you should be prepared to survive without your usual data connection. This might include things like:<br /> * downloading offline maps in advance. ([http://maps.me/ maps.me] for Android and iOS lets you download offline OpenStreetMap maps by country or part-of-country.)<br /> * knowing where you're going to need to be (hotels, meeting locations) before you leave<br /> <br /> = On Foreign Soil =<br /> <br /> * Data/Voice rates<br /> ** You can use Skype to call US 1-800 numbers toll free from anywhere in the world.<br /> ** Before you leave your home country, add $20-40 of SkypeOut credits to your account. While Skype to Skype calls are free, SkypeOut credits will let you call any number internationally for about $.02 per minute.<br /> ** International text messages are typically NOT covered under your mobile plan. For US cell plans, it's usually about $.50 per SMS. If you have a good international rate, think long and hard about when you use SMS and why. A conversation about when you landed and where to meet and what time to get there on SMS may be more than a 2 minute call that covers the same details.<br /> ** [http://readwrite.com/2014/06/17/5-secrets-avoiding-hefty-international-data-roaming-charges-fees 5 secrets to avoiding hefty international data roaming fees] <br /> * Finding wifi<br /> ** In airports, airlines' priority lounges often have no wifi password, and you can access their hotspots from outside the lounge. (See note above for JFK airport.)<br /> ** Starbucks, McDonalds, and Burger King are sadly ubiquitous, and often have free wifi.<br /> ** You can sometimes find the password for a business's wifi in the comments for that business on FourSquare.<br /> * Language barriers<br /> ** Grab some business cards or stationery with your hotel's address on them before you head out. You can hand one to a cabbie whose language you do not speak, to get yourself back to home base. <br /> <br /> Still to write/update:<br /> * Language barriers<br /> ** Add Line2 details...<br /> <br /> ==Coping with jet lag==<br /> * Do not go to sleep. Do not nap. Stay up as long as you possibly can. Eat meals at local times and get into bed when it's dark outside. It will hurt on day one but by day three, you'll be glad you did. <br /> * If you absolutely must sleep, do a 20 minute powernap and then get up, walk around, and do not fall back to sleep. (Powernapping pro tip: [https://www.vox.com/2014/8/28/6074177/coffee-naps-caffeine-science take a &quot;coffee nap&quot;]: quickly drink a cup of coffee, and ''then'' take a nap; the coffee will wake you up in a short while, and you'll be more alert than with a nap or a coffee alone.) <br /> * In a pinch, Benedryl (dipenhydramine) can help you reset your internal clock and it's substantially gentler on your system than the prescription sleep aids. (It's also good for nausea if you get motion sickness, and of course, allergic reactions.)<br /> * If you find yourself awake when you should be sleeping (by local time), avoid bright screens (computers, phones, e-readers), because they activate wakefulness in your brain. Try reading a paper book or magazine (radical, I know). If you must use a screen, set it to white text on a black background, to reduce the overall brightness; or get an app (such as [https://justgetflux.com/ f.lux] for Mac/iOS or [https://play.google.com/store/apps/details?id=com.urbandroid.lux Twilight] for Android) that reduces the amount of blue light emitted by your device at night.<br /> * If possible, follow the [http://www.wikihow.com/Prevent-Jet-Lag-with-a-Modified-Diet Anti-Jet Lag Diet]; this is easier to do at home than while traveling, but IME even an approximation helps. <br /> ** As an abbreviated version: eat as little as possible on your day of travel, avoiding caffeine and alcohol; eat a high-protein breakfast at breakfast time in your new time zone.<br /> ** Bring protein bars with you to ensure that you can get protein at the right time.<br /> <br /> <br /> = Eating =<br /> <br /> Eat like a local.<br /> <br /> Never ask the front desk at your hotel for a dinner recommendation. If possible, ask anyone else to weigh in. The bellhop, your taxi driver, the barista at Starbucks, Yelp, Chowhound, etc. The best recommendations come from people who are actually living and working in the area. (TripAdvisor tells you what people who ''don't'' live there think.) The concierge at the hotel will always orient toward broad, tourist-pacifying tastes. The food will be edible, but forgettable. They'll never tell you about the super tasty hole-in-the-wall joint three blocks away.<br /> <br /> = Staying healthy =<br /> * Wash hands frequently! <br /> * Carry and use hand-sanitizer wipes. (A bottle of hand-sanitizer gel takes up valuable room in your liquids bag.) Sanitize your hands in-flight before you eat or drink, and after washing your hands in the lavatory (on-board water, again). Also use them to wipe off [http://www.travelmath.com/feature/airline-hygiene-exposed/ tray tables, seatbelt buckles, and air vents], where germs lurk on airplanes.<br /> * Set the fan above your seat on the plane to low or medium, and position it to blow into your lap, just in front of your face. This will help knock airborne pathogens out of the air, so you'll be less likely to breathe them in. ([http://www.npr.org/blogs/goatsandsoda/2014/07/14/319194689/pathogens-on-a-plane-how-to-stay-healthy-in-flight?ft=1 (NPR) Pathogens on a plane: how to stay healthy in flight])<br /> * Keep your exercise routine as much as possible. Exercise burns calories, relieves stress, and helps reset your body clock, if you're in a different time zone.<br /> ** Pick a hotel that has a fitness center. If you must use a hotel that doesn't have one (or you need specific equipment, like a stationary bike) call and ask; they may have an arrangement with a nearby gym.<br /> ** If you're out of luck on the fitness center, bring an exercise DVD, and/or small lightweight equipment like a jump rope or tension bands. Or do a [http://well.blogs.nytimes.com/2013/05/09/the-scientific-7-minute-workout/ body-weight-only exercise routine].<br /> ** Bring quick-drying workout clothes. Rinse them in the shower, and dry them over the shower rod, so they're ready for tomorrow.<br /> ** Bring athletic shoes that double as casual street shoes, so you don't need to take up luggage space with extra shoes.<br /> ** See the Quartz [http://qz.com/287800/the-complete-guide-to-staying-in-shape-on-the-road/ Complete guide to staying in shape on the road].<br /> <br /> = Redux =<br /> <br /> '''Most people travel infrequently, and aren’t very skilled at it...'''<br /> * and there are a lot of people, so despite the infrequency of their travel, the Don’t Know path is very crowded<br /> * Businesses on the Don’t Know path have no loyalty to you (since infrequent travellers have no meaningful loyalty to them) so their main goal is to extract money from you immediately, even at the cost of the relationship<br /> * People on the Don’t Know path have to deal with the same Don’t Know problems every single day, which is exhausting and saps their empathy<br /> <br /> '''BUT - If you know what you’re doing...'''<br /> * You can shortcut around the Don’t Know path everywhere. Airports, Hotels, Restaurants<br /> * The businesses you deal with will view you as a regular, and want to keep you happy<br /> * The people you deal with will view you as a breath of fresh air, and feel understood, and be grateful and human in the ways that travel never is for others.<br /> <br /> = More advice =<br /> * [http://christianheilmann.com/2014/02/16/how-i-save-money-when-traveling-for-work-san-franciscovalleyus/ How I save money when traveling for work] by Christian Heilmann<br /> <br /> These podcasts have some excellent advice on business travel:<br /> * [http://www.manager-tools.com/2009/07/airline-travel-basics-1-part-1 Airline Travel Basics, part 1]<br /> * [http://www.manager-tools.com/2009/08/airline-travel-basics-1-part-2 Airline Travel Basics, part 2]<br /> * [http://www.manager-tools.com/2008/08/business-travel-packing Business Travel Packing]<br /> * [http://www.manager-tools.com/2009/07/travel-airline-seats Travel - Airline Seats]<br /> <br /> The what and how of packing only a carry-on: [http://www.onebag.com/ Onebag.com]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Travel_Guide&diff=1243347 2022-07-11T20:30:27Z

<p>Mhoye: More cleanup</p> <hr /> <div>----<br /> :: This page was originally created on Mozilla's internal intranet. However, it contains lots of information that could be useful to Mozillians who travel to Mozilla events, or really, anyone who travels, period. The original page (and its history) disappeared when the intranet site was retired.<br /> ----<br /> Travel doesn’t have to be terrible. In fact, there may be no other part of your life where a handful of modest optimizations can make such an enormous difference. How different would travelling become, if:<br /> <br /> * You never lost your luggage.<br /> * You could get from the airport entrance to your flight's gate in minutes.<br /> * You had lounge access at the airport, upgraded flights, maybe even nicer rooms in hotels.<br /> * You knew you didn't have to eat junk on the road, but could discover great local restaurants instead.<br /> <br /> We have secrets. We have millions of miles travelled between us, and we'd like to show you how it's done.<br /> <br /> First, here are the 3 simplest things you can do to make travel a lot better:<br /> # Never, ever check your luggage.<br /> # Check in online as early as possible.<br /> # Pick a Frequent Flyer program<br /> <br /> Do these every time, and you’re already in the 80th percentile for travel success. What follows below is travel brilliance.<br /> <br /> = Planning =<br /> <br /> == Quick Tips ==<br /> * Scan a copy of your passport and any other travel documents and put them somewhere web accessible but password protected (like Dropbox or Google Drive). This is helpful for getting replacements, and for getting consular help in the meantime.<br /> * Print a copy of those scans - particularly your passport, covid test and vaccination status - and keep them in your carry-on. Do this regardless of the current policies of the countries you're travelling to or through - if policies change while you're on the road, you might have a problem.<br /> * Let your credit card company know that you travel. Anti-fraud measures might lock your card the first time you use it on foreign soil, but they can flag your account so that doesn’t happen. This is no fun to discover after the fact.<br /> * Different airlines have different size restrictions for carryon luggage; know your limits for the whole trip and stay inside them.<br /> <br /> == Pick a Frequent Flyer Program ==<br /> <br /> Prices are generally going to be competitive, so figure out your most common trip(s) and figure out which airline/alliance is best for those. Use that group for everything. You can easily sign up for FF programs online, and add it to your travel agency profile (Egencia for Mozilla employees).<br /> <br /> Even if you travel rarely, you'll eventually accrue enough mileage for free travel, and having a FF number makes online check-in easier.<br /> <br /> If you travel often enough, though, (25k+/year on most airlines) you start earning preferred status. This is the difference between &quot;scum&quot; and &quot;How can I help you?&quot; You have shorter lines for agents, shorter lines for security, you board first. You get access to elite lounges while you wait, and free upgrades to business class to make the trip more pleasant. These are little niceties, but they add up, and make travel much nicer. You can often share status with someone less privileged, which means your spouse likes traveling with you more, too.<br /> <br /> == Check In Online ==<br /> <br /> Every airline will let you check in online, usually 24 hours before your flight leaves. I know this will feel weird the first time, but it is an absolute necessity. With online check-in and no checked luggage, you can skip all the lines at the airport except security (and possibly customs/immigration).<br /> <br /> Checking in early may put you into a lower &quot;group&quot; for boarding (or at least not the suckiest, all-the-overhead-bins-are-full group). Check in as early as possible, even if you don't know how many bags you will check (correct answer: 0). You can always add (and pay for) checked bags when you get to the airport.<br /> <br /> The one '''exception''' to this guideline is that if you think your flight might be delayed or cancelled due to weather, ''don't'' check in online ahead of time. If you have to re-book, and you are already checked-in, the agent will have to &quot;uncheck&quot; you, which may slow down the re-booking process and cause you to miss out on alternate flight options. Keep in mind that weather problems cause ripple effects even in locations where weather is good. For example, your flight out of sunny Phoenix might be cancelled because the aircraft is grounded by a snowstorm in Chicago. (See this Egencia blog post for [http://info.egencia.com/wintertraveltips2014.html tips for avoiding weather delays].)<br /> <br /> Online check-in also lets you choose your seats, which brings us to...<br /> <br /> == Choose Your Seats ==<br /> <br /> * Take a window seat for very short flights or very long flights. Window seats have more shoulder room, less hassle from other passengers, and a window. The only downside is bladder management, but on short flights you can stick it out and on long ones you can get up when your fellow passengers do.<br /> * ''Every'' plane has some seats that suck. No recline, noisy, cold, lack of floor storage or slightly narrower than most, [http://www.seatguru.com SeatGuru] will tell you what to avoid. It'll also tell you which seats are great (extra legroom, etc) that you should take given half a chance. Usually, exit-row seats have extra legroom (good for tall people), and the last row and the row in front of the exit row do not recline (bad in general). The first row in a section (where you have a bulkhead in front of you instead of another seat) typically does not have under-seat storage, so everything must go in overhead bins, but it typically does have more legroom. (Seatguru will tell you whether or not this is the case on a particular plane.)<br /> * ''The Middle Seat Gambit'' - If you’re traveling with someone else, check in online together and look for an empty 3-person row. Take the aisle and window. Middle seats fill up last, there’s a decent chance the seat stays empty. If so, you have a lot more space to dump things during the flight, and more legroom since you can use that space instead of putting things under the seat in front of you.<br /> * If you’re traveling alone, you can still use the middle seat gambit by checking in online and looking at the seat map for someone acting as a de facto accomplice.<br /> * If there is only one (worst possible) seat left when you go to select seats, ''don't take it''. It will be claimed by someone else, and the gate agent will assign you a different seat. A flight that full might mean that someone gets bumped, but lack of a seat assignment doesn't guarantee it will be you.<br /> <br /> == Manage Layovers ==<br /> <br /> Flying nonstop to your destination is always easiest, but if that’s not a possibility for whatever reason, here are some other things to keep in mind:<br /> <br /> * Major metropolitan centers are often served by multiple airports, and each airline will have a preference. If you can’t get the flight you want with the airline you like, look to see whether you’re just pointing at the wrong airport.<br /> * If you can’t fly nonstop, you probably at least have your choice of connection airports, and the choice matters there. What’s more, a given airline will have certain preferred connection cities, so a couple trips should get you a reasonably complete list. (For example, connecting from Toronto to San Francisco on Star Alliance, it is much preferable to connect in Denver or Vancouver than it is to connect in Chicago O’Hare.) Consider the immigration/customs procedures of the country you're connecting in if it's separate from the origin or destination (e.g., prefer Vancouver over a US airport for connecting between Toronto and Auckland, since the US requires internationally-connecting passengers to go through immigration and customs).<br /> * If you have to have a connection, you might also have the opportunity to fly to a better airport (e.g., if you have to connect to Washington, DC, you are likely to be able to fly to DCA instead of IAD).<br /> * Take the season and likely weather into account when picking connecting airports; avoid snowy airports in winter, thunderstorm-y airports in summer.<br /> * If you have to layover overnight, prefer airports that have on-site hotels (and for god’s sake prefer Munich over Frankfurt).<br /> * If you’re crossing a border during your flight, it’s often preferable to layover in-country before crossing over. It means your first flight is domestic, so you can arrive later at the airport since there’s no immigration headache there. <br /> * Another reason not to check a bag is that when you have a connection after arriving in some countries (e.g., the USA, but not EU countries), you have to claim your bag, take it through customs (even though they rarely look at it), and then check it again for your connecting flight. More time and hassle.<br /> * Remember to account for boarding time when calculating layovers. If flight A arrives at 12:00 and flight B leaves at 1:00, you do not have an hour, you have about 20 minutes (because you need to get OFF of flight A once it arrives, transit to whichever gate/terminal flight B is in, and then be there for flight B '''boarding''', not flight B '''departure''').<br /> <br /> = Immigration and Customs =<br /> <br /> == General advice ==<br /> * Make sure you know what the requirements are for crossing all immigration and customs barriers before you do so. If you don't know what those requirements are, embassy or consulate websites are often useful, as are the US government's [http://travel.state.gov/content/passports/english/country.html country specific information] (though somewhat tending towards information useful to Americans).<br /> ** This includes vaccination status and testing, which varies on a country by country basis and will continue to do so for the foreseeable future.<br /> * Make sure you have any documentation needed in your carry-on luggage. When entering a country where you're not a citizen or resident, you should carry proof of onward travel, particularly if the reservation on which you're flying doesn't return you to your home country (e.g., because you're traveling on separate reservations).<br /> * If you're ''transferring'' in a country (or multi-country immigration zone) that's different from your origin or destination, figure out whether you'll need to deal with immigration there, and if so, what the rules are. This might vary depending on the airport, or in some cases even on which terminal you arrive at and depart from. (In the latter case, airport websites are often helpful.)<br /> * Don't carry any non-commercially-packaged food through customs, not even the apple you got in the airport. Many places have strict agricultural control policies that prohibit doing so; it's not worth the trouble.<br /> * Always carry a pen (blue or black) somewhere in your checked luggage for filling out the immigration and customs forms.<br /> <br /> = Packing =<br /> <br /> '''Quick Tips'''<br /> * Have a toiletry bag that you keep stocked, rather than trying to remember to pack toothbrushes &amp;c the day of. It doesn’t cost much to buy the duplicates once, and saves hassle/forgetting.<br /> * Put your favourite head, stomach, and sleep meds in the toiletry bag. You can buy most things on the road, but meds are sometimes an exception.<br /> * Throw a couple of large ziploc bags in there, too. They are immensely useful for storing wet clothing or leaking bottles or, by contrast, for putting things like passports in when you need them to stay dry. They weigh nothing and disappear into a pocket until needed.<br /> * Layers. You can adapt to a wide range of climates, even multi-city travel, by packing layers. Shirt, Sweater, Hoodie, Jacket is plenty warm, packs much more compactly than a parka, and gives you middle ground for an overwarm restaurant or an overcool office.<br /> * While you're packing, make a text list on your phone of everything you pack. Towards the end of your trip (such as waiting for your flight home), put a '+' next to every item you actually used. Next time, don't pack the things you didn't use. Also, if your bag goes missing, you have a list of what was in it.<br /> <br /> == Don’t Check Luggage ==<br /> <br /> :: Repeat after me: Checked luggage is for chumps.<br /> <br /> :: Again. Checked luggage is for chumps.<br /> <br /> :: -- George Clooney, ''Up in the Air''<br /> <br /> Every time you give your bag to the airlines, you're inviting them to lose it, abuse it, leave it in your departure city, forget about it on the tarmac during a rain delay, etc. North American airlines will allow you one carry on suitcase and one “personal bag” which usually means a purse or laptop. This is easily enough for a week of travel, and can be extended indefinitely with laundry service. Invest in a good carry-on and bring it with you.<br /> <br /> Put everything you need during the flight in your laptop bag, in case you have to gate-check your carry-on suitcase (common on short flights with smaller planes).<br /> <br /> == Choose the Right Luggage ==<br /> Checked luggage will inevitably be destroyed over time, regardless of quality. If you stick to carry on, though, good luggage will last forever; be willing to pay once for something that gets it right. Your happiness while traveling is worth it.<br /> <br /> His bias for non-rolling luggage notwithstanding, [http://www.onebag.com/bags.html this is the single best guide out there] for evaluating luggage. The highlights:<br /> <br /> * Lighter is better<br /> * Curvy designs rob you of packing volume, prefer right angles<br /> * Chain zippers are stronger than coil zippers (look for YKK as the brand of zipper)<br /> * Pocket design and positioning matters<br /> * So do tie-downs<br /> <br /> In truth, the best way to maximize quality while minimizing weight is to let go of the dependence on rolling bags. Soft-sided, non-wheeled bags are exceptionally light and versatile. [http://www.tombihn.com Tom Bihn] and [http://www.redoxx.com/ Red Oxx] are your best plays. Tom Bihn’s Aeronaut is is a full-sized carry-on that converts to a backpack for long walks across cobblestones/sprints to catch a connection/etc. The Red Oxx Air Boss was designed by the same guy who wrote the luggage-choosing guide above.<br /> <br /> If you're not ready to let go of wheeled bags, any manufacturer with a lifetime warranty is probably worth considering. These include:<br /> <br /> * [http://www.briggs-riley.com/ Briggs &amp; Riley]<br /> * [http://www.travelpro.com Travelpro] (&quot;the best&quot; carry-on according to [http://thewirecutter.com/reviews/best-carry-on-luggage/ The Wirecutter])<br /> * Certain models of [http://shop.eaglecreek.com/lightweight-carry-on/l/111 Eagle Creek] (not all models have a lifetime warranty)<br /> <br /> Pay attention to the bag’s extensible arm: is it well constructed? What does it do to your interior space? 2 segments of extension or 3? Moving parts make everything more fragile -- if you are choosing moving parts in your luggage, they need to be brilliant.<br /> <br /> == Buy It There (BIT) ==<br /> <br /> Don’t try to anticipate every contingency and pack for it. You will bog yourself down with unnecessary cruft. Pack for what you ''know'' you’ll need, or at most what you reasonably expect to need the majority of the time. You can find contact solution, toothpaste, aspirin, and dental floss at almost any convenience store. For the rest, shove an extra $50 into a pocket somewhere and buy whatever you need there, if it comes up. <br /> <br /> (Good news: It comes up less often than you’d think.)<br /> <br /> BIT exceptions: <br /> There are some things you don't want to source while traveling - if you only use one specific brand of shampoo, conditioner, etc, transfer it to a small, travel-friendly bottle. Depending on where you're traveling BIT can be tough if you don't speak the language and are looking for something very specific (like Cipro in India or a flat iron in China). Goes without saying, but BIT does *not* apply to medications (remember that what requires a prescription varies by country, but you can apply it if you know that something can be bought without a prescription at your destination).<br /> <br /> === Corollary: Wash It There ===<br /> If you’re gone for longer than a carry-on can reasonably contain (which is longer than you think), don’t fail over to multiple suitcases; just get things laundered partway through. Your hotel will offer laundry service, though it will be overpriced. Most of the time you’ll find a wash and fold place within walking distance or a service that does pick up and next day drop off.<br /> <br /> Also keep in mind that at most Mozilla or other geek events, you will probably acquire at least one or two t-shirts. You can bring one or two fewer shirts; if this guideline fails, wash one of the ones you brought.<br /> <br /> If you bring quick-drying underwear and socks, you can wash them in the sink or bathtub and dry them overnight on the towel rack (except in humid climates). You can skip bringing detergent by using the hotel's shampoo (as long as you don't mind your underwear smelling like &quot;ginger lemongrass&quot; or whatever); shampoo is just mild detergent. Check the plumbing before you fill the sink; some hotels don't install the lever for raising the plug. Before hanging items to dry, roll them in a towel and squeeze out excess moisture.<br /> <br /> == Counterpoint: The case for checking a suitcase ==<br /> A few heavy-traveling Mozillians are in the &quot;checked bag&quot; camp. Add your reasons for using this strategy here:<br /> * Problems with checked luggage are actually quite rare.<br /> * You don't have to schlep a roll-aboard through the airport with you, including squeezing it into tiny toilet stalls.<br /> * You can pack a few extra things that help you be more comfortable on an extended trip.<br /> * At least one airline (American) gives early boarding privileges (after Elite and Priority but before Zone 1) to passengers with no overhead baggage.<br /> * You aren't limited to 100ml bottles of liquid/gel/cream, and can bring home ''properly packed'' wine, booze, perfume, etc. (Wrap the bottle in at least two plastic bags and nestle it in the groove left by the extending handle, surrounded tightly by clothes.)<br /> * Having airline status often helps your bag appear on the belt faster. Also, if the final segment of your trip is an international arrival in the United States, you're unlikely to have to wait long for your bag, since all baggage goes to the same belt, so it gets there quickly.<br /> * TIP: Get a suitcase with four wheels. Baggage handlers can slide it across the floor of the cargo hold instead of tossing it, subjecting the suitcase and its contents to much less abuse. Anything that protrudes, like carry straps or zipper pulls, can get snagged and chewed up in baggage-handling equipment; go for streamlined.<br /> * TIP: Ask for your checked luggage to be marked &quot;Fragile&quot;. It will be loaded on top of other bags, and usually be unloaded first.<br /> * TIP: If you check luggage, don't let your eyes off the bag until there's a tag on it, and if you can, check that the tag is correct (with your name and correct destination airport on it). One of the common reasons for lost/delayed luggage is getting the wrong tag on it right at the check-in desk.<br /> * TIP: Things to make sure are '''not''' in your checked bag: everything you need to get through customs and immigration and get to your final destination. Any electronics that might be stolen. Lithium-ion batteries (prohibited).<br /> <br /> Some airlines (particularly non-North American or discount airlines) have much lower limits for what you're allowed to carry on, so you'll have to check luggage anyway.<br /> <br /> Some airlines (e.g., Air France, KLM) will even want to weigh your carry-on bag (often although not reliably), and want it to be a weight that's lower than what it is with your laptop in it (e.g., 6kg, 8kg). Remember that your laptop often counts as a separate personal item and you can take it out of the bag before weighing.<br /> <br /> ==Packing Techniques and Tools==<br /> Your strategy for how to put your stuff in your suitcase is very much a matter of personal preference, along with the type of travel you're doing (destination vs. touring) and the type of clothes you bring. Here are some ideas that may be helpful.<br /> <br /> * The [http://www.onebag.com/pack.html bundle method] is great for avoiding wrinkles, but it tends to require that you unbundle ''everything'' to get out any single thing.<br /> * It's extremely helpful to have some kind of containers to organize your stuff. Purpose-made packing &quot;cubes&quot; are great, but are absurdly expensive. You can get by with zip-top plastic bags if you don't travel often, or while you're waiting to find ready-made cubes on sale. <br /> * If you buy only one packing accessory, consider getting a [http://www.amazon.com/Eagle-Creek-Travel-Pack-It-Folder/dp/B002YIRC3O/ packing folder], which helps you fold larger items (shirts, pants, skirts) to a uniform footprint, and then encloses them like an envelope.<br /> * Compression bags, which let you squeeze all the air out of your clothes, are good only for clothes that don't easily wrinkle. However, a compression bag can be great as a laundry bag to minimize the volume of dirty clothes on your way home. Either way, have a cloth or plastic bag you can use to keep used laundry separate. <br /> <br /> = Airport Hacking =<br /> '''Quick Tips'''<br /> * ABC: Always Be Charging. Wherever you come to rest, be charging. Maybe your flight has power plugs, that's swell, but maybe they stop working, or your seatmate gets to it first, or you need it to charge your phone. If you're at rest for more than 10 minutes, find a plug. If you bring a power strip so others can plug in, too, you can make friends anywhere :-)<br /> * Watch where uniformed crew members go. They know the best eateries in any given airport, and even where to stand on the tram platform in order to get off quickly at the other end.<br /> * The internet knows about delays before your gate agents do. Bookmark [http://flightaware.com/live/ flightaware] right now, and use it from your phone at the airport to keep tabs. Caveat: Flightaware may show your flight as delayed because the inbound plane you're getting on is delayed; if the airline substitutes another aircraft, your flight could be on time or only a little delayed.<br /> * If you do see signs of a significant delay, particularly at night when it's likely you'll be put off until morning, act swiftly before the lines form. Talk to gate agents about rebooking onto other flights and if the line there is long, be on the phone with your airline as well. First to rebook means first to call hotels and taxis and all the rest. Being last to rebook means sleeping in the airport. If you have elite status, call the customer service number for elite members, not the general customer service number.<br /> * When you get off the plane, the restroom closest to your gate will be crowded with other people from your flight. Keep going to the next one further away.<br /> * No one wants to sleep in an airport, but flight delays or cancellations, or just poor planning, may require it. There is actually a whole website devoted to [http://www.sleepinginairports.net/tips.htm sleeping in airports].<br /> <br /> <br /> == Being prepared for security ==<br /> * Veteran move: if you have a digital boarding pass, set a screenshot of that boarding pass as the background of your lock screen, so you can see the QR code without unlocking the phone.<br /> * Bring identification. [http://www.tsa.gov/traveler-information/acceptable-ids Here's a list of acceptable IDs] in the US. If you forget your ID, all is not lost. It's possible, with some extra hassle, to travel within the US even if you don't have your identification. [http://blog.tsa.gov/2013/04/tsa-travel-tips-tuesday-can-you-fly.html Here's what the TSA says to do if you don't have ID.]<br /> * Have photocopies - paper copies - of your passport and one other piece of ID (and where necessary, vaccination status or test results.)<br /> * Avoid getting into a screening line behind people who look like they don't travel often (families with kids, retirement-age folks, large groups).<br /> * Wear slip-on shoes and socks. Do not go barefoot in airports (And, for the love of God, Do Not Sit Or Lie Down On The Floors. Airport floors are disgusting, you have no idea.)<br /> * Consider not wearing a belt, or wear one with no metal, so you don't have to take it off.<br /> * Avoid clothes with extra pockets, like cargo pants. They can be flagged by the body scanner, and cause you to get a pat-down. Same for &quot;travel&quot; clothes with hidden pockets; these can be handy while touring, but not while flying. Even a hoodie can win you a pat-down for the hood and kangaroo pocket. <br /> * On the other hand, a jacket with lots of pockets is like an extra carry-on; you have to remove it for security anyway, and you can keep your in-flight necessities (gadgets, etc.) close to hand during your flight.<br /> * Know the drill with liquids, gels, and creams: containers at most 100ml/3oz, in a clear zip-top bag, 1 liter/1 quart size. Have this in an external pocket of your carry-on, ready to pull out and put in a bin. (If you travel often, you might want to get a sturdier bag than the grocery store kind. It must still be clear and zip-top.)<br /> ** Don't pack little bottles of booze. Yes, it's under the limit, yes you're technically allowed to carry it through security. Don't.<br /> * Avoid large metal jewelry.<br /> * Take everything, but especially metal (keys, coins, etc.), out of your pockets.<br /> * '''Leave your pocket knives and multitools at home.'''<br /> * If you're wearing an activity monitor, such as a FitBit, take it off for screening.<br /> * You should hang onto your ID and boarding pass as you go through the line, but you can't carry them through screening; put them in your bin.<br /> * Put the bin with your shoes, jacket, and liquids onto the conveyor belt first. You can be getting dressed while the rest of your stuff comes through.<br /> * Take your laptop out of your bag and put it in a separate bin. You can usually leave it in a sleeve, as long as there's nothing else in the sleeve. <br /> * Consider getting a checkpoint-friendly laptop bag, with a laptop-only section that folds out without taking out the computer. The less you handle your laptop, the less likely you are to drop it. (US TSA allows you leave the computer in this type of bag; other countries often do not.)<br /> * Don't start going through the screening machine or metal detectors before you can see your stuff moving down the conveyor belt.<br /> <br /> == US Trusted Traveler Programs ==<br /> If you frequently cross US borders, you can save time and hassle in the long run by enrolling in one of the programs that provide expedited entry for pre-approved travelers. Enrolling involves an application fee and form, and an in-person interview at an entry point, so there is a start-up cost in time and money. Which program you should enroll in depends on the type of crossing you do most; you can enroll in more than one. <br /> <br /> * When entering the US, if you're not in a &quot;trusted traveler&quot; program, try to get into the immigration queue that is ''next to'' the Global Entry lane. If no one is in the Global Entry lane, the officer there will often take people from the nearby queue, making it move faster. Do likewise for NEXUS when entering Canada.<br /> * Wear Firefox gear when going through immigration, anywhere. It creates goodwill and starts pleasant conversations.<br /> <br /> ===Automated Passport Control===<br /> Automated Passport Control kiosks are available to citizens of the US, Canada, and [http://www.cbp.gov/travel/international-visitors/frequently-asked-questions-about-visa-waiver-program-vwp-and-electronic-system-travel Visa Waiver Program] countries, for entry into the US, in an expanding number of North American cities. Unlike Global Entry or Nexus, these kiosks require no pre-registration. You swipe your passport, let the kiosk take a photo, answer some questions, and then get a receipt that you show to a Customs and Border Patrol officer. The kiosk replaces filling out a customs card by hand.<br /> <br /> See the [http://www.cbp.gov/travel/us-citizens/Automated%20Passport%20Control Automated Passport Control] webpage for a list of cities with APC kiosks.<br /> <br /> === Global Entry ===<br /> [http://globalentry.gov/about.html Global Entry] provides expedited screening for entry ''into'' the US at certain airports. Once in the program, you can go to an automated kiosk instead of an immigration agent (skipping the enormous lines that result from multiple international flights arriving at about the same time), and you can answer the customs questions at the kiosk instead of filling out a paper form. Unless there is an issue with your kiosk interaction (such as it couldn't read your fingerprints), you don't need to talk to a CBP agent. Global Entry is open to U.S. citizens, lawful permanent residents of the U.S., Dutch citizens, South Korean citizens and Mexican nationals.<br /> <br /> === NEXUS ===<br /> [http://www.globalentry.gov/nexus.html NEXUS] provides expedited screening for crossing the US-Canada border in both directions. It can be used at land and sea entry points as well as at airports. You can use the NEXUS-only lanes at land crossings only if every person in the vehicle (including children) has a NEXUS card. Using NEXUS at an airport requires scanning your irises. If you wear contact lenses, you must remove them for the initial iris scan that is taken after your enrollment interview.<br /> <br /> === Other US programs ===<br /> * [http://www.globalentry.gov/netherlands.html FLUX] expedites passage between the US and '''the Netherlands''', and is open to US and Dutch citizens.<br /> * Global Entry members can receive expedited entry into '''[http://www.globalentry.gov/newzealand.html New Zealand]'''.<br /> * [http://www.globalentry.gov/sentri.html SENTRI] provides expedited entry into the US from '''Mexico''' at specific land crossings.<br /> * [http://www.globalentry.gov/korea.html Smart Entry Service] provides expedited entry into the Republic of '''Korea'''. It is open to US and Korean citizens.<br /> * [http://www.globalentry.gov/smartgate.html SmartGate] provides streamlined entry into '''Australia''' for US Global Entry members. Visa requirements still apply.<br /> * [http://www.globalentry.gov/tsa.html TSA PreCheck] enables US Global Entry and Canadian NEXUS members to use designated TSA airport screening lanes, without removing liquids, laptops, shoes, jackets, or belts. You must provide your membership number when booking flights with participating airlines. TSA is expanding the PreCheck program to include more people, including US military members and those invited by their airline's frequent flyer program. You must still apply, pay a fee, and go through an interview. See the [http://www.tsa.gov/tsa-precheck TSA PreCheck] website for details.<br /> <br /> == Other countries' traveler programs ==<br /> * The UK's [https://www.gov.uk/registered-traveller Registered Traveller service] enables certain citizens of Australia, Canada, Japan, New Zealand and the USA to get faster entry to the UK, without filling out a landing card. <br /> <br /> <br /> == Country-specific notes ==<br /> <br /> '''Note: Much of the per-country information is pre-covid, and needs to be verified or updated.'''<br /> <br /> === USA ===<br /> * visitors under the [https://travel.state.gov/content/travel/en/us-visas/tourism-visit/visa-waiver-program.html visa waiver program] (those who don't need a visa) must apply online for an [http://www.cbp.gov/travel/international-visitors/esta ESTA].<br /> <br /> === Canada ===<br /> * visitors who do not need a visa, are entering Canada by air, and are not US citizens or Canadian citizens or Canadian permanent residents, must apply online for an [http://www.cic.gc.ca/english/visit/eta.asp eTA].<br /> <br /> === Schengen Area (Europe) ===<br /> * The [http://en.wikipedia.org/wiki/Schengen_Area Schengen Area] is an immigration-barrier-free zone covering most of the European Union and some additional non-EU countries, but not the UK or Ireland.<br /> * If you need a visa to visit the Schengen Area, it is easier to get such a visa if your point of arrival in the Schengen Area is the same country as your destination. (For example, if you're traveling to Spain, it is easier to arrive in Madrid after connecting in the UK or US than connecting via Amsterdam, since in the latter case getting the visa requires dealing with both the Spanish and Dutch authorities.)<br /> * If your nationality requires a visa to visit the Schengen Area and your trip does not terminate in Schengen, avoid making more than one connection in Schengen; in such a case you must get a Schengen visa, even though that's not your destination. Schengen immigration authorities look at your ''next'' point of travel (not your final one) to decide whether you need a visa; if it is Schengen, they will ask for one.<br /> <br /> === New Zealand ===<br /> * Make sure to declare any shoes in your checked luggage. The authorities just want to look at them and maybe clean the dirt off for you, but they'll be upset if you don't declare them.<br /> * Don't even think about [http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&amp;objectid=11404025 bringing fresh fruit] into New Zealand or you will get an instant fine.<br /> <br /> === Australia ===<br /> * Visitors who can can enter without a visa must apply online for an [https://www.eta.immi.gov.au/ ETA].<br /> <br /> = Flying =<br /> <br /> '''Quick Tips'''<br /> * Hydrate, hydrate, hydrate. Air in an airplane at altitude is incredibly dry and dries you out. Drink water whenever you can. Bring an empty water bottle (even better: collapsible) and fill it from a water fountain inside security. (Some airports, like SFO, have water bottle filling spots that make this a little easier.) Don't drink the water that comes out of the water tanks onboard an airplane, including coffee and tea; you don't want to know how disgusting those tanks are. If you get water in the beverage service, ask for fizzy water (club soda) to ensure it came out of a bottle or can. If you need to brush your teeth in-flight, use water from your water bottle, not the tap in the toilet.<br /> * Request an alternate meal (kosher, indian, vegan, whatever) - they tend to be tastier, and often come first. (However, the downside to the meal coming first is that the tray is going to be in your way substantially longer.)<br /> * If you're in an aisle seat, you’ll find that the aisle-side armrest won’t lift. This is annoying, because it is much easier to deplane with that thing out of the way. Reach back to where the armrest joins the back of the chair -- there may be a release latch or button. (This works on some Boeing 777s; most smaller craft do not have this feature. See [http://brokensecrets.com/2011/01/17/raising-the-airplane-aisle-armrest/ this article] for a photo.)<br /> * Always wear shoes before going to the airplane lavatories; never go barefoot or wearing socks only. <br /> <br /> == Headphones ==<br /> Enjoying music or movies during travel is much better with headphones designed for travel use. You need to consider three types: <br /> * active noise-cancelling headphones<br /> * those without noise-cancellation<br /> * in-ear monitors. <br /> Generally speaking, on airplanes, active noise-cancellation will be better on the plane but worse when you're not on the plane (in the hotel room, for instance.) A quality headphone without noise cancellation will almost always sound better when not on an airplane. In-ear monitors allow for excellent sound quality and also allow one to rest your head on a pillow without the headphone pushing against one's ear, but some are uncomfortable with putting anything in one's ear. In-ear monitors are also much more compact. For those who want the sound quality of in-ear monitors and the compactness, but find that fit is a problem, consider Comply foam tip replacements which can be selected to fit your ear size.<br /> <br /> * For active noise cancellation headphones, the Bose Quiet Comfort 15 is the most popular model sold and for good reason. However if you want the headphone to be good when the noise-cancellation is turned off, you may want to consider the [http://www.psbspeakers.com/products/headphones/M4U-2-Headphones Psb m4u 2], which is more expensive but also more versatile.<br /> * For headphones without active noise cancellation, consider rugged models that have reputations burnished by decades of use by audio professionals such as the Sennheiser HD-25 1-ii. Another popular option is the V-Moda M-80 which has similar sound quality, has a good reputation for build quality, and also comes with a nice travel case.<br /> * For in ear monitors, there are too many to list but one line that is very popular is the Shure SE series which have models from $99 on up. These are very rugged models which allow for replaceable cables, replaceable tips and have very good sound quality.<br /> Additional resources for headphones include [http://www.innerfidelity.com/content/innerfidelitys-wall-fame Innerfidelity's Wall of Fame] and Head-fi.org's [http://www.head-fi.org/t/618255/check-out-the-head-fi-summer-2012-buying-guide 2012 Summer Buying Guide].<br /> <br /> == Make friends with TSA and your flight crew ==<br /> <br /> Airplanes are a sea of grumpy, tired, unhappy people. A little friendliness goes a long way -- especially if you're regularly flying the same route with the same flight crew.<br /> <br /> == Seat etiquette ==<br /> The following tips are about showing consideration to your fellow passengers, who unfortunately may not even notice it. But violating these norms is likely to cause annoyance. You don't want to be &quot;that guy&quot;, do you?<br /> <br /> * The person in the middle seats gets to use both armrests. The people in the window and aisle seats get a little extra space, so yielding one armrest each is the least they can do. In any case, try to keep your elbows in your own space.<br /> * Consider the person behind you before reclining your seat into their space, especially if they are trying to eat or use a laptop. Avoid reclining abruptly (though it's not always possible to control this). Raise your seat back during meals.<br /> * If you need to leave your seat during the flight, try to avoid hoisting yourself up by yanking on the seat in front of you. This may be difficult to avoid if the seat is reclined (see above).<br /> * If you have an individual touchscreen in the seat back in front of you, jabbing it forcefully doesn't make the touchscreen work any better. If it's really not responding to touch input, try controlling it from the armrest controls.<br /> <br /> * [http://www.independenttraveler.com/travel-tips/travelers-ed/the-etiquette-of-seat-backs-and-elbow-room The Independent Traveler: The etiquette of seat backs and elbow room]<br /> <br /> <br /> <br /> Still to write:<br /> * how to sleep (Needs to be written by someone who is actually able to sleep on planes)<br /> ** [http://gizmodo.com/how-to-get-the-best-sleep-of-your-life-on-an-airplane-1598708044 Gizmodo: How to get the best sleep of your life on an airplane]<br /> ** [http://www.independenttraveler.com/travel-tips/travelers-ed/sleeping-on-planes Independent Traveler: Sleeping on Planes]<br /> * move on long flights<br /> <br /> = Tips for specific airports =<br /> As a general rule of thumb, in any airport, the terminal or concourse that serves international flights has nicer shops and restaurants than the areas for domestic flights. So, if you're traveling domestically, have time to kill, and can get into the international terminal without going through passport control, you might want to go hang out there.<br /> <br /> == AMS Amsterdam ==<br /> * in the international section (only?), there are nice quiet places to sit on the upper level outside the lounges (even if you don't have lounge access)<br /> * if you want to take the train to/from the airport, hoard coins (€4 to Amsterdam-Centraal, less to Amsterdam-Lelylaan or Amsterdam Zuid), since the ticket machines don't take bills or American credit cards. (The city trams/buses in Amsterdam do take bills, but this is a national train.)<br /> * note that the entirety of the outside-[https://en.wikipedia.org/wiki/Schengen_Area Schengen]-immigration part of the airport does security at the gate, per flight<br /> <br /> == AUS Austin, Texas ==<br /> The food available in the airport is actually pretty good, since most of the food concessions offer menus from local restaurants. Get to the airport early enough to have a last plate of barbecue or breakfast tacos. <br /> <br /> Another reason to get to the airport early is the &quot;Knot Anymore&quot; chair massages available near gates 13 and 7. Austin is awash in good massage therapists, so the ones working in the airport are far better than most airport massage services.<br /> <br /> == CDG Paris / Charles de Gaulle ==<br /> * CDG airport has multiple airport hotels on premises (on the around-the-airport CDGVal shuttle train); typically at least one of the fancy ones has good prices because it isn't hosting a conference that week, but there's also an Ibis. <br /> * CDG airport has four disconnected parts:<br /> ** Terminal 1 (the cylinder with pods) (United is here)<br /> ** Terminal 3 (the discount airlines)<br /> ** Terminal 2A-2B-2C-2D-2E-2F (the bulk of the airport) (Air France is here)<br /> *** note that there are two satellite piers attached by train (outside immigration but not inside security) attached to Terminal 2E (the attached part of terminal 2E is called K, the satellites are called L and M)<br /> ** Terminal 2G<br /> * transport<br /> ** there's a train (CDGVal) connecting Terminal 1, Terminal 3 / Roissypole (where most but not all of the hotels are), and Terminal 2 (the station is between 2C/2D/2E/2F)<br /> ** high speed trains stop only at the terminal 2 station (between 2C/2D/2E/2F)<br /> ** RER trains (Paris's suburban rail network) stop at Terminal 2 (same station, again) and at &quot;Terminal 1&quot; (which is actually the Terminal 3 / Roissypole station for CDGVal)<br /> ** Terminal 2G is reachable only by shuttle (I think, never done it)<br /> ** If you want to take the RER to/from the airport, hoard coins in advance to pay the €9.50, since foreign cards don't work, and the machines don't take bills. <br /> ** The RoissyBus is only €10.50 and runs nonstop between CDG and the Paris Opera, only a few blocks from the Mozilla Paris office. Look for signs for &quot;RoissyBus&quot; or &quot;Paris by bus&quot; within each terminal to find the bus stop.<br /> <br /> == JFK New York ==<br /> * The wifi password of the British Airways' lounge is &quot;London&quot; (according to Reddit). You can usually get in range of the wifi hotspot without going inside the lounge.<br /> <br /> == LHR London Heathrow ==<br /> * Terminal 5 (international) <br /> ** If you need to take the train to concourse B or C, go to the far end of the platform. You'll bypass the crowds at the near end, and be closest to the escalators when you exit.<br /> ** If you need to backtrack from concourses B or C to concourse A, ''don't'' take the train; you'll be routed through security again. There's a pedestrian tunnel that parallels the train, and comes out next to elevators that let out inside security in concourse A. The tunnel doors are marked &quot;Emergency Exit&quot;, but do not have alarms, and in fact open automatically, to accommodate mobility-assistance carts. Stay to the left (remember: you're in England) to keep from being run over by them.<br /> ** If you're going to the Mozilla London office, [[London#From_Heathrow_by_traincheck the directions]] and don't bother with Heathrow Express.<br /> <br /> == NCE Nice, France ==<br /> * if you have a really early flight, there are multiple decent airport hotels nearby. But do '''not''', under any circumstances, stay at the Etap.<br /> * if you want to avoid a really early flight, consider as an alternative doing an overnight layover at CDG, which has multiple airport hotels walking distance from Terminal 1 (but poorly signed). Make sure your layover is long enough, though.<br /> * if you're traveling to west of the airport (e.g., towards W3C's European offices near Antibes) and want to take public transit, it's possible to walk to the Nice - St. Augustin train station ('''not''' the main Nice - Ville train station) in about 15-20 minutes, but there's basically no signage. But definitely look at the train schedules before trying this. Buses from the bus station (gare routière) at the airport may be better.<br /> * there's a free shuttle between Terminals 1 and 2. Don't try walking between terminals.<br /> * There are bus stations at both terminals, but some bus routes stop at both terminal and some stop only at Terminal 1. You need to buy a ticket at the station before boarding.<br /> * the airport does not have water fountains behind security. But restaurants will probably be willing to fill up a water bottle for you, especially if you've bought something there.<br /> <br /> == NRT Tokyo/Narita ==<br /> * If you can do so just as easily, fly to Haneda Airport (HND) instead, which is closer to the city.<br /> * Don't even ''think'' of taking a taxi. It will take hours, and cost multiple hundreds of US dollars.<br /> * Two companies (JR and Keisei) run trains to Tokyo, and both have express and local services at different prices. Choices depend on where in Tokyo you're going. Google Maps might be helpful, or just figure it out when you get there.<br /> * Consider taking a [http://www.limousinebus.co.jp/en/ Limousine Bus] to somewhere close to your destination, and take a taxi from there.<br /> <br /> == ORD Chicago O'Hare ==<br /> * In Terminal 3, at the beginning of concourse G, there is a &quot;Chicago Urban Garden&quot; on the second floor, with aeroponic herbs and vegetables. This is a nice quiet place to wait if you don't have access to an airline lounge. <br /> <br /> == SFO San Francisco ==<br /> * if you're through security and looking for food, realize that some pairs of terminals are connected behind security. In particular, there are four separated behind-security zones at SFO right now: International-G/Terminal3-F/Terminal3-E, Terminal2-D/Terminal1-C, Terminal1-B, and International-A. In particular, if you're in C, you can probably find better food and better places to sit in D, and at some hours there's not much open in G, but you can head over to F.<br /> * The recently renovated terminal areas are the International Terminal (2000), Terminal 2 (gates D) (2011), and Terminal 3 gates E only (2014)<br /> * If you're taking BART to the airport, you can take the airtrain or walk to get around the airport from the airport BART station. You should definitely walk to International (G or A, which share a large central checkin hall but have separate gate areas), maybe walk to Terminal 3 (at least if you're ready to go straight to the security line), and you can walk to the other terminal if you like.<br /> <br /> == SJC San Jose CA ==<br /> <br /> == TPE Taipei Taoyuan ==<br /> * if you're coming from within Asia to Taipei, fly to Songshan Airport (TSA) instead<br /> * if you have Star Alliance gold, there are multiple EVA lounges to choose from. The main one, with all the good food, is on the same side of the open (to the floor below) space as the tropical bar one, with entrance across the hallway from it (not across the open space)<br /> <br /> == YVR Vancouver ==<br /> * As airports go this one is a pretty beautiful. If you're departing to the US from Vancouver note that you will go through US customs and immigration at YVR, so arrive 2 hours before your scheduled departure time. <br /> <br /> = Trains =<br /> <br /> * for booking long-distance trains within Europe, https://www.trainline.eu/ is often better than the national train company sites, because they tend to be clearer about both giving you the better options for ticket retrieval and explaining those options to you<br /> <br /> = Hotels =<br /> <br /> '''Quick Tips'''<br /> * Ask for upgrades. I know, this sounds trite, but it works. If you don’t know how that works, just remember, when checking in, to ask “Is there a better room available?” If they say yes, you’re set. If they say no, that’s fine. If they say “yes, for a price” then you can consider that price and make the call. We’ve gotten $2000/night rooms on a $180/night booking just by asking. This tends to work well when the hotel has a lot of open inventory (particularly effective in LAS, less effective near Moscone during a conference).<br /> * When checking in, adjust your interactions with the clerk based on whether they smile when you approach. Chit-chat with a smiling clerk, but not with an unsmiling clerk. The latter is just as much a form of establishing rapport as chit-chat, because you're not wasting the time of a transaction-oriented person. And establishing rapport can make the marginal difference in whether they decide to give you an upgrade.<br /> * Expensive hotels tend to have sensors in the minibars, but most of the rest still just have housekeeping track what’s missing each visit and bill you. If you do get the munchies, just head out to a convenience store the next day before housekeeping and buy matching replacements at the saner price. <br /> * You can avoid the minibar entirely by grabbing a granola bar or two from a Mozilla kitchen before departing. They are bound to be healthier than anything you find in the minibar late night. <br /> * Every hotel has a bucket of standard toiletry items (toothbrush, razor, &amp;c). You should have a toiletry bag stocked and ready to go (see above) but if you find yourself missing something, just call the front desk.<br /> * Likewise, every hotel has a bucket of left-behind chargers/power cables.<br /> * Set your climate controls when you first get into the room. Forgetting until you come back after dinner ready for sleep and finding the room is hot and stale is no fun.<br /> * Some hotels won’t let the climate controls work unless your room keycard is stuck into a switch by the door. This isn’t a magstripe reader, it’s just a physical switch - use a business card or a folded up piece of paper (or your library card) and have your room the way you want it.<br /> * If the drapes that don't quite meet, and therefore let in unwanted sunlight or street light, use one or two big binder clips to keep the drapes closed.<br /> * You can usually get a later check-out time just by asking. This doesn't work indefinitely, but they can't clean every room at once, so asking for 1pm instead of 11am just means they move your room to the bottom of the list for cleaning that day.<br /> * Repack for departure before you go to sleep, except for the clothes and toiletries you'll need in the morning. That way, if you oversleep for whatever reason, you can throw on your clothes, grab those last items, and go without wasting any more time.<br /> * To avoid leaving things behind:<br /> ** Bring your original packing checklist, and use it to repack.<br /> ** Pull all the linens off the bed and throw all used towels into the shower, so you're sure nothing's hidden, and check every wall socket for chargers.<br /> ** If you unpack into drawers, check every drawer before you leave.<br /> <br /> == Pick a hotel, get into the frequent guest program ==<br /> <br /> Same deal as airlines. At the least, it eventually adds up to free stays, but getting to status means room upgrades, easier check-in, more flexibility on check-in/check-out times, and extra points for each stay. Some hotel loyalty points can also be transferred to airline loyalty programs.<br /> <br /> It can be harder to consistently stay with the same hotel group than to consistently fly the same airline (they're sold out or not convenient, the conference hotel is elsewhere, etc.). However, it's good to join the loyalty program for any hotel you stay at, before you make your reservation. You may get a better rate or a better room. Hotel staff seem to give an extra measure of courtesy and consideration when you're in the loyalty program. (When booking by phone, I've had a &quot;sold out&quot; group rate suddenly become available when I gave my membership number.) If you haven't joined by the time you check in, ask the clerk to sign you up; they'll get credit for signing you up, and will be even more inclined to treat you nicely.<br /> <br /> Linked below are the programs associated with the hotels that are typically used for visiting Mozilla in Mountain View.<br /> <br /> {|<br /> |-<br /> |Holiday Inn Express<br /> |[http://www.priorityclub.com/ Priority Club]<br /> |<br /> |-<br /> |Avante/Wild Palms<br /> |[http://www.joyoflifeclub.com/ Joy of Life Club]<br /> |(Does not give points for stays that are paid through corporate billing.)<br /> |}<br /> <br /> == Choose Your Room ==<br /> <br /> It's a good practice to indicate that you have any preference on your room at all. Put this into your loyalty program profile and your travel agency profile (Egencia, for Mozilla employees), so it's transmitted with your reservation. If you have no preference, they will put you in the room for people who do not indicate a preference. You know, the one in the basement. With the leaky faucet and carpet from 1973. <br /> <br /> If you have a choice between one or two beds, choose two, even though you'll only use one for sleeping. The other one makes a great surface for spreading out your stuff. Often, hotel beds are on casters, so you can shove the extra bed against the wall, to prevent stuff falling between the bed and the wall.<br /> <br /> Generally, you'll do well to ask for a high floor and a room away from the elevator. Many hotels do renovations by floor starting from the top and working their way down. So high floors have a better chance of being recently renovated. They are also further away from street noise or the bar in the atrium. A room away from the elevator means less foot traffic and not waking up at 5am to repeated &quot;ding!&quot; of the elevator door opening. For motels, you want upstairs (less foot traffic) and outside (away from the courtyard with the pool).<br /> <br /> If the room is awful, don't be afraid to walk back downstairs and see if they have anything a bit more updated. If the whole hotel is awful, check your luggage at the desk and walk in a square block radius around the hotel to see if there's something less frightening. <br /> <br /> Never pick a hotel based on a picture of the lobby. Lobbies are always the first thing to get renovated.<br /> <br /> == Tipping Hotel Staff ==<br /> If you believe in tipping (which varies across cultures):<br /> * If you take a hotel shuttle from the airport, be sure to tip the shuttle driver. Don't just hand it to them and walk away; look them in the eye and express genuine appreciation for their service while you give them the tip. This is your first contact with the hotel staff, and if you make a good impression, word will spread to the other staff, and you'll get great service throughout your stay. This driver may also be the person who gets you to your outbound flight, through heavy traffic, just in the nick of time.<br /> * Similarly, leave a tip for housekeeping after the first night. This paves the way for good service when you make special requests, such as extra towels or toiletries, or to come back later because you're still in the room. Leave the money on top of a note that says at least &quot;Thanks!&quot; so the housekeeper knows it's for them.<br /> <br /> = Money =<br /> <br /> * Exchange: Do not change money at the airport. The rates are higher there than anywhere else. If you have a local bureau de change, use that, or order currency online for pickup at the airport. If you can find a company that does that (Travelex in the UK, at least) the rates will be much better than those posted on the wall that they charge you when you are a captive customer. The best rates are likely to be had by using an ATM. <br /> * Debit: Using an ATM card can be an easy and inexpensive way to secure some local currency. Make sure your card will work abroad before you travel. Common ATM networks that are broadly available include Pulse and Plus. Consider getting a debit card with no foreign transaction fees (Charles Schwab offers one).<br /> * Stay organized: It's helpful to keep your currency separate from your home currency, particularly if you're going to cycle through multiple currencies during your trip (usd &gt; euro &gt; pounds). Don't underestimate the power of a ziploc baggie if you're American and unaccustomed to coinage-heavy currencies.<br /> <br /> == Credit cards ==<br /> The US has historically had a different system (magnetic strips) for credit card security from the rest of the world (which uses the chip-and-pin system). This can cause headaches for both Americans traveling abroad, and others traveling to the US, as the systems are incompatible. Most US stores now support chip-and-signature cards, but you might run into smaller ones that don't have chip-reading equipment (e.g., a food truck using Square). <br /> <br /> * A very few US banks offer true chip-and-pin cards, including Citibank and [https://www.andrewsfcu.org/credit_cards_and_loans/credit_cards/globetrek_rewards.html Andrews Federal Credit Union]. The latter also has no annual fee and no international transaction fees. See this extensive but not exhaustive [http://thepointsguy.com/2013/05/us-credit-cards-with-smart-chips/ list of US-based chip-and-pin cards]. <br /> * You can get a pre-paid, reloadable chip-and-pin card called [http://www.cashpassport.com/1/travelex/ &quot;Cash Passport&quot;] from Travelex. You can buy it and reload it online or at Travelex locations in the US. You can load it in multiple currencies: GBP, EUR, CAD, AUD and JPY. The security seems a bit crappy (you can't change the PIN, and their only security question is mother's maiden name), but since it's pre-paid, you can limit your financial exposure, and reload online as needed.<br /> <br /> Another issue for travelers is transaction fees when making purchases in currencies other than your home currency; these can range from 1% up to as much as 7%. US-based credit cards that don't charge international transaction fees include CapitalOne and Andrews FCU.<br /> <br /> More and more US retailers have card readers that accept chip-based cards, so the situation is improving for visitors to the US. However, they probably don't understand the PIN system, so you will still need to sign (either on the reader, or on paper).<br /> <br /> = Preparing to be less-online than normal =<br /> <br /> If your cellphone plan doesn't have reasonable data roaming, or if you might be in areas with poor cell coverage, you should be prepared to survive without your usual data connection. This might include things like:<br /> * downloading offline maps in advance. ([http://maps.me/ maps.me] for Android and iOS lets you download offline OpenStreetMap maps by country or part-of-country.)<br /> * knowing where you're going to need to be (hotels, meeting locations) before you leave<br /> <br /> = On Foreign Soil =<br /> <br /> * Data/Voice rates<br /> ** You can use Skype to call US 1-800 numbers toll free from anywhere in the world.<br /> ** Before you leave your home country, add $20-40 of SkypeOut credits to your account. While Skype to Skype calls are free, SkypeOut credits will let you call any number internationally for about $.02 per minute.<br /> ** International text messages are typically NOT covered under your mobile plan. For US cell plans, it's usually about $.50 per SMS. If you have a good international rate, think long and hard about when you use SMS and why. A conversation about when you landed and where to meet and what time to get there on SMS may be more than a 2 minute call that covers the same details.<br /> ** [http://readwrite.com/2014/06/17/5-secrets-avoiding-hefty-international-data-roaming-charges-fees 5 secrets to avoiding hefty international data roaming fees] <br /> * Finding wifi<br /> ** In airports, airlines' priority lounges often have no wifi password, and you can access their hotspots from outside the lounge. (See note above for JFK airport.)<br /> ** Starbucks, McDonalds, and Burger King are sadly ubiquitous, and often have free wifi.<br /> ** You can sometimes find the password for a business's wifi in the comments for that business on FourSquare.<br /> * Language barriers<br /> ** Grab some business cards or stationery with your hotel's address on them before you head out. You can hand one to a cabbie whose language you do not speak, to get yourself back to home base. <br /> <br /> Still to write/update:<br /> * Language barriers<br /> ** Add Line2 details...<br /> <br /> ==Coping with jet lag==<br /> * Do not go to sleep. Do not nap. Stay up as long as you possibly can. Eat meals at local times and get into bed when it's dark outside. It will hurt on day one but by day three, you'll be glad you did. <br /> * If you absolutely must sleep, do a 20 minute powernap and then get up, walk around, and do not fall back to sleep. (Powernapping pro tip: [https://www.vox.com/2014/8/28/6074177/coffee-naps-caffeine-science take a &quot;coffee nap&quot;]: quickly drink a cup of coffee, and ''then'' take a nap; the coffee will wake you up in a short while, and you'll be more alert than with a nap or a coffee alone.) <br /> * In a pinch, Benedryl (dipenhydramine) can help you reset your internal clock and it's substantially gentler on your system than the prescription sleep aids. (It's also good for nausea if you get motion sickness, and of course, allergic reactions.)<br /> * If you find yourself awake when you should be sleeping (by local time), avoid bright screens (computers, phones, e-readers), because they activate wakefulness in your brain. Try reading a paper book or magazine (radical, I know). If you must use a screen, set it to white text on a black background, to reduce the overall brightness; or get an app (such as [https://justgetflux.com/ f.lux] for Mac/iOS or [https://play.google.com/store/apps/details?id=com.urbandroid.lux Twilight] for Android) that reduces the amount of blue light emitted by your device at night.<br /> * If possible, follow the [http://www.wikihow.com/Prevent-Jet-Lag-with-a-Modified-Diet Anti-Jet Lag Diet]; this is easier to do at home than while traveling, but IME even an approximation helps. <br /> ** As an abbreviated version: eat as little as possible on your day of travel, avoiding caffeine and alcohol; eat a high-protein breakfast at breakfast time in your new time zone.<br /> ** Bring protein bars with you to ensure that you can get protein at the right time.<br /> <br /> = Transportation =<br /> <br /> '''Quick Tips'''<br /> * Talk to cabbies. Not only do they know their city, they are less likely to have kickbacks in place than the hotel concierge, more likely to give you good answers.<br /> * Learn the taxi rules. Las Vegas doesn’t let you hail cabs on the street (creates traffic problems). New York cabs have credit card swipes in the back seat, whereas DC cabs just started actually using their meters at all. San Francisco cabs won’t let you exit except curbside.<br /> <br /> Still to write:<br /> * public transit<br /> * hotel shuttles<br /> <br /> == Rental Cars ==<br /> <br /> === Enterprise Rent-a-Car ===<br /> <br /> Mozilla's preferred vendor<br /> <br /> === Hertz ===<br /> <br /> If for some reason you end up with Hertz (late evening arrivals mean Enterprise might be closed) you'll want to sign up for [[HertzBusinessAccountProgram|Hertz #1 Gold]] and use that. At most airports, you walk in, your name is on a board with a parking spot number, and the keys and contract are already in the car waiting for you. Really nice after a 5+ hour flight!<br /> <br /> = Eating =<br /> <br /> Eat like a local.<br /> <br /> Never ask the front desk at your hotel for a dinner recommendation. If possible, ask anyone else to weigh in. The bellhop, your taxi driver, the barista at Starbucks, Yelp, Chowhound, etc. The best recommendations come from people who are actually living and working in the area. (TripAdvisor tells you what people who ''don't'' live there think.) The concierge at the hotel will always orient toward broad, tourist-pacifying tastes. The food will be edible, but forgettable. They'll never tell you about the super tasty hole-in-the-wall joint three blocks away.<br /> <br /> = Staying healthy =<br /> * Wash hands frequently! <br /> * Carry and use hand-sanitizer wipes. (A bottle of hand-sanitizer gel takes up valuable room in your liquids bag.) Sanitize your hands in-flight before you eat or drink, and after washing your hands in the lavatory (on-board water, again). Also use them to wipe off [http://www.travelmath.com/feature/airline-hygiene-exposed/ tray tables, seatbelt buckles, and air vents], where germs lurk on airplanes.<br /> * Set the fan above your seat on the plane to low or medium, and position it to blow into your lap, just in front of your face. This will help knock airborne pathogens out of the air, so you'll be less likely to breathe them in. ([http://www.npr.org/blogs/goatsandsoda/2014/07/14/319194689/pathogens-on-a-plane-how-to-stay-healthy-in-flight?ft=1 (NPR) Pathogens on a plane: how to stay healthy in flight])<br /> * Keep your exercise routine as much as possible. Exercise burns calories, relieves stress, and helps reset your body clock, if you're in a different time zone.<br /> ** Pick a hotel that has a fitness center. If you must use a hotel that doesn't have one (or you need specific equipment, like a stationary bike) call and ask; they may have an arrangement with a nearby gym.<br /> ** If you're out of luck on the fitness center, bring an exercise DVD, and/or small lightweight equipment like a jump rope or tension bands. Or do a [http://well.blogs.nytimes.com/2013/05/09/the-scientific-7-minute-workout/ body-weight-only exercise routine].<br /> ** Bring quick-drying workout clothes. Rinse them in the shower, and dry them over the shower rod, so they're ready for tomorrow.<br /> ** Bring athletic shoes that double as casual street shoes, so you don't need to take up luggage space with extra shoes.<br /> ** See the Quartz [http://qz.com/287800/the-complete-guide-to-staying-in-shape-on-the-road/ Complete guide to staying in shape on the road].<br /> <br /> = Redux =<br /> <br /> '''Most people travel infrequently, and aren’t very skilled at it...'''<br /> * and there are a lot of people, so despite the infrequency of their travel, the Don’t Know path is very crowded<br /> * Businesses on the Don’t Know path have no loyalty to you (since infrequent travellers have no meaningful loyalty to them) so their main goal is to extract money from you immediately, even at the cost of the relationship<br /> * People on the Don’t Know path have to deal with the same Don’t Know problems every single day, which is exhausting and saps their empathy<br /> <br /> '''BUT - If you know what you’re doing...'''<br /> * You can shortcut around the Don’t Know path everywhere. Airports, Hotels, Restaurants<br /> * The businesses you deal with will view you as a regular, and want to keep you happy<br /> * The people you deal with will view you as a breath of fresh air, and feel understood, and be grateful and human in the ways that travel never is for others.<br /> <br /> = More advice =<br /> * [http://www.jonobacon.org/2016/08/10/the-bacon-travel-survival-guide/ Travel Survival Guide] by Jono Bacon<br /> * [http://christianheilmann.com/2014/02/16/how-i-save-money-when-traveling-for-work-san-franciscovalleyus/ How I save money when traveling for work] by Christian Heilmann<br /> <br /> These podcasts have some excellent advice on business travel:<br /> * [http://www.manager-tools.com/2009/07/airline-travel-basics-1-part-1 Airline Travel Basics, part 1]<br /> * [http://www.manager-tools.com/2009/08/airline-travel-basics-1-part-2 Airline Travel Basics, part 2]<br /> * [http://www.manager-tools.com/2008/08/business-travel-packing Business Travel Packing]<br /> * [http://www.manager-tools.com/2009/07/travel-airline-seats Travel - Airline Seats]<br /> <br /> The what and how of packing only a carry-on: [http://www.onebag.com/ Onebag.com]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Travel_Guide&diff=1243346 2022-07-11T20:24:55Z

<p>Mhoye: Updates for modernity.</p> <hr /> <div>----<br /> :: This page was originally created on Mozilla's internal intranet. However, it contains lots of information that could be useful to Mozillians who travel to Mozilla events, or really, anyone who travels, period. The original page (and its history) disappeared when the intranet site was retired.<br /> ----<br /> Travel doesn’t have to suck. In fact, there are probably relatively few parts of your life where a handful of modest optimizations can make such a tremendous difference. <br /> <br /> * We never lose our luggage.<br /> * We can get from the airport entrance to our gate in minutes.<br /> * We get lounge access at the airport, upgraded flights, nicer rooms in hotels.<br /> * We don’t eat junk on the road. Indeed, we often discover great restaurants.<br /> <br /> We have secrets. We have millions of miles traveled between us, and we'd like to show you how it's done.<br /> <br /> But first, the 3 simplest things you can do to make travel a lot better:<br /> # Never, ever check your luggage.<br /> # Check in online as early as possible.<br /> # Pick a Frequent Flyer program<br /> <br /> Do those three and you’re already in the 80th percentile for travel success. What follows below is travel brilliance.<br /> <br /> = Planning =<br /> <br /> == Quick Tips ==<br /> * Scan a copy of your passport and any other travel documents and put them somewhere web accessible but password protected (like Dropbox or Google Drive). This is helpful for getting replacements, and for getting consular help in the meantime.<br /> * Print a copy of those scans - particularly your passport, covid test and vaccination status - and keep them in your carry-on. Do this regardless of the current policies of the countries you're travelling to or through - if policies change while you're on the road, you might have a problem.<br /> * Let your credit card company know that you travel. Anti-fraud measures might lock your card the first time you use it on foreign soil, but they can flag your account so that doesn’t happen. This is no fun to discover after the fact.<br /> * Different airlines have different size restrictions for carryon luggage; know your limits for the whole trip and stay inside them.<br /> <br /> == Pick a Frequent Flyer Program ==<br /> <br /> Prices are generally going to be competitive, so figure out your most common trip(s) and figure out which airline/alliance is best for those. Use that group for everything. You can easily sign up for FF programs online, and add it to your travel agency profile (Egencia for Mozilla employees).<br /> <br /> Even if you travel rarely, you'll eventually accrue enough mileage for free travel, and having a FF number makes online check-in easier.<br /> <br /> If you travel often enough, though, (25k+/year on most airlines) you start earning preferred status. This is the difference between &quot;scum&quot; and &quot;How can I help you?&quot; You have shorter lines for agents, shorter lines for security, you board first. You get access to elite lounges while you wait, and free upgrades to business class to make the trip more pleasant. These are little niceties, but they add up, and make travel much nicer. You can often share status with someone less privileged, which means your spouse likes traveling with you more, too.<br /> <br /> == Check In Online ==<br /> <br /> Every airline will let you check in online, usually 24 hours before your flight leaves. I know this will feel weird the first time, but it is an absolute necessity. With online check-in and no checked luggage, you can skip all the lines at the airport except security (and possibly customs/immigration).<br /> <br /> Checking in early may put you into a lower &quot;group&quot; for boarding (or at least not the suckiest, all-the-overhead-bins-are-full group). Check in as early as possible, even if you don't know how many bags you will check (correct answer: 0). You can always add (and pay for) checked bags when you get to the airport.<br /> <br /> The one '''exception''' to this guideline is that if you think your flight might be delayed or cancelled due to weather, ''don't'' check in online ahead of time. If you have to re-book, and you are already checked-in, the agent will have to &quot;uncheck&quot; you, which may slow down the re-booking process and cause you to miss out on alternate flight options. Keep in mind that weather problems cause ripple effects even in locations where weather is good. For example, your flight out of sunny Phoenix might be cancelled because the aircraft is grounded by a snowstorm in Chicago. (See this Egencia blog post for [http://info.egencia.com/wintertraveltips2014.html tips for avoiding weather delays].)<br /> <br /> Online check-in also lets you choose your seats, which brings us to...<br /> <br /> == Choose Your Seats ==<br /> <br /> * Take a window seat for very short flights or very long flights. Window seats have more shoulder room, less hassle from other passengers, and a window. The only downside is bladder management, but on short flights you can stick it out and on long ones you can get up when your fellow passengers do.<br /> * ''Every'' plane has some seats that suck. No recline, noisy, cold, lack of floor storage or slightly narrower than most, [http://www.seatguru.com SeatGuru] will tell you what to avoid. It'll also tell you which seats are great (extra legroom, etc) that you should take given half a chance. Usually, exit-row seats have extra legroom (good for tall people), and the last row and the row in front of the exit row do not recline (bad in general). The first row in a section (where you have a bulkhead in front of you instead of another seat) typically does not have under-seat storage, so everything must go in overhead bins, but it typically does have more legroom. (Seatguru will tell you whether or not this is the case on a particular plane.)<br /> * ''The Middle Seat Gambit'' - If you’re traveling with someone else, check in online together and look for an empty 3-person row. Take the aisle and window. Middle seats fill up last, there’s a decent chance the seat stays empty. If so, you have a lot more space to dump things during the flight, and more legroom since you can use that space instead of putting things under the seat in front of you.<br /> * If you’re traveling alone, you can still use the middle seat gambit by checking in online and looking at the seat map for someone acting as a de facto accomplice.<br /> * If there is only one (worst possible) seat left when you go to select seats, ''don't take it''. It will be claimed by someone else, and the gate agent will assign you a different seat. A flight that full might mean that someone gets bumped, but lack of a seat assignment doesn't guarantee it will be you.<br /> <br /> == Manage Layovers ==<br /> <br /> Flying nonstop to your destination is always easiest, but if that’s not a possibility for whatever reason, here are some other things to keep in mind:<br /> <br /> * Major metropolitan centers are often served by multiple airports, and each airline will have a preference. If you can’t get the flight you want with the airline you like, look to see whether you’re just pointing at the wrong airport.<br /> * If you can’t fly nonstop, you probably at least have your choice of connection airports, and the choice matters there. What’s more, a given airline will have certain preferred connection cities, so a couple trips should get you a reasonably complete list. (For example, connecting from Toronto to San Francisco on Star Alliance, it is much preferable to connect in Denver or Vancouver than it is to connect in Chicago O’Hare.) Consider the immigration/customs procedures of the country you're connecting in if it's separate from the origin or destination (e.g., prefer Vancouver over a US airport for connecting between Toronto and Auckland, since the US requires internationally-connecting passengers to go through immigration and customs).<br /> * If you have to have a connection, you might also have the opportunity to fly to a better airport (e.g., if you have to connect to Washington, DC, you are likely to be able to fly to DCA instead of IAD).<br /> * Take the season and likely weather into account when picking connecting airports; avoid snowy airports in winter, thunderstorm-y airports in summer.<br /> * If you have to layover overnight, prefer airports that have on-site hotels (and for god’s sake prefer Munich over Frankfurt).<br /> * If you’re crossing a border during your flight, it’s often preferable to layover in-country before crossing over. It means your first flight is domestic, so you can arrive later at the airport since there’s no immigration headache there. <br /> * Another reason not to check a bag is that when you have a connection after arriving in some countries (e.g., the USA, but not EU countries), you have to claim your bag, take it through customs (even though they rarely look at it), and then check it again for your connecting flight. More time and hassle.<br /> * Remember to account for boarding time when calculating layovers. If flight A arrives at 12:00 and flight B leaves at 1:00, you do not have an hour, you have about 20 minutes (because you need to get OFF of flight A once it arrives, transit to whichever gate/terminal flight B is in, and then be there for flight B '''boarding''', not flight B '''departure''').<br /> <br /> = Immigration and Customs =<br /> <br /> == General advice ==<br /> * Make sure you know what the requirements are for crossing all immigration and customs barriers before you do so. If you don't know what those requirements are, embassy or consulate websites are often useful, as are the US government's [http://travel.state.gov/content/passports/english/country.html country specific information] (though somewhat tending towards information useful to Americans).<br /> ** This includes vaccination status and testing, which varies on a country by country basis and will continue to do so for the foreseeable future.<br /> * Make sure you have any documentation needed in your carry-on luggage. When entering a country where you're not a citizen or resident, you should carry proof of onward travel, particularly if the reservation on which you're flying doesn't return you to your home country (e.g., because you're traveling on separate reservations).<br /> * If you're ''transferring'' in a country (or multi-country immigration zone) that's different from your origin or destination, figure out whether you'll need to deal with immigration there, and if so, what the rules are. This might vary depending on the airport, or in some cases even on which terminal you arrive at and depart from. (In the latter case, airport websites are often helpful.)<br /> * Don't carry any non-commercially-packaged food through customs, not even the apple you got in the airport. Many places have strict agricultural control policies that prohibit doing so; it's not worth the trouble.<br /> * Always carry a pen (blue or black) somewhere in your checked luggage for filling out the immigration and customs forms.<br /> <br /> = Packing =<br /> <br /> '''Quick Tips'''<br /> * Have a toiletry bag that you keep stocked, rather than trying to remember to pack toothbrushes &amp;c the day of. It doesn’t cost much to buy the duplicates once, and saves hassle/forgetting.<br /> * Put your favourite head, stomach, and sleep meds in the toiletry bag. You can buy most things on the road, but meds are sometimes an exception.<br /> * Throw a couple of large ziploc bags in there, too. They are immensely useful for storing wet clothing or leaking bottles or, by contrast, for putting things like passports in when you need them to stay dry. They weigh nothing and disappear into a pocket until needed.<br /> * Layers. You can adapt to a wide range of climates, even multi-city travel, by packing layers. Shirt, Sweater, Hoodie, Jacket is plenty warm, packs much more compactly than a parka, and gives you middle ground for an overwarm restaurant or an overcool office.<br /> * While you're packing, make a text list on your phone of everything you pack. Towards the end of your trip (such as waiting for your flight home), put a '+' next to every item you actually used. Next time, don't pack the things you didn't use. Also, if your bag goes missing, you have a list of what was in it.<br /> <br /> == Don’t Check Luggage ==<br /> <br /> :: Repeat after me: Checked luggage is for chumps.<br /> <br /> :: Again. Checked luggage is for chumps.<br /> <br /> :: -- George Clooney, ''Up in the Air''<br /> <br /> Every time you give your bag to the airlines, you're inviting them to lose it, abuse it, leave it in your departure city, forget about it on the tarmac during a rain delay, etc. North American airlines will allow you one carry on suitcase and one “personal bag” which usually means a purse or laptop. This is easily enough for a week of travel, and can be extended indefinitely with laundry service. Invest in a good carry-on and bring it with you.<br /> <br /> Put everything you need during the flight in your laptop bag, in case you have to gate-check your carry-on suitcase (common on short flights with smaller planes).<br /> <br /> == Choose the Right Luggage ==<br /> Checked luggage will inevitably be destroyed over time, regardless of quality. If you stick to carry on, though, good luggage will last forever; be willing to pay once for something that gets it right. Your happiness while traveling is worth it.<br /> <br /> His bias for non-rolling luggage notwithstanding, [http://www.onebag.com/bags.html this is the single best guide out there] for evaluating luggage. The highlights:<br /> <br /> * Lighter is better<br /> * Curvy designs rob you of packing volume, prefer right angles<br /> * Chain zippers are stronger than coil zippers (look for YKK as the brand of zipper)<br /> * Pocket design and positioning matters<br /> * So do tie-downs<br /> <br /> In truth, the best way to maximize quality while minimizing weight is to let go of the dependence on rolling bags. Soft-sided, non-wheeled bags are exceptionally light and versatile. [http://www.tombihn.com Tom Bihn] and [http://www.redoxx.com/ Red Oxx] are your best plays. Tom Bihn’s Aeronaut is is a full-sized carry-on that converts to a backpack for long walks across cobblestones/sprints to catch a connection/etc. The Red Oxx Air Boss was designed by the same guy who wrote the luggage-choosing guide above.<br /> <br /> If you're not ready to let go of wheeled bags, any manufacturer with a lifetime warranty is probably worth considering. These include:<br /> <br /> * [http://www.briggs-riley.com/ Briggs &amp; Riley]<br /> * [http://www.travelpro.com Travelpro] (&quot;the best&quot; carry-on according to [http://thewirecutter.com/reviews/best-carry-on-luggage/ The Wirecutter])<br /> * Certain models of [http://shop.eaglecreek.com/lightweight-carry-on/l/111 Eagle Creek] (not all models have a lifetime warranty)<br /> <br /> Pay attention to the bag’s extensible arm: is it well constructed? What does it do to your interior space? 2 segments of extension or 3? Moving parts make everything more fragile -- if you are choosing moving parts in your luggage, they need to be brilliant.<br /> <br /> == Buy It There (BIT) ==<br /> <br /> Don’t try to anticipate every contingency and pack for it. You will bog yourself down with unnecessary cruft. Pack for what you ''know'' you’ll need, or at most what you reasonably expect to need the majority of the time. You can find contact solution, toothpaste, aspirin, and dental floss at almost any convenience store. For the rest, shove an extra $50 into a pocket somewhere and buy whatever you need there, if it comes up. <br /> <br /> (Good news: It comes up less often than you’d think.)<br /> <br /> BIT exceptions: <br /> There are some things you don't want to source while traveling - if you only use one specific brand of shampoo, conditioner, etc, transfer it to a small, travel-friendly bottle. Depending on where you're traveling BIT can be tough if you don't speak the language and are looking for something very specific (like Cipro in India or a flat iron in China). Goes without saying, but BIT does *not* apply to medications (remember that what requires a prescription varies by country, but you can apply it if you know that something can be bought without a prescription at your destination).<br /> <br /> === Corollary: Wash It There ===<br /> If you’re gone for longer than a carry-on can reasonably contain (which is longer than you think), don’t fail over to multiple suitcases; just get things laundered partway through. Your hotel will offer laundry service, though it will be overpriced. Most of the time you’ll find a wash and fold place within walking distance or a service that does pick up and next day drop off.<br /> <br /> Also keep in mind that at most Mozilla or other geek events, you will probably acquire at least one or two t-shirts. You can bring one or two fewer shirts; if this guideline fails, wash one of the ones you brought.<br /> <br /> If you bring quick-drying underwear and socks, you can wash them in the sink or bathtub and dry them overnight on the towel rack (except in humid climates). You can skip bringing detergent by using the hotel's shampoo (as long as you don't mind your underwear smelling like &quot;ginger lemongrass&quot; or whatever); shampoo is just mild detergent. Check the plumbing before you fill the sink; some hotels don't install the lever for raising the plug. Before hanging items to dry, roll them in a towel and squeeze out excess moisture.<br /> <br /> == Counterpoint: The case for checking a suitcase ==<br /> A few heavy-traveling Mozillians are in the &quot;checked bag&quot; camp. Add your reasons for using this strategy here:<br /> * Problems with checked luggage are actually quite rare.<br /> * You don't have to schlep a roll-aboard through the airport with you, including squeezing it into tiny toilet stalls.<br /> * You can pack a few extra things that help you be more comfortable on an extended trip.<br /> * At least one airline (American) gives early boarding privileges (after Elite and Priority but before Zone 1) to passengers with no overhead baggage.<br /> * You aren't limited to 100ml bottles of liquid/gel/cream, and can bring home ''properly packed'' wine, booze, perfume, etc. (Wrap the bottle in at least two plastic bags and nestle it in the groove left by the extending handle, surrounded tightly by clothes.)<br /> * Having airline status often helps your bag appear on the belt faster. Also, if the final segment of your trip is an international arrival in the United States, you're unlikely to have to wait long for your bag, since all baggage goes to the same belt, so it gets there quickly.<br /> * TIP: Get a suitcase with four wheels. Baggage handlers can slide it across the floor of the cargo hold instead of tossing it, subjecting the suitcase and its contents to much less abuse. Anything that protrudes, like carry straps or zipper pulls, can get snagged and chewed up in baggage-handling equipment; go for streamlined.<br /> * TIP: Ask for your checked luggage to be marked &quot;Fragile&quot;. It will be loaded on top of other bags, and usually be unloaded first.<br /> * TIP: If you check luggage, don't let your eyes off the bag until there's a tag on it, and if you can, check that the tag is correct (with your name and correct destination airport on it). One of the common reasons for lost/delayed luggage is getting the wrong tag on it right at the check-in desk.<br /> * TIP: Things to make sure are '''not''' in your checked bag: everything you need to get through customs and immigration and get to your final destination. Any electronics that might be stolen. Lithium-ion batteries (prohibited).<br /> <br /> Some airlines (particularly non-North American or discount airlines) have much lower limits for what you're allowed to carry on, so you'll have to check luggage anyway.<br /> <br /> Some airlines (e.g., Air France, KLM) will even want to weigh your carry-on bag (often although not reliably), and want it to be a weight that's lower than what it is with your laptop in it (e.g., 6kg, 8kg). Remember that your laptop often counts as a separate personal item and you can take it out of the bag before weighing.<br /> <br /> ==Packing Techniques and Tools==<br /> Your strategy for how to put your stuff in your suitcase is very much a matter of personal preference, along with the type of travel you're doing (destination vs. touring) and the type of clothes you bring. Here are some ideas that may be helpful.<br /> <br /> * The [http://www.onebag.com/pack.html bundle method] is great for avoiding wrinkles, but it tends to require that you unbundle ''everything'' to get out any single thing.<br /> * It's extremely helpful to have some kind of containers to organize your stuff. Purpose-made packing &quot;cubes&quot; are great, but are absurdly expensive. You can get by with zip-top plastic bags if you don't travel often, or while you're waiting to find ready-made cubes on sale. <br /> * If you buy only one packing accessory, consider getting a [http://www.amazon.com/Eagle-Creek-Travel-Pack-It-Folder/dp/B002YIRC3O/ packing folder], which helps you fold larger items (shirts, pants, skirts) to a uniform footprint, and then encloses them like an envelope.<br /> * Compression bags, which let you squeeze all the air out of your clothes, are good only for clothes that don't easily wrinkle. However, a compression bag can be great as a laundry bag to minimize the volume of dirty clothes on your way home. Either way, have a cloth or plastic bag you can use to keep used laundry separate. <br /> <br /> = Airport Hacking =<br /> '''Quick Tips'''<br /> * ABC: Always Be Charging. Wherever you come to rest, be charging. Maybe your flight has power plugs, that's swell, but maybe they stop working, or your seatmate gets to it first, or you need it to charge your phone. If you're at rest for more than 10 minutes, find a plug. If you bring a power strip so others can plug in, too, you can make friends anywhere :-)<br /> * Watch where uniformed crew members go. They know the best eateries in any given airport, and even where to stand on the tram platform in order to get off quickly at the other end.<br /> * The internet knows about delays before your gate agents do. Bookmark [http://flightaware.com/live/ flightaware] right now, and use it from your phone at the airport to keep tabs. Caveat: Flightaware may show your flight as delayed because the inbound plane you're getting on is delayed; if the airline substitutes another aircraft, your flight could be on time or only a little delayed.<br /> * If you do see signs of a significant delay, particularly at night when it's likely you'll be put off until morning, act swiftly before the lines form. Talk to gate agents about rebooking onto other flights and if the line there is long, be on the phone with your airline as well. First to rebook means first to call hotels and taxis and all the rest. Being last to rebook means sleeping in the airport. If you have elite status, call the customer service number for elite members, not the general customer service number.<br /> * When you get off the plane, the restroom closest to your gate will be crowded with other people from your flight. Keep going to the next one further away.<br /> * No one wants to sleep in an airport, but flight delays or cancellations, or just poor planning, may require it. There is actually a whole website devoted to [http://www.sleepinginairports.net/tips.htm sleeping in airports].<br /> <br /> <br /> == Being prepared for security ==<br /> * Veteran move: if you have a digital boarding pass, set a screenshot of that boarding pass as the background of your lock screen, so you can see the QR code without unlocking the phone.<br /> * Bring identification. [http://www.tsa.gov/traveler-information/acceptable-ids Here's a list of acceptable IDs] in the US. If you forget your ID, all is not lost. It's possible, with some extra hassle, to travel within the US even if you don't have your identification. [http://blog.tsa.gov/2013/04/tsa-travel-tips-tuesday-can-you-fly.html Here's what the TSA says to do if you don't have ID.]<br /> * Have photocopies - paper copies - of your passport and one other piece of ID (and where necessary, vaccination status or test results.)<br /> * Avoid getting into a screening line behind people who look like they don't travel often (families with kids, retirement-age folks, large groups).<br /> * Wear slip-on shoes and socks. Do not go barefoot in airports (And, for the love of God, Do Not Sit Or Lie Down On The Floors. Airport floors are disgusting, you have no idea.)<br /> * Consider not wearing a belt, or wear one with no metal, so you don't have to take it off.<br /> * Avoid clothes with extra pockets, like cargo pants. They can be flagged by the body scanner, and cause you to get a pat-down. Same for &quot;travel&quot; clothes with hidden pockets; these can be handy while touring, but not while flying. Even a hoodie can win you a pat-down for the hood and kangaroo pocket. <br /> * On the other hand, a jacket with lots of pockets is like an extra carry-on; you have to remove it for security anyway, and you can keep your in-flight necessities (gadgets, etc.) close to hand during your flight.<br /> * Know the drill with liquids, gels, and creams: containers at most 100ml/3oz, in a clear zip-top bag, 1 liter/1 quart size. Have this in an external pocket of your carry-on, ready to pull out and put in a bin. (If you travel often, you might want to get a sturdier bag than the grocery store kind. It must still be clear and zip-top.)<br /> ** Don't pack little bottles of booze. Yes, it's under the limit, yes you're technically allowed to carry it through security. Don't.<br /> * Avoid large metal jewelry.<br /> * Take everything, but especially metal (keys, coins, etc.), out of your pockets.<br /> * '''Leave your pocket knives and multitools at home.'''<br /> * If you're wearing an activity monitor, such as a FitBit, take it off for screening.<br /> * You should hang onto your ID and boarding pass as you go through the line, but you can't carry them through screening; put them in your bin.<br /> * Put the bin with your shoes, jacket, and liquids onto the conveyor belt first. You can be getting dressed while the rest of your stuff comes through.<br /> * Take your laptop out of your bag and put it in a separate bin. You can usually leave it in a sleeve, as long as there's nothing else in the sleeve. <br /> * Consider getting a checkpoint-friendly laptop bag, with a laptop-only section that folds out without taking out the computer. The less you handle your laptop, the less likely you are to drop it. (US TSA allows you leave the computer in this type of bag; other countries often do not.)<br /> * Don't start going through the screening machine or metal detectors before you can see your stuff moving down the conveyor belt.<br /> <br /> == US Trusted Traveler Programs ==<br /> If you frequently cross US borders, you can save time and hassle in the long run by enrolling in one of the programs that provide expedited entry for pre-approved travelers. Enrolling involves an application fee and form, and an in-person interview at an entry point, so there is a start-up cost in time and money. Which program you should enroll in depends on the type of crossing you do most; you can enroll in more than one. <br /> <br /> * When entering the US, if you're not in a &quot;trusted traveler&quot; program, try to get into the immigration queue that is ''next to'' the Global Entry lane. If no one is in the Global Entry lane, the officer there will often take people from the nearby queue, making it move faster. Do likewise for NEXUS when entering Canada.<br /> * Wear Firefox gear when going through immigration, anywhere. It creates goodwill and starts pleasant conversations.<br /> <br /> ===Automated Passport Control===<br /> Automated Passport Control kiosks are available to citizens of the US, Canada, and [http://www.cbp.gov/travel/international-visitors/frequently-asked-questions-about-visa-waiver-program-vwp-and-electronic-system-travel Visa Waiver Program] countries, for entry into the US, in an expanding number of North American cities. Unlike Global Entry or Nexus, these kiosks require no pre-registration. You swipe your passport, let the kiosk take a photo, answer some questions, and then get a receipt that you show to a Customs and Border Patrol officer. The kiosk replaces filling out a customs card by hand.<br /> <br /> See the [http://www.cbp.gov/travel/us-citizens/Automated%20Passport%20Control Automated Passport Control] webpage for a list of cities with APC kiosks.<br /> <br /> === Global Entry ===<br /> [http://globalentry.gov/about.html Global Entry] provides expedited screening for entry ''into'' the US at certain airports. Once in the program, you can go to an automated kiosk instead of an immigration agent (skipping the enormous lines that result from multiple international flights arriving at about the same time), and you can answer the customs questions at the kiosk instead of filling out a paper form. Unless there is an issue with your kiosk interaction (such as it couldn't read your fingerprints), you don't need to talk to a CBP agent. Global Entry is open to U.S. citizens, lawful permanent residents of the U.S., Dutch citizens, South Korean citizens and Mexican nationals.<br /> <br /> === NEXUS ===<br /> [http://www.globalentry.gov/nexus.html NEXUS] provides expedited screening for crossing the US-Canada border in both directions. It can be used at land and sea entry points as well as at airports. You can use the NEXUS-only lanes at land crossings only if every person in the vehicle (including children) has a NEXUS card. Using NEXUS at an airport requires scanning your irises. If you wear contact lenses, you must remove them for the initial iris scan that is taken after your enrollment interview.<br /> <br /> === Other US programs ===<br /> * [http://www.globalentry.gov/netherlands.html FLUX] expedites passage between the US and '''the Netherlands''', and is open to US and Dutch citizens.<br /> * Global Entry members can receive expedited entry into '''[http://www.globalentry.gov/newzealand.html New Zealand]'''.<br /> * [http://www.globalentry.gov/sentri.html SENTRI] provides expedited entry into the US from '''Mexico''' at specific land crossings.<br /> * [http://www.globalentry.gov/korea.html Smart Entry Service] provides expedited entry into the Republic of '''Korea'''. It is open to US and Korean citizens.<br /> * [http://www.globalentry.gov/smartgate.html SmartGate] provides streamlined entry into '''Australia''' for US Global Entry members. Visa requirements still apply.<br /> * [http://www.globalentry.gov/tsa.html TSA PreCheck] enables US Global Entry and Canadian NEXUS members to use designated TSA airport screening lanes, without removing liquids, laptops, shoes, jackets, or belts. You must provide your membership number when booking flights with participating airlines. TSA is expanding the PreCheck program to include more people, including US military members and those invited by their airline's frequent flyer program. You must still apply, pay a fee, and go through an interview. See the [http://www.tsa.gov/tsa-precheck TSA PreCheck] website for details.<br /> <br /> == Other countries' traveler programs ==<br /> * The UK's [https://www.gov.uk/registered-traveller Registered Traveller service] enables certain citizens of Australia, Canada, Japan, New Zealand and the USA to get faster entry to the UK, without filling out a landing card. <br /> <br /> <br /> == Country-specific notes ==<br /> <br /> === USA ===<br /> * visitors under the [https://travel.state.gov/content/travel/en/us-visas/tourism-visit/visa-waiver-program.html visa waiver program] (those who don't need a visa) must apply online for an [http://www.cbp.gov/travel/international-visitors/esta ESTA].<br /> <br /> === Canada ===<br /> * visitors who do not need a visa, are entering Canada by air, and are not US citizens or Canadian citizens or Canadian permanent residents, must apply online for an [http://www.cic.gc.ca/english/visit/eta.asp eTA].<br /> <br /> === Schengen Area (Europe) ===<br /> * The [http://en.wikipedia.org/wiki/Schengen_Area Schengen Area] is an immigration-barrier-free zone covering most of the European Union and some additional non-EU countries, but not the UK or Ireland.<br /> * If you need a visa to visit the Schengen Area, it is easier to get such a visa if your point of arrival in the Schengen Area is the same country as your destination. (For example, if you're traveling to Spain, it is easier to arrive in Madrid after connecting in the UK or US than connecting via Amsterdam, since in the latter case getting the visa requires dealing with both the Spanish and Dutch authorities.)<br /> * If your nationality requires a visa to visit the Schengen Area and your trip does not terminate in Schengen, avoid making more than one connection in Schengen; in such a case you must get a Schengen visa, even though that's not your destination. Schengen immigration authorities look at your ''next'' point of travel (not your final one) to decide whether you need a visa; if it is Schengen, they will ask for one.<br /> <br /> === New Zealand ===<br /> * Make sure to declare any shoes in your checked luggage. The authorities just want to look at them and maybe clean the dirt off for you, but they'll be upset if you don't declare them.<br /> * Don't even think about [http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&amp;objectid=11404025 bringing fresh fruit] into New Zealand or you will get an instant fine.<br /> <br /> === Australia ===<br /> * Visitors who can can enter without a visa must apply online for an [https://www.eta.immi.gov.au/ ETA].<br /> <br /> = Flying =<br /> <br /> '''Quick Tips'''<br /> * Hydrate, hydrate, hydrate. Air in an airplane at altitude is incredibly dry and dries you out. Drink water whenever you can. Bring an empty water bottle (even better: collapsible) and fill it from a water fountain inside security. (Some airports, like SFO, have water bottle filling spots that make this a little easier.) Don't drink the water that comes out of the water tanks onboard an airplane, including coffee and tea; you don't want to know how disgusting those tanks are. If you get water in the beverage service, ask for fizzy water (club soda) to ensure it came out of a bottle or can. If you need to brush your teeth in-flight, use water from your water bottle, not the tap in the toilet.<br /> * Request an alternate meal (kosher, indian, vegan, whatever) - they tend to be tastier, and often come first. (However, the downside to the meal coming first is that the tray is going to be in your way substantially longer.)<br /> * If you're in an aisle seat, you’ll find that the aisle-side armrest won’t lift. This is annoying, because it is much easier to deplane with that thing out of the way. Reach back to where the armrest joins the back of the chair -- there may be a release latch or button. (This works on some Boeing 777s; most smaller craft do not have this feature. See [http://brokensecrets.com/2011/01/17/raising-the-airplane-aisle-armrest/ this article] for a photo.)<br /> * Always wear shoes before going to the airplane lavatories; never go barefoot or wearing socks only. <br /> <br /> == Headphones ==<br /> Enjoying music or movies during travel is much better with headphones designed for travel use. You need to consider three types: <br /> * active noise-cancelling headphones<br /> * those without noise-cancellation<br /> * in-ear monitors. <br /> Generally speaking, on airplanes, active noise-cancellation will be better on the plane but worse when you're not on the plane (in the hotel room, for instance.) A quality headphone without noise cancellation will almost always sound better when not on an airplane. In-ear monitors allow for excellent sound quality and also allow one to rest your head on a pillow without the headphone pushing against one's ear, but some are uncomfortable with putting anything in one's ear. In-ear monitors are also much more compact. For those who want the sound quality of in-ear monitors and the compactness, but find that fit is a problem, consider Comply foam tip replacements which can be selected to fit your ear size.<br /> <br /> * For active noise cancellation headphones, the Bose Quiet Comfort 15 is the most popular model sold and for good reason. However if you want the headphone to be good when the noise-cancellation is turned off, you may want to consider the [http://www.psbspeakers.com/products/headphones/M4U-2-Headphones Psb m4u 2], which is more expensive but also more versatile.<br /> * For headphones without active noise cancellation, consider rugged models that have reputations burnished by decades of use by audio professionals such as the Sennheiser HD-25 1-ii. Another popular option is the V-Moda M-80 which has similar sound quality, has a good reputation for build quality, and also comes with a nice travel case.<br /> * For in ear monitors, there are too many to list but one line that is very popular is the Shure SE series which have models from $99 on up. These are very rugged models which allow for replaceable cables, replaceable tips and have very good sound quality.<br /> Additional resources for headphones include [http://www.innerfidelity.com/content/innerfidelitys-wall-fame Innerfidelity's Wall of Fame] and Head-fi.org's [http://www.head-fi.org/t/618255/check-out-the-head-fi-summer-2012-buying-guide 2012 Summer Buying Guide].<br /> <br /> == Make friends with TSA and your flight crew ==<br /> <br /> Airplanes are a sea of grumpy, tired, unhappy people. A little friendliness goes a long way -- especially if you're regularly flying the same route with the same flight crew.<br /> <br /> == Seat etiquette ==<br /> The following tips are about showing consideration to your fellow passengers, who unfortunately may not even notice it. But violating these norms is likely to cause annoyance. You don't want to be &quot;that guy&quot;, do you?<br /> <br /> * The person in the middle seats gets to use both armrests. The people in the window and aisle seats get a little extra space, so yielding one armrest each is the least they can do. In any case, try to keep your elbows in your own space.<br /> * Consider the person behind you before reclining your seat into their space, especially if they are trying to eat or use a laptop. Avoid reclining abruptly (though it's not always possible to control this). Raise your seat back during meals.<br /> * If you need to leave your seat during the flight, try to avoid hoisting yourself up by yanking on the seat in front of you. This may be difficult to avoid if the seat is reclined (see above).<br /> * If you have an individual touchscreen in the seat back in front of you, jabbing it forcefully doesn't make the touchscreen work any better. If it's really not responding to touch input, try controlling it from the armrest controls.<br /> <br /> * [http://www.independenttraveler.com/travel-tips/travelers-ed/the-etiquette-of-seat-backs-and-elbow-room The Independent Traveler: The etiquette of seat backs and elbow room]<br /> <br /> <br /> <br /> Still to write:<br /> * how to sleep (Needs to be written by someone who is actually able to sleep on planes)<br /> ** [http://gizmodo.com/how-to-get-the-best-sleep-of-your-life-on-an-airplane-1598708044 Gizmodo: How to get the best sleep of your life on an airplane]<br /> ** [http://www.independenttraveler.com/travel-tips/travelers-ed/sleeping-on-planes Independent Traveler: Sleeping on Planes]<br /> * move on long flights<br /> <br /> = Tips for specific airports =<br /> As a general rule of thumb, in any airport, the terminal or concourse that serves international flights has nicer shops and restaurants than the areas for domestic flights. So, if you're traveling domestically, have time to kill, and can get into the international terminal without going through passport control, you might want to go hang out there.<br /> <br /> == AMS Amsterdam ==<br /> * in the international section (only?), there are nice quiet places to sit on the upper level outside the lounges (even if you don't have lounge access)<br /> * if you want to take the train to/from the airport, hoard coins (€4 to Amsterdam-Centraal, less to Amsterdam-Lelylaan or Amsterdam Zuid), since the ticket machines don't take bills or American credit cards. (The city trams/buses in Amsterdam do take bills, but this is a national train.)<br /> * note that the entirety of the outside-[https://en.wikipedia.org/wiki/Schengen_Area Schengen]-immigration part of the airport does security at the gate, per flight<br /> <br /> == AUS Austin, Texas ==<br /> The food available in the airport is actually pretty good, since most of the food concessions offer menus from local restaurants. Get to the airport early enough to have a last plate of barbecue or breakfast tacos. <br /> <br /> Another reason to get to the airport early is the &quot;Knot Anymore&quot; chair massages available near gates 13 and 7. Austin is awash in good massage therapists, so the ones working in the airport are far better than most airport massage services.<br /> <br /> == CDG Paris / Charles de Gaulle ==<br /> * CDG airport has multiple airport hotels on premises (on the around-the-airport CDGVal shuttle train); typically at least one of the fancy ones has good prices because it isn't hosting a conference that week, but there's also an Ibis. <br /> * CDG airport has four disconnected parts:<br /> ** Terminal 1 (the cylinder with pods) (United is here)<br /> ** Terminal 3 (the discount airlines)<br /> ** Terminal 2A-2B-2C-2D-2E-2F (the bulk of the airport) (Air France is here)<br /> *** note that there are two satellite piers attached by train (outside immigration but not inside security) attached to Terminal 2E (the attached part of terminal 2E is called K, the satellites are called L and M)<br /> ** Terminal 2G<br /> * transport<br /> ** there's a train (CDGVal) connecting Terminal 1, Terminal 3 / Roissypole (where most but not all of the hotels are), and Terminal 2 (the station is between 2C/2D/2E/2F)<br /> ** high speed trains stop only at the terminal 2 station (between 2C/2D/2E/2F)<br /> ** RER trains (Paris's suburban rail network) stop at Terminal 2 (same station, again) and at &quot;Terminal 1&quot; (which is actually the Terminal 3 / Roissypole station for CDGVal)<br /> ** Terminal 2G is reachable only by shuttle (I think, never done it)<br /> ** If you want to take the RER to/from the airport, hoard coins in advance to pay the €9.50, since foreign cards don't work, and the machines don't take bills. <br /> ** The RoissyBus is only €10.50 and runs nonstop between CDG and the Paris Opera, only a few blocks from the Mozilla Paris office. Look for signs for &quot;RoissyBus&quot; or &quot;Paris by bus&quot; within each terminal to find the bus stop.<br /> <br /> == JFK New York ==<br /> * The wifi password of the British Airways' lounge is &quot;London&quot; (according to Reddit). You can usually get in range of the wifi hotspot without going inside the lounge.<br /> <br /> == LHR London Heathrow ==<br /> * Terminal 5 (international) <br /> ** If you need to take the train to concourse B or C, go to the far end of the platform. You'll bypass the crowds at the near end, and be closest to the escalators when you exit.<br /> ** If you need to backtrack from concourses B or C to concourse A, ''don't'' take the train; you'll be routed through security again. There's a pedestrian tunnel that parallels the train, and comes out next to elevators that let out inside security in concourse A. The tunnel doors are marked &quot;Emergency Exit&quot;, but do not have alarms, and in fact open automatically, to accommodate mobility-assistance carts. Stay to the left (remember: you're in England) to keep from being run over by them.<br /> ** If you're going to the Mozilla London office, [[London#From_Heathrow_by_traincheck the directions]] and don't bother with Heathrow Express.<br /> <br /> == NCE Nice, France ==<br /> * if you have a really early flight, there are multiple decent airport hotels nearby. But do '''not''', under any circumstances, stay at the Etap.<br /> * if you want to avoid a really early flight, consider as an alternative doing an overnight layover at CDG, which has multiple airport hotels walking distance from Terminal 1 (but poorly signed). Make sure your layover is long enough, though.<br /> * if you're traveling to west of the airport (e.g., towards W3C's European offices near Antibes) and want to take public transit, it's possible to walk to the Nice - St. Augustin train station ('''not''' the main Nice - Ville train station) in about 15-20 minutes, but there's basically no signage. But definitely look at the train schedules before trying this. Buses from the bus station (gare routière) at the airport may be better.<br /> * there's a free shuttle between Terminals 1 and 2. Don't try walking between terminals.<br /> * There are bus stations at both terminals, but some bus routes stop at both terminal and some stop only at Terminal 1. You need to buy a ticket at the station before boarding.<br /> * the airport does not have water fountains behind security. But restaurants will probably be willing to fill up a water bottle for you, especially if you've bought something there.<br /> <br /> == NRT Tokyo/Narita ==<br /> * If you can do so just as easily, fly to Haneda Airport (HND) instead, which is closer to the city.<br /> * Don't even ''think'' of taking a taxi. It will take hours, and cost multiple hundreds of US dollars.<br /> * Two companies (JR and Keisei) run trains to Tokyo, and both have express and local services at different prices. Choices depend on where in Tokyo you're going. Google Maps might be helpful, or just figure it out when you get there.<br /> * Consider taking a [http://www.limousinebus.co.jp/en/ Limousine Bus] to somewhere close to your destination, and take a taxi from there.<br /> <br /> == ORD Chicago O'Hare ==<br /> * In Terminal 3, at the beginning of concourse G, there is a &quot;Chicago Urban Garden&quot; on the second floor, with aeroponic herbs and vegetables. This is a nice quiet place to wait if you don't have access to an airline lounge. <br /> <br /> == SFO San Francisco ==<br /> * if you're through security and looking for food, realize that some pairs of terminals are connected behind security. In particular, there are four separated behind-security zones at SFO right now: International-G/Terminal3-F/Terminal3-E, Terminal2-D/Terminal1-C, Terminal1-B, and International-A. In particular, if you're in C, you can probably find better food and better places to sit in D, and at some hours there's not much open in G, but you can head over to F.<br /> * The recently renovated terminal areas are the International Terminal (2000), Terminal 2 (gates D) (2011), and Terminal 3 gates E only (2014)<br /> * If you're taking BART to the airport, you can take the airtrain or walk to get around the airport from the airport BART station. You should definitely walk to International (G or A, which share a large central checkin hall but have separate gate areas), maybe walk to Terminal 3 (at least if you're ready to go straight to the security line), and you can walk to the other terminal if you like.<br /> <br /> == SJC San Jose CA ==<br /> <br /> == TPE Taipei Taoyuan ==<br /> * if you're coming from within Asia to Taipei, fly to Songshan Airport (TSA) instead<br /> * if you have Star Alliance gold, there are multiple EVA lounges to choose from. The main one, with all the good food, is on the same side of the open (to the floor below) space as the tropical bar one, with entrance across the hallway from it (not across the open space)<br /> <br /> == YVR Vancouver ==<br /> * As airports go this one is a pretty beautiful. If you're departing to the US from Vancouver note that you will go through US customs and immigration at YVR, so arrive 2 hours before your scheduled departure time. <br /> <br /> = Trains =<br /> <br /> * for booking long-distance trains within Europe, https://www.trainline.eu/ is often better than the national train company sites, because they tend to be clearer about both giving you the better options for ticket retrieval and explaining those options to you<br /> <br /> = Hotels =<br /> <br /> '''Quick Tips'''<br /> * Ask for upgrades. I know, this sounds trite, but it works. If you don’t know how that works, just remember, when checking in, to ask “Is there a better room available?” If they say yes, you’re set. If they say no, that’s fine. If they say “yes, for a price” then you can consider that price and make the call. We’ve gotten $2000/night rooms on a $180/night booking just by asking. This tends to work well when the hotel has a lot of open inventory (particularly effective in LAS, less effective near Moscone during a conference).<br /> * When checking in, adjust your interactions with the clerk based on whether they smile when you approach. Chit-chat with a smiling clerk, but not with an unsmiling clerk. The latter is just as much a form of establishing rapport as chit-chat, because you're not wasting the time of a transaction-oriented person. And establishing rapport can make the marginal difference in whether they decide to give you an upgrade.<br /> * Expensive hotels tend to have sensors in the minibars, but most of the rest still just have housekeeping track what’s missing each visit and bill you. If you do get the munchies, just head out to a convenience store the next day before housekeeping and buy matching replacements at the saner price. <br /> * You can avoid the minibar entirely by grabbing a granola bar or two from a Mozilla kitchen before departing. They are bound to be healthier than anything you find in the minibar late night. <br /> * Every hotel has a bucket of standard toiletry items (toothbrush, razor, &amp;c). You should have a toiletry bag stocked and ready to go (see above) but if you find yourself missing something, just call the front desk.<br /> * Likewise, every hotel has a bucket of left-behind chargers/power cables.<br /> * Set your climate controls when you first get into the room. Forgetting until you come back after dinner ready for sleep and finding the room is hot and stale is no fun.<br /> * Some hotels won’t let the climate controls work unless your room keycard is stuck into a switch by the door. This isn’t a magstripe reader, it’s just a physical switch - use a business card or a folded up piece of paper (or your library card) and have your room the way you want it.<br /> * If the drapes that don't quite meet, and therefore let in unwanted sunlight or street light, use one or two big binder clips to keep the drapes closed.<br /> * You can usually get a later check-out time just by asking. This doesn't work indefinitely, but they can't clean every room at once, so asking for 1pm instead of 11am just means they move your room to the bottom of the list for cleaning that day.<br /> * Repack for departure before you go to sleep, except for the clothes and toiletries you'll need in the morning. That way, if you oversleep for whatever reason, you can throw on your clothes, grab those last items, and go without wasting any more time.<br /> * To avoid leaving things behind:<br /> ** Bring your original packing checklist, and use it to repack.<br /> ** Pull all the linens off the bed and throw all used towels into the shower, so you're sure nothing's hidden, and check every wall socket for chargers.<br /> ** If you unpack into drawers, check every drawer before you leave.<br /> <br /> == Pick a hotel, get into the frequent guest program ==<br /> <br /> Same deal as airlines. At the least, it eventually adds up to free stays, but getting to status means room upgrades, easier check-in, more flexibility on check-in/check-out times, and extra points for each stay. Some hotel loyalty points can also be transferred to airline loyalty programs.<br /> <br /> It can be harder to consistently stay with the same hotel group than to consistently fly the same airline (they're sold out or not convenient, the conference hotel is elsewhere, etc.). However, it's good to join the loyalty program for any hotel you stay at, before you make your reservation. You may get a better rate or a better room. Hotel staff seem to give an extra measure of courtesy and consideration when you're in the loyalty program. (When booking by phone, I've had a &quot;sold out&quot; group rate suddenly become available when I gave my membership number.) If you haven't joined by the time you check in, ask the clerk to sign you up; they'll get credit for signing you up, and will be even more inclined to treat you nicely.<br /> <br /> Linked below are the programs associated with the hotels that are typically used for visiting Mozilla in Mountain View.<br /> <br /> {|<br /> |-<br /> |Holiday Inn Express<br /> |[http://www.priorityclub.com/ Priority Club]<br /> |<br /> |-<br /> |Avante/Wild Palms<br /> |[http://www.joyoflifeclub.com/ Joy of Life Club]<br /> |(Does not give points for stays that are paid through corporate billing.)<br /> |}<br /> <br /> == Choose Your Room ==<br /> <br /> It's a good practice to indicate that you have any preference on your room at all. Put this into your loyalty program profile and your travel agency profile (Egencia, for Mozilla employees), so it's transmitted with your reservation. If you have no preference, they will put you in the room for people who do not indicate a preference. You know, the one in the basement. With the leaky faucet and carpet from 1973. <br /> <br /> If you have a choice between one or two beds, choose two, even though you'll only use one for sleeping. The other one makes a great surface for spreading out your stuff. Often, hotel beds are on casters, so you can shove the extra bed against the wall, to prevent stuff falling between the bed and the wall.<br /> <br /> Generally, you'll do well to ask for a high floor and a room away from the elevator. Many hotels do renovations by floor starting from the top and working their way down. So high floors have a better chance of being recently renovated. They are also further away from street noise or the bar in the atrium. A room away from the elevator means less foot traffic and not waking up at 5am to repeated &quot;ding!&quot; of the elevator door opening. For motels, you want upstairs (less foot traffic) and outside (away from the courtyard with the pool).<br /> <br /> If the room is awful, don't be afraid to walk back downstairs and see if they have anything a bit more updated. If the whole hotel is awful, check your luggage at the desk and walk in a square block radius around the hotel to see if there's something less frightening. <br /> <br /> Never pick a hotel based on a picture of the lobby. Lobbies are always the first thing to get renovated.<br /> <br /> == Tipping Hotel Staff ==<br /> If you believe in tipping (which varies across cultures):<br /> * If you take a hotel shuttle from the airport, be sure to tip the shuttle driver. Don't just hand it to them and walk away; look them in the eye and express genuine appreciation for their service while you give them the tip. This is your first contact with the hotel staff, and if you make a good impression, word will spread to the other staff, and you'll get great service throughout your stay. This driver may also be the person who gets you to your outbound flight, through heavy traffic, just in the nick of time.<br /> * Similarly, leave a tip for housekeeping after the first night. This paves the way for good service when you make special requests, such as extra towels or toiletries, or to come back later because you're still in the room. Leave the money on top of a note that says at least &quot;Thanks!&quot; so the housekeeper knows it's for them.<br /> <br /> = Money =<br /> <br /> * Exchange: Do not change money at the airport. The rates are higher there than anywhere else. If you have a local bureau de change, use that, or order currency online for pickup at the airport. If you can find a company that does that (Travelex in the UK, at least) the rates will be much better than those posted on the wall that they charge you when you are a captive customer. The best rates are likely to be had by using an ATM. <br /> * Debit: Using an ATM card can be an easy and inexpensive way to secure some local currency. Make sure your card will work abroad before you travel. Common ATM networks that are broadly available include Pulse and Plus. Consider getting a debit card with no foreign transaction fees (Charles Schwab offers one).<br /> * Stay organized: It's helpful to keep your currency separate from your home currency, particularly if you're going to cycle through multiple currencies during your trip (usd &gt; euro &gt; pounds). Don't underestimate the power of a ziploc baggie if you're American and unaccustomed to coinage-heavy currencies.<br /> <br /> == Credit cards ==<br /> The US has historically had a different system (magnetic strips) for credit card security from the rest of the world (which uses the chip-and-pin system). This can cause headaches for both Americans traveling abroad, and others traveling to the US, as the systems are incompatible. Most US stores now support chip-and-signature cards, but you might run into smaller ones that don't have chip-reading equipment (e.g., a food truck using Square). <br /> <br /> * A very few US banks offer true chip-and-pin cards, including Citibank and [https://www.andrewsfcu.org/credit_cards_and_loans/credit_cards/globetrek_rewards.html Andrews Federal Credit Union]. The latter also has no annual fee and no international transaction fees. See this extensive but not exhaustive [http://thepointsguy.com/2013/05/us-credit-cards-with-smart-chips/ list of US-based chip-and-pin cards]. <br /> * You can get a pre-paid, reloadable chip-and-pin card called [http://www.cashpassport.com/1/travelex/ &quot;Cash Passport&quot;] from Travelex. You can buy it and reload it online or at Travelex locations in the US. You can load it in multiple currencies: GBP, EUR, CAD, AUD and JPY. The security seems a bit crappy (you can't change the PIN, and their only security question is mother's maiden name), but since it's pre-paid, you can limit your financial exposure, and reload online as needed.<br /> <br /> Another issue for travelers is transaction fees when making purchases in currencies other than your home currency; these can range from 1% up to as much as 7%. US-based credit cards that don't charge international transaction fees include CapitalOne and Andrews FCU.<br /> <br /> More and more US retailers have card readers that accept chip-based cards, so the situation is improving for visitors to the US. However, they probably don't understand the PIN system, so you will still need to sign (either on the reader, or on paper).<br /> <br /> = Preparing to be less-online than normal =<br /> <br /> If your cellphone plan doesn't have reasonable data roaming, or if you might be in areas with poor cell coverage, you should be prepared to survive without your usual data connection. This might include things like:<br /> * downloading offline maps in advance. ([http://maps.me/ maps.me] for Android and iOS lets you download offline OpenStreetMap maps by country or part-of-country.)<br /> * knowing where you're going to need to be (hotels, meeting locations) before you leave<br /> <br /> = On Foreign Soil =<br /> <br /> * Data/Voice rates<br /> ** You can use Skype to call US 1-800 numbers toll free from anywhere in the world.<br /> ** Before you leave your home country, add $20-40 of SkypeOut credits to your account. While Skype to Skype calls are free, SkypeOut credits will let you call any number internationally for about $.02 per minute.<br /> ** International text messages are typically NOT covered under your mobile plan. For US cell plans, it's usually about $.50 per SMS. If you have a good international rate, think long and hard about when you use SMS and why. A conversation about when you landed and where to meet and what time to get there on SMS may be more than a 2 minute call that covers the same details.<br /> ** [http://readwrite.com/2014/06/17/5-secrets-avoiding-hefty-international-data-roaming-charges-fees 5 secrets to avoiding hefty international data roaming fees] <br /> * Finding wifi<br /> ** In airports, airlines' priority lounges often have no wifi password, and you can access their hotspots from outside the lounge. (See note above for JFK airport.)<br /> ** Starbucks, McDonalds, and Burger King are sadly ubiquitous, and often have free wifi.<br /> ** You can sometimes find the password for a business's wifi in the comments for that business on FourSquare.<br /> * Language barriers<br /> ** Grab some business cards or stationery with your hotel's address on them before you head out. You can hand one to a cabbie whose language you do not speak, to get yourself back to home base. <br /> <br /> Still to write/update:<br /> * Language barriers<br /> ** Add Line2 details...<br /> <br /> ==Coping with jet lag==<br /> * Do not go to sleep. Do not nap. Stay up as long as you possibly can. Eat meals at local times and get into bed when it's dark outside. It will hurt on day one but by day three, you'll be glad you did. <br /> * If you absolutely must sleep, do a 20 minute powernap and then get up, walk around, and do not fall back to sleep. (Powernapping pro tip: [https://www.vox.com/2014/8/28/6074177/coffee-naps-caffeine-science take a &quot;coffee nap&quot;]: quickly drink a cup of coffee, and ''then'' take a nap; the coffee will wake you up in a short while, and you'll be more alert than with a nap or a coffee alone.) <br /> * In a pinch, Benedryl (dipenhydramine) can help you reset your internal clock and it's substantially gentler on your system than the prescription sleep aids. (It's also good for nausea if you get motion sickness, and of course, allergic reactions.)<br /> * If you find yourself awake when you should be sleeping (by local time), avoid bright screens (computers, phones, e-readers), because they activate wakefulness in your brain. Try reading a paper book or magazine (radical, I know). If you must use a screen, set it to white text on a black background, to reduce the overall brightness; or get an app (such as [https://justgetflux.com/ f.lux] for Mac/iOS or [https://play.google.com/store/apps/details?id=com.urbandroid.lux Twilight] for Android) that reduces the amount of blue light emitted by your device at night.<br /> * If possible, follow the [http://www.wikihow.com/Prevent-Jet-Lag-with-a-Modified-Diet Anti-Jet Lag Diet]; this is easier to do at home than while traveling, but IME even an approximation helps. <br /> ** As an abbreviated version: eat as little as possible on your day of travel, avoiding caffeine and alcohol; eat a high-protein breakfast at breakfast time in your new time zone.<br /> ** Bring protein bars with you to ensure that you can get protein at the right time.<br /> <br /> = Transportation =<br /> <br /> '''Quick Tips'''<br /> * Talk to cabbies. Not only do they know their city, they are less likely to have kickbacks in place than the hotel concierge, more likely to give you good answers.<br /> * Learn the taxi rules. Las Vegas doesn’t let you hail cabs on the street (creates traffic problems). New York cabs have credit card swipes in the back seat, whereas DC cabs just started actually using their meters at all. San Francisco cabs won’t let you exit except curbside.<br /> <br /> Still to write:<br /> * public transit<br /> * hotel shuttles<br /> <br /> == Rental Cars ==<br /> <br /> === Enterprise Rent-a-Car ===<br /> <br /> Mozilla's preferred vendor<br /> <br /> === Hertz ===<br /> <br /> If for some reason you end up with Hertz (late evening arrivals mean Enterprise might be closed) you'll want to sign up for [[HertzBusinessAccountProgram|Hertz #1 Gold]] and use that. At most airports, you walk in, your name is on a board with a parking spot number, and the keys and contract are already in the car waiting for you. Really nice after a 5+ hour flight!<br /> <br /> = Eating =<br /> <br /> Eat like a local.<br /> <br /> Never ask the front desk at your hotel for a dinner recommendation. If possible, ask anyone else to weigh in. The bellhop, your taxi driver, the barista at Starbucks, Yelp, Chowhound, etc. The best recommendations come from people who are actually living and working in the area. (TripAdvisor tells you what people who ''don't'' live there think.) The concierge at the hotel will always orient toward broad, tourist-pacifying tastes. The food will be edible, but forgettable. They'll never tell you about the super tasty hole-in-the-wall joint three blocks away.<br /> <br /> = Staying healthy =<br /> * Wash hands frequently! <br /> * Carry and use hand-sanitizer wipes. (A bottle of hand-sanitizer gel takes up valuable room in your liquids bag.) Sanitize your hands in-flight before you eat or drink, and after washing your hands in the lavatory (on-board water, again). Also use them to wipe off [http://www.travelmath.com/feature/airline-hygiene-exposed/ tray tables, seatbelt buckles, and air vents], where germs lurk on airplanes.<br /> * Set the fan above your seat on the plane to low or medium, and position it to blow into your lap, just in front of your face. This will help knock airborne pathogens out of the air, so you'll be less likely to breathe them in. ([http://www.npr.org/blogs/goatsandsoda/2014/07/14/319194689/pathogens-on-a-plane-how-to-stay-healthy-in-flight?ft=1 (NPR) Pathogens on a plane: how to stay healthy in flight])<br /> * Keep your exercise routine as much as possible. Exercise burns calories, relieves stress, and helps reset your body clock, if you're in a different time zone.<br /> ** Pick a hotel that has a fitness center. If you must use a hotel that doesn't have one (or you need specific equipment, like a stationary bike) call and ask; they may have an arrangement with a nearby gym.<br /> ** If you're out of luck on the fitness center, bring an exercise DVD, and/or small lightweight equipment like a jump rope or tension bands. Or do a [http://well.blogs.nytimes.com/2013/05/09/the-scientific-7-minute-workout/ body-weight-only exercise routine].<br /> ** Bring quick-drying workout clothes. Rinse them in the shower, and dry them over the shower rod, so they're ready for tomorrow.<br /> ** Bring athletic shoes that double as casual street shoes, so you don't need to take up luggage space with extra shoes.<br /> ** See the Quartz [http://qz.com/287800/the-complete-guide-to-staying-in-shape-on-the-road/ Complete guide to staying in shape on the road].<br /> <br /> = Redux =<br /> <br /> '''Most people travel infrequently, and aren’t very skilled at it...'''<br /> * and there are a lot of people, so despite the infrequency of their travel, the Don’t Know path is very crowded<br /> * Businesses on the Don’t Know path have no loyalty to you (since infrequent travellers have no meaningful loyalty to them) so their main goal is to extract money from you immediately, even at the cost of the relationship<br /> * People on the Don’t Know path have to deal with the same Don’t Know problems every single day, which is exhausting and saps their empathy<br /> <br /> '''BUT - If you know what you’re doing...'''<br /> * You can shortcut around the Don’t Know path everywhere. Airports, Hotels, Restaurants<br /> * The businesses you deal with will view you as a regular, and want to keep you happy<br /> * The people you deal with will view you as a breath of fresh air, and feel understood, and be grateful and human in the ways that travel never is for others.<br /> <br /> = More advice =<br /> * [http://www.jonobacon.org/2016/08/10/the-bacon-travel-survival-guide/ Travel Survival Guide] by Jono Bacon<br /> * [http://christianheilmann.com/2014/02/16/how-i-save-money-when-traveling-for-work-san-franciscovalleyus/ How I save money when traveling for work] by Christian Heilmann<br /> <br /> These podcasts have some excellent advice on business travel:<br /> * [http://www.manager-tools.com/2009/07/airline-travel-basics-1-part-1 Airline Travel Basics, part 1]<br /> * [http://www.manager-tools.com/2009/08/airline-travel-basics-1-part-2 Airline Travel Basics, part 2]<br /> * [http://www.manager-tools.com/2008/08/business-travel-packing Business Travel Packing]<br /> * [http://www.manager-tools.com/2009/07/travel-airline-seats Travel - Airline Seats]<br /> <br /> The what and how of packing only a carry-on: [http://www.onebag.com/ Onebag.com]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1240564 2022-02-11T18:00:08Z

<p>Mhoye: </p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communication, and Mozilla's preferred open discussion platform.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that the great majority of the rooms on our Matrix instance, like Bugzilla and Discourse, are public-facing forums that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://chat.mozilla.org/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account and (where relevant) invite your new account into conversations you'd like to continue, using your old account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> * [https://nheko-reborn.github.io/ Nheko Reborn] (Windows, Linux and macOS)<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> === Creating a new room ===<br /> <br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). <br /> <br /> On creation, you can make the decision of whether or not your room should be publicly discoverable or use end-to-end (&quot;E2E&quot;) encryption; for public rooms intended to involve community participation, we recommend *not* enabling E2E, as that enables new participants to see scrollback. A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> Any public room on the server should also invite the moderator account, and provide it the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG] and let site moderators support you in the process.<br /> <br /> Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective defense options Matrix provides.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> ==== Mozilla offices ====<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> ==== Local communities ====<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - ''Communauté Mozilla francophone'' — French-speaking Mozilla community ([https://mozfr.org/ mozfr.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - ''Deutschsprachige Mozilla-Community'' — German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - ''Comunidad en español de Mozilla'' ([https://www.mozilla-hispano.org/ mozilla-hispano.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - ''Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla''<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - ''Comunidad Mozilla en España''<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====German====<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] – Deutschsprachige Mozilla-Community<br /> * [https://chat.mozilla.org/#/room/#firefox.de:mozilla.org #firefox.de:mozilla.org] - Deutschsprachiger Firefox-Chat<br /> * [https://chat.mozilla.org/#/room/#common-voice-de:mozilla.org #common-voice-de:mozilla.org] - Alles rund um Common Voice auf Deutsch<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> ====Spanish====<br /> * [https://matrix.to/#/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] – Spanish-speaking community / Canal para hispanohablantes<br /> * [https://matrix.to/#/#spain:mozilla.org #spain:mozilla.org] – Spanish community (Spain) / Canal enfocado en España<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Community_Hardware&diff=1239362 2021-12-03T14:53:29Z

<p>Mhoye: Note that the program is on hiatus.</p> <hr /> <div>== Overview ==<br /> <br /> Currently, this program is on hiatus until our offices re-open and our hardware stocks are replenished. We appreciate your patience.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Add-ons/Reviewers&diff=1238919 2021-11-08T17:29:18Z

<p>Mhoye: /* Please hold. */</p> <hr /> <div><br /> <br /> While we're grateful for your interest, the Addons Community Reviewer program is currently on hiatus. We'll make an announcement in the Addons forum on Discourse.Mozilla.org when we have more to share.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Add-ons/Reviewers/Applying&diff=1238918 2021-11-08T17:28:48Z

<p>Mhoye: </p> <hr /> <div><br /> While we're grateful for your interest, the Addons Community Reviewer program is currently on hiatus. We'll make an announcement in the Addons forum on Discourse.Mozilla.org when we have more to share.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Add-ons/Reviewers/Applying&diff=1238917 2021-11-08T17:01:50Z

<p>Mhoye: </p> <hr /> <div><br /> While we're grateful for your interest, the Addons Community reviewer program is currently on hiatus.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Modules/Activities&diff=1235972 2021-06-07T16:35:06Z

<p>Mhoye: Consolidating commit access policy and implementation into a single Commit Access Management module.</p> <hr /> <div>&lt;noinclude&gt;<br /> '''Only module owners may edit this page.''' <br /> <br /> They may:<br /> <br /> * update any information about their module except the name of the owner<br /> * add or remove sub-modules<br /> * change the owner of a sub-module <br /> * add emeritus owners or peers<br /> <br /> Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br /> &lt;/noinclude&gt;<br /> {{Module<br /> |name=Governance<br /> |description=Policies and process for how we distribute authority and govern ourselves; including:<br /> * Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br /> * Management of the source tree<br /> * Balancing different constituencies of the Mozilla project<br /> * Maintaining the Mozilla identity as we take on new activities<br /> <br /> [http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=governance<br /> |url=https://wiki.mozilla.org/GovernanceIssues<br /> |components=mozilla.org::Governance<br /> }}<br /> <br /> ===Governance Sub Modules===<br /> <br /> {{Module<br /> |name=Module Ownership System<br /> |description=Healthy operation of the module ownership system, including topics such as:<br /> * Filling vacant roles where appropriate<br /> * Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br /> * Creating and staffing new modules where new parts of the project evolve.<br /> * Figuring out what to do if a module isn't getting enough attention<br /> * Resolving conflicts among module owners <br /> |owner= [mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker], Guillermo Movia (as 'observer'. This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br /> |ownersemeritus=Brendan Eich<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Commit Access Management<br /> |description= Governance structure for the work of implementing, managing and enforcing Mozilla's commit access systems and policies.<br /> |owner=[mailto:glob@mozilla.com Byron Jones (&quot;glob&quot;)]<br /> |peers=[mailto:mconnor@mozilla.com Mike Connor], [mailto:jlin@mozilla.com Johnathan Lin], [mailto:mhoye@mozilla.com Mike Hoye]<br /> |ownersemeritus=Mitchell Baker, Josh Matthews<br /> |peersemeritus=Marcia Knous<br /> |group=<br /> |url=http://www.mozilla.org/hacking/committer/<br /> |components=mozilla.org::Repository Account Requests<br /> }}<br /> <br /> {{Module<br /> |name=Security Policy<br /> |description=Policies for handling security issues in Mozilla code<br /> |owner=[mailto:dveditz@mozilla.com Dan Veditz]<br /> |peers=[mailto:security@mozilla.org Tom Ritter]<br /> |peersemeritus= Al Billings<br /> |group=dev-security<br /> |url=http://www.mozilla.org/security/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla CA Certificate Policy<br /> |description=Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies.<br /> |owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |peers=[mailto:bwilson@mozilla.com Ben Wilson]<br /> |ownersemeritus=Frank Hecker, Wayne Thayer<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer<br /> |group=dev-security-policy<br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Code Review Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=<br /> |url=http://www.mozilla.org/hacking/reviewers.html<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Performance Regression Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |group=<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Planet Mozilla<br /> |description=Content and policy for planet.mozilla.org, including topics such as:<br /> * which blogs are syndicated to planet.mozilla.org<br /> * which content from syndicated blogs is included<br /> * other planet.mozilla.org policy issues <br /> |owner=[mailto:mhoye@mozilla.com Mike Hoye]<br /> |peers=[mailto:asa@mozilla.org Asa Dotzler]<br /> |group=<br /> |url=<br /> |components=Websites::planet.mozilla.org<br /> |ownersemeritus=Robert Accettura<br /> |peersemeritus=Reed Loden<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla Public License<br /> |description=Maintenance and development of the MPL<br /> * changes in the legal landscape which could /should be reflected<br /> * changes in FLOSS development practices which could / should be reflected <br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br /> |peersemeritus=Gervase Markham<br /> |group=governance-mpl-update<br /> |url=<br /> |components=mozilla.org::Licensing<br /> }}<br /> <br /> {{Module<br /> |name=CA Certificates<br /> |description=Determine which root certificates should be included in Mozilla software products, which trust bits should be set on them, and which of them should be enabled for EV treatment. Evaluate requests from Certification Authorities (CAs) for inclusion or removal of root certificates, and for updating trust bit settings or enabling EV treatment for already included root certificates.<br /> |owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |peers=[mailto:bwilson@mozilla.com Ben Wilson]<br /> |ownersemeritus=Frank Hecker<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Ryan Sleevi<br /> |group=dev-security-policy <br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=mozilla.org::CA Certificates<br /> }}<br /> <br /> {{Module<br /> |name=Participation Metrics<br /> |description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br /> * determining which questions are most important to ask (how many people do X?)<br /> * determining what data is relevant to answer these questions<br /> * designing and operating a system to generate the requested data<br /> * analyzing the resulting metrics<br /> * notifying appropriate people when participation starts to change significantly<br /> * assisting various groups to understand and use the metrics to strengthen participation<br /> * produce periodic report/analysis of participation metrics <br /> |owner=[mailto:ppapadeas@mozilla.com Pierros Papadeas]<br /> |peers=[mailto:dboswell@mozilla.com David Boswell], [mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]<br /> |group=<br /> |url=https://wiki.mozilla.org/Contribute/Dashboards<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Internet Public Policy<br /> |description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: &quot;courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives.&quot; <br /> This includes topics such as:<br /> *determining if Mozilla should take an official position on a particular public policy issue<br /> *determining what that position is <br /> *determining how mozilla communicates our position <br /> **global, multi-regional, regional or local action<br /> **direct action, or support of action by other aligned groups<br /> **public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD<br /> *strengthening local community capabilities to address public policy issues <br /> |owner=[mailto:handerson@mozilla.com Harvey Anderson]<br /> |peers=[mailto:mitchell@mozilla.org Mitchell Baker], [mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman]<br /> |url=https://wiki.mozilla.org/Netpolicy<br /> |group=https://mail.mozilla.org/listinfo/netpolicy<br /> |components=<br /> |notes=Area Expert Advisors: Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos<br /> }}<br /> Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not. <br /> <br /> <br /> {{Module<br /> |name=Weekly Project All Hands Meeting<br /> |description=Responsibility for the weekly meetings, including:<br /> * determining and implementing the best organization and structure for the meeting<br /> * Determining and implementing the most useful content<br /> * Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br /> |owner=[mailto:asa@mozilla.org Asa Dotzler]<br /> |peers=MoCo Desktop IT services<br /> |ownersemeritus=[mailto:potch@mozilla.com Matt Claypotch]<br /> |group=mozilla.governance<br /> |url=https://wiki.mozilla.org/WeeklyUpdates<br /> |components=<br /> }}<br /> <br /> (It's a new thing to have a group such as &quot;MoCo Desktop IT services&quot; as a<br /> &quot;peer.&quot; We're trying this based on the idea that anyone in the Desktop IT group<br /> should be able to resolve problems and make fixes to the systems.)<br /> <br /> ===Other===<br /> <br /> {{Module<br /> |name=Tree Sheriffs<br /> |description=Tree Sheriffs aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. <br /> |owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen] (:RyanVM)<br /> |peers=[mailto:shengst@mozilla.com Sebastian Hengst] (:Aryx)<br /> |ownersemeritus=Ed Morley<br /> |peersemeritus=Carsten Book, Wes Kocher<br /> |group=https://mail.mozilla.org/listinfo/sheriffs<br /> |url=https://wiki.mozilla.org/Sheriffing<br /> }}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1234639 2021-03-24T20:51:33Z

<p>Mhoye: /* &quot;What is the Matrix?&quot; */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communication, and Mozilla's preferred open discussion platform.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that the great majority of the rooms on our Matrix instance, like Bugzilla and Discourse, are public-facing forums that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> === Creating a new room ===<br /> <br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). <br /> <br /> On creation, you can make the decision of whether or not your room should be publicly discoverable or use end-to-end (&quot;E2E&quot;) encryption; for public rooms intended to involve community participation, we recommend *not* enabling E2E, as that enables new participants to see scrollback. A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> Any public room on the server should also invite the moderator account, and provide it the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG] and let site moderators support you in the process.<br /> <br /> Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective defense options Matrix provides.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> ==== Mozilla offices ====<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> ==== Local communities ====<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - ''Communauté Mozilla francophone'' — French-speaking Mozilla community ([https://mozfr.org/ mozfr.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - ''Deutschsprachige Mozilla-Community'' — German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - ''Comunidad en español de Mozilla'' ([https://www.mozilla-hispano.org/ mozilla-hispano.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - ''Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla''<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - ''Comunidad Mozilla en España''<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====German====<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] – Deutschsprachige Mozilla-Community<br /> * [https://chat.mozilla.org/#/room/#firefox.de:mozilla.org #firefox.de:mozilla.org] - Deutschsprachiger Firefox-Chat<br /> * [https://chat.mozilla.org/#/room/#common-voice-de:mozilla.org #common-voice-de:mozilla.org] - Alles rund um Common Voice auf Deutsch<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1233119 2021-01-14T17:52:53Z

<p>Mhoye: Added some details and moved the create-a-room page up.</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that the great majority of the rooms on our Matrix instance, like Bugzilla and Discourse, are public-facing forums that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> === Creating a new room ===<br /> <br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). <br /> <br /> On creation, you can make the decision of whether or not your room should be publicly discoverable or use end-to-end (&quot;E2E&quot;) encryption; for public rooms intended to involve community participation, we recommend *not* enabling E2E, as that enables new participants to see scrollback. A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> Any public room on the server should also invite the moderator account, and provide it the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG] and let site moderators support you in the process.<br /> <br /> Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective defense options Matrix provides.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> ==== Mozilla offices ====<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> ==== Local communities ====<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - ''Communauté Mozilla francophone'' — French-speaking Mozilla community ([https://mozfr.org/ mozfr.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - ''Deutschsprachige Mozilla-Community'' — German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - ''Comunidad en español de Mozilla'' ([https://www.mozilla-hispano.org/ mozilla-hispano.org])<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - ''Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla''<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - ''Comunidad Mozilla en España''<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====German====<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] – Deutschsprachige Mozilla-Community<br /> * [https://chat.mozilla.org/#/room/#firefox.de:mozilla.org #firefox.de:mozilla.org] - Deutschsprachiger Firefox-Chat<br /> * [https://chat.mozilla.org/#/room/#common-voice-de:mozilla.org #common-voice-de:mozilla.org] - Alles rund um Common Voice auf Deutsch<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1231825 2020-10-23T16:49:46Z

<p>Mhoye: /* Community Participation at Mozilla */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that the great majority of the rooms on our Matrix instance, like Bugzilla and Discourse, are public-facing forums that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - Deutschsprachige Mozilla-Community - German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - Comunidad Mozilla en España<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> === Guidelines for creating a new room ===<br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). Any public room on the server should invite the moderator account with the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG]. Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective-defense options Matrix provides.<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1231824 2020-10-23T16:48:54Z

<p>Mhoye: /* Community Participation at Mozilla */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that our Matrix instance, like Bugzilla and Discourse, is a public-facing forum that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - Deutschsprachige Mozilla-Community - German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - Comunidad Mozilla en España<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> === Guidelines for creating a new room ===<br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). Any public room on the server should invite the moderator account with the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG]. Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective-defense options Matrix provides.<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1231823 2020-10-23T16:48:33Z

<p>Mhoye: /* Community Participation at Mozilla */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation.<br /> <br /> Please note that Matrix, like Bugzilla and Discourse, is a public-facing forum that can be read anonymously, and should be considered a public place. Your participation in public rooms like Mozilla-General will be publicly visible. Some people create alternative accounts or log in with alternative email addresses for this reason. See [https://www.mozilla.org/privacy/websites/ Mozilla's Websites, Communications &amp; Cookies Privacy Notice] for more information on our privacy policies.<br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - Deutschsprachige Mozilla-Community - German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - Comunidad Mozilla en España<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> === Guidelines for creating a new room ===<br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). Any public room on the server should invite the moderator account with the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG]. Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective-defense options Matrix provides.<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1230551 2020-09-02T14:36:13Z

<p>Mhoye: /* Changing Accounts */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> In order to maintain continuity in conversations, you will need to export your encryption keys from the old account and import them into the new account. The options to do this are under your account settings, in Security And Privacy, under Cryptography near the bottom of that window.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click the compass icon &quot;Explore rooms&quot; in the upper left next to the search-bar and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - Deutschsprachige Mozilla-Community - German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - Comunidad Mozilla en España<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> === Guidelines for creating a new room ===<br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). Any public room on the server should invite the moderator account with the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG]. Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective-defense options Matrix provides.<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1229798 2020-08-04T18:17:40Z

<p>Mhoye: </p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://app.element.io/#/welcome Element webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by joining the [https://app.element.io/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://app.element.io/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; although many are [https://wiki.mozilla.org/Matrix#Commonly_used_rooms linked below]. In the meantime, those are friendly channels and the people there will be able to help you find your way around.<br /> <br /> You can join our rooms using Matrix via the [https://app.element.io Element web app], the [https://element.io Element native mobile app for your platform], or any other Matrix client.<br /> <br /> Using Element Web or Desktop you can view our room directory using the following steps:<br /> # Click on the Explore button<br /> [[File:Element Explore button.png|Element Explore button location|frame|none]]<br /> # Click on the dropdown that says &quot;Matrix rooms (yourserver.com)&quot;<br /> [[File:Matrix rooms dropdown.png|frame|none]]<br /> # Click Add a new server<br /> # Type in &lt;code&gt;mozilla.org&lt;/code&gt; and click Add<br /> Now you can view the Mozilla server's room directory and join a room.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> === Changing Accounts === <br /> <br /> While you can change your &quot;display name&quot; in Matrix, because of low-level design decisions in the Matrix protocol, accounts cannot be renamed nor can accounts names be re-used, and deactivating them is permanent. For most Matrix users this is not an issue, but accounts tied to SSO such as Mozilla's cannot be reassigned to new owners. Changing the address associated with an SSO-bound Matrix account cannot be done, so you'll need to create a new account for yourself and deactivate the old one if that's what intend.<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> The Mozilla Matrix server requires Single Sign-On. Clients which currently support Single Sign-On include:<br /> <br /> * Element, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://element.io/get-started download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Element Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> * [https://apps.apple.com/app/vector/id1083446067 Element iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> * [https://github.com/tulir/gomuks gomuks] a terminal client for Matrix<br /> * [https://github.com/quotient-im/Quaternion Quaternion] a Qt5-based client for Windows, Linux, and macOS<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> These details will be autofilled for you in most clients if you enter your full username (e.g. @susan:mozilla.org rather than susan) into the username field. In general it is preferable to do that rather than trying to remember what the homeserver URL is.<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click Explore in the upper left and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> ====Viewing Room Members====<br /> Once you have joined a room you can view the room members by clicking on the person icon in the top right. You may notice (depending on your client) that all members appear &quot;offline&quot; or greyed out, this is intentional as &quot;presence&quot; is not enabled for the Mozilla homeserver.<br /> <br /> See the field &quot;enable_presence_by_hs_url&quot; in the configuration file https://chat.mozilla.org/config.json<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Software Development ===<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#devtools:mozilla.org #devtools:mozilla.org] - Firefox Developer Tools discussion<br /> * [https://chat.mozilla.org/#/room/#basket:mozilla.org #basket:mozilla.org] - Development of basket.mozilla.org ([https://github.com/mozmeao/basket basket])<br /> * [https://chat.mozilla.org/#/room/#fxa:mozilla.org #fxa:mozilla.org] - Development of Firefox Accounts ([https://github.com/mozilla/fxa fxa])<br /> * [https://chat.mozilla.org/#/room/#pontoon:mozilla.org #pontoon:mozilla.org] - Development of pontoon.mozilla.org ([https://github.com/mozilla/pontoon Pontoon])<br /> * [https://chat.mozilla.org/#/room/#www:mozilla.org #www:mozilla.org] - Development of www.mozilla.org ([https://github.com/mozilla/bedrock bedrock])<br /> * [https://chat.mozilla.org/#/room/#maildev:mozilla.org #maildev:mozilla.org] - Development of Thunderbird ([https://www.thunderbird.net/ thunderbird])<br /> * [https://chat.mozilla.org/#/room/#seamonkey:mozilla.org #seamonkey:mozilla.org] - Development of SeaMonkey ([https://www.seamonkey-project.org/ SeaMonkey])<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#fx-desktop-community:mozilla.org #fx-desktop-community:mozilla.org] - Discussion about Firefox Desktop<br /> * [https://chat.mozilla.org/#/room/#fx-android-community:mozilla.org #fx-android-community:mozilla.org] - Discussion about Firefox for Android<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> * [https://chat.mozilla.org/#/room/#accessibility:mozilla.org #accessibility:mozilla.org] Discussion of the accessibility (a11y) of Mozilla applications and services<br /> * [https://chat.mozilla.org/#/room/#addons:mozilla.org #addons:mozilla.org] Discussion about Firefox add-ons<br /> * [https://chat.mozilla.org/#/room/#nightly:mozilla.org #nightly:mozilla.org] Discussion about Firefox Nightly<br /> * [https://chat.mozilla.org/#/room/#SUMO:mozilla.org #SUMO:mozilla.org] Discussion about Mozilla Support<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#atlanta:mozilla.org #atlanta:mozilla.org] - General chat for the Mozilla community in and around Atlanta, GA, USA<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#mozilla.de:mozilla.org #mozilla.de:mozilla.org] - Deutschsprachige Mozilla-Community - German-speaking Mozilla community<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#mozilla-japan:mozilla.org #mozilla-japan:mozilla.org] - General chat for the Mozilla Japan Community<br /> * [https://chat.mozilla.org/#/room/#mozilla-uk:mozilla.org #mozilla-uk:mozilla.org] - General chat for the Mozilla UK Community<br /> * [https://chat.mozilla.org/#/room/#moztw:mozilla.org #moztw:mozilla.org] - General chat for the Taiwan Community<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> * [https://chat.mozilla.org/#/room/#spain:mozilla.org #spain:mozilla.org] - Comunidad Mozilla en España<br /> * [https://chat.mozilla.org/#/room/#taipei:mozilla.org #taipei:mozilla.org] - General chat for people in the Taipei office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====French====<br /> <br /> * [https://github.com/mozfr/besogne/wiki/Matrix French-speaking community wiki page]<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> === Guidelines for creating a new room ===<br /> How you create a new room depends on your client ([https://element.io/help#rooms Element help]). Any public room on the server should invite the moderator account with the &lt;code&gt;admin&lt;/code&gt; role. This will help you administer the room in compliance with the [https://www.mozilla.org/en-US/about/governance/policies/participation/ CPG]. Providing access to the moderator account is a two step process:<br /> # Issue the invitation: &lt;code&gt;/invite @moderator:mozilla.org&lt;/code&gt;<br /> # After &lt;code&gt;@moderator:mozilla.org&lt;/code&gt; joins the room, grant them the admin role.<br /> <br /> A public room is one where anyone can join without an invite. I.e. the &quot;''only people who have been invited''&quot; option has not been enabled.<br /> <br /> While the Moderator account with only &quot;mod&quot; privileges lets us protect channels against individual bad actors, it does not give that account the access needed to change channel-wide access control lists. You need to grant the Moderator &quot;admin&quot; privileges to be able to take advantage of the collective-defense options Matrix provides.<br /> <br /> == Feedback ==<br /> For feedback on Element and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=IRC&diff=1227484 2020-05-22T19:55:28Z

<p>Mhoye: Clarifying the IRC shutdown.</p> <hr /> <div>{{outdated}}<br /> <br /> = As of March 2020, IRC.mozilla.org has been permanently decommissioned =<br /> <br /> As of 2nd March 2020, Mozilla has moved away from IRC to [[Matrix]] for its public channels and the IRC server was shut down.<br /> <br /> This page is being retained for historical and reference purposes only.<br /> <br /> <br /> &lt;div style=&quot;float:right; margin-left:2.5em&quot;&gt;__TOC__&lt;/div&gt;<br /> ==Getting Started ==<br /> IRC stands for &quot;Internet Relay Chat&quot;. It's a protocol for real-time chat sessions. (Read more [http://en.wikipedia.org/wiki/Irc about IRC on Wikipedia].) It was invented before the World Wide Web, so it was adopted by early open source contributors and Web developers, and it has been used by those communities ever since. Like email, no single company controls IRC. IRC servers are offered by many individuals and organizations. Users log in to a particular server to chat with other users on that server, using a client program designed for IRC; just as there are many programs for reading email, there are many different IRC client programs. Chat discussions take place in &quot;channels,&quot; which have names starting with a '#' symbol. <br /> <br /> Mozilla runs an IRC server to host channels for discussion of topics related to the Mozilla project.<br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors in IRC that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the channel moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> ===Pick an IRC client===<br /> <br /> There are several ways to participate in IRC and here are a some common options.<br /> <br /> ====Web clients====<br /> * [https://mibbit.com/ Mibbit] web-based chat client. <br /> * [https://kiwiirc.com/ Kiwi IRC] Open Source web-based chat client that works on mobile too.<br /> * [https://thelounge.chat/ The Lounge] is a self-hosted web IRC client.<br /> * [https://www.irccloud.com/ IRCCloud] is a great IRC app that is compatible with Android phones, iPhone, iPad, and iPod touch. Requires iOS 8 or later. It has both a free and a paid option.<br /> <br /> ====Desktop clients====<br /> * [https://konversation.kde.org/ Konversation] is a client for Linux, you can probably get it as a package from your distribution. Its look and feel is similar to that of ChatZilla while being built on [http://www.kde.org/ KDE].<br /> * [https://www.codeux.com/textual/ Textual] is an IRC client created specifically for macOS. Open source but paid on the App Store.<br /> * [https://irssi.org/ Irssi] Your text mode chatting application since 1999.<br /> * [https://weechat.org/ WeeChat] WeeChat is a fast, light and extensible chat client, with a text-based user interface.<br /> * [https://hexchat.github.io/ HexChat] is a great chat program for both Linux and Windows.<br /> * [https://www.mozilla.org/en-US/thunderbird/ Thunderbird] is a communication client made by Mozilla. As of version 15, it has IRC support.<br /> <br /> ====Mobile clients====<br /> =====iOS=====<br /> * [https://apps.apple.com/us/app/igloo-irc/id1331074069 Igloo IRC] The chillest IRC client<br /> * [https://apps.apple.com/us/app/palaver-irc/id538073623 Palaver IRC] is a modern IRC client for iPhone and iPad featuring a unique user interface which makes using IRC a pleasure. It fits you and your mobile devices perfectly..<br /> <br /> =====Android=====<br /> * [https://play.google.com/store/apps/details?id=io.mrarm.irc Revolution IRC Client] is the next-generation IRC client for Android, made with design and functionality in mind.<br /> * [https://play.google.com/store/apps/details?id=app.holoirc HoloIRC] is an [https://github.com/holoirc/HoloIRC open source] IRC client for Android.<br /> <br /> ====Clients that haven't received updates in a while====<br /> * [https://colloquy.info/ Colloquy] is a Mac client with a nice looking interface. It also has a mobile client for iPad/iPhone/iTouch.<br /> * [http://limechat.net/mac/ Limechat] is a cross-platform IRC client by Satoshi Nakagawa. Warning: main site is in Japanese, this is not just for Mac, there are [http://hp.vector.co.jp/authors/VA022249/files/lime218.exe Windows] and [http://limechat.net/iphone/ iOS] versions as well. A number of people have happily switched from Colloquy to Limechat.<br /> * [http://www.instantbird.com Instantbird] is a cross-platform multi-protocol instant messaging client based on Mozilla technologies (and libpurple from Pidgin) with an emphasis on simplicity and extensibility.<br /> * [https://www.yaaic.org/ Yaaic] is a free (as in freedom), multiserver, Android IRC client, now fully conformant with the UI style of the Iced Cream Sandwich (and later).<br /> <br /> See also [https://en.wikipedia.org/wiki/Comparison_of_IRC_clients Comparison of IRC clients] at Wikipedia.<br /> <br /> ===Connect to the Mozilla IRC server===<br /> <br /> The Mozilla IRC server settings are:<br /> Nickname: Your_IRC_nickname<br /> Server Protocol: IRC<br /> Chat Server: irc.mozilla.org<br /> Proxy: None<br /> Chat Server Port: 6697<br /> Chat Server Port for users of [https://bugzilla.mozilla.org/show_bug.cgi?id=716814 mobile carriers that block IRC (e.g. Verizon)] : 8443<br /> SSL Connection: Checked<br /> Server Password: [blank]<br /> Real Name: Your Name<br /> <br /> ====Mibbit==== <br /> * [https://chat.mibbit.com/?server=irc.mozilla.org:+6697 Click here to connect]<br /> * enter a nickname for yourself, then click GO (no channel needed at first, but you can put one in if you know where you're going)<br /> * look for a &quot;Mozilla&quot; tab right under the Mibbit logo and click on it (it doesn't come to the front automatically for some reason)<br /> [[File:mibbit_connection.png|400px]]<br /> <br /> ====Colloquy====<br /> Set up a connection as per the screenshot and hit 'connect':<br /> <br /> [[File:create_connection_colloquy.png|400px]]<br /> <br /> ====Chatzilla ====<br /> Use the &lt;tt&gt;/networks&lt;/tt&gt; command to display the list of predefined IRC networks. Click on &lt;tt&gt;moznet&lt;/tt&gt; in the list.<br /> <br /> [[File:chatzilla_networks.png|400px]]<br /> <br /> ====Andchat ====<br /> [[File:Andchat-mozilla-irc-setup.png|240px|right]]<br /> * Name : Mozilla<br /> * Address : &lt;b&gt;irc.mozilla.org&lt;/b&gt;<br /> * Port<br /> ** The normal port value is &lt;b&gt;6697&lt;/b&gt;<br /> ** [https://bugzilla.mozilla.org/show_bug.cgi?id=716814 Some mobile carriers (like Verizon)] block all common IRC ports. If this affects you, use port &lt;b&gt;8443&lt;/b&gt; instead<br /> * SSL : &lt;b&gt;checked&lt;/b&gt;<br /> * Nick 1 : Your_IRC_nickname<br /> NOTE : In 2012, Verizon blocked all access to irc.mozilla.org over cellular connections. Any connection attempts now get a 504 Gateway Timeout<br /> <br /> === Nicknames ===<br /> ====Choosing a nickname====<br /> Nicknames on IRC can become a major part of your identity if you spend a significant amount of time talking with people in IRC. Sometimes you may even find that people in real life call you by your IRC handle. If you're having trouble coming up with a catchy nickname or if you're concerned about getting stuck with something that seems funny now but will be tiresome to you in a few weeks, a good way to create a nickname is to take the first letter of your first and most or all of your last name to make a nick that people will recognize as you.<br /> <br /> Often in IRC people look for others by using tab complete so if someone's name is John they might type a 'j' and then tab several times to see who's in the channel whose name starts with a 'j'.<br /> <br /> Using just your first name can also be a good option, if it's unique. But:<br /> # Beware that IRC &quot;seems&quot; case-sensitive but actually isn't: e.g. &lt;tt&gt;/whois mossop&lt;/tt&gt; (all lowercase) will return info on Mossop (with initial capital) if he's online, and &lt;tt&gt;/nick mossop&lt;/tt&gt; will either be refused (if Mossop is online) or make NickServ tell you that this nick is registered and that you should IDENTIFY with its password if it's yours (if he isn't). ([[#Register your nickname|See below]] about this NickServ stuff.)<br /> <br /> ====Set your nickname====<br /> Now that you're connected to the IRC server, you can set/register your nickname with Nickserv. If you’re going to be hanging around a lot (and we hope that you will!), you will want to register your nickname. That way, other people can’t pose as you on the channel and you can join password-protected channels. First, set your preferred nickname by either doing:<br /> <br /> /nick NICKNAME<br /> <br /> (where NICKNAME is the desired nickname); or if you are using a client you may have already set your nickname and/or can change it through the application's interface. Note that if someone has already registered your preferred nick, you’ll need to use a different one.<br /> <br /> ====Register your nickname====<br /> Once you have settled on a nickname here’s how to register:<br /> <br /> /nickserv register yourPassword yourEmailAccountName@yourMailProvider<br /> <br /> Email address is mandatory.<br /> <br /> Get the confirmation code from your email inbox. Type the following command and replace confirmation_code with the code sent to you in the email (NEVER replace the word &quot;nickserv&quot; in /msg nickserv ... with your nick). It has the template shown below. If you don't see our email in any folder (check spam too) you could try /nickserv resend .<br /> <br /> /nickserv confirm confirmation_code<br /> <br /> Congratulations! Your nickname is now registered if you see a message reply containing<br /> <br /> &quot;Your email address of [YourEmailAddress] has been confirmed&quot;.<br /> <br /> Next time you log on, you will need to identify yourself to nickserv as follows (&lt;u&gt;after&lt;/u&gt; you get the nickname):<br /> <br /> /msg nickserv identify [YOUR PASSWORD]<br /> <br /> Once you have identified yourself, you will be able to join password-protected irc channels and also, if needed, disconnect anyone using the nickname without the password. See &lt;tt&gt;/msg NickServ help&lt;/tt&gt; for details.<br /> <br /> ====Reset or change your Nickserv password====<br /> If you have forgotten your Nickserv password, you can have a reset password email sent to your registered email address:<br /> <br /> /msg nickserv resetpass [nickname] [YourEmailAddress]<br /> <br /> If you do remember your password and just want to change it (&lt;u&gt;after&lt;/u&gt; you identify with your nickname):<br /> <br /> /msg nickserv set password [new-password]<br /> <br /> === Interesting umodes ===<br /> Using the /umode command with one of the following parameters will cause the specified effect.<br /> * +B - Marks a user as a bot for /whois reporting purposes.<br /> * +x - Cloaking - Hide part of a user's hostname (on by default).<br /> * +c - Blocks private messages from everyone except for people that are in at least 1 channel with you.<br /> * +R - Blocks private messages from unregistered users.<br /> * +d - Deaf - Stop receiving channel messages &amp; notices. Useful if you want to silence all the channels you're in, but still be available for /msg.<br /> * +I - Hides the list of channels you're in from other users when they /whois you.<br /> <br /> === Joining Channels ===<br /> <br /> IRC channels are like 'rooms' where people talk or hang out. Their names begin with a # (octothorpe, hash, pound sign etc.). Do not confuse them with social media 'hashtags' :-)<br /> <br /> For most irc.mozilla.org channels you can join them with the following command:<br /> <br /> /join #channel_name<br /> <br /> This will open a tab, window or section in your IRC client that allows you to participate in discussions on that channel.<br /> <br /> For a password protected channel you need to include the password:<br /> <br /> /join #channel_name [CHANNEL PASSWORD]<br /> <br /> If doing this command does not open a new tab or otherwise allow you to enter the channel for discussion, please check the steps above about registering your nick and make sure you have identified yourself to Nickserv.<br /> <br /> ===Start a private message===<br /> You can start a private chat with another person who is also on irc.mozilla.org by doing<br /> <br /> /msg [other person's nickname] [initiating message, like 'hi']<br /> <br /> This creates a new tab or channel that is just between you and that person. You must have a message to create the new tab/room otherwise the /msg command will complain that there are not enough arguments.<br /> <br /> If you want to know if the person you're trying to chat with is in the room you can either enter the first letter of their nick and then hit tab to tab-complete all the nicks in the channel that start with this letter until you see the one you are looking for or you can use <br /> /names<br /> This will give you a list of all the people in the room you are currently in. To start a private chat, you must be in the room with someone. If you're not sure what room someone is in you can go to the main irc.mozilla.org tab/room and do<br /> <br /> /whois [other person's nickname] <br /> <br /> which will tell you (hopefully) their real name as well as list the channels they are currently in with that nick.<br /> <br /> ===Create your own channel===<br /> To start a channel for multiple people to hang out and chat in, create a unique channel like this:<br /> /j #my_channel_name<br /> <br /> Now you can tell all your friends, teammates, community members where to find the backchannel you've created!<br /> <br /> ===Registering a channel===<br /> If the channel you've created is going to be permanent, you'll want to register it with chanserv. Does 'chanserv' sound familiar? That's right - it works very much like 'nickserv' :)<br /> <br /> # eg: /msg chanserv register #moz-in-my-town &quot;a channel for people who work on mozilla and live in my town&quot;<br /> /msg chanserv REGISTER [channel name] [password (optional)] [description]<br /> <br /> ===Managing a channel===<br /> <br /> ====Managing channel operators====<br /> Now that you have registered your channel, let's add some users to assist with channel management. These users are called channel operators. They can be managed through chanserv:<br /> <br /> /msg chanserv aop #mychannel add nick<br /> /msg chanserv aop #mychannel del nick<br /> /msg chanserv aop #mychannel list<br /> <br /> ====Channel Modes====<br /> For a list of all channel modes supported by our IRC network, please visit [http://wiki.inspircd.org/2.0/Channel_Modes]. A list of particularly unique &amp; interesting channel modes follows.<br /> <br /> * +u - Auditorium mode - Hides everyone in a channel except yourself (potentially useful for #moco or #townhall).<br /> * +e - Ban exception - Same syntax as +b, but allows you to exclude someone from a ban.<br /> * +B - Block ALL CAPS MESSAGES.<br /> * +c - Block color messages.<br /> * +S - Strip color from messages.<br /> * +g - Message filtering using simple string matches. Example: '''/msg chanserv mode #channel lock add +g *candy*'''. Now, no one in #channel can use the word candy. Use multiple '''lock add''' commands to add more words. To see the list of banned words, omit the + symbol, e.g.: '''/mode #channel g'''.<br /> * +d - Silence join/part messages until the person speaks. Useful for channels with people who, e.g., IRC from their laptop and flood channels with join/quit messages every time they close their laptop.<br /> * +f - Flood protection - Example: '''/msg chanserv mode #channel lock add +f 7:3''' - If a user types 7 or more line within 3 seconds, they will be kicked. You can also do '''/msg chanserv mode #channel lock add +f *7:3''' to make them kickbanned instead of just kicked.<br /> * +j - Join Flood Protection - Example: '''/msg chanserv mode #channel lock add +j 20:5''' - If 20 or more clients join #channel within 5 seconds, the channel will be locked for 60 seconds, preventing anyone from joining.<br /> * +C - Stops users from using /ctcp on a channel<br /> * +Q - Prevents users from using /kick on a channel<br /> * +M - Prevents unregistered users to speak in a channel (vs +R that requires registration to even join)<br /> * +N - Prevents users from changing their nick while in a channel with +N set. Can also be used as an extban to prevent a specific user from changing their nick, e.g.: '''/msg chanserv mode #channel lock add +b N:lerxst!*@*''' would prevent lerxst from changing his nick to anything else.<br /> * +R - Requires users to be registered (and identified) before joining the channel<br /> * +T - Prevents users from using /notice on a channel. Also works as an extban (see +N for syntax)<br /> * +b m - Mute - Extban for preventing a user from speaking in channel. e.g.: '''/msg chanserv mode #channel lock add +b m:lerxst!*@*''' prevents lerxst from speaking #channel.<br /> * +l x - Limit - Prevents users from joining a channel if the number of clients exceeds x. Example: '''/msg chanserv mode #channel lock add +l 5''' prevents users from joining #channel if there are already 5 users present.<br /> * +L - Redirect - If a channel's limit is exceeded (via +l), this forces users to join the specified channel. Example: '''/msg chanserv mode #channel lock add +L #channel-overflow'''. If you want to redirect everyone attempting to join a channel, set +l to 0.<br /> * +z - SSL only - Users can only join a channel if they're connected via SSL<br /> <br /> Use chanserv to permanently set a channel's mode:<br /> <br /> /msg chanserv mode #mychannel lock add +-mode<br /> <br /> eg:<br /> <br /> /msg chanserv mode #mychannel lock add +R<br /> <br /> ===Changing the channel password===<br /> <br /> To set a password, use:<br /> <br /> /msg chanserv mode #mychannel set +k my-great-password<br /> <br /> ===Join some channels right now!===<br /> Being new to IRC can be intimidating. Mozilla's IRC channels are very friendly and welcoming but some of them are geared to teams trying to get things done where others are more relaxed and open to new folks giving IRC or other Mozilla tools a try.<br /> #mozillians - meet other Mozilla project folks all over the world<br /> #newbies - kind of self-explanatory, right?<br /> #introduction - a place to get started and be welcoming to new contributors<br /> #sf,#toronto - remote office's water-cooler hotspot for socializing and planning lunch<br /> <br /> ==Need General Help with IRC?==<br /> If you're able to connect to IRC and join channels, try asking for help in [ircs://irc.mozilla.org/introduction #introduction], [ircs://irc.mozilla.org/mozillians #mozillians], [ircs://irc.mozilla.org/newbies #newbies], [ircs://irc.mozilla.org/seneca #seneca] or [ircs://irc.mozilla.org/coding #coding]. The folks who hang out in those channels will be happy to help.<br /> <br /> You can also get help from IRC by doing:<br /> /help<br /> This will give you a list of all the IRC commands and then you can do /help [command] to get info on that particular command.<br /> &lt;pre&gt;<br /> Example:<br /> /help msg<br /> <br /> IRC returns:<br /> MSG [-&lt;server tag&gt;] [-channel | -nick] &lt;targets&gt; &lt;message&gt;<br /> Sends a message to a nick or a channel. <br /> Usually this is used for sending private messages to other persons.<br /> Examples:<br /> <br /> /MSG friend Hi, what's up?<br /> &lt;/pre&gt;<br /> You can also visit [http://irchelp.org irchelp.org] to learn about how IRC works, or find a client you can use to connect to the chat server.<br /> <br /> /!\ '''If you're using ChatZilla,''' note that &lt;tt&gt;/help&lt;/tt&gt; is a ChatZilla command which gets you a ChatZilla answer. In ChatZilla, &lt;tt&gt;/commands&lt;/tt&gt; returns the list of all known commands (including the aliases you defined yourself), and &lt;tt&gt;/help ''command''&lt;/tt&gt; (without the slash before ''command'') gives you help on ''/command''. These are usually enough, but you &lt;u&gt;can&lt;/u&gt; get help '''from the server''' when using ChatZilla, by using &lt;tt&gt;/quote help&lt;/tt&gt; or (on the Mozilla network) &lt;tt&gt;/helpop&lt;/tt&gt;<br /> <br /> ==How to ask questions on IRC==<br /> <br /> * Join a question-friendly channel like [ircs://irc.mozilla.org/introduction #introduction], [ircs://irc.mozilla.org/mozillians #mozillians], [ircs://irc.mozilla.org/newbies #newbies], [ircs://irc.mozilla.org/seneca #seneca] or [ircs://irc.mozilla.org/coding #coding].<br /> * Ask away! You don't have to ask permission to ask first. It is better to just blurt out your question, even though you don't know if anyone is paying attention.<br /> * Leave your IRC client open if nobody answers right away. Most of the folks on IRC do not spend all day watching their IRC client. They just leave it open while they're doing other things. It might be an hour before the right person notices your question. When answering someone's question, especially if there's a delay, the nick of the questioner should be used in the answer so that you'll see a highlighted line with their response. (eg: &quot;lsblakk: the answer is 42&quot;)<br /> * Be prepared to ask in several places. Very often the first response to a question is, &quot;I don't know, but you should ask that question in #developers or #devtools or #jsapi or any of a hundred other special-purpose channels. Over time, you'll get a better sense of which questions to ask where, but to start with, it's always OK to ask in #introduction.<br /> * Remember to be courteous. Don't repeat your question every time someone new enters the room. Don't individually ask everybody in the room if they know the answer. Don't type &lt;code&gt;helllooooooooo&lt;/code&gt;. And if someone is rude to you, please do the rest of us a favor and respond politely anyway.<br /> <br /> ==Commonly Used Mozilla IRC Channels==<br /> <br /> There are many different [https://wiki.mozilla.org/IRC irc channels] for various topics. If you have ChatZilla, you can just click the provided links below to join that particular channel. For other clients, connect to server irc.mozilla.org and type /join channelname, replacing channelname with the name of the channel (including the leading &quot;#&quot;). All channels use English unless otherwise specified.<br /> <br /> ===Development and Planning===<br /> <br /> These channels are frequently used for discussions regarding development and planning of Firefox and Thunderbird.<br /> <br /> ====Project Channels====<br /> * [ircs://irc.mozilla.org/firefox #firefox] - Firefox project discussion and end-user help. ''Another official #firefox channel is maintained on the [ircs://irc.freenode.net/firefox Freenode] network)<br /> * [ircs://irc.mozilla.org/accessibility #accessibility] - Discussion about accessibility in Mozilla applications - developers and end users welcome<br /> * [ircs://irc.mozilla.org/addons #addons] - End user support for add-ons, extensions, and themes<br /> * [ircs://irc.mozilla.org/addon-reviewers #addon-reviewers] - Support for add-on reviews<br /> * [ircs://irc.mozilla.org/amo #amo] - Development of the addons.mozilla.org (AMO) website<br /> * [ircs://irc.mozilla.org/balrog #balrog] - Balrog (Application Update Service) project discussion.<br /> * [ircs://irc.mozilla.org/bmo #bmo] - Bugzilla.Mozilla.Org discussion (mainly on #bugzilla below)<br /> * [ircs://irc.mozilla.org/bugzilla #bugzilla] - Bugzilla project discussion<br /> * [ircs://irc.mozilla.org/calendar #calendar] - Calendar project and Lightning. ''This addon is for Thunderbird and SeaMonkey while the freestanding Sunbird isn't actively developed.''<br /> * [ircs://irc.mozilla.org/chatzilla #chatzilla] - Discussion about ChatZilla, the IRC client extension<br /> * [ircs://irc.mozilla.org/firefoxstudents #firefoxstudents] - [[StudentAmbassadors|Student Ambassadors]] main channel<br /> * [ircs://irc.mozilla.org/instantbird #instantbird] - Instantbird project discussion<br /> * [ircs://irc.mozilla.org/js #js] - Discussion about JavaScript programming<br /> * [ircs://irc.mozilla.org/l10n #l10n] - Discussion about localization (l10n) of Mozilla applications<br /> * [ircs://irc.mozilla.org/mdn #mdn] - Discussion about developer documentation<br /> * [ircs://irc.mozilla.org/mdndev #mdndev] - Discussion about development of the documentation web site (Kuma platform)<br /> * [ircs://irc.mozilla.org/mozillazine #mozillazine] - Community for Users, Web Authors, and Testers; go here if you need help<br /> * [ircs://irc.mozilla.org/mozdev #mozdev] - Discussion of and support for free project hosting at mozdev.org<br /> * [ircs://irc.mozilla.org/mozwebqa #mozwebqa] - Home of Mozilla's web-testing efforts<br /> * [ircs://irc.mozilla.org/nightingale #nightingale] - Nightingale project discussion<br /> * [ircs://irc.mozilla.org/nightly #nightly] - Home of the Firefox [[Nightly|Nightly]] community<br /> * [ircs://irc.mozilla.org/qa #qa] - Mozilla QA Community of users and testers dedicated to improving the quality of Firefox and other Mozilla applications<br /> * [ircs://irc.mozilla.org/remo #remo] - [[ReMo|Mozilla Reps]] main channel<br /> * [ircs://irc.mozilla.org/remo-dev #remo-dev] - Discussion about webdev and planning of next Mozilla Reps web properties<br /> * [ircs://irc.mozilla.org/rust #rust] - General discussion about the Rust programming language<br /> * [ircs://irc.mozilla.org/rust-beginners #rust-beginners] - Discussion for beginners of the Rust programming language<br /> * [ircs://irc.mozilla.org/rust-gamedev #rust-gamedev] - Computer graphics and game development with Rust<br /> * [ircs://irc.mozilla.org/rust-internals #rust-internals] - Rust compiler and library development<br /> * [ircs://irc.mozilla.org/rust-osdev #rust-osdev] - Operating system development with Rust<br /> * [ircs://irc.mozilla.org/seamonkey #seamonkey] - Community project to revive the bundled application suite (The main channel is now [ircs://chat.freenode.net/seamonkey at Freenode].)<br /> * [ircs://irc.mozilla.org/servo #servo] - Development of a research web browser in Rust<br /> * [ircs://irc.mozilla.org/songbird #songbird] - Songbird project discussion<br /> * [ircs://irc.mozilla.org/sumo #sumo] - [[Support|Mozilla Support]] main channel<br /> * [ircs://irc.mozilla.org/sync #sync] - Discussion of [[CloudServices/Sync|Firefox Sync]], including self-hosting<br /> * [ircs://irc.mozilla.org/testpilot #testpilot] - Discussion about the [[Test Pilot]] project prototyping new features in Firefox.<br /> * [ircs://irc.mozilla.org/themedev #themedev] - Discussion about theme development<br /> * [ircs://irc.mozilla.org/thunderbird #thunderbird] - Thunderbird project discussion and end-user help<br /> * [ircs://irc.mozilla.org/tb-support-crew #tb-support-crew] - for Thunderbird support meta discussion NOT for Thunderbird support;<br /> ** ''informal'' companion IRC channel to the [[Thunderbird/tb-support-crew|tb-support-crew mailing list]]<br /> * [ircs://irc.mozilla.org/tb-qa #tb-qa] - QA Community of users and testers dedicated to improving the quality of Thunderbird<br /> * [ircs://irc.mozilla.org/transvision #transvision] - Transvision (l10n QA tool in PHP) project discussion<br /> * [ircs://irc.mozilla.org/webextensions #webextensions] - Webextensions addons and API dev<br /> * [ircs://irc.mozilla.org/webcompat #webcompat] - Home of Mozilla's [https://wiki.mozilla.org/Compatibility Web compatibility effort]<br /> * [ircs://irc.mozilla.org/webtools #webtools] - Bonsai, LXR, Tinderbox, and Mozbot project discussion<br /> * [ircs://irc.mozilla.org/womoz #womoz] - Women &amp; Mozilla Discussion channel<br /> * [ircs://irc.mozilla.org/xul #xul] - Discussion about the XUL interface specification language<br /> <br /> ====General Discussion====<br /> <br /> * [ircs://irc.mozilla.org/contributors #contributors] - A offtopic channel for all contributors to chat in and discuss their projects with each other (although this channel still exists, discussion has moved to [ircs://irc.mozilla.org/mozillians #mozillians])<br /> * [ircs://irc.mozilla.org/developers #developers] - general Firefox and Gecko development discussion<br /> * [ircs://irc.mozilla.org/planning #planning] - discussion of upcoming Firefox and Gecko branch and trunk releases<br /> <br /> ====Specific Areas====<br /> <br /> * [ircs://irc.mozilla.org/airmozilla #airmozilla] - discussion around https://air.mozilla.org/<br /> * [ircs://irc.mozilla.org/ateam #ateam] - Automation &amp; Tools development discussion<br /> * [ircs://irc.mozilla.org/audio #audio] - development discussion for audio specifically<br /> * [ircs://irc.mozilla.org/webmaker #badges] - discussion and support channel for the Mozilla Open Badges project<br /> * [ircs://irc.mozilla.org/bluetooth #bluetooth] - development discussion for bluetooth specifically<br /> * [ircs://irc.mozilla.org/build #build] - The build system - make/autoconf etc<br /> * [ircs://irc.mozilla.org/ci #ci] - discussion about Continuous Integration infrastructure at Mozilla (formerly Release Engineering)<br /> * [ircs://irc.mozilla.org/content #content] - development discussion for DOM code<br /> * [ircs://irc.mozilla.org/devtools #devtools] - development discussion for Firefox DevTools<br /> * [ircs://irc.mozilla.org/e10s #e10s] - development discussion for Electrolysis<br /> * [ircs://irc.mozilla.org/fistbump #fistbump] - visual design for both products and marketing; copywriting<br /> * [ircs://irc.mozilla.org/focus #focus] - Focus mobile browser development discussion<br /> * [ircs://irc.mozilla.org/fx-team #fx-team] - Firefox front-end development discussion and team channel<br /> * [ircs://irc.mozilla.org/fxa #fxa] - Firefox Accounts development and support channel<br /> * [ircs://irc.mozilla.org/fxos #fxos] - Firefox OS development<br /> * [ircs://irc.mozilla.org/gfx #gfx] - development discussion for graphics, widget and OS-specific code<br /> * [ircs://irc.mozilla.org/identity #identity] - Persona and BrowserID protocol discussion<br /> * [ircs://irc.mozilla.org/jsapi #jsapi] - development discussion for the JavaScript engine<br /> * [ircs://irc.mozilla.org/jsctypes #jsctypes] - discussion and support for js-ctypes development<br /> * [ircs://irc.mozilla.org/labs #labs] - discussion of development of Mozilla Labs projects<br /> * [ircs://irc.mozilla.org/layout #layout] - development discussion for layout code<br /> * [ircs://irc.mozilla.org/macdev #macdev] - OSX developers<br /> * [ircs://irc.mozilla.org/maildev #maildev] - Thunderbird development channel<br /> * [ircs://irc.mozilla.org/media #media] - development discussion for audio/video and related topics like WebRTC<br /> * [ircs://irc.mozilla.org/memshrink #memshrink] - development discussion about memory consumption <br /> * [ircs://irc.mozilla.org/mobile #mobile] - Firefox mobile development discussion<br /> * [ircs://irc.mozilla.org/necko #necko] - development discussion for the networking code<br /> * [ircs://irc.mozilla.org/newslettercode #newslettercode] - community newsletter channel<br /> * [ircs://irc.mozilla.org/power #power] - development discussion about power consumption <br /> * [ircs://irc.mozilla.org/push #push] - Push server and DOM API development channel<br /> * [ircs://irc.mozilla.org/seamonkey #seamonkey] - SeaMonkey development channel (The main channel is now [ircs://chat.freenode.net/seamonkey at Freenode].)<br /> * [ircs://irc.mozilla.org/security #security] - security discussions and public channel for all Security teams<br /> * [ircs://irc.mozilla.org/services-dev #services-dev] - Cloud Services discussion channel<br /> * [ircs://irc.mozilla.org/telemetry #telemetry] - Telemetry development channel<br /> * [ircs://irc.mozilla.org/ur #ur] - discussion of user experience research for all Mozilla projects<br /> * [ircs://irc.mozilla.org/ux #ux] - discussion of visual and interactive user experience design for all Mozilla projects<br /> * [ircs://irc.mozilla.org/videol10n #videol10n] - making/translating subtitles for Mozilla related videos <br /> * [ircs://irc.mozilla.org/webdev #webdev] - the web development group's channel<br /> * [ircs://irc.mozilla.org/webmaker #webmaker] - discussion and support channel for Mozilla Webmaker<br /> * [ircs://irc.mozilla.org/wiki #wiki] - discussion and support channel for MozillaWiki<br /> * [ircs://irc.mozilla.org/windev #windev] - development discussion for Windows platforms<br /> * [ircs://irc.mozilla.org/www #www] - discussion of the development of www.mozilla.org<br /> <br /> ====Specific Locations====<br /> * [ircs://irc.mozilla.org/atlanta #atlanta] - general chat for people in the Atlanta, GA area<br /> * [ircs://irc.mozilla.org/atlanta #auckland] - general chat for people in Auckland or elsewhere in New Zealand<br /> * [ircs://irc.mozilla.org/australia #australia] - general chat for the Australian Mozilla community<br /> * [ircs://irc.mozilla.org/bangladesh #bangladesh] - general chat for the Mozilla Bangladesh community<br /> * [ircs://irc.mozilla.org/berlin #berlin] - general chat for Mozilla Berlin<br /> * [ircs://irc.mozilla.org/berlin #community-berlin] - general chat for the Berlin Mozilla community<br /> * [ircs://irc.mozilla.org/canada #canada] - general chat for the Canadian Mozilla community<br /> * [ircs://irc.mozilla.org/chicago #chicago] - general chat for the Mozilla Chicago community<br /> * [ircs://irc.mozilla.org/india #india] - general chat for the Mozilla India community<br /> * [ircs://irc.mozilla.org/kerala #kerala] - general chat for the Mozilla Kerala community<br /> * [ircs://irc.mozilla.org/london #london] - general chat for people connected to or interested in the London MozSpace<br /> * [ircs://irc.mozilla.org/michigan #michigan] - general chat for the Mozillian Michigan community<br /> * [ircs://irc.mozilla.org/montreal #montreal] - general chat for people in Montreal, including community. Bilingual channel. (French-English)<br /> * [ircs://irc.mozilla.org/mozilla-cm #mozilla-cm] - general chat for the Mozilla Cameroon community<br /> * [ircs://irc.mozilla.org/mozilla.ch #mozilla.ch] - general chat for people in Switzerland<br /> * [ircs://irc.mozilla.org/mozpdx #mozpdx] - general chat for the Mozilla Portland community<br /> * [ircs://irc.mozilla.org/munich #munich] - general chat for the Mozilla Munich Area community<br /> * [ircs://irc.mozilla.org/mv #mv] - general chat for people in the Mountain View office<br /> * [ircs://irc.mozilla.org/rochester #rochester] - general chat for people in the Rochester, NY area<br /> * [ircs://irc.mozilla.org/sf #SF] - general chat for people in the San Francisco office<br /> * [ircs://irc.mozilla.org/seattle #seattle] - general chat for people in the greater Seattle area<br /> * [ircs://irc.mozilla.org/socal #socal] - general chat for people in the greater Southern California area<br /> * [ircs://irc.mozilla.org/spain #spain] - general chat for people in Spain<br /> * [ircs://irc.mozilla.org/tokyo #tokyo] - general chat for people in the Tokyo office and area<br /> * [ircs://irc.mozilla.org/toronto #toronto] - general chat for people in the Toronto office<br /> * [ircs://irc.mozilla.org/triangle #triangle] - general chat for people in the Raleigh/Durham, NC area<br /> * [ircs://irc.mozilla.org/tulsa #tulsa] - general chat for people in the Tulsa area<br /> * [ircs://irc.mozilla.org/uk #uk] - general chat for the Mozilla UK community<br /> * [ircs://irc.mozilla.org/vancouver #vancouver] - general chat for people in the Vancouver office<br /> <br /> ====Channels in Other Languages====<br /> <br /> =====Arabic=====<br /> <br /> * [ircs://irc.mozilla.org/arabicmozilla #arabicmozilla]<br /> * [ircs://irc.mozilla.org/mozilla-algeria #mozilla-algeria]<br /> * [ircs://irc.mozilla.org/mozilla-eg #mozilla-eg]<br /> * [ircs://irc.mozilla.org/mozillatunisia #mozillatunisia]<br /> <br /> =====Azerbaijani=====<br /> <br /> * [ircs://irc.mozilla.org/mozillaz #mozillaz]<br /> <br /> =====Bangladesh=====<br /> <br /> * [ircs://irc.mozilla.org/#bangladesh #bangladesh]<br /> <br /> =====Brazilian Portuguese=====<br /> <br /> * [ircs://irc.mozilla.org/developers-br #developers-br]<br /> * [ircs://irc.mozilla.org/firefox-br #firefox-br]<br /> * [ircs://irc.mozilla.org/mozilla-br #mozilla-br]<br /> * [ircs://irc.mozilla.org/openwebapps-br #openwebapps-br]<br /> * [ircs://irc.mozilla.org/sumo-br #sumo-br]<br /> * [ircs://irc.mozilla.org/webmaker-br #webmaker-br]<br /> <br /> =====Bulgarian=====<br /> * [ircs://irc.mozilla.org/mozilla-bg #mozilla-bg]<br /> <br /> =====Catalan=====<br /> * [ircs://irc.mozilla.org/mozilla-cat #mozilla-cat]<br /> <br /> =====Chinese=====<br /> <br /> * [ircs://irc.mozilla.org/china #china]<br /> * [ircs://irc.mozilla.org/mozilla-taiwan #mozilla-taiwan]<br /> * [ircs://irc.mozilla.org/taipei-platform #taipei-platform]<br /> <br /> =====Croatian=====<br /> <br /> * [ircs://irc.mozilla.org/croatia #croatia]<br /> <br /> =====Czech=====<br /> <br /> * currently none, see [[L10n:Teams:cs|this page]] to know how to reach us<br /> <br /> =====Danish=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.dk #mozilla.dk]<br /> <br /> =====Dutch=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.nl #mozilla.nl]<br /> <br /> =====Esperanto=====<br /> <br /> * [ircs://irc.mozilla.org/Mozilla-eo #Mozilla-eo]<br /> <br /> =====Finnish=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.fi #mozilla.fi]<br /> <br /> =====French=====<br /> <br /> * [ircs://irc.mozilla.org/mozfr #mozfr] Main channel for community members work<br /> * [ircs://irc.mozilla.org/frenchmoz #frenchmoz] Main channel for Francophone community chat<br /> * [ircs://irc.mozilla.org/L10n-fr #L10n-fr] Main channel for French localization (Telegram invite link available in channel topic)<br /> * [ircs://irc.mozilla.org/L10n-fr #SUMO-fr] Main channel for ''only'' French SUMO localization discussions ([https://t.me/joinchat/A7h94Q_P6nP9PpKx7GKKDg mirror on Telegram])<br /> * [ircs://irc.mozilla.org/devfr #devfr] Main channel for developers (both webdev and platform)<br /> * [ircs://irc.mozilla.org/politiques #politiques] Channel for Open Policy &amp; Advocacy discussions<br /> * [ircs://irc.mozilla.org/support-fr #support-fr] Technical support<br /> * [ircs://irc.mozilla.org/xulfr #xulfr] Historically XUL technology channel<br /> * [ircs://irc.mozilla.org/rust-fr #rust-fr] Rust language channel<br /> <br /> =====German=====<br /> * [ircs://irc.mozilla.org/de #de]<br /> * [ircs://irc.mozilla.org/chatzilla.de #chatzilla.de]<br /> * [ircs://irc.mozilla.org/firefox.de #firefox.de]<br /> * [ircs://irc.mozilla.org/firefoxOS.de #firefoxOS.de]<br /> * [ircs://irc.mozilla.org/mozilla.de #mozilla.de]<br /> * [ircs://irc.mozilla.org/thunderbird.de #thunderbird.de]<br /> <br /> =====Greek=====<br /> * [ircs://irc.mozilla.org/athens #athens] <br /> <br /> =====Hebrew=====<br /> * [ircs://irc.mozilla.org/mozilla.il #mozilla.il] <br /> <br /> =====Indonesia=====<br /> * [ircs://irc.mozilla.org/idmoz #idmoz]<br /> <br /> =====Italian=====<br /> * [ircs://irc.mozilla.org/developers-it #developers-it]<br /> <br /> =====Japanese=====<br /> <br /> * [ircs://irc.mozilla.org/firefox-jp #firefox-jp (iso-2022-jp)]<br /> * [ircs://irc.mozilla.org/japan #japan (UTF-8)]<br /> <br /> =====Korean=====<br /> * [ircs://irc.mozilla.org/mozillakr #mozillakr]<br /> <br /> =====Lithuanian=====<br /> * [ircs://irc.mozilla.org/mozilla-lt #mozilla-lt]<br /> <br /> =====Marathi=====<br /> * [ircs://irc.mozilla.org/marathi #marathi]<br /> <br /> =====Myanmar=====<br /> * [ircs://irc.mozilla.org/mozillamm #mozillamm]<br /> <br /> =====Norwegian=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.no #mozilla.no]<br /> <br /> =====Persian=====<br /> <br /> * [ircs://irc.mozilla.org/iranmozilla #iranmozilla]<br /> <br /> =====Polish=====<br /> <br /> * [ircs://irc.mozilla.org/aviarypl #aviarypl]<br /> <br /> =====Portuguese (Portugal)=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla-portugal #mozilla-portugal]<br /> <br /> =====Philippines=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla-ph #mozilla-ph]<br /> <br /> =====Romanian=====<br /> <br /> * [ircs://irc.mozilla.org/romania #romania]<br /> <br /> =====Russian=====<br /> * [ircs://irc.mozilla.org/mozilla-ru #mozilla-ru]<br /> <br /> =====Serbian=====<br /> * [ircs://irc.mozilla.org/mozilla.sr #mozilla.sr]<br /> <br /> =====Sinhala=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.lk #mozilla.lk]<br /> <br /> =====Slovak=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla-sk #mozilla-sk]<br /> <br /> =====Slovenia=====<br /> <br /> * [ircs://irc.mozilla.org/slozilla #slozilla]<br /> <br /> =====Spanish=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla-hispano #mozilla-hispano]<br /> * [ircs://irc.mozilla.org/mozilla-mexico #mozilla-mexico]<br /> * [ircs://irc.mozilla.org/mozilla-venezuela #mozilla-venezuela]<br /> <br /> =====Swedish=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla.se #mozilla.se]<br /> <br /> =====Tunisian=====<br /> <br /> * [ircs://irc.mozilla.org/mozillatunisia #mozillatunisia]<br /> <br /> =====Ukrainian=====<br /> <br /> * [ircs://irc.mozilla.org/mozilla-ua #mozilla-ua]<br /> <br /> =====Wolof=====<br /> <br /> * [ircs://irc.mozilla.org/l10n-wo #l10n-wo]<br /> <br /> == Connection Notice ==<br /> <br /> When you connect to our IRC server, you will get portscanned from 63.245.208.159, 63.245.212.23, or 63.245.216.214. This is an unfortunate but necessary step in order to cut down on the number of viruses and other malicious users attempting to communicate via our IRC servers. The portscan is checking for common ports used by known viruses and open proxy servers to ensure that your machine is not infected before allowing you to remain connected. By connecting to our IRC servers, you agree to have your computer portscanned by our server. If you don't like this, don't connect.<br /> <br /> == Privacy Information ==<br /> <br /> Our servers do not keep records of any of your conversations, but anyone in the channels you are in might do so and publish those conversation logs (and some channels are actively logged by users on those channels). If you have questions about this, ask the other users in the channel you are concerned about (every channel has its own culture). In general, you should assume that anything you say on IRC that is not in a private message will be recorded and possibly published somewhere, and even then you are depending on your trust that the person you are sending the message to will not to share it.<br /> <br /> ==Quotes Database==<br /> <br /> Sometimes people say silly or memorable things on our server. We memorialize them forever on the [http://quotes.burntelectrons.org/ quotes database] managed by Tim De Pauw.<br /> <br /> ==Persistent Connection==<br /> If you have access to a host that is always on you can run an irc session on it and connect/disconnect from that session without losing everything. This allows you to keep scrollback, stay present in channels when you are away, and have logs of what happens when you're not around. In this example I will use people.mozilla.org as my host. If someone can add good instructions for setting up a proxy in another way, please do. This tutorial will assume that you have an account on people.mozilla.org (or another server where you can ssh to it and run both 'screen' and 'irssi'), details on how to set this up are below. An alternative is [http://wiki.znc.in/ZNC ZNC].<br /> <br /> ===On the server===<br /> &lt;pre&gt;<br /> ssh lsblakk@people.mozilla.org<br /> ## create a bin dir<br /> mkdir bin<br /> cd bin<br /> vim irc<br /> ## paste the following two lines (without the initial spaces) in the empty file:<br /> #!/bin/bash<br /> screen -raAd<br /> ## now hit ESC followed by :x and enter to save this file<br /> ## make the file executable<br /> chmod -c a+x irc<br /> ## Start your irssi session:<br /> screen irssi<br /> &lt;/pre&gt;<br /> ====Add Network/Server====<br /> Replace &lt;nick&gt; and &lt;password&gt; with your registered Mozilla IRC nickname and password.<br /> The following creates an autoconnect to irc.mozilla.org under the name Mozilla.<br /> &lt;pre&gt;<br /> /SERVER ADD -ssl -auto -network Mozilla irc.mozilla.org 6697<br /> /NETWORK ADD -nick &lt;nick&gt; -user &lt;nick&gt; -autosendcmd &quot;/^msg nickserv identify &lt;password&gt;;wait 2000&quot; Mozilla<br /> &lt;/pre&gt;<br /> <br /> ====Add Channels (optional)====<br /> Replace &lt;nowiki&gt;#channel&lt;/nowiki&gt; with the channel you'd like to add. &lt;pass&gt; is an optional field, used when an IRC channel requires a password.<br /> &lt;pre&gt;<br /> /CHANNEL ADD -auto #channel Mozilla &lt;pass&gt;<br /> &lt;/pre&gt;<br /> ...repeat till satisfied!<br /> ====Good practices====<br /> &lt;pre&gt;<br /> /HILIGHT &lt;nick&gt;<br /> &lt;/pre&gt;<br /> '''more soon'''<br /> <br /> ===References===<br /> * [http://www.irssi.org/documentation/startup Irssi Startup HOWTO]<br /> * [http://quadpoint.org/articles/irssi/ Irssi Basics]</div>

Mhoye https://wiki.mozilla.org/index.php?title=SummerOfCode/ApplicationTemplate&diff=1225271 2020-03-20T17:28:40Z

<p>Mhoye: IRC -&gt; Matrix.</p> <hr /> <div>__NOTOC__<br /> <br /> &lt;p&gt;&lt;em&gt;The following template may help, but it is not compulsory that you use it.&lt;/em&gt;&lt;/p&gt;<br /> <br /> &lt;p&gt;&lt;em&gt;Please make the title of your application exactly the same as the title of the project on the Ideas List (if you are applying to do one of our ideas). This helps us sort, and makes sure your proposal doesn't get overlooked.&lt;/em&gt;&lt;/p&gt;<br /> <br /> &lt;p&gt;Good proposals should clear, brief and concise. You should feel free to use the space you need, but our experience has been projects that take eight to ten pages or more to describe cannot reasonably be delivered and shipped in the time GSOC allows.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Personal Details&lt;/h3&gt;<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;Name:&lt;/li&gt;<br /> &lt;li&gt;Email:&lt;/li&gt;<br /> &lt;li&gt;Matrix ID, if you have one:&lt;/li&gt;<br /> &lt;li&gt;Telephone:&lt;/li&gt;<br /> &lt;li&gt;Other contact methods:&lt;/li&gt;<br /> &lt;li&gt;Country of residence:&lt;/li&gt;<br /> &lt;li&gt;Timezone:&lt;/li&gt;<br /> &lt;li&gt;Primary language:&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;h3&gt;Project Proposal&lt;/h3&gt;<br /> <br /> &lt;p&gt;Which project are you applying to do? If the project idea contains several options, say which ones you are going to pick. Explain, at a high level, what you hope to achieve in the time. You need to show you understand what is required. Describe any work or research on this project you have already done.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Schedule of Deliverables&lt;/h3&gt;<br /> <br /> &lt;p&gt;What are the milestones and deliverables for your project? You will be assessed against these. Note that we prefer realism to extravagant claims of possible achievement, and the more concrete, the better. Also, please give us some idea of &lt;i&gt;how&lt;/i&gt; you decided how long each part would take.&lt;/p&gt;<br /> <br /> &lt;p&gt;Do you have any other commitments during the GSoC period? How will they affect your work?&lt;/p&gt;<br /> <br /> &lt;h3&gt;Open Source Development Experience&lt;/h3&gt;<br /> <br /> &lt;p&gt;Any experience you have, even a few bug reports or some tiny 2-line patch to something obscure. Please give links to online examples of your code, if you have any.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Work/Internship Experience&lt;/h3&gt;<br /> <br /> &lt;p&gt;Anything relevant to the project, or related to browsers, web design or software development.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Academic Experience&lt;/h3&gt;<br /> <br /> &lt;p&gt;What you're studying in university/college (even if it doesn't seem relevant), why you chose it, and how you're doing.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Why Me&lt;/h3&gt;<br /> <br /> &lt;p&gt;Tell us, with reference perhaps to the information above, why you in particular are the right person to pick for this project. Note that everyone claims to be enthusiastic and hard working; that's probably not enough on its own.&lt;/p&gt;<br /> <br /> &lt;h3&gt;Why Mozilla&lt;/h3&gt;<br /> <br /> &lt;p&gt;Tell us why you chose to apply to us in particular.&lt;/p&gt;</div>

Mhoye https://wiki.mozilla.org/index.php?title=GitHub&diff=1225270 2020-03-20T17:16:18Z

<p>Mhoye: </p> <hr /> <div>This page is specifically about [https://github.com/mozilla the &quot;mozilla&quot; organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].<br /> &lt;div id=&quot;contact&quot;&gt;<br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Do you have a GitHub administration question for an org?&lt;br &gt; See [[#other_github|table]] for contact info for each organization.<br /> |}<br /> <br /> == News ==<br /> * 2019-02-19 - Mozilla's Code of Conduct is required to be included in every repository, following [[/Repository Requirements|this procedure]].<br /> * 2018-03-29 - new [[/Repository Security|Guidelines for securing sensitive repositories]] published. These are good practices for any repository that does &quot;releases&quot;, and some groups my require adherence on their repositories.<br /> <br /> == Recommendations and FAQ ==<br /> <br /> The actions below are specifically for the 'mozilla' organization on GitHub. Other organizations may have different or additional procedure. Please refer to the [[#other_github|other organizations]] table below for the proper service request address and contact information.<br /> <br /> === Where should I ask additional questions? ===<br /> * Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and one of the volunteers will respond. We're also available on #github on Matrix.<br /> <br /> === How do I hook up a new GitHub Actions or 3rd party application to a repository in the mozilla org? ===<br /> {{note|There are now multiple 3rd party application types. &quot;GitHub Apps&quot; (nee integrations) are the new approach and preferred.|gotcha}}<br /> {{note|Some 3rd party apps use GitHub as an OAuth identity provider for their website (e.g. for a dashboard). An ''OAuth Application'' will block the installation process if the app is not already approved. The &quot;Request access&quot; block is what this section describes.|gotcha}}<br /> <br /> Each type has it's own installation and approval process. Please follow the instructions in the correct section below.<br /> <br /> ==== GitHub Actions ====<br /> [https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions GitHub Actions] allow automation to be initiated by various repository events. However, GitHub Actions are only enabled on &quot;modern&quot; accounts. Many of the Mozilla orgs are &quot;legacy&quot; accounts (including 'mozilla'), so GitHub actions are not always available. Check with your organization owners if you have questions. <br /> <br /> {{note|GitHub Actions have not yet been evaluated for use on &quot;sensitive repositories&quot;. Please work with your security team if you wish to utilize GitHub Actions on a sensitive repository.|gotcha}}<br /> <br /> ==== GitHub Apps Installation &amp; Approval Process ====<br /> <br /> GitHub Apps (formerly called &quot;integrations&quot;) are &quot;Installed&quot; into either the entire organization, or into individual repositories. Each integration has a documented and granular access to repository resources. This is good.<br /> <br /> However, the GitHub App installation can only be done by an organization owner, who may have to do additional housekeeping. This is not so good, so please plan accordingly (you may need to coordinate with [[#contact|GitHub owners]]).<br /> <br /> * File a request using this [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&amp;comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&amp;component=Github%3A%20Administration&amp;product=mozilla.org&amp;short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE bug template]<br /> * Include answers to the questions prompted for in the above template. Additional notes:<br /> ** ''Which repositories do you want to have access? (all or list)'' -- &quot;All&quot; will rarely be granted - every repository should have control over anything that can access their repository.<br /> ** ''Are any of those repositories private?'' -- In general, OAuth apps will not be granted access to private repositories, as that grants access to ''all'' private repositories.<br /> ** ''Provide link to vendor's description of permissions needed and why'' -- Hopefully they have this documented, or at least provide a screenshot of the authorization screen which lists the permissions. If not, we may ask you (the requestor) to engage with the app's support team to obtain the answers.<br /> ** ''Provide the Install link for a GitHub app'' -- mandatory, as we can't install the app without it.<br /> <br /> * If you are not an &quot;admin&quot; for the repository, an &quot;admin&quot; will have to approve the request. Please set a &quot;Need Info&quot; on the appropriate repository admin.<br /> <br /> ===== Initial Installation =====<br /> If this is the first time this GitHub App is being installed in the organization, a few extra checks and coordination are needed. An organization owner will need to perform these steps:<br /> * Determine if the GitHub App previously had an OAUTH version in use in the same org. (The simplest way is to see if the app is listed under the &quot;Third-party Application&quot; section of the organization settings page. ''Any mention'' -- including &quot;declined&quot; -- counts as &quot;in use&quot; for this purpose.)<br /> ** If the OAuth app was in use, check the app installation documentation to see if there are any caveats. (We've only seen one app transition where there was an impact, but better safe than sorry.)<br /> ** If there are caveats that apply, ask the requestor to contact all current repositories using the classic OAUTH application to coordinate, cc'ing [[#contact|GitHub owners]]. This task is non-trivial, you usually need to access the OAuth app's dashboard, and have knowledge of how the app works. ('''Do NOT''' authenticate to any OAuth app with your owner account.)<br /> * Install the GitHub app for &quot;specific repositories&quot;, and enable the ones in the request.<br /> <br /> '''Please do not install GitHub apps with organization wide scope without first discussing with [[#contact|GitHub owners]].'''<br /> <br /> ===== Additional Installations or Removals =====<br /> If the GitHub App has already been installed in the organization, the new repository simply needs to be added or removed from the list. An organization owner has to make this change. Please still [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&amp;comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&amp;component=Github%3A%20Administration&amp;product=mozilla.org&amp;short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE file a bug]. As before, a repository admin has to approve the request.<br /> <br /> If you're an org owner, you can [https://github.com/organizations/mozilla/settings/installations see what has already been installed].<br /> <br /> ==== OAUTH (classic) Applications ====<br /> <br /> * Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a &quot;Request access&quot; button during the set up flow. You'll need to click that button to request approval. See below for an example:<br /> <br /> [[File:github_approval.png]]<br /> <br /> * In some cases, the application does not need to be &quot;approved&quot; to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)<br /> <br /> * In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, open a bug using [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&amp;comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&amp;component=Github%3A%20Administration&amp;product=mozilla.org&amp;short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE this template].<br /> ** Please be sure to have clicked the &quot;Request Approval&quot; link before submitting bug.<br /> * Include answers to these questions:<br /> ** Provide link to vendor's description of permissions needed and why<br /> ** Provide installation instructions (both may be needed):<br /> <br /> === Reviewing owners and permissions ===<br /> As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.<br /> <br /> === Can I be an Owner of the Mozilla Organization? ===<br /> The Owners group on GitHub has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner, they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.<br /> <br /> === Can I be a Member of the Mozilla Organization? ===<br /> &lt;div id=&quot;join&quot;&gt; &lt;/div&gt;<br /> ==== Contributor Information ====<br /> Good news! You do not need to be a member of the Mozilla organization on GitHub before you can contribute to Mozilla!!!! We have several sites which can help you find the best fit for contribution:<br /> * General [https://www.mozilla.org/en-US/contribute/ volunteering options],<br /> * Or pick from [http://whatcanidoformozilla.org/ these areas],<br /> * Or jump right into [http://www.joshmatthews.net/bugsahoy/ fixing a bug].<br /> * If you're already a contributor (THANK YOU!) looking for a place to have your work recognized (even if not coding related), please see the [https://www.mozilla.org/credits/FAQ Credits FAQ] for inclusion in the [https://www.mozilla.org/credits/ credits].<br /> <br /> Once you're working on a project, the project leaders and/or team maintainers can help you get access to anything you need. Instructions for them are directly following.<br /> <br /> ==== Team Maintainers &amp; Project Leads ====<br /> <br /> Project owners and team maintainers may find the following information helpful when asking for access for a new team member:<br /> <br /> * We prefer the use of github teams when granting permissions to org members. (Collaborators have to be added individually.)<br /> * All members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical. Of course, anyone interacting with Mozilla repositories agrees to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines]<br /> ** &quot;Outside Collaborator&quot;: repository admins can grant outside collaborator to any GitHub account. &quot;Outside Collaborator&quot; is roughly analogous to &quot;Level 1a&quot; access to Mozilla-hosted repositories.<br /> ** &quot;Team Member&quot;: team maintainers can add GitHub users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the ''team maintainer'' should [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;bug_type=task&amp;cf_fx_iteration=---&amp;cf_fx_points=---&amp;comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Team_Maintainers_.26_Project_Leads%2C%20and%20need%20help%20adding%20a%20contributor%20to%20the%20org%3A%0D%0A%0D%0AName%3A%20%0D%0AMozilla%20Email%3A%20%0D%0AGithub%20Profile%20link%3A%20%2AStaff%20%2A%2AMUST%2A%2A%20have%20their%20verified%20GitHub%20identity%20listed%20in%20their%20people.m.o%20entry%2A%0D%0AGithub%20Team%28s%29%20%2AREQUIRED%2A%3A%20%0D%0A%0D%0AIf%20this%20is%20not%20being%20requested%20by%20a%20team%20maintainer%2C%20please%20request%20their%20approval%20via%20need-info.&amp;component=Github%3A%20Administration&amp;contenttypemethod=list&amp;contenttypeselection=text%2Fplain&amp;defined_groups=1&amp;filed_via=standard_form&amp;flag_type-4=X&amp;flag_type-607=X&amp;flag_type-800=X&amp;flag_type-803=X&amp;flag_type-936=X&amp;form_name=enter_bug&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=Unspecified&amp;priority=--&amp;product=mozilla.org&amp;rep_platform=Unspecified&amp;target_milestone=---&amp;version=other file a bug using this link] to add you to their team, as a form of vouching. &quot;Team Member&quot; is roughly analogous to &quot;Level 2&quot; or &quot;Level 3&quot;, with the distinction being the content of the repositories managed by the team.<br /> <br /> To get access for a new Contributor, please have the ''team maintainer'' or ''repository admin'' [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;bug_type=task&amp;cf_fx_iteration=---&amp;cf_fx_points=---&amp;comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Team_Maintainers_.26_Project_Leads%2C%20and%20need%20help%20adding%20a%20contributor%20to%20the%20org%3A%0D%0A%0D%0AName%3A%20%0D%0AMozilla%20Email%3A%20%0D%0AGithub%20Profile%20link%3A%20%2AStaff%20%2A%2AMUST%2A%2A%20have%20their%20verified%20GitHub%20identity%20listed%20in%20their%20people.m.o%20entry%2A%0D%0AGithub%20Team%28s%29%20%2AREQUIRED%2A%3A%20%0D%0A%0D%0AIf%20this%20is%20not%20being%20requested%20by%20a%20team%20maintainer%2C%20please%20request%20their%20approval%20via%20need-info.&amp;component=Github%3A%20Administration&amp;contenttypemethod=list&amp;contenttypeselection=text%2Fplain&amp;defined_groups=1&amp;filed_via=standard_form&amp;flag_type-4=X&amp;flag_type-607=X&amp;flag_type-800=X&amp;flag_type-803=X&amp;flag_type-936=X&amp;form_name=enter_bug&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=Unspecified&amp;priority=--&amp;product=mozilla.org&amp;rep_platform=Unspecified&amp;target_milestone=---&amp;version=other file a bug using this link], and fill in the details.<br /> <br /> '''Please Note:'''<br /> * All staff (folks with an entry in people.mozilla.org) '''MUST''' have their verified GitHub identity entered there.<br /> * We will cancel any invitation to the organization which is not accepted within 2 weeks.<br /> * All members of the Mozilla organization on GitHub '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].<br /> * Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.<br /> <br /> === Should I make a separate github organization or just create a repository in an existing one? ===<br /> This is a personal preference, in general. (Some product lines may have policies about source code locations.) If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details. Additional resources on establishing an organization are:<br /> * [https://mana.mozilla.org/wiki/display/POLICIES/Standard%3A+GitHub+repositories+and+organizations Mozilla Standards] &lt;small&gt;''login required''&lt;/small&gt;<br /> * [[/Repository Security|Guidelines for securing sensitive repositories]]<br /> * If you need any paid services, contact github owners for access to [https://github.com/mozilla/admin_for_mozilla_private/wiki/Billing-Notes Billing Notes]<br /> <br /> === Forking vs Transferring ===<br /> '''Do not &quot;fork&quot; a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.<br /> <br /> If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:<br /> <br /> # If you're not a member of any team, talk to an [[#contact|org admin]].<br /> # Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.<br /> # Choose which teams should be given access. All chosen teams will have only 'read' access at this point.<br /> # [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&amp;bug_file_loc=http%3A%2F%2F&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;cc=gene%40mozilla.com&amp;cf_fx_iteration=---&amp;cf_fx_points=---&amp;comment=I%20just%20transferred%20the%20NAME_HERE%20repository%20to%20the%20ORG_NAME_HERE%20organization%2C%20and%20thus%20no%20longer%20have%20admin%20access.%0D%0A%0D%0APlease%20enable%20admin%20access%20for%3A%0D%0A-%20the%20TEAM_NAME%20team%20%28preferred%29%2C%20or%0D%0A-%20just%20me%20--%20I%27ll%20take%20care%20of%20the%20rest&amp;component=Github%3A%20Administration&amp;contenttypemethod=list&amp;contenttypeselection=text%2Fplain&amp;defined_groups=1&amp;flag_type-4=X&amp;flag_type-607=X&amp;flag_type-800=X&amp;flag_type-803=X&amp;form_name=enter_bug&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=Unspecified&amp;priority=--&amp;product=mozilla.org&amp;rep_platform=Unspecified&amp;short_desc=Admin%20access%20needed%20to%20transferred%20repository&amp;target_milestone=---&amp;version=other File a bug] to grant admin permissions to a team or yourself. {{note|As soon as you transfer, your repository will be in &quot;limbo&quot; (only you will have write access) due to a GitHub bug. Make arrangements in advance to have an owner available to process the bug.|gotcha}}<br /> # Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on GitHub (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)<br /> <br /> === Do I need to be an owner to create repositories? ===<br /> Not in the 'mozilla' organization. If you are a member, you can create a repository. Other organizations may restrict repository creation. However, it's preferred that you create repositories in the context of a team. Teams are created [https://github.com/orgs/mozilla/teams here], if necessary. Once you have created a repo, you can configure it to give rights to members of particular teams.<br /> <br /> {{note|Remember that all repositories must comply with the [[GitHub/Repository Requirements]].|reminder}}<br /> <br /> The 'mozilla' organziation does have a limited number of private repositories available. These are reserved for repositories containing [[Security/Data_Classification|non-public data]], or other business reason. Please request private repositories using this [https://bugzilla.mozilla.org/enter_bug.cgi?bug_type=task&amp;comment=I%27ve%20read%20all%20of%20the%20%5Brepository%20creation%5D%5B1%5D%20section%2C%20and%20want%20to%20request%20a%20private%20repository.%20I%27ve%20filled%20in%20all%20the%20required%20fields.%0D%0A%0D%0AName%20of%20Repository%3A%20%20REQUIRED%0D%0ALink%20to%20your%20people.m.o%20entry%20with%20verified%20GitHub%20login%3A%20REQUIRED%0D%0A%0D%0A%5BData%20Classification%5D%5B2%5D%20of%20data%20in%20repo%3A%20REQUIRED%0D%0AOther%20business%20justification%20for%20private%20repo%3A%0D%0AWhen%20can%20the%20repository%20be%20made%20public%3F%20REQUIRED%0D%0A%0D%0A%5B1%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Do_I_need_to_be_an_owner_to_create_repositories.3F%0D%0A%5B2%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FSecurity%2FData_Classification%0D%0A&amp;component=Github%3A%20Administration&amp;form_name=enter_bug&amp;product=mozilla.org&amp;short_desc=Request%20for%20a%20Private%20Repository%20in%20the%20mozilla%20GitHub%20organization&amp;groups=mozilla-employee-confidential Bugzilla template]. Be sure to answer all questions marked 'REQUIRED' in the form.<br /> <br /> As the creator, you will automatically have &quot;admin&quot; permissions on the repository. Repository Admins are responsible for the security settings of the repository. This includes approving (or not) requests for GitHub Apps to be added to the app.<br /> <br /> Please review all the settings for your new repository, and disable features you will not be using. The default values can change, and new services added, so specific guidance can't be given. But do you really need that wiki? Or the project board? You can always enable them later if you decide you need them.<br /> <br /> === We have sensitive code or data in this repository - any extra steps I should take? ===<br /> Yes. Even if your repository is private, there are steps you can take to ensure you know if something has changed. See the [[GitHub/Repository Security]] page for additional information and a checklist.<br /> <br /> === We're done with this project - what should we do with the repository? ===<br /> <br /> That is really up to the team. However, if you have forks or other active user participation, it's a good idea to be clear about the status of Mozilla's commitment to the project. Your options include:<br /> * Delete the repo (obviously the worst alternative).<br /> * Add the [http://unmaintained.tech/ Unmaintained] badge to the readme<br /> * Archive the repository, using [https://help.github.com/articles/about-archiving-repositories/ GitHub's suggestions].<br /> <br /> '''PLEASE''' make sure the repository is clearly licensed before leaving it. Without a license, many other folks can not build upon your work.<br /> <br /> === Are there requirements for when or how I should create a new team? ===<br /> No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).<br /> <br /> On large teams we recommend you separate teams for read/write and repository administration.<br /> <br /> &lt;div id=&quot;other_github&quot;&gt;&lt;/div&gt;<br /> === Is &quot;mozilla&quot; the only github &quot;organization&quot; related to Mozilla? ===<br /> No, there are plenty of Mozilla-related &quot;organizations&quot; on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own &quot;organization&quot;. Here is a (probably incomplete) list of them:<br /> &lt;div style=&quot;display: flex; flex-flow: row wrap; width: 100%;&quot;&gt;<br /> &lt;div style=&quot;order: 1; flex-grow: 3; margin: 0.5em; border: 0.1em solid darkgreen; padding: 0.5em; background-color: palegreen; min-width: auto; text-align: center;&quot;&gt;<br /> &lt;big&gt;'''NOTE:''' All GitHub Organizations in this section are subject to the [[GitHub/Repository_Requirements|Repository Requirements]].&lt;/big&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> {| class=&quot;wikitable sortable&quot; <br /> |-<br /> ! Organization !! Description !! Contact Owner !! Service Requests<br /> |-<br /> | [https://github.com/mozilla mozilla] || Mozilla main organization || Matrix [https://chat.mozilla.org/#/room/#github-admin:mozilla.org #github-admin:mozilla.org]; Email {{emailentry|github-owners|mozilla.org|at=is}} || Please check above for a more specific link, otherwise use [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&amp;component=Github%3A%20Administration&amp;form_name=enter_bug&amp;product=mozilla.org&amp; mozilla.org :: Github: Administration]<br /> |-<br /> | [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || Slack/🔒it-all||<br /> |-<br /> |[https://github.com/mozillabrasil mozillabrasil] || Mozilla Brazil|| ?<br /> |-<br /> | [https://github.com/bugzilla bugzilla] || Bugzilla (the product, not bugzilla.mozilla.org) || #bugzilla||<br /> |- <br /> | [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?||<br /> |-<br /> | [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?||<br /> |-<br /> | [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?||<br /> |-<br /> | [https://github.com/mdn mdn] || Mozilla Developer Network || [https://github.com/jwhitlock John Whitlock]||<br /> |-<br /> | [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?||<br /> |-<br /> | [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?||<br /> |-<br /> | [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?||<br /> |-<br /> | [https://github.com/mozilla-bteam mozilla-bteam] || Bugzilla.Mozilla.org || #bteam||<br /> |-<br /> | [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}||<br /> |-<br /> | [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?||<br /> |-<br /> | [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?||<br /> |-<br /> | [https://github.com/mozilla-iam mozilla-iam] || Mozilla's identity and access management || kang||<br /> |-<br /> | [https://github.com/mozilla-iot mozilla-iot] || Mozilla's Internet of Things program || {{Mozillian|dbryant|David Bryant}}, {{Mozillian|bfrancis|Ben Francis}}||<br /> |-<br /> | [https://github.com/mozilla-lockbox mozilla-lockbox] || Mozilla Lockbox iOS, Android, desktop extension || [https://github.com/orgs/mozilla-lockbox/people?utf8=%E2%9C%93&amp;query=role%3Aowner mozilla-lockbox owners]||<br /> |-<br /> | [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?||<br /> |-<br /> | [https://github.com/mozilla-platform-ops mozilla-platform-ops] || Mozilla Platform Operations || [[Platform_Operations]]||<br /> |-<br /> | [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}||<br /> |-<br /> | [https://github.com/mozilla-releng mozilla-releng] || Mozilla Release Engineering || #releng||<br /> |-<br /> | [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&amp;query=role%3Aowner mozilla-services owners]|| [https://github.com/mozilla-services/github-management/issues Open Issue]<br /> |-<br /> | [https://github.com/mozilla-mobile/ mozilla-mobile] || Mobile: Android Product Team &amp; Firefox iOS teams || [https://github.com/orgs/mozilla-mobile/people?utf8=%E2%9C%93&amp;query=role%3Aowner mozilla-mobile owners]||<br /> |-<br /> | [https://github.com/mozilla-spidermonkey mozilla-spidermonkey] || Mozilla SpiderMonkey Team tools and embedding info || #jsapi||<br /> |-<br /> | [https://github.com/mozilla-standards mozilla-standards] || Mozilla Standards (for IPR Contributions) || [https://mozillians.org/u/dbaron/ dbaron], [https://mozillians.org/u/annevk/ annevk]||<br /> |-<br /> | [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}||<br /> |-<br /> | [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?||<br /> |-<br /> | [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?||<br /> |-<br /> | [https://github.com/MozillaReality MozillaReality] || Mozilla Mixed Reality program || {{Mozillian|larsberg|Lars Bergstrom}}, {{Mozillian|plamb|Philip Lamb}}||<br /> |-<br /> | [https://github.com/MozillaScience MozillaScience] || Mozilla Science Lab || ?||<br /> |-<br /> | [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?||<br /> |-<br /> | [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}||<br /> |-<br /> | [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || {{Mozillian|bclark|Brian Clark}}, {{Mozillian|shobson|Stephanie Hobson}}||<br /> |-<br /> | [https://github.com/mozfr mozfr] || Mozilla Francophone ||||<br /> |-<br /> | [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?||<br /> |-<br /> | [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}||<br /> |-<br /> | [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, {{Mozillian|jdm|Josh Matthews}}||<br /> |-<br /> | [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Francesco Lodolo https://mozillians.org/u/flod/||<br /> |-<br /> | [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || [https://github.com/gregarndt Greg Arndt]||<br /> |-<br /> | [https://github.com/MozillaCH MozillaCH] || Mozilla [[Switzerland]] || {{Mozillian|mkohler|Michael Kohler}}, {{Mozillian|freaktechnik|freaktechnik}}||<br /> |-<br /> | [https://github.com/mozmeao MozMEAO] || Mozilla [[Marketing]] || {{Mozillian|bensternthal|Benjamin Sternthal}}, {{Mozillian|pmac|Paul McLanahan}}||<br /> |-<br /> | [https://github.com/mozilla-payments mozilla-payments] || Implementation of Web Payment APIs || {{Mozillian|Marcos Caceres}}||<br /> |-<br /> | [https://github.com/mozilla-jetpack mozilla-jetpack] || Resources for Mozilla's Add-on SDK || ?||<br /> |-<br /> | [https://github.com/web-ext-experiments web-ext-experiments] || WebExtension API Experiments || {{Mozillian|andym|Andy McKay}}||<br /> |-<br /> | [https://github.com/mozilla-conduit mozilla-conduit] || Mozilla Conduit work || {{Mozillian|mcote|Mark Côté}}||<br /> |-<br /> | [https://github.com/mozsearch mozsearch] || The code that runs Searchfox.org || {{Mozillian|kats|Kartikaya Gupta}}||<br /> |-<br /> | [https://github.com/MozillaCZ/ MozillaCZ] || [https://www.mozilla.cz/ Mozilla.cz] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|MekliCZ|Michal Vašíček}}, {{Mozillian|zelitomas|Tomáš Zelina}}||<br /> |-<br /> | [https://github.com/MozillaSK/ MozillaSK] || [https://www.mozilla.sk/ Mozilla.sk] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|kusavica|Juraj Cigáň}}||<br /> |}<br /> <br /> === Are there other unofficial or Mozilla-related repositories hosted on Github? ===<br /> Why, yes! In no particular order:<br /> <br /> * [https://github.com/kinetiknz/cubeb/ https://github.com/kinetiknz/cubeb/] : Cubeb cross platform audio library.<br /> * [https://github.com/djg/cubeb-rs/ https://github.com/djg/cubeb-rs/] : Rust bindings for cubeb.<br /> * [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer.<br /> * [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.<br /> * [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.<br /> * [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters<br /> * [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler<br /> * [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology<br /> * [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.<br /> * [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.<br /> * [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications<br /> * [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests<br /> * [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.<br /> * [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)<br /> * [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.<br /> * [https://github.com/jeffbryner/MozDef https://github.com/jeffbryner/MozDef]: Mozilla Defense Platform.<br /> * [https://github.com/jgraham/webdriver-rust https://github.com/jgraham/webdriver-rust]: WebDriver library for Rust.<br /> * [https://github.com/ehsan/mozilla-cvs-history https://github.com/ehsan/mozilla-cvs-history]: A git conversion of the full Mozilla CVS history, useful for code archaeology.<br /> * [https://github.com/djg/audioipc-2 https://github.com/djg/audioipc-2]: Audio IPC for Gecko.<br /> * [https://github.com/hsivonen/encoding_rs https://github.com/hsivonen/encoding_rs]: encoding_rs (character encoding converters for Gecko)<br /> * [https://github.com/choller/firefox-asan-reporter https://github.com/choller/firefox-asan-reporter] : Internal addon used in conjunction with special ASan builds of Firefox.<br /> * [https://github.com/jrmuizel/qcms https://github.com/jrmuizel/qcms] : Fork of 'quick color management' for Firefox<br /> * https://github.com/webcompat : Web Compatibility Team (Industry wide) -- {{Mozillian|miketaylr|Mike Taylor}}</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2020-03-02&diff=1224433 2020-03-02T15:51:09Z

<p>Mhoye: Adding my name.</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch anonymously at https://air.mozilla.org.<br /> * join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion<br /> * If you plan on presenting, please join the Zoom video chat 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> * '''Presenters only:''' Zoom Meeting ID: 828 817 988 [https://mozilla.zoom.us/j/828817988 https://mozilla.zoom.us/j/828817988.] Do '''not''' use this room if you're not planning to speak. <br /> * One-tap mobile<br /> ** +16465588656,,828817988# US (New York)<br /> ** +17207072699,,828817988# US<br /> * Dial-in by your location<br /> ** +1 646 558 8656 US (New York)<br /> ** +1 720 707 2699 US<br /> ** 877 853 5257 US Toll-free<br /> ** +61 2 8015 2088 Australia<br /> ** +61 8 7150 1149 Australia<br /> ** 1800 893 423 Australia Toll-free<br /> ** +1 647 558 0588 Canada<br /> ** +33 1 8288 0188 France<br /> ** +33 7 5678 4048 France<br /> ** 0 805 082 588 France Toll-free<br /> ** +49 30 5679 5800 Germany<br /> ** +49 69 8088 3899 Germany<br /> ** +49 30 3080 6188 Germany<br /> ** 800 724 3138 Germany Toll-free<br /> ** +852 5808 6088 Hong Kong, China<br /> ** +44 203 695 0088 United Kingdom<br /> ** +44 203 966 3809 United Kingdom<br /> ** +44 203 051 2874 United Kingdom<br /> ** 0 800 031 5717 United Kingdom Toll-free<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> <br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details. <br /> <br /> ''' Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details. <br /> <br /> <br /> '''[https://refactr.tech/index.html/ REFACTR.TECH 2020]''' Atlanta, GA | 2020-04-22<br /> <br /> '''[https://smashingconf.com/sf-2020/ Smashing Conference San Francisco]''' San Francisco | 2020-04-21<br /> <br /> '''[https://beyondtellerrand.com/events/dusseldorf-2020/ beyond tellerrand // DÜSSELDORF]''' Dusseldorf | 2020-04-27<br /> <br /> '''[https://www.writethedocs.org/conf/portland/2020/ Write the Docs, Portland]''' Portland | 2020-05 03-05<br /> <br /> '''[https://smashingconf.com/austin-2020/ Smashing Conference Austin]''' Austin | 2020-06-09<br /> <br /> '''[https://beyondtellerrand.com/events/berlin-2020/ beyond tellerrand // BERLIN]''' Berlin | 2020-09-07<br /> <br /> '''[https://smashingconf.com/freiburg-2020/ Smashing Conference Freiburg]''' Freiburg | 2020-09-07<br /> <br /> '''[https://www.writethedocs.org/conf/prague/2019/ Write the Docs, Prague]''' Prague | 2020-09 15-17<br /> <br /> '''[https://smashingconf.com/ny-2020/ Smashing Conference New York]''' New York | 2020-10-20<br /> <br /> '''[https://beyondtellerrand.com/events/munich-2020/ beyond tellerrand // MUNICH]''' Munich | 2020-11-02<br /> <br /> <br /> <br /> ''' Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> [https://2020.indieweb.org/london 🎡 IndieWebCamp London 2020] | 03/14/20 - 03/15/20 | London, England<br /> <br /> CSS Conf Colombia | 03/21/20 | Medellín, Colombia<br /> <br /> Mozilla x Bit Web of Things Workshop | 03/23/20 | Davis, CA<br /> <br /> PerfMatters Conference 2020 | 03/31/20 - 04/02/20 | Redwood City, CA USA<br /> <br /> JS Kongress Munich | 04/15-16/20 | Munich, Germany<br /> <br /> PyCon US 2020 | 04/15-18/20 | Pittsburgh, USA<br /> <br /> Smashing Conference San Francisco 2020 | 04/21-22/20 | San Francisco<br /> <br /> REFACTR.TECH 2020 | 04/22-24/20 | Atlanta<br /> <br /> Mozilla x Bit Web of Things Workshop | 04/23/20 | Davis, CA<br /> <br /> JS Heros | 04/23-24/20 | Cluj-Napoca, Cluj, Romania<br /> <br /> beyond tellerrand // DÜSSELDORF | 04/27-29/20 | Dusseldorf<br /> <br /> Frontend United Minsk 2020 | 05/01-02/20 | Minsk, Republic of Belarus<br /> <br /> Write the Docs Portland 2020 | 05/03-05/20 | Portland, US<br /> <br /> Rust Latam Conference | 05/22-23/20 | Mexico City<br /> <br /> Tech Interior 2020 | 05/23/20| Jaboticabal, São Paulo, Brazil<br /> <br /> Rustfest Utrecht | 06/06-07/20 | Utrecht, The Netherlands<br /> <br /> Smashing Conference Austin 2020 | 06/9-10/20 | Austin<br /> <br /> CSS Day | 06/11-12/20 | Amsterdam, Netherlands<br /> <br /> [https://2020.indieweb.org/summit ⛰ IndieWeb Summit 2020] | 06/27/20 - 06/28/20 | Portland, Oregon, USA<br /> <br /> Smashing Conference Freiburg 2020 | 09/7-8/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // BERLIN | 09/7-10/20 | Berlin<br /> <br /> Smashing Conference New York 2020 | 10/20-21/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // MUNICH | 11/2-4/20 | Munich<br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Mike Hoye<br /> | Today, I bring you good news of the present and future.<br /> | Your Development Environment<br /> | The Future (but also Toronto)<br /> | Yes.<br /> | <br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Their Name<br /> | Your Name<br /> | Intro location<br /> | Their Location<br /> | Their Role<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix:Bots&diff=1223766 2020-02-13T20:58:37Z

<p>Mhoye: bolding</p> <hr /> <div>== Matrix Bots! ==<br /> <br /> One of the many joys of Matrix is that making bots that do useful or amusing things is simple and fun. Unfortunately, like everything made of software, making things is a lot simpler and more fun than maintaining them, so we have a few things we need to ask of bot developers to keep Matrix usable and sustainable for everyone.<br /> <br /> === Bot Guidelines ===<br /> <br /> This list isn't mandatory, but we ask that you consider these suggestions carefully.<br /> <br /> * Please use a service account! You can request one in Bugzilla, under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&amp;component=Matrix Infrastructure &amp; Operations :: Matrix]. This lets us restrict account access to only what the bot needs, and if your bot misbehaves we can disable the service credentials rather than disabling yours. <br /> * If your bot sends messages automatically, consider building in some rate-limiting so it doesn't spam people or channels accidentally.<br /> * Remember: like all Mozilla forums, Matrix is governed by our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and '''authors are responsible for their bots' actions'''.<br /> * Finally, as a courtesy we ask that you add your bot to the following list in case somebody needs to contact you.<br /> <br /> === Matrix Bot List ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Bot Name !! Bot description !! Owner Bugmail !! Bot Service Account !! Source Repository<br /> |-<br /> | || || || ||<br /> |-<br /> |}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix:Bots&diff=1223765 2020-02-13T19:50:13Z

<p>Mhoye: Formatting</p> <hr /> <div>== Matrix Bots! ==<br /> <br /> One of the many joys of Matrix is that making bots that do useful or amusing things is simple and fun. Unfortunately, like everything made of software, making things is a lot simpler and more fun than maintaining them, so we have a few things we need to ask of bot developers to keep Matrix usable and sustainable for everyone.<br /> <br /> === Bot Guidelines ===<br /> <br /> This list isn't mandatory, but we ask that you consider these suggestions carefully.<br /> <br /> * Please use a service account! You can request one in Bugzilla, under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&amp;component=Matrix Infrastructure &amp; Operations :: Matrix]. This lets us restrict account access to only what the bot needs, and if your bot misbehaves we can disable the service credentials rather than disabling yours. <br /> * If your bot sends messages automatically, consider building in some rate-limiting so it doesn't spam people or channels accidentally.<br /> * Remember: like all Mozilla forums, Matrix is governed by our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and *author are responsible for their bot's actions*.<br /> * Finally, as a courtesy we ask that you add your bot to the following list in case somebody needs to contact you.<br /> <br /> === Matrix Bot List ===<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Bot Name !! Bot description !! Owner Bugmail !! Bot Service Account !! Source Repository<br /> |-<br /> | || || || ||<br /> |-<br /> |}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix:Bots&diff=1223763 2020-02-13T19:39:36Z

<p>Mhoye: </p> <hr /> <div>== Matrix Bots! ==<br /> <br /> One of the many joys of Matrix is that making bots that do useful or amusing things is simple and fun. Unfortunately, like everything made of software, making things is a lot simpler and more fun than maintaining them, so we have a few things we need to ask of bot developers to keep Matrix usable and sustainable for everyone.<br /> <br /> This list isn't mandatory, but we ask that you consider these suggestions carefully.<br /> <br /> - Please use a service account! You can request one in Bugzilla, under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&amp;component=Matrix Infrastructure &amp; Operations :: Matrix]. This lets us restrict account access to only what the bot needs, and if your bot misbehaves we can disable the service credentials rather than disabling yours. <br /> - If your bot sends messages automatically, consider building in some rate-limiting so it doesn't spam people or channels accidentally.<br /> - Remember: like all Mozilla forums, Matrix is governed by our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and *author are responsible for their bot's actions*.<br /> - Finally, as a courtesy we ask that you add your bot to the following list in case somebody needs to contact you:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Bot Name !! Bot description !! Owner Bugmail !! Bot Service Account !! Source Repository<br /> |-<br /> | || || || ||<br /> |-<br /> |}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix:Bots&diff=1223762 2020-02-13T19:29:42Z

<p>Mhoye: Creating Bot Registry page.</p> <hr /> <div>== Matrix Bots! ==<br /> <br /> One of the many joys of Matrix is that making bots that do useful or amusing things is simple and fun. Unfortunately, like everything made of software, making things is a lot simpler and more fun than maintaining them, so we have a few things we need to ask of bot developers to keep Matrix usable and sustainable for everyone.<br /> <br /> This list isn't mandatory, but please consider these suggestions carefully.<br /> <br /> - Please use a service account! You can request one in Bugzilla, under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&amp;component=Matrix Infrastructure &amp; Operations :: Matrix]. This lets us restrict account access to only what the bot needs, and if your bot misbehaves we can disable the service credentials rather than disabling yours. <br /> - If your bot sends messages automatically, consider building in some rate-limiting so it doesn't spam people or channels accidentally.<br /> - Remember: like all Mozilla forums, Matrix is governed by our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and *author are responsible for their bot's actions*.<br /> - Finally, as a courtesy we ask that you add your bot to the following list in case somebody needs to contact you:<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Bot Name !! Bot description !! Owner Bugmail !! Bot Service Account !! Source Repository<br /> |-<br /> | || || || ||<br /> |-<br /> |}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1223730 2020-02-12T21:10:54Z

<p>Mhoye: </p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://riot.im/app/#/welcome Riot webapp] and create an account. Once you're signed in, clicking these links will let you join the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Mozilla, already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by opening the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; we're working on it and we'll have a longer list of channels here soon. In the meantime, those are friendly channels and the people there will be able to help you find your way around. You can start using Matrix directly via the [https://riot.im/app/ Riot webapp] or one of the many [https://riot.im/ native applications] available.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix, already part of Mozilla? ===<br /> <br /> [https://riot.im/app/#/room/#general:mozilla.org Then get over there!] <br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> Clients which currently support Single Sign-On include:<br /> <br /> * riot-web, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://riot.im/download/desktop/ download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Riot Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> ** [https://play.google.com/store/apps/details?id=im.vector.riotx RiotX] is the next generation Matrix client for Android (also [https://f-droid.org/en/packages/im.vector.riotx/ available on F-Droid])<br /> * [https://apps.apple.com/gb/app/riot-im/id1083446067 Riot iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click Explore in the upper left and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Project rooms ===<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Riot and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1223729 2020-02-12T21:09:57Z

<p>Mhoye: Corrections</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started == <br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://riot.im/app/#/welcome Riot webapp] and create an account. Once you're signed in, you can join the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Mozilla, already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by opening the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; we're working on it and we'll have a longer list of channels here soon. In the meantime, those are friendly channels and the people there will be able to help you find your way around. You can start using Matrix directly via the [https://riot.im/app/ Riot webapp] or one of the many [https://riot.im/ native applications] available.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] section below.<br /> <br /> === Already using Matrix, already part of Mozilla? ===<br /> <br /> [https://riot.im/app/#/room/#general:mozilla.org Then get over there!] <br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> <br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> <br /> * Review the CPG and privacy notices and press the Sign In button<br /> <br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> <br /> * On the sign in page, proceed to Sign in with single sign-on<br /> <br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> <br /> * Pick your choice of services to authenticate from<br /> <br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> <br /> * Pick your username!<br /> <br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> Clients which currently support Single Sign-On include:<br /> <br /> * riot-web, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://riot.im/download/desktop/ download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Riot Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> ** [https://play.google.com/store/apps/details?id=im.vector.riotx RiotX] is the next generation Matrix client for Android (also [https://f-droid.org/en/packages/im.vector.riotx/ available on F-Droid])<br /> * [https://apps.apple.com/gb/app/riot-im/id1083446067 Riot iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> <br /> ==== Connection parameters ====<br /> <br /> While the default parameters in most clients will work just fine, if you're already part of the Mozilla community or want to connect directly to the Mozilla Matrix instance. To do that, you'll need to change the following settings:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click Explore in the upper left and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Project rooms ===<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Riot and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1223728 2020-02-12T20:43:44Z

<p>Mhoye: /* New to Matrix, new to Mozilla? */</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started ==<br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://riot.im/app/#/welcome Riot webapp] and create an account. Once you're signed in, you can join the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [https://wiki.mozilla.org/Matrix#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Mozilla, already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by opening the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; we're working on it and we'll have a longer list of channels here soon. In the meantime, those are friendly channels and the people there will be able to help you find your way around. You can start using Matrix directly via the [https://riot.im/app/ Riot webapp] or one of the many [https://riot.im/ native applications] available.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [Connect to Matrix] section below.<br /> <br /> === Already using Matrix, already part of Mozilla? ===<br /> <br /> [https://riot.im/app/#/room/#general:mozilla.org Then get over there!] <br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> * Review the CPG and privacy notices and press the Sign In button<br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> * On the sign in page, proceed to Sign in with single sign-on<br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> * Pick your choice of services to authenticate from<br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> * Pick your username!<br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> Clients which currently support Single Sign-On include:<br /> <br /> * riot-web, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://riot.im/download/desktop/ download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Riot Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> ** [https://play.google.com/store/apps/details?id=im.vector.riotx RiotX] is the next generation Matrix client for Android (also [https://f-droid.org/en/packages/im.vector.riotx/ available on F-Droid])<br /> * [https://apps.apple.com/gb/app/riot-im/id1083446067 Riot iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> <br /> ==== Connection parameters ====<br /> <br /> Irrespective of the choice of client, here are the parameters to connect your client to the Mozilla Matrix instance:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click Explore in the upper left and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Project rooms ===<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Riot and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Matrix&diff=1223727 2020-02-12T20:42:20Z

<p>Mhoye: Update and cleanup - mhoye</p> <hr /> <div><br /> == &quot;What is the Matrix?&quot; ==<br /> [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. <br /> <br /> After a long evaluation period, Mozilla has switched to Matrix from [[IRC]] as our preferred open discussion platform. Matrix is a huge improvement in usability, accessibility and safety for the Mozilla community, and we're excited to make this change.<br /> <br /> == Community Participation at Mozilla ==<br /> <br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes the participation of everyone who shares our goals and wants to contribute in a healthy and constructive manner within our communities. To that end, as with all Mozilla spaces and events we expect participants in our Matrix forums to support and uphold the Mozilla [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] as a condition of participation. <br /> <br /> == Getting Started ==<br /> <br /> === New to Matrix, new to Mozilla? === <br /> <br /> Start with the [https://riot.im/app/#/welcome Riot webapp] and create an account. Once you're signed in, you can join the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] channel for general questions or [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. There are lots more channels to choose from - there's a list of some of them below - and we'll have more as soon as we get them sorted out. <br /> <br /> For more details, scroll down to [#Connect_to_Matrix Connect to Matrix ] below.<br /> <br /> === New to Mozilla, already using Matrix? ===<br /> <br /> If you're already using Matrix, you can join the Mozilla conversation by opening the [https://riot.im/app/#/room/#general:mozilla.org #general:mozilla.org] room for general topics and [https://riot.im/app/#/room/#introduction:mozilla.org #introduction:mozilla.org] if you're interested in getting involved with the Mozilla development process. The whole Mozilla list of rooms isn't settled out and synchronizing across the Matrix ecosystem yet; we're working on it and we'll have a longer list of channels here soon. In the meantime, those are friendly channels and the people there will be able to help you find your way around. You can start using Matrix directly via the [https://riot.im/app/ Riot webapp] or one of the many [https://riot.im/ native applications] available.<br /> <br /> === New to Matrix, already part of Mozilla? ===<br /> <br /> [https://chat.mozilla.org/#/login Mozilla's Matrix server] is configured to use Mozilla IAM, and supports the following accounts:<br /> <br /> * Mozilla LDAP<br /> * [https://www.mozilla.org/firefox/accounts/ Firefox Accounts]<br /> * [https://github.com/ Github]<br /> * [https://myaccount.google.com/ Google]<br /> <br /> Any of those will work if you go through the [https://chat.mozilla.org/ web interface]; the details are in the [Connect to Matrix] section below.<br /> <br /> === Already using Matrix, already part of Mozilla? ===<br /> <br /> [https://riot.im/app/#/room/#general:mozilla.org Then get over there!] <br /> <br /> === Community Participation Guidelines ===<br /> The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community<br /> <br /> Despite our very best efforts, occasionally people do experience behaviors on Matrix that are not inline with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines]. If happens to you, please reach out to the room moderator or use our [https://events.mozilla.org/communityparticipationhotline reporting hotline].<br /> <br /> == Connect to Matrix ==<br /> <br /> === Register a username ===<br /> The quickest way to register a username on Mozilla Matrix is through the web interface.<br /> <br /> * Open https://chat.mozilla.org/<br /> * Review the CPG and privacy notices and press the Sign In button<br /> [[File:Chatmo-welcome-screen.png|frame|none|alt=Welcome screen on chat.mozilla.org]]<br /> * On the sign in page, proceed to Sign in with single sign-on<br /> [[File:Chatmo-signin-page.png|frame|none|alt=Sign in page on chat.mozilla.org]]<br /> * Pick your choice of services to authenticate from<br /> [[File:Am-screen.png|frame|none|alt=Mozilla IAM sign in page]]<br /> * Pick your username!<br /> [[File:Chatmo-pick-username.png|frame|none|alt=Pick your username on chat.mozilla.org]]<br /> <br /> === Clients ===<br /> <br /> Matrix supports a variety of clients on web, desktop, and mobile. You can readily connect to the web client from https://chat.mozilla.org/. Matrix maintains a list of clients on [https://matrix.org/clients/ their website].<br /> <br /> Clients which currently support Single Sign-On include:<br /> <br /> * riot-web, the software behind [https://chat.mozilla.org chat.mozilla.org]<br /> ** this is also available as a desktop client: [https://riot.im/download/desktop/ download here]<br /> * [https://play.google.com/store/apps/details?id=im.vector.app Riot Android] (also [https://f-droid.org/en/packages/im.vector.alpha/ available on F-Droid])<br /> ** [https://play.google.com/store/apps/details?id=im.vector.riotx RiotX] is the next generation Matrix client for Android (also [https://f-droid.org/en/packages/im.vector.riotx/ available on F-Droid])<br /> * [https://apps.apple.com/gb/app/riot-im/id1083446067 Riot iOS]<br /> * weechat, using the [https://github.com/poljar/weechat-matrix/ weechat-matrix protocol script]. Note the [https://github.com/poljar/weechat-matrix/#single-sign-on Single Sign-On instructions].<br /> <br /> ==== Connection parameters ====<br /> <br /> Irrespective of the choice of client, here are the parameters to connect your client to the Mozilla Matrix instance:<br /> <br /> {|<br /> |-<br /> | '''Homeserver'''<br /> | &lt;nowiki&gt;https://mozilla.modular.im&lt;/nowiki&gt;<br /> |-<br /> | '''Identity server'''<br /> | &lt;nowiki&gt;https://vector.im&lt;/nowiki&gt;<br /> |}<br /> <br /> === Joining a room ===<br /> <br /> When connected to the Mozilla Matrix server you can join Mozilla rooms and also rooms on other Matrix servers.<br /> <br /> There are several different ways to join a room:<br /> * You can follow an external link. (For example, see the links to commonly used rooms lower on this page.)<br /> * You can follow links from inside a discussion on Matrix.<br /> * You can receive an invitation from another Matrix member.<br /> * There are also platform specific methods:<br /> ** On https://chat.mozilla.org/ you can click Explore in the upper left and search the known rooms to see information about the rooms and then preview or join the rooms. On the left side you can select or enter another Matrix server and search for non-Mozilla rooms.<br /> ** Other platforms: TBA<br /> <br /> When you follow a link you you may be given a choice to preview the contents of the room or to join. If the room doesn't allow preview you may be asked if you want to join it without a preview first.<br /> <br /> But it is also easy to leave a room. On https://chat.mozilla.org/ find the room name (or icon) in the room list on the left and click the three vertical dots to the left of the name. There are several options on how you want to read the room. plus the option to leave.<br /> <br /> == Commonly used rooms ==<br /> <br /> === General discussion ===<br /> * [https://chat.mozilla.org/#/room/#general:mozilla.org #general:mozilla.org ] - General discussions about Mozilla<br /> * [https://chat.mozilla.org/#/room/#developers:mozilla.org #developers:mozilla.org] - General Firefox and Gecko development discussion<br /> * [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction:mozilla.org] - Help with basics of developing for Mozilla<br /> * [https://chat.mozilla.org/#/room/#synchronicity:mozilla.org #synchronicity:mozilla.org] - Sorting out bugs and papercuts in the migration from IRC to Matrix<br /> <br /> === Project rooms ===<br /> <br /> === Specific areas ===<br /> * [https://chat.mozilla.org/#/room/#l10n-community:mozilla.org #l10n-community:mozilla.org] - Discussion about localization (l10n) of Mozilla applications<br /> <br /> === Specific locations ===<br /> * [https://chat.mozilla.org/#/room/#berlin:mozilla.org #berlin:mozilla.org] - General chat for people in the Berlin office<br /> * [https://chat.mozilla.org/#/room/#canada:mozilla.org #canada:mozilla.org] - General chat for the Canadian Mozilla community<br /> * [https://chat.mozilla.org/#/room/#mozfr:mozilla.org #mozfr:mozilla.org] - Communauté francophone de mozfr.org - French speaking community from mozfr.org<br /> * [https://chat.mozilla.org/#/room/#Mozilla_NL:mozilla.org #Mozilla_NL:mozilla.org] - Voor Nederlands sprekende medewerkers en vrijwilligers van Mozilla<br /> * [https://chat.mozilla.org/#/room/#mozilla-hispano:mozilla.org #mozilla-hispano:mozilla.org] - Comunidad en español de Mozilla https://www.mozilla-hispano.org/<br /> * [https://chat.mozilla.org/#/room/#toronto:mozilla.org #toronto:mozilla.org] - General chat for people in the Toronto office<br /> * [https://chat.mozilla.org/#/room/#vancouver:mozilla.org #vancouver:mozilla.org] - General chat for people in the Vancouver office<br /> <br /> === Rooms in other languages ===<br /> <br /> ====Lithuanian====<br /> * [https://chat.mozilla.org/#/room/#l10n-lt:mozilla.org #l10n-lt:mozilla.org] – Lithuanian l10n community<br /> <br /> == Feedback ==<br /> For feedback on Riot and Matrix, head to [https://chat.mozilla.org/#synchronicity:mozilla.org #synchronicity:mozilla.org]<br /> <br /> == History ==<br /> * On March 2020, Mozilla moved from [[IRC]] to Matrix.</div>

Mhoye https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&diff=1222822 2020-01-23T16:13:37Z

<p>Mhoye: removing dead bots</p> <hr /> <div>Some times you want a BMO account that is not a real person.<br /> That's okay -- in fact it is a good security measure!<br /> <br /> However this comes with some problems -- if we (the bmo admins) can't tell who owns a bot,<br /> and we have to make a decision that might break we have no way of informing the owner except<br /> to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,<br /> we can help avoid future breakages!<br /> <br /> If you include a link to the repo, things can be even smoother.<br /> <br /> Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. <br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo<br /> |-<br /> | pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/<br /> |-<br /> | treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub's Bugzilla integration]<br /> |-<br /> | intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder<br /> |-<br /> | orangefactor@bots.tld || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/<br /> |-<br /> | webops-kanban@mozilla.bugs || atoll || Unknown || Token || <br /> |-<br /> | mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown<br /> |-<br /> | release-mgmt-account-bot@mozilla.tld || cdenizet@mozilla.com || rest || api-key || https://github.com/mozilla/relman-auto-nag/<br /> |-<br /> | slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi<br /> |-<br /> | flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown<br /> |- <br /> | webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD<br /> |-<br /> | pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker<br /> |-<br /> | moc-queue-bot@mozilla.bugs || moc@mozilla.com || rest || api-key || git-internal/puppet/modules/moc_bug_queuemon<br /> |-<br /> | omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools<br /> |-<br /> | bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]<br /> |-<br /> | reviewbot@mozilla.com || babadie@mozilla.com || rest || api-key; phabricator-token || https://github.com/mozilla/code-review<br /> |-<br /> | upliftbot@mozilla.com || babadie@mozilla.com || rest || api-key; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/uplift/bot<br /> |-<br /> | wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync<br /> |-<br /> | release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use<br /> |-<br /> | foxsec-pytest@mozilla.com || abahnken@mozilla.com || rest; xmlrpc || api-key || https://github.com/mozilla-services/pytest-services<br /> |-<br /> | experimenter@mozilla.com || jbuckley@mozilla.com || rest || api-key || https://github.com/mozilla/experimenter<br /> |-<br /> | bugmail@firebot.glob.uno || glob@mozilla.com || rest || anon || https://github.com/globau/firebot<br /> |-<br /> | bteam-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard<br /> |-<br /> | conduit-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard/tree/conduit<br /> |- <br /> | jitbugs@mozilla.bugs || mgaudet@mozilla.com || n/a || n/a || Watchable Account for JavaScript JIT Bug Reviews<br /> |-<br /> | relops-bug-generator@mozilla.com || jwatkins@mozilla.com || n/a || n/a || Automated Bug Generation for RelOps<br /> |-<br /> | mozilla-apprentice@mcc.id.au || cam@mcc.id.au || rest || api-key || https://github.com/heycam/wg-tracker<br /> |-<br /> | security-baseline@bots.tld || sbennetts@mozilla.com || rest || api-key || https://github.com/mozilla-services/foxsec<br /> |}</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2020-01-13&diff=1222278 2020-01-13T19:02:46Z

<p>Mhoye: /* Speakers */</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2020-01-13 or anonymously at https://air.mozilla.org. Watch live in the Hubs 3D space (in browser) at https://hubs.mozilla.com/1rNht23/hubs-commons/. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=gIE2MJeC2pg.<br /> * join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion<br /> * If you plan on presenting, please join the Zoom video chat 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> * '''Presenters only:''' Zoom Meeting ID: 828 817 988 [https://mozilla.zoom.us/j/828817988 https://mozilla.zoom.us/j/828817988.] Do '''not''' use this room if you're not planning to speak. <br /> * One-tap mobile<br /> ** +16465588656,,828817988# US (New York)<br /> ** +17207072699,,828817988# US<br /> * Dial-in by your location<br /> ** +1 646 558 8656 US (New York)<br /> ** +1 720 707 2699 US<br /> ** 877 853 5257 US Toll-free<br /> ** +61 2 8015 2088 Australia<br /> ** +61 8 7150 1149 Australia<br /> ** 1800 893 423 Australia Toll-free<br /> ** +1 647 558 0588 Canada<br /> ** +33 1 8288 0188 France<br /> ** +33 7 5678 4048 France<br /> ** 0 805 082 588 France Toll-free<br /> ** +49 30 5679 5800 Germany<br /> ** +49 69 8088 3899 Germany<br /> ** +49 30 3080 6188 Germany<br /> ** 800 724 3138 Germany Toll-free<br /> ** +852 5808 6088 Hong Kong, China<br /> ** +44 203 695 0088 United Kingdom<br /> ** +44 203 966 3809 United Kingdom<br /> ** +44 203 051 2874 United Kingdom<br /> ** 0 800 031 5717 United Kingdom Toll-free<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> <br /> * The Mozilla Tech Speakers crew would like to give a big thanks to Jyotsna Gupta who spoke about WebExtensions at the University of Moratuwa this past week. Thanks Jyotsna for helping to spread the word!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * [https://wiki.mozilla.org/Add-ons/Community/Meetings Add-ons Community Meeting]<br /> ** 16:30 UTC / 8:30am PST | [[ https://mozilla.zoom.us/j/651669664|Zoom meeting room]]<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> * [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit# Add-ons Show &amp; Tell]<br /> ** Bring your add-ons related projects to our monthly demos meeting! <br /> ** 13:30 UTC / 7:30am PST | [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit#heading=h.jpqwxn76o9w2 Agenda] | [https://mozilla.zoom.us/j/219966745 Zoom]<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> <br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details. <br /> <br /> '''[https://halfstackconf.com/ Halfstack]''' Phoenix, AZ | 2020-01-17 <br /> <br /> '''[https://refactr.tech/index.html/ REFACTR.TECH 2020]''' Atlanta, GA | 2020-04-22<br /> <br /> '''[https://2020.pycascades.com/ PyCascades]''' Portland | 2020-02-08<br /> <br /> '''[https://smashingconf.com/sf-2020/ Smashing Conference San Francisco]''' San Francisco | 2020-04-21<br /> <br /> '''[https://beyondtellerrand.com/events/dusseldorf-2020/ beyond tellerrand // DÜSSELDORF]''' Dusseldorf | 2020-04-27<br /> <br /> '''[https://smashingconf.com/austin-2020/ Smashing Conference Austin]''' Austin | 2020-06-09<br /> <br /> '''[https://beyondtellerrand.com/events/berlin-2020/ beyond tellerrand // BERLIN]''' Berlin | 2020-09-07<br /> <br /> '''[https://smashingconf.com/freiburg-2020/ Smashing Conference Freiburg]''' Freiburg | 2020-09-07<br /> <br /> '''[https://smashingconf.com/ny-2020/ Smashing Conference New York]''' New York | 2020-10-20<br /> <br /> '''[https://beyondtellerrand.com/events/munich-2020/ beyond tellerrand // MUNICH]''' Munich | 2020-11-02<br /> <br /> <br /> <br /> ''' Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> Halfstack | 01/17/20 | Phoenix<br /> <br /> You Got This 2020 | 01/18/20 | Birmingham, UK<br /> <br /> PyCascades 2020 | 02/08/20 - 02/09/20| Portland<br /> <br /> Open Source Festival | 02/20/20 - 02/22/20 | Lagos, Nigeria<br /> <br /> Mozilla x Bit Web of Things Workshop | 02/21/20 | Davis, CA<br /> <br /> [https://2020.indieweb.org/austin 🌮 IndieWebCamp Austin 2020] | 02/22/20 - 02/23/20 | Austin, Texas, USA<br /> <br /> [https://2020.indieweb.org/london 🎡 IndieWebCamp London 2020] | 03/14/20 - 03/15/20 | London, England<br /> <br /> PerfMatters Conference 2020 | 03/31/20 - 04/02/20 | Redwood City, CA USA<br /> <br /> JS Kongress Munich | 04/15-16/20 | Munich, Germany<br /> <br /> Smashing Conference San Francisco 2020 | 04/21-22/20 | San Francisco<br /> <br /> REFACTR.TECH 2020 | 04/22-24/20 | Atlanta<br /> <br /> Mozilla x Bit Web of Things Workshop | 04/23/20 | Davis, CA<br /> <br /> beyond tellerrand // DÜSSELDORF | 04/27-29/20 | Dusseldorf<br /> <br /> Smashing Conference Austin 2020 | 06/9-10/20 | Austin<br /> <br /> [https://2020.indieweb.org/summit ⛰ IndieWeb Summit 2020] | 06/27/20 - 06/28/20 | Portland, Oregon, USA<br /> <br /> Smashing Conference Freiburg 2020 | 09/7-8/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // BERLIN | 09/7-10/20 | Berlin<br /> <br /> Smashing Conference New York 2020 | 10/20-21/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // MUNICH | 11/2-4/20 | Munich<br /> <br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Asa Dotzler<br /> | Team Firefox<br /> | Weekly Firefox Update<br /> | MTV<br /> | no<br /> | na<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2020-01-13 2020-01-13]<br /> |-<br /> | Ali Spivak<br /> | Director of Developer Relations<br /> | Emerging Technologies Update<br /> | MTV<br /> | no<br /> | n/a<br /> | [https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#January_13th.2C_2020 ET headlines]<br /> |-<br /> | Mike Hoye<br /> | Context Engineering<br /> | GSOC &amp; Engineering Org Lightning Talks<br /> | MoTo<br /> | no<br /> | n/a<br /> | <br /> |-<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Alex Dalenberg<br /> | Carolyn O'Hara<br /> | NYC<br /> | NYC<br /> | Recommendations Editor, Pocket<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2020-01-13&diff=1222275 2020-01-13T19:02:18Z

<p>Mhoye: /* Speakers */</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2020-01-13 or anonymously at https://air.mozilla.org. Watch live in the Hubs 3D space (in browser) at https://hubs.mozilla.com/1rNht23/hubs-commons/. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=gIE2MJeC2pg.<br /> * join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion<br /> * If you plan on presenting, please join the Zoom video chat 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> * '''Presenters only:''' Zoom Meeting ID: 828 817 988 [https://mozilla.zoom.us/j/828817988 https://mozilla.zoom.us/j/828817988.] Do '''not''' use this room if you're not planning to speak. <br /> * One-tap mobile<br /> ** +16465588656,,828817988# US (New York)<br /> ** +17207072699,,828817988# US<br /> * Dial-in by your location<br /> ** +1 646 558 8656 US (New York)<br /> ** +1 720 707 2699 US<br /> ** 877 853 5257 US Toll-free<br /> ** +61 2 8015 2088 Australia<br /> ** +61 8 7150 1149 Australia<br /> ** 1800 893 423 Australia Toll-free<br /> ** +1 647 558 0588 Canada<br /> ** +33 1 8288 0188 France<br /> ** +33 7 5678 4048 France<br /> ** 0 805 082 588 France Toll-free<br /> ** +49 30 5679 5800 Germany<br /> ** +49 69 8088 3899 Germany<br /> ** +49 30 3080 6188 Germany<br /> ** 800 724 3138 Germany Toll-free<br /> ** +852 5808 6088 Hong Kong, China<br /> ** +44 203 695 0088 United Kingdom<br /> ** +44 203 966 3809 United Kingdom<br /> ** +44 203 051 2874 United Kingdom<br /> ** 0 800 031 5717 United Kingdom Toll-free<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> <br /> * The Mozilla Tech Speakers crew would like to give a big thanks to Jyotsna Gupta who spoke about WebExtensions at the University of Moratuwa this past week. Thanks Jyotsna for helping to spread the word!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * [https://wiki.mozilla.org/Add-ons/Community/Meetings Add-ons Community Meeting]<br /> ** 16:30 UTC / 8:30am PST | [[ https://mozilla.zoom.us/j/651669664|Zoom meeting room]]<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> * [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit# Add-ons Show &amp; Tell]<br /> ** Bring your add-ons related projects to our monthly demos meeting! <br /> ** 13:30 UTC / 7:30am PST | [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit#heading=h.jpqwxn76o9w2 Agenda] | [https://mozilla.zoom.us/j/219966745 Zoom]<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> <br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details. <br /> <br /> '''[https://halfstackconf.com/ Halfstack]''' Phoenix, AZ | 2020-01-17 <br /> <br /> '''[https://refactr.tech/index.html/ REFACTR.TECH 2020]''' Atlanta, GA | 2020-04-22<br /> <br /> '''[https://2020.pycascades.com/ PyCascades]''' Portland | 2020-02-08<br /> <br /> '''[https://smashingconf.com/sf-2020/ Smashing Conference San Francisco]''' San Francisco | 2020-04-21<br /> <br /> '''[https://beyondtellerrand.com/events/dusseldorf-2020/ beyond tellerrand // DÜSSELDORF]''' Dusseldorf | 2020-04-27<br /> <br /> '''[https://smashingconf.com/austin-2020/ Smashing Conference Austin]''' Austin | 2020-06-09<br /> <br /> '''[https://beyondtellerrand.com/events/berlin-2020/ beyond tellerrand // BERLIN]''' Berlin | 2020-09-07<br /> <br /> '''[https://smashingconf.com/freiburg-2020/ Smashing Conference Freiburg]''' Freiburg | 2020-09-07<br /> <br /> '''[https://smashingconf.com/ny-2020/ Smashing Conference New York]''' New York | 2020-10-20<br /> <br /> '''[https://beyondtellerrand.com/events/munich-2020/ beyond tellerrand // MUNICH]''' Munich | 2020-11-02<br /> <br /> <br /> <br /> ''' Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> Halfstack | 01/17/20 | Phoenix<br /> <br /> You Got This 2020 | 01/18/20 | Birmingham, UK<br /> <br /> PyCascades 2020 | 02/08/20 - 02/09/20| Portland<br /> <br /> Open Source Festival | 02/20/20 - 02/22/20 | Lagos, Nigeria<br /> <br /> Mozilla x Bit Web of Things Workshop | 02/21/20 | Davis, CA<br /> <br /> [https://2020.indieweb.org/austin 🌮 IndieWebCamp Austin 2020] | 02/22/20 - 02/23/20 | Austin, Texas, USA<br /> <br /> [https://2020.indieweb.org/london 🎡 IndieWebCamp London 2020] | 03/14/20 - 03/15/20 | London, England<br /> <br /> PerfMatters Conference 2020 | 03/31/20 - 04/02/20 | Redwood City, CA USA<br /> <br /> JS Kongress Munich | 04/15-16/20 | Munich, Germany<br /> <br /> Smashing Conference San Francisco 2020 | 04/21-22/20 | San Francisco<br /> <br /> REFACTR.TECH 2020 | 04/22-24/20 | Atlanta<br /> <br /> Mozilla x Bit Web of Things Workshop | 04/23/20 | Davis, CA<br /> <br /> beyond tellerrand // DÜSSELDORF | 04/27-29/20 | Dusseldorf<br /> <br /> Smashing Conference Austin 2020 | 06/9-10/20 | Austin<br /> <br /> [https://2020.indieweb.org/summit ⛰ IndieWeb Summit 2020] | 06/27/20 - 06/28/20 | Portland, Oregon, USA<br /> <br /> Smashing Conference Freiburg 2020 | 09/7-8/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // BERLIN | 09/7-10/20 | Berlin<br /> <br /> Smashing Conference New York 2020 | 10/20-21/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // MUNICH | 11/2-4/20 | Munich<br /> <br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Asa Dotzler<br /> | Team Firefox<br /> | Weekly Firefox Update<br /> | MTV<br /> | no<br /> | na<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2020-01-13 2020-01-13]<br /> |-<br /> | Ali Spivak<br /> | Director of Developer Relations<br /> | Emerging Technologies Update<br /> | MTV<br /> | no<br /> | n/a<br /> | [https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#January_13th.2C_2020 ET headlines]<br /> |-<br /> | Mike Hoye<br /> | <br /> | GSOC &amp; Engineering Org Lightning Talks<br /> | MoTo<br /> | no<br /> | n/a<br /> | <br /> |-<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Alex Dalenberg<br /> | Carolyn O'Hara<br /> | NYC<br /> | NYC<br /> | Recommendations Editor, Pocket<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2020-01-13&diff=1222274 2020-01-13T19:01:34Z

<p>Mhoye: /* Speakers */</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2020-01-13 or anonymously at https://air.mozilla.org. Watch live in the Hubs 3D space (in browser) at https://hubs.mozilla.com/1rNht23/hubs-commons/. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=gIE2MJeC2pg.<br /> * join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion<br /> * If you plan on presenting, please join the Zoom video chat 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> * '''Presenters only:''' Zoom Meeting ID: 828 817 988 [https://mozilla.zoom.us/j/828817988 https://mozilla.zoom.us/j/828817988.] Do '''not''' use this room if you're not planning to speak. <br /> * One-tap mobile<br /> ** +16465588656,,828817988# US (New York)<br /> ** +17207072699,,828817988# US<br /> * Dial-in by your location<br /> ** +1 646 558 8656 US (New York)<br /> ** +1 720 707 2699 US<br /> ** 877 853 5257 US Toll-free<br /> ** +61 2 8015 2088 Australia<br /> ** +61 8 7150 1149 Australia<br /> ** 1800 893 423 Australia Toll-free<br /> ** +1 647 558 0588 Canada<br /> ** +33 1 8288 0188 France<br /> ** +33 7 5678 4048 France<br /> ** 0 805 082 588 France Toll-free<br /> ** +49 30 5679 5800 Germany<br /> ** +49 69 8088 3899 Germany<br /> ** +49 30 3080 6188 Germany<br /> ** 800 724 3138 Germany Toll-free<br /> ** +852 5808 6088 Hong Kong, China<br /> ** +44 203 695 0088 United Kingdom<br /> ** +44 203 966 3809 United Kingdom<br /> ** +44 203 051 2874 United Kingdom<br /> ** 0 800 031 5717 United Kingdom Toll-free<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> <br /> * The Mozilla Tech Speakers crew would like to give a big thanks to Jyotsna Gupta who spoke about WebExtensions at the University of Moratuwa this past week. Thanks Jyotsna for helping to spread the word!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * [https://wiki.mozilla.org/Add-ons/Community/Meetings Add-ons Community Meeting]<br /> ** 16:30 UTC / 8:30am PST | [[ https://mozilla.zoom.us/j/651669664|Zoom meeting room]]<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> * [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit# Add-ons Show &amp; Tell]<br /> ** Bring your add-ons related projects to our monthly demos meeting! <br /> ** 13:30 UTC / 7:30am PST | [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit#heading=h.jpqwxn76o9w2 Agenda] | [https://mozilla.zoom.us/j/219966745 Zoom]<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> <br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details. <br /> <br /> '''[https://halfstackconf.com/ Halfstack]''' Phoenix, AZ | 2020-01-17 <br /> <br /> '''[https://refactr.tech/index.html/ REFACTR.TECH 2020]''' Atlanta, GA | 2020-04-22<br /> <br /> '''[https://2020.pycascades.com/ PyCascades]''' Portland | 2020-02-08<br /> <br /> '''[https://smashingconf.com/sf-2020/ Smashing Conference San Francisco]''' San Francisco | 2020-04-21<br /> <br /> '''[https://beyondtellerrand.com/events/dusseldorf-2020/ beyond tellerrand // DÜSSELDORF]''' Dusseldorf | 2020-04-27<br /> <br /> '''[https://smashingconf.com/austin-2020/ Smashing Conference Austin]''' Austin | 2020-06-09<br /> <br /> '''[https://beyondtellerrand.com/events/berlin-2020/ beyond tellerrand // BERLIN]''' Berlin | 2020-09-07<br /> <br /> '''[https://smashingconf.com/freiburg-2020/ Smashing Conference Freiburg]''' Freiburg | 2020-09-07<br /> <br /> '''[https://smashingconf.com/ny-2020/ Smashing Conference New York]''' New York | 2020-10-20<br /> <br /> '''[https://beyondtellerrand.com/events/munich-2020/ beyond tellerrand // MUNICH]''' Munich | 2020-11-02<br /> <br /> <br /> <br /> ''' Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> Halfstack | 01/17/20 | Phoenix<br /> <br /> You Got This 2020 | 01/18/20 | Birmingham, UK<br /> <br /> PyCascades 2020 | 02/08/20 - 02/09/20| Portland<br /> <br /> Open Source Festival | 02/20/20 - 02/22/20 | Lagos, Nigeria<br /> <br /> Mozilla x Bit Web of Things Workshop | 02/21/20 | Davis, CA<br /> <br /> [https://2020.indieweb.org/austin 🌮 IndieWebCamp Austin 2020] | 02/22/20 - 02/23/20 | Austin, Texas, USA<br /> <br /> [https://2020.indieweb.org/london 🎡 IndieWebCamp London 2020] | 03/14/20 - 03/15/20 | London, England<br /> <br /> PerfMatters Conference 2020 | 03/31/20 - 04/02/20 | Redwood City, CA USA<br /> <br /> JS Kongress Munich | 04/15-16/20 | Munich, Germany<br /> <br /> Smashing Conference San Francisco 2020 | 04/21-22/20 | San Francisco<br /> <br /> REFACTR.TECH 2020 | 04/22-24/20 | Atlanta<br /> <br /> Mozilla x Bit Web of Things Workshop | 04/23/20 | Davis, CA<br /> <br /> beyond tellerrand // DÜSSELDORF | 04/27-29/20 | Dusseldorf<br /> <br /> Smashing Conference Austin 2020 | 06/9-10/20 | Austin<br /> <br /> [https://2020.indieweb.org/summit ⛰ IndieWeb Summit 2020] | 06/27/20 - 06/28/20 | Portland, Oregon, USA<br /> <br /> Smashing Conference Freiburg 2020 | 09/7-8/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // BERLIN | 09/7-10/20 | Berlin<br /> <br /> Smashing Conference New York 2020 | 10/20-21/20 | Freiburg, Germany<br /> <br /> beyond tellerrand // MUNICH | 11/2-4/20 | Munich<br /> <br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Asa Dotzler<br /> | Team Firefox<br /> | Weekly Firefox Update<br /> | MTV<br /> | no<br /> | na<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2020-01-13 2020-01-13]<br /> |-<br /> | Ali Spivak<br /> | Director of Developer Relations<br /> | Emerging Technologies Update<br /> | MTV<br /> | no<br /> | n/a<br /> | [https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#January_13th.2C_2020 ET headlines]<br /> |-<br /> | Mike Hoye<br /> | Context Engineering<br /> | GSOC &amp; Engineering Org Lightning Talks<br /> | MoTo<br /> | no<br /> | n/a<br /> | <br /> |-<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Alex Dalenberg<br /> | Carolyn O'Hara<br /> | NYC<br /> | NYC<br /> | Recommendations Editor, Pocket<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=CA/Policy_Participants&diff=1218098 2019-09-20T20:34:24Z

<p>Mhoye: </p> <hr /> <div>This is an optional list of the names, affiliations (if speaking for a company) and backgrounds of participants in the [https://www.mozilla.org/en-US/about/forums/#dev-security-policy mozilla.dev.security.policy] group. If you participate in this group, feel free to add yourself or not; please do not add anyone other than yourself. If getting a wiki account seems like a hassle, email mhoye@mozilla.com with your info and he will add it.<br /> <br /> Please keep the list in alphabetical order by first character of name, as used in From: email header. Use &quot;definition list&quot; markup (; for your name, : for the description).<br /> <br /> ; Alex Gaynor<br /> : Works for Mozilla; posting in a personal capacity with views not necessarily representing the views of Mozilla, unless otherwise noted.<br /> ; Ben Laurie<br /> : Founder of the Certificate Transparency project; posting in a personal capacity except where otherwise indicated.<br /> ; Devon O'Brien<br /> : Works for [https://www.google.com/ Google]; PKI policy for Chrome/ChromeOS; Posting in a personal capacity, with posts not necessarily representing the views of Google, except where otherwise noted.<br /> ; Eric Mill<br /> : [https://www.techcongress.io/ TechCongress] fellow, currently supporting the U.S. Senate for 2019. Posting in a personal capacity and not representing TechCongress or the U.S. Senate.<br /> ; Gijs Kruitbosch<br /> : Mozilla employee who works on Firefox frontend; Posting in a personal capacity except where otherwise indicated. Even when posting in official capacity, posts do not imply anything about the official position of the Mozilla CA Certificate Module (with which Gijs is not involved).<br /> ; Ken Myers<br /> : Senior Manager with Protiviti and also supports the U.S. Federal PKI; Always posting in a personal capacity except where otherwise indicated.<br /> ; Jason Milionis<br /> : University student on Electrical and Computer Engineering at the National Technical University of Athens; Firefox Student Ambassador; Posting in a personal capacity except where otherwise indicated.<br /> ; Kathleen Wilson<br /> : Owner of the [[Modules/All#CA_Certificates|Mozilla CA Certificates Module]]; posting in an official capacity.<br /> ; Kirk Hall <br /> : Works as Director Policy and Compliance - SSL for Entrust Datacard. I previously worked with Trend Micro and GeoTrust.<br /> ; Nick Lamb<br /> : aka tialaramex; Employee of [https://www.kynd.io/ Kynd]; posting in a personal capacity.<br /> ; Peter Bowen<br /> : Works for [https://aws.amazontrust.com/ Amazon Web Services]; posting in a personal capacity with posts not necessarily representing views of Amazon, except where otherwise indicated. <br /> ; Robin Alden<br /> : Works for [https://sectigo.com/ Sectigo Ltd]/; posting in an official capacity except where otherwise indicated.<br /> ; Rob Stradling<br /> : Works for [https://sectigo.com/ Sectigo Ltd]/; author of [https://crt.sh/ crt.sh]; posting in a personal capacity, with views not necessarily representing the views of Sectigo (unless otherwise noted).<br /> ; Ryan Hurst<br /> : Works for [https://www.google.com/ Google]; Product Manager for Certificate Transparency and other PKI related projects. Posting in an official capacity except where otherwise indicated.<br /> ; Ryan Sleevi<br /> : Peer of the [[Modules/All#CA_Certificates|CA Certificates Module]]; Works for [https://www.google.com/ Google]; PKI policy for Chrome/ChromeOS; Posting in a personal capacity, with posts not necessarily representing the views of Google or the Mozilla CA Certificate Module, except where otherwise noted.<br /> ; Tim Smith<br /> : Product data science at Mozilla since April 2018. Not organizationally associated with the root program; posts in personal capacity.<br /> ; Tom Ritter<br /> : Works at Mozilla but is not involved with the Mozilla CA Certificate Module, Firefox UI Frontend. Just cares about TLS, CAs, and CT. Not posting in an official capacity, unless otherwise noted (but probably never ever will.)<br /> ; Wayne Thayer<br /> : Works at Mozilla as a CA Program Manager; posting in an official capacity except where otherwise indicated.<br /> <br /> &lt;!-- Don't add your name down here - alphabetical order! Read the instructions :-) --&gt;</div>

Mhoye https://wiki.mozilla.org/index.php?title=Etherpad&diff=1217385 2019-09-03T20:13:48Z

<p>Mhoye: </p> <hr /> <div>= Mozilla Etherpad =<br /> <br /> Etherpad is a collaborative editing tool hosted by Mozilla. It is useful for co-operative document creation and editing, but should not be used as a long-term storage solution.<br /> <br /> '''Documents created in an Etherpad are temporary.''' If you need the text in an etherpad to be available at a later date, please put a copy of it in Mana, WikiMo or a Google Doc.<br /> <br /> == Link ==<br /> https://pad.mozilla.org/<br /> <br /> This is a '''public''' pad, so be careful what you put up there!</div>

Mhoye https://wiki.mozilla.org/index.php?title=Modules/Activities&diff=1216127 2019-08-07T14:05:17Z

<p>Mhoye: Updating Wikimo module ownership and removing defunct modules, per Governance discussion</p> <hr /> <div>&lt;noinclude&gt;<br /> '''Only module owners may edit this page.''' <br /> <br /> They may:<br /> <br /> * update any information about their module except the name of the owner<br /> * add or remove sub-modules<br /> * change the owner of a sub-module <br /> * add emeritus owners or peers<br /> <br /> Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br /> &lt;/noinclude&gt;<br /> {{Module<br /> |name=Governance<br /> |description=Policies and process for how we distribute authority and govern ourselves; including:<br /> * Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br /> * Management of the source tree<br /> * Balancing different constituencies of the Mozilla project<br /> * Maintaining the Mozilla identity as we take on new activities<br /> <br /> [http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=governance<br /> |url=https://wiki.mozilla.org/GovernanceIssues<br /> |components=mozilla.org::Governance<br /> }}<br /> <br /> ===Governance Sub Modules===<br /> <br /> {{Module<br /> |name=Module Ownership System<br /> |description=Healthy operation of the module ownership system, including topics such as:<br /> * Filling vacant roles where appropriate<br /> * Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br /> * Creating and staffing new modules where new parts of the project evolve.<br /> * Figuring out what to do if a module isn't getting enough attention<br /> * Resolving conflicts among module owners <br /> |owner= [mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker], Guillermo Movia (as 'observer'. This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br /> |ownersemeritus=Brendan Eich<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Commit Access Policy<br /> |description=<br /> |owner=[mailto:mconnor@mozilla.com Mike Connor]<br /> |peers=<br /> |ownersemeritus=Mitchell Baker<br /> |group=<br /> |url=http://www.mozilla.org/hacking/committer/<br /> |components=mozilla.org::Miscellaneous<br /> }}<br /> <br /> {{Module<br /> |name=Commit Access Implementation<br /> |description= Governance structure for the work of enforcing and implementing Mozilla's commit access policy.<br /> |owner=[mailto:marcia@mozilla.com Marcia Knous]<br /> |peers=[mailto:jmatthews@mozilla.com Josh Matthews]<br /> |group=<br /> |url=https://wiki.mozilla.org/Commit_Access_Implementation_module<br /> |components=mozilla.org::Repository Account Requests<br /> }}<br /> <br /> {{Module<br /> |name=Security Policy<br /> |description=<br /> |owner=[mailto:dveditz@mozilla.com Dan Veditz]<br /> |peers=[mailto:security@mozilla.org Al Billings]<br /> |group=dev-security<br /> |url=http://www.mozilla.org/security/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla CA Certificate Policy<br /> |description=Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies.<br /> |owner=[mailto:wthayer@mozilla.com Wayne Thayer]<br /> |peers=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |ownersemeritus=Frank Hecker, Kathleen Wilson<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham<br /> |group=dev-security-policy<br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Code Review Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |peersemeritus=Brendan Eich<br /> |group=<br /> |url=http://www.mozilla.org/hacking/reviewers.html<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Performance Regression Policy<br /> |description=<br /> |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee]<br /> |peers=<br /> |group=<br /> |url=<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Planet Mozilla<br /> |description=Content and policy for planet.mozilla.org, including topics such as:<br /> * which blogs are syndicated to planet.mozilla.org<br /> * which content from syndicated blogs is included<br /> * other planet.mozilla.org policy issues <br /> |owner=[mailto:mhoye@mozilla.com Mike Hoye]<br /> |peers=[mailto:asa@mozilla.org Asa Dotzler]<br /> |group=<br /> |url=<br /> |components=Websites::planet.mozilla.org<br /> |ownersemeritus=Robert Accettura<br /> |peersemeritus=Reed Loden<br /> }}<br /> <br /> {{Module<br /> |name=Mozilla Public License<br /> |description=Maintenance and development of the MPL<br /> * changes in the legal landscape which could /should be reflected<br /> * changes in FLOSS development practices which could / should be reflected <br /> |owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br /> |peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br /> |peersemeritus=Gervase Markham<br /> |group=governance-mpl-update<br /> |url=<br /> |components=mozilla.org::Licensing<br /> }}<br /> <br /> {{Module<br /> |name=CA Certificates<br /> |description=Determine which root certificates should be included in Mozilla software products, which trust bits should be set on them, and which of them should be enabled for EV treatment. Evaluate requests from Certification Authorities (CAs) for inclusion or removal of root certificates, and for updating trust bit settings or enabling EV treatment for already included root certificates.<br /> |owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br /> |peers=[mailto:sleevi@google.com Ryan Sleevi], [mailto:wthayer@mozilla.com Wayne Thayer]<br /> |ownersemeritus=Frank Hecker<br /> |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham<br /> |group=dev-security-policy <br /> |url=http://www.mozilla.org/projects/security/certs/policy/<br /> |components=mozilla.org::CA Certificates<br /> }}<br /> <br /> {{Module<br /> |name=Participation Metrics<br /> |description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br /> * determining which questions are most important to ask (how many people do X?)<br /> * determining what data is relevant to answer these questions<br /> * designing and operating a system to generate the requested data<br /> * analyzing the resulting metrics<br /> * notifying appropriate people when participation starts to change significantly<br /> * assisting various groups to understand and use the metrics to strengthen participation<br /> * produce periodic report/analysis of participation metrics <br /> |owner=[mailto:ppapadeas@mozilla.com Pierros Papadeas]<br /> |peers=[mailto:dboswell@mozilla.com David Boswell], [mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]<br /> |group=<br /> |url=https://wiki.mozilla.org/Contribute/Dashboards<br /> |components=<br /> }}<br /> <br /> {{Module<br /> |name=Internet Public Policy<br /> |description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: &quot;courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives.&quot; <br /> This includes topics such as:<br /> *determining if Mozilla should take an official position on a particular public policy issue<br /> *determining what that position is <br /> *determining how mozilla communicates our position <br /> **global, multi-regional, regional or local action<br /> **direct action, or support of action by other aligned groups<br /> **public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD<br /> *strengthening local community capabilities to address public policy issues <br /> |owner=[mailto:handerson@mozilla.com Harvey Anderson]<br /> |peers=[mailto:mitchell@mozilla.org Mitchell Baker], [mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman]<br /> |url=https://wiki.mozilla.org/Netpolicy<br /> |group=https://mail.mozilla.org/listinfo/netpolicy<br /> |components=<br /> |notes=Area Expert Advisors: Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos<br /> }}<br /> Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not. <br /> <br /> <br /> {{Module<br /> |name=Weekly Project All Hands Meeting<br /> |description=Responsibility for the weekly meetings, including:<br /> * determining and implementing the best organization and structure for the meeting<br /> * Determining and implementing the most useful content<br /> * Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br /> |owner=[mailto:asa@mozilla.org Asa Dotzler]<br /> |peers=MoCo Desktop IT services<br /> |ownersemeritus=[mailto:potch@mozilla.com Matt Claypotch]<br /> |group=mozilla.governance<br /> |url=https://wiki.mozilla.org/WeeklyUpdates<br /> |components=<br /> }}<br /> <br /> (It's a new thing to have a group such as &quot;MoCo Desktop IT services&quot; as a<br /> &quot;peer.&quot; We're trying this based on the idea that anyone in the Desktop IT group<br /> should be able to resolve problems and make fixes to the systems.)<br /> <br /> ===Other===<br /> <br /> {{Module<br /> |name=Tree Sheriffs<br /> |description=Tree Sheriffs aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. <br /> |owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen] (RyanVM)<br /> |peers=[mailto:wkocher@mozilla.com Wes Kocher (KWierso)], [mailto:cbook@mozilla.com Carsten Book (Tomcat)]<br /> |group=dev-tree-management<br /> |url=https://wiki.mozilla.org/Sheriffing<br /> |components=Tree Management::Visibility Requests<br /> }}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Modules/Mozilla_Websites&diff=1216126 2019-08-07T13:58:35Z

<p>Mhoye: Updating Wikimo module ownership and removing defunct modules, per Governance discussion</p> <hr /> <div>&lt;noinclude&gt;<br /> '''Only module owners may edit this page.''' <br /> <br /> They may:<br /> <br /> * update any information about their module except the name of the owner<br /> * add or remove sub-modules<br /> * change the owner of a sub-module <br /> * add emeritus owners or peers<br /> <br /> Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br /> &lt;/noinclude&gt;<br /> {{Module<br /> |name=Mozilla Communities Web Services<br /> |description=Web services provided to Mozilla's network of communities<br /> |owner=[mailto:stefan@mozilla.org.uk Stefan Costen]<br /> |peers=[mailto:majken@gmail.com Majken Connor], [mailto:tom@mozilla.org.uk Tom Farrow]<br /> |forum=https://discourse.mozilla-community.org/c/mcws<br /> }}<br /> {{Module<br /> |name=Mozilla Websites<br /> |description=Web apps developed or maintained inside Mozilla<br /> |owner=[mailto:lthomson@mozilla.com Laura Thomson]<br /> |peers=[mailto:wenzel@mozilla.com Fred Wenzel], [mailto:wclouser@mozilla.com Wil Clouser]<br /> |forum=https://groups.google.com/forum/mozilla.dev.webdev<br /> |url=https://wiki.mozilla.org/Webdev<br /> }}<br /> <br /> ===Mozilla Websites: Sub Modules===<br /> <br /> {{Module<br /> |name=Air Mozilla<br /> |description=Air Mozilla (webapp)<br /> |owner=[mailto:peterbe@mozilla.com Peter Bengtsson]<br /> |peers=[mailto:lthomson@mozilla.com Laura Thomson], [mailto:rmilewski@mozilla.com Richard Milewski], [mailto:lonnen@mozilla.com Chris Lonnen]<br /> |source_dirs=https://github.com/mozilla/airmozilla<br /> |group=https://lists.mozilla.org/listinfo/dev-mozilla-org<br /> |url=https://air-dev.allizom.org/<br /> |components=Product: Air Mozilla<br /> }}<br /> <br /> {{Module<br /> |name=AMO<br /> |description=Home of web extensions and themes.<br /> |owner=[mailto:scolville@mozilla.com Stuart Colville]<br /> |peers=[mailto:kmcmillan@mozilla.com Kumar McMillan], [mailto:mpillard@mozilla.com Mathieu Pillard]<br /> |ownersemeritus=Wil Clouser (2006-2014), Andy McKay (2014-2016) <br /> |source_dirs=https://github.com/mozilla/addons-server, https://github.com/mozilla/addons-frontend<br /> |group=https://lists.mozilla.org/listinfo/dev-addons<br /> |url=https://addons.mozilla.org/en-US/firefox/<br /> |components=Product: addons.mozilla.org<br /> }}<br /> <br /> {{Module<br /> |name=Bouncer<br /> |description=Mirror management software and download service<br /> |owner=[mailto:lthomson@mozilla.com Laura Thomson]<br /> |peers=Fred Wenzel, [mailto:aricaud@mozilla.com Anthony Ricaud]<br /> |source_dirs=https://github.com/mozilla/tuxedo<br /> |group=https://lists.mozilla.org/listinfo/dev-webdev<br /> |url=https://wiki.mozilla.org/Bouncer<br /> |components=Product: Webtools Component: Bouncer<br /> }}<br /> <br /> {{Module<br /> |name=Corsica<br /> |description=Empathic screen coordination service<br /> |owner=[mailto:lonnen@mozilla.com Chris Lonnen]<br /> |peers=[mailto:mcooper@mozilla.com Mike Cooper], [mailto:potch@mozilla.com Matt Claypotch]<br /> |source_dirs=https://github.com/mozilla/corsica<br /> |group=<br /> |url=<br /> |components=https://github.com/mozilla/corsica/issues<br /> }}<br /> <br /> {{Module<br /> |name=DXR<br /> |description=Source code static analysis and browsing<br /> |owner=[mailto:erik@mozilla.com Erik Rose]<br /> |peers=[mailto:abbeyj@gmail.com James Abbatiello], [mailto:willkg@mozilla.com Will Kahn-Greene], [mailto:mchanlatte@mozilla.com Marcell Vazquez-Chanlatte]<br /> |source_dirs=https://github.com/mozilla/dxr<br /> |group=https://lists.mozilla.org/listinfo/dev-static-analysis<br /> |url=https://dxr.mozilla.org/<br /> |components=Product: Webtools Component: DXR<br /> }}<br /> <br /> {{Module<br /> |name=Elmo<br /> |description=L10n web tool and dashboard<br /> |owner=[mailto:axel@mozilla.com Axel Hecht]<br /> |peers=[mailto:peterbe@mozilla.com Peter Bengtsson]<br /> |source_dirs=https://github.com/mozilla/elmo<br /> |group=https://lists.mozilla.org/listinfo/tools-elmo<br /> |url=https://l10n.mozilla.org/<br /> |components=Product: Webtools Component: Elmo<br /> }}<br /> <br /> {{Module<br /> |name=MDN Web Docs<br /> |description=Developer documentation site for web, Firefox, Firefox OS, Apps, etc<br /> |owner=[mailto:rjohnson@mozilla.com Ryan Johnson]<br /> |peers=[mailto:sneethling@mozilla.com Schalk Neethling],[mailto:dflanagan@mozilla.com David Flanagan],[mailto:pbengtsson@mozilla.com Peter Bengtsson]<br /> |ownersemeritus=[mailto:lcrouch@mozilla.com Luke Crouch], [mailto:shobson@mozilla.com Stephanie Hobson], [mailto:jwhitlock@mozilla.com John Whitlock]<br /> |peersemeritus=[mailto:jezdez@mozilla.com Jannis Leidel], [mailto:dwalsh@mozilla.com David Walsh], [mailto:openjck@mozilla.com John Karahalis], [mailto:robhudson@mozilla.com Rob Hudson], [mailto:willkg@mozilla.com Will Kahn-Greene]<br /> |source_dirs=https://github.com/mozilla/kuma, https://github.com/mdn<br /> |group=https://discourse.mozilla.org/c/mdn<br /> |url=https://developer.mozilla.org/<br /> |components=Product: developer.mozilla.org<br /> }}<br /> <br /> {{Module<br /> |name=Pad.Mozilla.Org (Formerly MoPad / Etherpad)<br /> |description=Mozilla's etherpad lite instance<br /> |owner=[mailto:mhoye@mozilla.com Mike Hoye]<br /> |ownersemeritus=[mailto:rhelmer@mozilla.com Rob Helmer]<br /> |peersemeritus=[mailto:nmaul@mozilla.com Jake Maul]<br /> |source_dirs=https://github.com/mozilla/etherpad-lite<br /> |group=https://lists.mozilla.org/listinfo/dev-webdev<br /> |url=https://wiki.mozilla.org/Etherpad<br /> |components=Websites::pad.mozilla.org<br /> }}<br /> <br /> {{Module<br /> |name=www.mozilla.org<br /> |description=Content and policy for www.mozilla.org. Sub-modules and their owners can be found [[Mozilla.org/Owners_List|here]].<br /> |owner=[mailto:pmclanahan@mozilla.com Paul McLanahan] (technical), [mailto:jbertsch@mozilla.com Jennifer Bertsch] (content)<br /> |peers=[mailto:ccook@mozilla.com Craig Cook], [mailto:agibson@mozilla.com Alex Gibson], [mailto:jpetto@mozilla.com Jon Petto]<br /> |source_dirs=https://github.com/mozilla/bedrock<br /> |group= dev-mozilla-org<br /> |url=https://www.mozilla.org/<br /> |components=www.mozilla.org <br /> }}<br /> <br /> {{Module<br /> |name=Mozilla Wiki<br /> |description=Mozilla Wiki<br /> |owner=[[User:SpikeUK1| Spike (Chris Foote)]]<br /> |peers=[[User:Mhoye|Mike Hoye]]<br /> |ownersemeritus=[[User:Ckoehler|Christie Koehler]]<br /> |peersemeritus=[[User:CaptainCalliope|Lyre Calliope]], [[User:GPHemsley|Gordon P. Hemsley]], [mailto:bkerensa@gmail.com Benjamin Kerensa]<br /> |source_dirs=https://github.com/mozilla/mediawiki-skins-gmo<br /> |group=https://lists.mozilla.org/listinfo/tools-wiki<br /> |url=https://wiki.mozilla.org<br /> |components=Websites &gt; wiki.mozilla.org<br /> }}<br /> <br /> {{Module<br /> |name=Mozillians<br /> |description=Community directory for Mozilla contributors.<br /> |owner=[https://mozillians.org/en-US/u/jgiannelos/ John Giannelos] [https://mozillians.org/en-US/u/akatsoulas/ Tasos Katsoulas]<br /> |peers=[https://mozillians.org/en-US/u/giorgos/ Giorgos Logiotatidis]<br /> |source_dirs=https://github.com/mozilla/mozillians<br /> |group=https://groups.google.com/forum/?fromgroups#!forum/mozilla-dev-community-tools<br /> |url=https://mozillians.org/<br /> |components=Product: Community Tools<br /> }}<br /> <br /> {{Module<br /> |name=Phonebook<br /> |description=Phonebook, talks to LDAP<br /> |owner=[mailto:atoll@mozilla.com Richard Soderberg]<br /> |peers=[mailto:lonnen@mozilla.com Lonnen], [mailto:tofumatt@mozilla.com Matthew R. McPherson]<br /> |source_dirs=https://github.com/mozilla/phonebook<br /> |group=https://lists.mozilla.org/listinfo/tools-phonebook<br /> |url=https://phonebook.mozilla.org/<br /> |components=Product: Webtools Component: Phonebook<br /> }}<br /> <br /> {{Module<br /> |name=Snippet Service<br /> |description=Snippet server for messaging found in highly trafficked product pages such as the Firefox start page.<br /> |owner=[mailto:glogiotatidis@mozilla.com Giorgos Logiotatidis]<br /> |peers=[mailto:mkelly@mozilla.com Michael Kelly]<br /> |source_dirs=https://github.com/mozilla/snippets-service<br /> |group=https://lists.mozilla.org/listinfo/dev-webdev<br /> |url=https://wiki.mozilla.org/Websites/Snippets<br /> |components=Product: Snippets<br /> }}<br /> <br /> {{Module<br /> |name=Socorro<br /> |description=Crash reporting for products (Firefox, etc)<br /> |owner=[mailto:willkg@mozilla.com Will Kahn-Greene]<br /> |peers=[mailto:lonnen@mozilla.com Chris Lonnen], <br /> [mailto:mkelly@mozilla.com Michael Kelly], [mailto:peterbe@mozilla.com Peter Bengtsson]<br /> |source_dirs=https://github.com/mozilla/socorro/<br /> |group=https://lists.mozilla.org/listinfo/tools-socorro<br /> |url=https://crash-stats.mozilla.com<br /> |components=Product: Socorro<br /> }}<br /> <br /> {{Module<br /> |name=Sumo<br /> |description=Mozilla support site and knowledgebase<br /> |owner=[mailto:mcooper@mozilla.com Mike Cooper]<br /> |peers=[mailto:willkg@mozilla.com Will Kahn-Greene], [mailto:rdalal@mozilla.com Rehan Dalal], [mailto:mkelly@mozilla.com Mike Kelly]<br /> |source_dirs=https://github.com/mozilla/kitsune<br /> |group=https://lists.mozilla.org/listinfo/dev-sumo<br /> |url=https://support.mozilla.org/en-US/home<br /> |components=Product: support.mozilla.org<br /> }}<br /> <br /> {{Module<br /> |name=telemetry.mozilla.org<br /> |description=The Firefox telemetry analysis websites and services, including sql.telemetry.mozilla.org, analysis.telemetry.mozilla.org, etc<br /> |owner=[mailto:chutten@mozilla.com Chris H-C]<br /> |peers=[mailto:fbertsch@mozilla.com Frank Bertsch], [mailto:chutten@mozilla.com Chris H-C], [mailto:bimsland@mozilla.com Blake Imsland], [mailto:jezdez@mozilla.com Jannis Leidel]<br /> |ownersemeritus=Roberto Vitillo<br /> |peersemeritus=Mauro Doglio<br /> |group=fx-data-platform@mozilla.com<br /> |source_dirs=https://github.com/mozilla/telemetry-dashboard, https://github.com/mozilla/telemetry-analysis-service, https://github.com/mozilla/redash, https://github.com/mozilla/python_mozaggregator, https://github.com/mozilla/cerberus, https://github.com/mozilla/medusa, https://github.com/mozilla/mozilla-reports, https://github.com/mozilla/telemetry-airflow/<br /> |url=https://telemetry.mozilla.org/, https://wiki.mozilla.org/Telemetry<br /> }}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Modules/Bugzilla&diff=1216125 2019-08-07T13:51:28Z

<p>Mhoye: Un-owned submodules have been removed, per previous discussion on Governance.</p> <hr /> <div>&lt;noinclude&gt;<br /> '''Only module owners may edit this page.''' <br /> <br /> They may:<br /> <br /> * update any information about their module except the name of the owner<br /> * add or remove sub-modules<br /> * change the owner of a sub-module <br /> * add emeritus owners or peers<br /> <br /> Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br /> &lt;/noinclude&gt;<br /> {{Module<br /> |name=Bugzilla<br /> |description=Bugzilla is the bug-tracking web application from Mozilla; this module's ownership includes responsibility for all of Bugzilla's internal components. <br /> |owner=[mailto:justdave@bugzilla.org Dave Miller]<br /> |ownersemeritus=Terry Weissman, Tara Hernandez<br /> |peers=[mailto:dylan@mozilla.com Dylan Hardison]<br /> |peersemeritus=Gervase Markham, Mark Côté, Byron Jones, Simon Green, Max Kanat-Alexander, Frédéric Buclin, Chris Yeh, Dan Mosedale<br /> |group=dev-apps-bugzilla<br /> |source_dirs=[http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary bugzilla/]<br /> |url=http://www.bugzilla.org/<br /> |components=<br /> }}</div>

Mhoye https://wiki.mozilla.org/index.php?title=Glossary&diff=1214610 2019-07-04T19:51:27Z

<p>Mhoye: </p> <hr /> <div>This page gives you a brief (one sentence) description of various terms that Mozillians use and might be confusing for newcomers.<br /> <br /> {{CompactTOC|center=yes|sym=yes|num=yes|nobreak=yes|seealso=yes}}<br /> <br /> ==A==<br /> ;[https://wiki.mozilla.org/Add-ons/Terminology Add-ons]<br /> :Bits of code that you can install to customize Firefox.<br /> ;All Hands<br /> : All MoCo and MoFo staffers plus key volunteers - also sometimes the all-mofo meetings that happen before the moco work weeks<br /> ;amo<br /> : [http://addons.mozilla.org/ addons.mozilla.org] - the central repository of mozilla addons.<br /> ;asknot<br /> : A web tool to find out contribution areas. [http://whatcanidoformozilla.org whatcanidoformozilla.org]<br /> <br /> ==B==<br /> ;b2g<br /> : Boot to Gecko, a component of FirefoxOS. Mostly defunct.<br /> ;back out<br /> : If a code change (to Firefox or anywhere else) goes badly, it may be &quot;backed out&quot;, meaning the change is undone. Sometimes several changes will be backed out at once, if it's unclear which one cause the problem.<br /> ;bikeshedding<br /> : Spending time arguing about trivial things, like the colour of the bike shed, instead of having meaningful discussion. See also: https://en.wikipedia.org/wiki/Law_of_triviality<br /> ;Bizdev<br /> : The Business Development team; this team is responsible for our partnership<br /> ;Blocker<br /> : A bug or problem that is severe enough that it would block a change or product release from happening.<br /> ;bmo<br /> : [http://bugzilla.mozilla.org/ bugzilla.mozilla.org] - our main bugzilla instance to keep track of various products (firefox, firefoxos, etc)<br /> ;Bug<br /> : In software a bug is an error in the program. Anything filed on bugzilla is also called a bug, even though we use it for purposes other than pointing out errors (like budget requests). (compare ''Github Issue'')<br /> ;Bugs Ahoy!<br /> : A [https://www.joshmatthews.net/bugsahoy/ website] for contributors to directly find unassigned ''Bugzilla'' bugs matching their interests. (Complementary to ''asknot''.)<br /> ;Bug report<br /> : The detailed description accompanying a bug or the act of reporting the bug itself. (Sometimes just called ''bug'')<br /> ;Bugzilla<br /> : A tool to keep track of bugs. (Compare ''bmo'') Used synonymous with BMO<br /> <br /> ==C==<br /> ;cbt<br /> : [[Contribute/Archive/Community Building Team|Community Building Team]]. Now been replaced by Participation team.<br /> ;central<br /> : Refers to the main source code repository [https://hg.mozilla.org/mozilla-central/ mozilla-central].<br /> ;Channel<br /> : The way people see your work. (e.g. The snippet, social media, the Mozilla homepage)<br /> ;[[Release Management/Chemspill|Chemspill]]<br /> : Short for &quot;chemical spill&quot;, this is historically intended to mean &quot;something is wrong with the Firefox release, so that we have to create a new release and ship it to all users as soon as possible, instead of waiting for the normally scheduled next release&quot;. More recently, &quot;Chemspill&quot; has come to denote any urgent problem in our products that requires an immediate company-wide effort in response. This isn't a term we use lightly, so when somebody says &quot;this is a chemspill&quot; you should put aside whatever you're doing and figure out how to help.<br /> ;Chop wood<br /> :Do practical work<br /> ;CI<br /> : Short for [https://en.wikipedia.org/wiki/Continuous_integration continuous integration]. The process of continually building, testing and deploying changes as they are submitted.<br /> ;CommSquared<br /> : [[CommSquared|Community Communications]] program<br /> ;Community Call<br /> : Community Call - episodic teleconferences for working groups of staffers and volunteers organized around particular projects. these calls are a chance for community members to share projects, learn about activities in their community, and ask questions. https://opennews.org/what/community/calls/<br /> ;Community Education<br /> : See ''Mozilla Community Education''<br /> ;Coral Project<br /> :The Coral Project: A MoFo collaboration with The New York Times, The Washington Post and the Knight Foundation to create open source tools and practices for publishers of all sizes, to build better communities around their journalism. http://coralproject.net<br /> <br /> ==D==<br /> ;DARCI<br /> : Similar to RACI.<br /> ;Discourse<br /> : A modern web based communication forum. Checkout [https://discourse.mozilla-community.org/ discourse.mozilla-community.org]<br /> <br /> ==E==<br /> ;e10s<br /> :Short for [[Electrolysis]] (e, ten letters, s)<br /> ;[[Electrolysis]]<br /> :An effort to increase security by splitting off the content rendering from the main Firefox process.<br /> ;ESR<br /> :Extended Support Release of Firefox. For more information checkout [https://www.mozilla.org/en-US/firefox/organizations/faq/ ESR Overview].<br /> <br /> ==F==<br /> ;File a ticket/bug/issue<br /> : Use Github (or Bugzilla) as an issue tracker to denote a single task.<br /> ;Firehose<br /> : The entirety of the Mozilla 'signal' flooding your inbox, IRC client, Skype, texts, phone, Vidyo, GitHub repos, social media, and every waking thought; the large body of information you have to parse (with help) into learning and action items for yourself.<br /> ;FSA<br /> : [[StudentAmbassadors|Firefox Student Ambassador]]<br /> <br /> ==G==<br /> ;GA<br /> : Could mean &quot;Google Analytics&quot; or &quot;General Audience&quot; (i.e., Firefox GA is the version/channel of Firefox that is released to most people, as opposed to Nightly or Beta). Also simply called Release.<br /> ;git<br /> : A version controlling system for writing code collaboratively.<br /> ;Github<br /> : A popular web-based git hosting system used in various Mozilla projects. [https://github.com github.com]<br /> ;Github Issue<br /> : An on-topic discussion, usually surrounding a single bug, hosted on a Github project. <br /> ;Github Pull Request<br /> : (abbreviated as PR) A way for programmers to submit their contributions to projects on Github. (compare ''Patch'')<br /> ;Go Faster<br /> : An initiative to speed up some parts of the Firefox release process. Includes System Add-ons and other miscellaneous release mechanisms. The normal process is for changes to &quot;ride the trains&quot;<br /> <br /> ==H==<br /> ;Heartbeat <br /> : scheduling paradigm we use to coordinate ; 2-week cycle of planning, prototyping, testing, iteration, sharing, clean-up, and prep Also known as a 'sprint'. Also sometimes refers to a feedback mechanism in Firefox where a random set of users are asked about how they feel about Firefox.<br /> ;Heroku <br /> : A platform for temporarily hosting a given piece of code before it is shipped to staging or production, usually for testing or demonstrating.<br /> ;hg<br /> : The binary used by the version control system [https://www.mercurial-scm.org/ Mercurial]. Often used in a sentence as short form for &quot;mercurial&quot;.<br /> ;Hive<br /> : [[Webmaker/Hive|Hive]] is A city-based network of educators, technologists, and other stakeholders championing web literacy through connected learning in communities around the world. Networks are the innovation incubators for the global MLN network. For example, much of the Clubs curriculum originated in Hive networks: http://hivelearningnetworks.org<br /> ;HRBP<br /> : &quot;HR Business Partners&quot;; a subgroup of the [[People]] team. HRBPs have a strategic role and advise the business leaders, including executives, directors and managers. At Mozilla, HRBPs also serve as the first point-of-contact for all HR-related issues. Mozilla Corporation business units are &quot;assigned&quot; to an HRBP; you can find yours [https://mana.mozilla.org/wiki/display/PR/People+Resources+Home here].<br /> <br /> ==I==<br /> ;i18n<br /> :Short for [https://developer.mozilla.org/en-US/docs/Glossary/I18N Internationalization] (i, eighteen letters, n)<br /> ;inbound<br /> : [https://hg.mozilla.org/integration/mozilla-inbound/ A repository] where changes to Firefox usually land first. Changes are batched up and moved to mozilla-central several times a day, so long as everything is building and testing well.<br /> ;IRC<br /> : [[IRC|Internet Relay Chat]] is a communication tool used by Mozillians to communicate<br /> <br /> ==K==<br /> ;Knight-Mozilla Fellows<br /> : Knight-Mozilla Fellows spend 10 months working with newsroom technology teams to write open-source code, analyze and visualize data, and explore tough problems facing journalism. We have 26 current and alumni fellows and we're currently selecting our 5th class of fellows.<br /> ;KPI<br /> : Key Performance indicator, KPIs are things we measure that let us know if what we're doing is &quot;working.&quot; As an example, we might have a KPI about the &quot;number of monthly active users.&quot; We keep an eye on that metric, and if it drops below a certain point, we know we've got a problem we need to fix! (Note: I've noticed we often use KPIs to mean &quot;targets,&quot; as in a specific numerical goal we're trying to reach. For example, &quot;500 Mozilla Clubs.&quot;)<br /> <br /> ==L==<br /> ;l10n<br /> : [[L10n|Localization]] is the translation of Mozilla products to various languages. (l, ten letters, n)<br /> ;lint<br /> : A [https://en.wikipedia.org/wiki/Lint_(software) lint program] is something that automatically checks for style problems in code, and helps enforce consistent style. See also [https://wiki.mozilla.org/DevTools/CodingStandards Coding Standards]<br /> <br /> ==M==<br /> ;mach<br /> : A command line dispatcher. [https://firefox-source-docs.mozilla.org/python/mach/index.html Mach] has a binary of the same name that lives at the root of the main repository. Other tools that live in-tree can register an entry point making 'mach' a single point of entry for a large variety of tasks that can be performed in the repository (such as running builds and tests). The name 'mach' comes from 'machen', the German word for do.<br /> ;Maker Party<br /> : Month-long summer campaign to activate, engage, and/or level-up users new and old by supporting them in planning small- and large-scale maker events that tie into MLN tools, curricula, and/or philosophies; often themed and sets up calls-to-action for the following year. [https://teach.mozilla.org/events/ teach.mozilla.org/events/]<br /> ;Mana<br /> : The name for land that you need to control to cast spells or summon creatures in Magic the Gathering. They are Swamps/black, Forests/green, Plains/White, Water/blue and Mountains/red and colorless. Also where a bunch of HR documents are stored - a wiki that is not available to the public.<br /> ;MCWS<br /> : [[MCWS|Mozilla Community Web Support]] - working group providing support for community webs services.<br /> ;MDN<br /> : [[MDN|Mozilla Developer Network]] - online resource for Web developers; lives at. [https://developer.mozilla.org/ developer.mozilla.org]<br /> ;Mercurial<br /> : The primary [https://en.wikipedia.org/wiki/Version_control version control system] (vcs) [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/ used at Mozilla]. Most of Mozilla's source code is hosted on [https://www.mercurial-scm.org/ Mercurial] servers.<br /> ;MLN<br /> : [https://learning.mozilla.org/en-US/ Mozilla Learning Network] – now-defunct web literacy educational initiative by Mozilla Foundation<br /> ;MoCo<br /> : Mozilla Corporation is a wholly owned subsidiary of the Mozilla Foundation that coordinates and integrates the development of products.<br /> ;Module<br /> :A piece of code functionality or area of responsibility within Mozilla. A &quot;module owner&quot; is the person who has ultimate decision making authority - a &quot;peer&quot; often makes day to day decisions that can be escalated to an owner - https://www.mozilla.org/en-US/about/governance/policies/module-ownership/<br /> ;MoFo<br /> : [[Mozilla Foundation]] is a non-profit organization that exists to support and collectively lead the Mozilla project.<br /> ;MozFest/Mozilla Festival<br /> : Open Web Leadership unconference shipped by Mozilla each fall (late October/early November), often at Ravensbourne, a design college in London, England. Characterized by mental sparks, science fairs, maker spaces, youth participation, free espresso, and work sprints - planned or unplanned - on organizational goals, outputs, and outcomes.<br /> ;Mozicorns<br /> : Crew aboard the first New Hire Onboarding Program of November, 2015. [https://mozillians.org/group/mozicorns/ mozillians.org/group/mozicorns]<br /> ;mozilla-central<br /> : [https://hg.mozilla.org/mozilla-central/ The repository] where most Firefox development happens, and which builds Firefox Nightly. Often referred to as &quot;central&quot; or &quot;m-c&quot;.<br /> ;Mozilla Clubs<br /> : Local groups that meet regularly to learn the Web, a part of the Mozilla Learning Network. [https://teach.mozilla.org/clubs/ teach.mozilla.org/clubs/]<br /> ;Mozilla Community Education<br /> : aims to empower Mozillians in their contributions, and personal goals through education and training. [http://education.mozilla-community.org/ education.mozilla-community.org] <br /> ;Mozilla Learning Network<br /> : offers programs and a global community dedicated to helping people learn to read, write and participate in the digital world [http://teach.mozilla.org/ teach.mozilla.org]<br /> ;Mozillians<br /> : A web-directory of Mozillians around the world. [http://mozillians.org/ mozillians.org]<br /> ;Mozilla Reps<br /> : Mozilla Volunteer with the status of &quot;representative&quot; they are part of a program and have special &quot;power&quot; such as asking for budget to run an event etc.<br /> ;MVP <br /> : Minimum viable product. The smallest increment of work needed to test a hypothesis about your product. Used to validate assumptions / prove the product is meeting user needs. Related: Minimum Loveable Product (see: https://fastmonkeys.files.wordpress.com/2014/06/how-to-build-a-minimum-viable-product.jpg?w=500&amp;h=421 )<br /> : Minimum Viable Partnership. http://intangible.ca/2012/03/27/minimum-viable-partnership/<br /> <br /> ==N==<br /> ;NDA<br /> : Non-Disclosure Agreement. With respect to private communication, in addition to employees there are non-employees who have signed an NDA, sometimes &quot;NDA&quot; is used to refer to this additional group of people.<br /> ;needinfo<br /> : A https://bugzilla.mozilla.org user can submit a &lt;code&gt;needinfo&lt;/code&gt; request another bugzilla user to ask a question about a bug. Mozilla uses &lt;code&gt;needinfo&lt;/code&gt; instead of assigning a bug to ask a question, as one would do in Jira.<br /> ;Nightly<br /> : [https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly Pre-release versions of Firefox] that are built directly from mozilla-central, for testing and development. Firefox Nightly is generally stable enough for everyday use though the occasional bug is expected.<br /> <br /> ==O==<br /> ;Ongoing versions<br /> : The last version number for each release channel of Firefox. (ESR, Release, Beta, Nightly)<br /> ;OpenNews<br /> : A joint project of Mozilla and the Knight Foundation that supports the community of news developers, designers, and data reporters helping journalism thrive on the open web. Runs the Knight-Mozilla Fellowships, Source, SRCCON, and associated programs. https://opennews.org/<br /> ;Orange<br /> : Synonymous for a failing task in CI (because it gets coloured orange in [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central treeherder]). Tasks that only fail occasionally are known as 'intermittent oranges', but this term is often shortened to just 'orange'.<br /> ;Outreachy<br /> : formerly the outreach program for women, (https://www.gnome.org/outreachy/) now a paid internship program for under-represented groups in tech sponsored by several open source organizations, including Mozilla.<br /> <br /> ==P==<br /> ;P1 (P2, P3, ...)<br /> : Priority levels, used by some groups for bugs in Bugzilla. P1 means most important, typically P2 means important but not ''most'' important, P3 is nice-to-have, P4 and P5 mean something will probably never get done. Sometimes an important issue or task is referred to as &quot;P1&quot;, even if it's not in Bugzilla.<br /> ;Participation<br /> : The [[Participation]] Team works to make people participate in Mozilla programs. <br /> ;Patch<br /> : A specific code contribution by programmers submitted as a text file. <br /> ;PHD<br /> : A &quot;Product Hypothesis Document&quot;: a template for proposing experiments for [https://wiki.mozilla.org/Firefox/Shield Shield]<br /> ;Point-release<br /> : A point release is when, for instance, Firefox 30 is released, then there is a problem and Firefox 30.1 must be released (instead of waiting for the regularly scheduled 6 week iteration that leads to Firefox 31). See also ''chemspill''<br /> ;Pontoon<br /> : [https://pontoon.mozilla.org/ Pontoon] is a site/tool for localization.<br /> ;PR<br /> : See Github Pull Request<br /> ;Project Call: <br /> : A community call where all aspects of Mozilla are discussed (usually 1x a week on Mondays in the US)<br /> ;PTO <br /> : Paid Time Off = Holidays (as referred by UK-based)/vacation (for Canada and US folks)/sick leave. In addition to PTO allowance, employees get parental leave &amp; a birthday off<br /> ;Push to production<br /> : most development (design and engineering) is first pushed to a &quot;staging&quot; server where it's tested. &quot;Push to production&quot; means it is merged to the production server where the world can see it!<br /> <br /> ==Q==<br /> ;QA<br /> : Quality assurance. [https://quality.mozilla.org/ quality.mozilla.org]<br /> <br /> ==R==<br /> ;RACI (pronounced Race-y)<br /> :A way to indicate the responsibilities of the various roles in a project.<br /> ;Rathole<br /> : A label for a discussion that has become too detailed for the forum, or has lost track of the original purpose of the discussion. &quot;(After a discussion of a specific bug has turned into a ten minute discussion of typechecking) I think we're ratholing here&quot;. See also Yak Shaving and Bike Shedding<br /> ;RC<br /> :Regional Coordinator; volunteer or (sometimes) staffer who supports Club Captains in beginning Web literacy Mozilla Clubs that teach the Web using MLN curriculum, at least in-part.<br /> ;Regression<br /> : When something that was working starts to break. I.e., a new bug is introduced.<br /> ;ReMo<br /> : [[ReMo|Mozilla Reps]] Program. Also see ''Mozilla Reps''<br /> ;Rep<br /> : Mozilla Representative, as part of Mozilla Reps program. [https://reps.mozilla.org/ reps.mozilla.org]<br /> ;Repro<br /> : Steps to reproduce a bug (see also STR)<br /> <br /> ==S==<br /> ;Sign-off<br /> : Some processes require &quot;sign-off&quot; by certain people or groups (e.g., by Privacy or QA). Sign-off requires informing an appropriate person, and getting positive acknowledgement to go forward.<br /> ;SHIELD<br /> : A mechanism for shipping changes or studies to groups of Firefox users. This can be used to test changes with representative Firefox users, or roll out changes to watch for regressions.<br /> ;Snippet<br /> : The call-to-action under the search box when you open the default Firefox window on your desktop or mobile See: https://fundraising.mozilla.org/what-is-the-snippet/<br /> ;Slack<br /> : A communications tool used by staff and NDA-ed contributors, https://mozilla.slack.com/<br /> ;Source<br /> :The OpenNews publication dedicated to amplifying the impact of open journalism code and the community of developers, designers, journalists, and editors who make it. We publish DVD commentary–style write ups from developers and designers, how-tos, and interviews with newsroom code leaders around the world. https://source.opennews.org/<br /> ;SRCCON<br /> :The OpenNews annual conference-unconference event built around highly participatory sessions and focused on technical and process challenges news technology and data teams encounter every day. Heading into its third year in 2016. http://srccon.org/<br /> ;STR<br /> :'Steps To Reproduce' is often cited on bugs as a way to reproduce the particular problem in question.<br /> ;SuMo<br /> : [[Sumo|Support Mozilla]] is for user support.<br /> ;System Add-on<br /> : These are add-ons that are built into Firefox. They can be updated with a special process, but cannot typically be seen by users, and cannot be uninstalled.<br /> <br /> ==T==<br /> ;Taskcluster<br /> : The continuous integration (CI) system used and [https://docs.taskcluster.net/docs developed by Mozilla].<br /> ;TLDR<br /> : Usually TL;DR, meaning 'too long; didn't read;' used as a tag for a summary above lengthy text.<br /> ;Trains<br /> : Firefox development happens primarily in the mozilla-central repository, which is used to build Firefox Nightly. The &quot;trains&quot; are how Nightly turns into Beta, and Beta turns into Release. If a change &quot;rides the trains&quot; that means it is distributed as part of this normal cycle of Nightly to Beta to Release. See also Uplift.<br /> ;Triage<br /> : The process of deciding what the next step for a new bug is. In Firefox, there are [https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html triage owners] responsible for making these decisions, and they follow [[Bugmasters/Process/Triage|our triage process]].<br /> ;Tree<br /> : Informal term referring to a branch of source code (e.g mozilla-central, mozilla-beta, etc). Saying something is &quot;in-tree&quot; means its source code lives in mozilla-central.<br /> ;Treeherder<br /> : The [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central main dashboard] used to view results from continuous integration (CI). The name 'Treeherder' is both a reference to The Lord of the Rings (Ents) and the fact that it is used to manage all of Mozilla's &quot;trees&quot;.<br /> <br /> ==U==<br /> ;Uplift<br /> : When a patch lands on mozilla-central in Nightly, it will normally get to users after Nightly turns to Beta, then Beta turns to Release. If the patch is &quot;uplifted&quot; then it is moved from Nightly/mozilla-central to the current Beta.<br /> <br /> ==V==<br /> ;vcs<br /> : Short for [https://en.wikipedia.org/wiki/Version_control version control system].<br /> <br /> ==W==<br /> ;Webmaker<br /> : Webmaker is now an app that can be used to create and share on the Web. [https://webmaker.org webmaker.org]. In the past it used to stand for what is now Mozilla Learning Network.<br /> ;WONTFIX<br /> : The (not very friendly sounding) way we acknowledge a bug or issue, but declare we won't fix it – either because it's not important enough, or because we don't consider it a bug. This is a resolution in Bugzilla, but is also used casually to refer to a decision not to do something.<br /> ;Workweek<br /> : A week where teams meet face to face and work together and sing and dance. They can be for the whole Moco Mofo ( example, you might hear about the Portland workweek or Whistler or Orlando) or they can be in smaller teams, like the fundraising team workweek.<br /> <br /> ==Y==<br /> ;Yak Shaving<br /> : When you find yourself doing a series of tasks you hadn't anticipated doing to accomplish your original goal<br /> ;Yammer<br /> : Previously used as a communications tool by Mozilla staff. Replaced by https://mozilla.slack.com/.</div>

Mhoye https://wiki.mozilla.org/index.php?title=Glossary&diff=1214609 2019-07-04T19:50:20Z

<p>Mhoye: </p> <hr /> <div>This page gives you a brief (one sentence) description of various terms that Mozillians use and might be confusing for newcomers.<br /> <br /> {{CompactTOC|center=yes|sym=yes|num=yes|nobreak=yes|seealso=yes}}<br /> <br /> ==A==<br /> ;[https://wiki.mozilla.org/Add-ons/Terminology Add-ons]<br /> :Bits of code that you can install to customize Firefox.<br /> ;All Hands<br /> : All MoCo and MoFo staffers plus key volunteers - also sometimes the all-mofo meetings that happen before the moco work weeks<br /> ;amo<br /> : [http://addons.mozilla.org/ addons.mozilla.org] - the central repository of mozilla addons.<br /> ;asknot<br /> : A web tool to find out contribution areas. [http://whatcanidoformozilla.org whatcanidoformozilla.org]<br /> <br /> ==B==<br /> ;b2g<br /> : Boot to Gecko, a component of FirefoxOS. Mostly defunct.<br /> ;back out<br /> : If a code change (to Firefox or anywhere else) goes badly, it may be &quot;backed out&quot;, meaning the change is undone. Sometimes several changes will be backed out at once, if it's unclear which one cause the problem.<br /> ;bikeshedding<br /> : Spending time arguing about trivial things, like the colour of the bike shed, instead of having meaningful discussion. See also: https://en.wikipedia.org/wiki/Law_of_triviality<br /> ;Bizdev<br /> : The Business Development team; this team is responsible for our partnership<br /> ;Blocker<br /> : A bug or problem that is severe enough that it would block a change or product release from happening.<br /> ;bmo<br /> : [http://bugzilla.mozilla.org/ bugzilla.mozilla.org] - our main bugzilla instance to keep track of various products (firefox, firefoxos, etc)<br /> ;Bug<br /> : In software a bug is an error in the program. Anything filed on bugzilla is also called a bug, even though we use it for purposes other than pointing out errors (like budget requests). (compare ''Github Issue'')<br /> ;Bugs Ahoy!<br /> : A [https://www.joshmatthews.net/bugsahoy/ website] for contributors to directly find unassigned ''Bugzilla'' bugs matching their interests. (Complementary to ''asknot''.)<br /> ;Bug report<br /> : The detailed description accompanying a bug or the act of reporting the bug itself. (Sometimes just called ''bug'')<br /> ;Bugzilla<br /> : A tool to keep track of bugs. (Compare ''bmo'') Used synonymous with BMO<br /> <br /> ==C==<br /> ;cbt<br /> : [[Contribute/Archive/Community Building Team|Community Building Team]]. Now been replaced by Participation team.<br /> ;central<br /> : Refers to the main source code repository [https://hg.mozilla.org/mozilla-central/ mozilla-central].<br /> ;Channel<br /> : The way people see your work. (e.g. The snippet, social media, the Mozilla homepage)<br /> ;[[Release Management/Chemspill|Chemspill]]<br /> : Short for &quot;chemical spill&quot;, this is historically intended to mean &quot;something is wrong with the Firefox release, so that we have to create a new release and ship it to all users as soon as possible, instead of waiting for the normally scheduled next release&quot;. More recently, &quot;Chemspill&quot; has come to denote any urgent problem in our products that requires an immediate company-wide effort in response. This isn't at term we use lightly, and when somebody says &quot;chemspill&quot; you put aside what you're doing and figure out how to help.<br /> ;Chop wood<br /> :Do practical work<br /> ;CI<br /> : Short for [https://en.wikipedia.org/wiki/Continuous_integration continuous integration]. The process of continually building, testing and deploying changes as they are submitted.<br /> ;CommSquared<br /> : [[CommSquared|Community Communications]] program<br /> ;Community Call<br /> : Community Call - episodic teleconferences for working groups of staffers and volunteers organized around particular projects. these calls are a chance for community members to share projects, learn about activities in their community, and ask questions. https://opennews.org/what/community/calls/<br /> ;Community Education<br /> : See ''Mozilla Community Education''<br /> ;Coral Project<br /> :The Coral Project: A MoFo collaboration with The New York Times, The Washington Post and the Knight Foundation to create open source tools and practices for publishers of all sizes, to build better communities around their journalism. http://coralproject.net<br /> <br /> ==D==<br /> ;DARCI<br /> : Similar to RACI.<br /> ;Discourse<br /> : A modern web based communication forum. Checkout [https://discourse.mozilla-community.org/ discourse.mozilla-community.org]<br /> <br /> ==E==<br /> ;e10s<br /> :Short for [[Electrolysis]] (e, ten letters, s)<br /> ;[[Electrolysis]]<br /> :An effort to increase security by splitting off the content rendering from the main Firefox process.<br /> ;ESR<br /> :Extended Support Release of Firefox. For more information checkout [https://www.mozilla.org/en-US/firefox/organizations/faq/ ESR Overview].<br /> <br /> ==F==<br /> ;File a ticket/bug/issue<br /> : Use Github (or Bugzilla) as an issue tracker to denote a single task.<br /> ;Firehose<br /> : The entirety of the Mozilla 'signal' flooding your inbox, IRC client, Skype, texts, phone, Vidyo, GitHub repos, social media, and every waking thought; the large body of information you have to parse (with help) into learning and action items for yourself.<br /> ;FSA<br /> : [[StudentAmbassadors|Firefox Student Ambassador]]<br /> <br /> ==G==<br /> ;GA<br /> : Could mean &quot;Google Analytics&quot; or &quot;General Audience&quot; (i.e., Firefox GA is the version/channel of Firefox that is released to most people, as opposed to Nightly or Beta). Also simply called Release.<br /> ;git<br /> : A version controlling system for writing code collaboratively.<br /> ;Github<br /> : A popular web-based git hosting system used in various Mozilla projects. [https://github.com github.com]<br /> ;Github Issue<br /> : An on-topic discussion, usually surrounding a single bug, hosted on a Github project. <br /> ;Github Pull Request<br /> : (abbreviated as PR) A way for programmers to submit their contributions to projects on Github. (compare ''Patch'')<br /> ;Go Faster<br /> : An initiative to speed up some parts of the Firefox release process. Includes System Add-ons and other miscellaneous release mechanisms. The normal process is for changes to &quot;ride the trains&quot;<br /> <br /> ==H==<br /> ;Heartbeat <br /> : scheduling paradigm we use to coordinate ; 2-week cycle of planning, prototyping, testing, iteration, sharing, clean-up, and prep Also known as a 'sprint'. Also sometimes refers to a feedback mechanism in Firefox where a random set of users are asked about how they feel about Firefox.<br /> ;Heroku <br /> : A platform for temporarily hosting a given piece of code before it is shipped to staging or production, usually for testing or demonstrating.<br /> ;hg<br /> : The binary used by the version control system [https://www.mercurial-scm.org/ Mercurial]. Often used in a sentence as short form for &quot;mercurial&quot;.<br /> ;Hive<br /> : [[Webmaker/Hive|Hive]] is A city-based network of educators, technologists, and other stakeholders championing web literacy through connected learning in communities around the world. Networks are the innovation incubators for the global MLN network. For example, much of the Clubs curriculum originated in Hive networks: http://hivelearningnetworks.org<br /> ;HRBP<br /> : &quot;HR Business Partners&quot;; a subgroup of the [[People]] team. HRBPs have a strategic role and advise the business leaders, including executives, directors and managers. At Mozilla, HRBPs also serve as the first point-of-contact for all HR-related issues. Mozilla Corporation business units are &quot;assigned&quot; to an HRBP; you can find yours [https://mana.mozilla.org/wiki/display/PR/People+Resources+Home here].<br /> <br /> ==I==<br /> ;i18n<br /> :Short for [https://developer.mozilla.org/en-US/docs/Glossary/I18N Internationalization] (i, eighteen letters, n)<br /> ;inbound<br /> : [https://hg.mozilla.org/integration/mozilla-inbound/ A repository] where changes to Firefox usually land first. Changes are batched up and moved to mozilla-central several times a day, so long as everything is building and testing well.<br /> ;IRC<br /> : [[IRC|Internet Relay Chat]] is a communication tool used by Mozillians to communicate<br /> <br /> ==K==<br /> ;Knight-Mozilla Fellows<br /> : Knight-Mozilla Fellows spend 10 months working with newsroom technology teams to write open-source code, analyze and visualize data, and explore tough problems facing journalism. We have 26 current and alumni fellows and we're currently selecting our 5th class of fellows.<br /> ;KPI<br /> : Key Performance indicator, KPIs are things we measure that let us know if what we're doing is &quot;working.&quot; As an example, we might have a KPI about the &quot;number of monthly active users.&quot; We keep an eye on that metric, and if it drops below a certain point, we know we've got a problem we need to fix! (Note: I've noticed we often use KPIs to mean &quot;targets,&quot; as in a specific numerical goal we're trying to reach. For example, &quot;500 Mozilla Clubs.&quot;)<br /> <br /> ==L==<br /> ;l10n<br /> : [[L10n|Localization]] is the translation of Mozilla products to various languages. (l, ten letters, n)<br /> ;lint<br /> : A [https://en.wikipedia.org/wiki/Lint_(software) lint program] is something that automatically checks for style problems in code, and helps enforce consistent style. See also [https://wiki.mozilla.org/DevTools/CodingStandards Coding Standards]<br /> <br /> ==M==<br /> ;mach<br /> : A command line dispatcher. [https://firefox-source-docs.mozilla.org/python/mach/index.html Mach] has a binary of the same name that lives at the root of the main repository. Other tools that live in-tree can register an entry point making 'mach' a single point of entry for a large variety of tasks that can be performed in the repository (such as running builds and tests). The name 'mach' comes from 'machen', the German word for do.<br /> ;Maker Party<br /> : Month-long summer campaign to activate, engage, and/or level-up users new and old by supporting them in planning small- and large-scale maker events that tie into MLN tools, curricula, and/or philosophies; often themed and sets up calls-to-action for the following year. [https://teach.mozilla.org/events/ teach.mozilla.org/events/]<br /> ;Mana<br /> : The name for land that you need to control to cast spells or summon creatures in Magic the Gathering. They are Swamps/black, Forests/green, Plains/White, Water/blue and Mountains/red and colorless. Also where a bunch of HR documents are stored - a wiki that is not available to the public.<br /> ;MCWS<br /> : [[MCWS|Mozilla Community Web Support]] - working group providing support for community webs services.<br /> ;MDN<br /> : [[MDN|Mozilla Developer Network]] - online resource for Web developers; lives at. [https://developer.mozilla.org/ developer.mozilla.org]<br /> ;Mercurial<br /> : The primary [https://en.wikipedia.org/wiki/Version_control version control system] (vcs) [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/ used at Mozilla]. Most of Mozilla's source code is hosted on [https://www.mercurial-scm.org/ Mercurial] servers.<br /> ;MLN<br /> : [https://learning.mozilla.org/en-US/ Mozilla Learning Network] – now-defunct web literacy educational initiative by Mozilla Foundation<br /> ;MoCo<br /> : Mozilla Corporation is a wholly owned subsidiary of the Mozilla Foundation that coordinates and integrates the development of products.<br /> ;Module<br /> :A piece of code functionality or area of responsibility within Mozilla. A &quot;module owner&quot; is the person who has ultimate decision making authority - a &quot;peer&quot; often makes day to day decisions that can be escalated to an owner - https://www.mozilla.org/en-US/about/governance/policies/module-ownership/<br /> ;MoFo<br /> : [[Mozilla Foundation]] is a non-profit organization that exists to support and collectively lead the Mozilla project.<br /> ;MozFest/Mozilla Festival<br /> : Open Web Leadership unconference shipped by Mozilla each fall (late October/early November), often at Ravensbourne, a design college in London, England. Characterized by mental sparks, science fairs, maker spaces, youth participation, free espresso, and work sprints - planned or unplanned - on organizational goals, outputs, and outcomes.<br /> ;Mozicorns<br /> : Crew aboard the first New Hire Onboarding Program of November, 2015. [https://mozillians.org/group/mozicorns/ mozillians.org/group/mozicorns]<br /> ;mozilla-central<br /> : [https://hg.mozilla.org/mozilla-central/ The repository] where most Firefox development happens, and which builds Firefox Nightly. Often referred to as &quot;central&quot; or &quot;m-c&quot;.<br /> ;Mozilla Clubs<br /> : Local groups that meet regularly to learn the Web, a part of the Mozilla Learning Network. [https://teach.mozilla.org/clubs/ teach.mozilla.org/clubs/]<br /> ;Mozilla Community Education<br /> : aims to empower Mozillians in their contributions, and personal goals through education and training. [http://education.mozilla-community.org/ education.mozilla-community.org] <br /> ;Mozilla Learning Network<br /> : offers programs and a global community dedicated to helping people learn to read, write and participate in the digital world [http://teach.mozilla.org/ teach.mozilla.org]<br /> ;Mozillians<br /> : A web-directory of Mozillians around the world. [http://mozillians.org/ mozillians.org]<br /> ;Mozilla Reps<br /> : Mozilla Volunteer with the status of &quot;representative&quot; they are part of a program and have special &quot;power&quot; such as asking for budget to run an event etc.<br /> ;MVP <br /> : Minimum viable product. The smallest increment of work needed to test a hypothesis about your product. Used to validate assumptions / prove the product is meeting user needs. Related: Minimum Loveable Product (see: https://fastmonkeys.files.wordpress.com/2014/06/how-to-build-a-minimum-viable-product.jpg?w=500&amp;h=421 )<br /> : Minimum Viable Partnership. http://intangible.ca/2012/03/27/minimum-viable-partnership/<br /> <br /> ==N==<br /> ;NDA<br /> : Non-Disclosure Agreement. With respect to private communication, in addition to employees there are non-employees who have signed an NDA, sometimes &quot;NDA&quot; is used to refer to this additional group of people.<br /> ;needinfo<br /> : A https://bugzilla.mozilla.org user can submit a &lt;code&gt;needinfo&lt;/code&gt; request another bugzilla user to ask a question about a bug. Mozilla uses &lt;code&gt;needinfo&lt;/code&gt; instead of assigning a bug to ask a question, as one would do in Jira.<br /> ;Nightly<br /> : [https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly Pre-release versions of Firefox] that are built directly from mozilla-central, for testing and development. Firefox Nightly is generally stable enough for everyday use though the occasional bug is expected.<br /> <br /> ==O==<br /> ;Ongoing versions<br /> : The last version number for each release channel of Firefox. (ESR, Release, Beta, Nightly)<br /> ;OpenNews<br /> : A joint project of Mozilla and the Knight Foundation that supports the community of news developers, designers, and data reporters helping journalism thrive on the open web. Runs the Knight-Mozilla Fellowships, Source, SRCCON, and associated programs. https://opennews.org/<br /> ;Orange<br /> : Synonymous for a failing task in CI (because it gets coloured orange in [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central treeherder]). Tasks that only fail occasionally are known as 'intermittent oranges', but this term is often shortened to just 'orange'.<br /> ;Outreachy<br /> : formerly the outreach program for women, (https://www.gnome.org/outreachy/) now a paid internship program for under-represented groups in tech sponsored by several open source organizations, including Mozilla.<br /> <br /> ==P==<br /> ;P1 (P2, P3, ...)<br /> : Priority levels, used by some groups for bugs in Bugzilla. P1 means most important, typically P2 means important but not ''most'' important, P3 is nice-to-have, P4 and P5 mean something will probably never get done. Sometimes an important issue or task is referred to as &quot;P1&quot;, even if it's not in Bugzilla.<br /> ;Participation<br /> : The [[Participation]] Team works to make people participate in Mozilla programs. <br /> ;Patch<br /> : A specific code contribution by programmers submitted as a text file. <br /> ;PHD<br /> : A &quot;Product Hypothesis Document&quot;: a template for proposing experiments for [https://wiki.mozilla.org/Firefox/Shield Shield]<br /> ;Point-release<br /> : A point release is when, for instance, Firefox 30 is released, then there is a problem and Firefox 30.1 must be released (instead of waiting for the regularly scheduled 6 week iteration that leads to Firefox 31). See also ''chemspill''<br /> ;Pontoon<br /> : [https://pontoon.mozilla.org/ Pontoon] is a site/tool for localization.<br /> ;PR<br /> : See Github Pull Request<br /> ;Project Call: <br /> : A community call where all aspects of Mozilla are discussed (usually 1x a week on Mondays in the US)<br /> ;PTO <br /> : Paid Time Off = Holidays (as referred by UK-based)/vacation (for Canada and US folks)/sick leave. In addition to PTO allowance, employees get parental leave &amp; a birthday off<br /> ;Push to production<br /> : most development (design and engineering) is first pushed to a &quot;staging&quot; server where it's tested. &quot;Push to production&quot; means it is merged to the production server where the world can see it!<br /> <br /> ==Q==<br /> ;QA<br /> : Quality assurance. [https://quality.mozilla.org/ quality.mozilla.org]<br /> <br /> ==R==<br /> ;RACI (pronounced Race-y)<br /> :A way to indicate the responsibilities of the various roles in a project.<br /> ;Rathole<br /> : A label for a discussion that has become too detailed for the forum, or has lost track of the original purpose of the discussion. &quot;(After a discussion of a specific bug has turned into a ten minute discussion of typechecking) I think we're ratholing here&quot;. See also Yak Shaving and Bike Shedding<br /> ;RC<br /> :Regional Coordinator; volunteer or (sometimes) staffer who supports Club Captains in beginning Web literacy Mozilla Clubs that teach the Web using MLN curriculum, at least in-part.<br /> ;Regression<br /> : When something that was working starts to break. I.e., a new bug is introduced.<br /> ;ReMo<br /> : [[ReMo|Mozilla Reps]] Program. Also see ''Mozilla Reps''<br /> ;Rep<br /> : Mozilla Representative, as part of Mozilla Reps program. [https://reps.mozilla.org/ reps.mozilla.org]<br /> ;Repro<br /> : Steps to reproduce a bug (see also STR)<br /> <br /> ==S==<br /> ;Sign-off<br /> : Some processes require &quot;sign-off&quot; by certain people or groups (e.g., by Privacy or QA). Sign-off requires informing an appropriate person, and getting positive acknowledgement to go forward.<br /> ;SHIELD<br /> : A mechanism for shipping changes or studies to groups of Firefox users. This can be used to test changes with representative Firefox users, or roll out changes to watch for regressions.<br /> ;Snippet<br /> : The call-to-action under the search box when you open the default Firefox window on your desktop or mobile See: https://fundraising.mozilla.org/what-is-the-snippet/<br /> ;Slack<br /> : A communications tool used by staff and NDA-ed contributors, https://mozilla.slack.com/<br /> ;Source<br /> :The OpenNews publication dedicated to amplifying the impact of open journalism code and the community of developers, designers, journalists, and editors who make it. We publish DVD commentary–style write ups from developers and designers, how-tos, and interviews with newsroom code leaders around the world. https://source.opennews.org/<br /> ;SRCCON<br /> :The OpenNews annual conference-unconference event built around highly participatory sessions and focused on technical and process challenges news technology and data teams encounter every day. Heading into its third year in 2016. http://srccon.org/<br /> ;STR<br /> :'Steps To Reproduce' is often cited on bugs as a way to reproduce the particular problem in question.<br /> ;SuMo<br /> : [[Sumo|Support Mozilla]] is for user support.<br /> ;System Add-on<br /> : These are add-ons that are built into Firefox. They can be updated with a special process, but cannot typically be seen by users, and cannot be uninstalled.<br /> <br /> ==T==<br /> ;Taskcluster<br /> : The continuous integration (CI) system used and [https://docs.taskcluster.net/docs developed by Mozilla].<br /> ;TLDR<br /> : Usually TL;DR, meaning 'too long; didn't read;' used as a tag for a summary above lengthy text.<br /> ;Trains<br /> : Firefox development happens primarily in the mozilla-central repository, which is used to build Firefox Nightly. The &quot;trains&quot; are how Nightly turns into Beta, and Beta turns into Release. If a change &quot;rides the trains&quot; that means it is distributed as part of this normal cycle of Nightly to Beta to Release. See also Uplift.<br /> ;Triage<br /> : The process of deciding what the next step for a new bug is. In Firefox, there are [https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html triage owners] responsible for making these decisions, and they follow [[Bugmasters/Process/Triage|our triage process]].<br /> ;Tree<br /> : Informal term referring to a branch of source code (e.g mozilla-central, mozilla-beta, etc). Saying something is &quot;in-tree&quot; means its source code lives in mozilla-central.<br /> ;Treeherder<br /> : The [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central main dashboard] used to view results from continuous integration (CI). The name 'Treeherder' is both a reference to The Lord of the Rings (Ents) and the fact that it is used to manage all of Mozilla's &quot;trees&quot;.<br /> <br /> ==U==<br /> ;Uplift<br /> : When a patch lands on mozilla-central in Nightly, it will normally get to users after Nightly turns to Beta, then Beta turns to Release. If the patch is &quot;uplifted&quot; then it is moved from Nightly/mozilla-central to the current Beta.<br /> <br /> ==V==<br /> ;vcs<br /> : Short for [https://en.wikipedia.org/wiki/Version_control version control system].<br /> <br /> ==W==<br /> ;Webmaker<br /> : Webmaker is now an app that can be used to create and share on the Web. [https://webmaker.org webmaker.org]. In the past it used to stand for what is now Mozilla Learning Network.<br /> ;WONTFIX<br /> : The (not very friendly sounding) way we acknowledge a bug or issue, but declare we won't fix it – either because it's not important enough, or because we don't consider it a bug. This is a resolution in Bugzilla, but is also used casually to refer to a decision not to do something.<br /> ;Workweek<br /> : A week where teams meet face to face and work together and sing and dance. They can be for the whole Moco Mofo ( example, you might hear about the Portland workweek or Whistler or Orlando) or they can be in smaller teams, like the fundraising team workweek.<br /> <br /> ==Y==<br /> ;Yak Shaving<br /> : When you find yourself doing a series of tasks you hadn't anticipated doing to accomplish your original goal<br /> ;Yammer<br /> : Previously used as a communications tool by Mozilla staff. Replaced by https://mozilla.slack.com/.</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2019-04-29&diff=1211400 2019-04-29T17:59:33Z

<p>Mhoye: IRC</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2019-04-29 or anonymously at https://air.mozilla.org. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=fYa0LfRUKzo<br /> * join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion<br /> * Presenters only: Vidyo room &quot;Brownbags&quot;. Do '''not''' use this room if you're not planning to speak. <br /> {{conf|8600}}<br /> ** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> <br /> * The Developer Relations team would like to give a big thank you to the Mozilla Tech Speakers who gave talks this past week at various conferences and events around the globe. This past week Mozilla Tech Speaker delivered a combined total of a dozen talks and workshops at developer-facing events. Big shout-outs to Ayah, Felipe, Flaki, Michelle, Yuliana, Carolyn, Jennifer, &amp; Yamama - we would like to thank you all for helping to spread your message about Mozilla and the Open Web!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> * 19:00-21:00 CEST [https://indieweb.org/events/2019-04-29-virtual-homebrew-website-club Homebrew Website Club Virtual EU]<br /> ** The '''Homebrew Website Club''' is a growing world-wide network of meetups for all levels of web users who want to take back control of their online identities and content from social media silos. <br /> ** Yes happening right now til 12:00 PDT / 15:00 EDT / 19:00 UTC<br /> ** Details to join: https://indieweb.org/events/2019-04-29-virtual-homebrew-website-club<br /> * Monday through Wednesday, [https://fitc.ca/event/to19/schedule/ FITC Toronto 2019] Toronto, Canada<br /> ** Future of Innovation, Technology, and Creativity is a Mozilla-sponsored event. There may still be complimentary tickets from th DevRel Sponsorship team. See the ticket request form linked below.<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * The '''Homebrew Website Club''' 17:30-19:30 local times at (exceptions in parentheses)<br /> ** '''Nürnberg (GERMANY)''' (18:00-20:00 CEST)<br /> ** '''London (ENGLAND)''' (19:00-20:30 BST)<br /> ** '''Nottingham (ENGLAND)'''<br /> ** '''New York City, NY (USA)'''<br /> ** '''Guadalajara (MEXICO)'''<br /> ** Details and '''RSVP!''' https://indieweb.org/events/2019-05-01-homebrew-website-club<br /> <br /> * [https://us.pycon.org/2019/ The PyCon 2019 conference in Cleveland, Ohio, USA,]<br /> ** A Mozilla-sponsored developer event, this is the largest annual gathering for the community using and developing the open-source Python programming language.<br /> ** May 1st through May 9th with tutorials, talks, and sprints.<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> * 18:00-19:30 BST [https://indieweb.org/events/2019-05-02-homebrew-website-club Homebrew Website Club Brighton], ENGLAND<br /> ** Details: https://indieweb.org/events/2019-05-02-homebrew-website-club<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> '''[https://2019.indieweb.org/berlin IndieWebCamp Berlin]''' at Mozilla Berlin! <br /> * A two-day maker event for creating and/or improving your personal website, using it instead of social media, and exploring the edges of decentralized web interactions and development<br /> ** Saturday Day 1: Introductions, Discussions, Brainstorming<br /> ** Sunday Day 2: Create/Hack/Dev/Design/Code Day.<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> * '''IndieWebCamp Berlin''' day 2 - see above.<br /> <br /> === Next Week ===<br /> May 11-12: '''[https://indieweb.org/2019/Düsseldorf IndieWebCamp Düsseldorf]''' at sipgate! <br /> * A two-day maker event for creating and/or improving your personal website, using it instead of social media, and exploring the edges of decentralized web interactions and development<br /> <br /> === Later Events and Available Tickets ===<br /> <br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ]. <br /> If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details.<br /> <br /> '''[https://fitc.ca/event/to19/ FITC Toronto 2019]''' Toronto, Canada | 2019-04-29 to 2019-05-01<br /> <br /> '''[https://2019.indieweb.org/berlin IndieWebCamp Berlin 2019]''', Germany | 2019-05-04 to 2019-05-05<br /> <br /> '''[https://btco.nf/DUS2019indiewebcamp IndieWebCamp Düsseldorf 2019]''', Germany | 2019-05-11 to 2019-05-12<br /> <br /> '''[http://www.writethedocs.org/conf/portland/2019/ Write the Docs 2019]''' Portland, Oregon, USA | 2019-05-19 to 2019-05-21<br /> <br /> '''[https://circlecitycon.com/ CircleCityCon 2019]''' Indianapolis, IN, USA | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://2019.jsconf.eu/ JSConfEU (and CSSConfEU)] ''' Berlin, Germany | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://layers.is Layers 2019]''' San Jose, CA, USA | 2019-06-03 to 2019-06-05<br /> <br /> '''[http://refactr.tech/index.html REFACTR.TECH 2019]''' Atlanta, GA | 2019-06-05 to 2019-06-07<br /> <br /> '''[https://pixelpioneers.co/ Pixel Pioneers]''' Bristol, UK | 2019-06-07<br /> <br /> '''[https://cssday.nl/2019 CSS Day]''' Amsterdam, Netherlands | 2019-06-13 to 2019-06-14<br /> <br /> '''[https://2019.jsconf.asia/ JSConf Asia]''' Singapore | 2019-06-14 to 2019-06-16<br /> <br /> '''[https://2019.indieweb.org/summit IndieWebSummit 2019]''' Portland, Oregon, USA | 2019-06-29 to 2019-06-30<br /> <br /> '''[http://codelandconf.com/ Codeland 2019]''' New York, NY, USA | 2019-07-22<br /> <br /> '''[https://braziljs.org/conf BrazilJS Conference]''' Porto Alegre, RS, Brazil | 2019-08-23 to 2019-08-24<br /> <br /> '''[https://ruhrjs.de/ RuhrJS 2019]''' Rotunde Bochum - Bochum Germany | 2019-10-05 to 2019-10-06<br /> <br /> '''[http://connect.tech/ CONNECT.TECH]''' Atlanta, GA, USA | 2019-10-16 to 2019-10-18<br /> <br /> '''[https://ntnu.edu/wac2019 Web Audio Conference 2019]''' Trondheim, Norway | 2019-12-04 to 2019-12-06<br /> <br /> <br /> '''Mozilla Sponsored Developer Events'''<br /> <br /> Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):<br /> <br /> Cordoba WebConf 2019 | 5/11/19 | Cordoba Argentina<br /> <br /> beyond tellerrand // DUSSELDORF | 5/13/19 | Dusseldorf, Germany<br /> <br /> AccessU 2019 | 5/14/19 | Austin, TX, USA<br /> <br /> 200 OK | 5/17/19 | Tulsa, OK, USA<br /> <br /> '''[https://indieweb.org/2019/Utrecht IndieWebCamp Utrecht 2019]''', Netherlands | 2019-05-18 to 2019-05-19<br /> <br /> Write the Docs Portland 2019 | 5/19/19 | Portland, Or, USA<br /> <br /> CircleCityCon | 5/31/19 | Indianapolis, IN, USA<br /> <br /> JSConf EU 2019, CSSconf EU 2019 | 5/31/19 | Berlin, Germany<br /> <br /> Layers | 6/3/19 | San Jose, CA, USA <br /> <br /> REFACTR.TECH | 6/5/19 | Atlanta, GA<br /> <br /> Pixel Pioneers Bristol | 6/6/19 | Bristol<br /> <br /> CSS Day | 6/13/19| Amsterdam, NL<br /> <br /> JSConf.Asia | 6/14/19 | Singapore, Singapore<br /> <br /> DinosaurJS | 6/20/19 | Denver, CO USA<br /> <br /> 2019 Game Devs of Color Expo | 7/6/19 | New York, NY, USA<br /> <br /> Codeland | 7/22/19 | New York, NY, USA<br /> <br /> BrazilJS Conference | 8/23/19 | Porto Alegre, RS, Brazil<br /> <br /> JSConf Korea 2019 | 9/3/19 | Seoul, South Korea<br /> <br /> Strange Loop 2019 | 9/12/19 | St. Louis, MO, USA<br /> <br /> W3C Developer Meetup | 9/16/19 | Fukuoka, Japan<br /> <br /> JSConf Budapest 2019 &amp; CSSConf Budapest 2019 | 9/25/19 | Budapest, Hungary<br /> <br /> View Source 2019 | 9/30/19 | Amsterdam, NL<br /> <br /> Fronteers | 10/3/19 | Amsterdam, NL<br /> <br /> RuhrJS 2019 | 10/5/19 | Bochum Germany<br /> <br /> Web Engines Hackfest 2019 | 10/14/19 | Galicia, Spain<br /> <br /> CONNECT.TECH | 10/16/19 | Atlanta, GA, USA<br /> <br /> beyond tellerrand // BERLIN 2019 | 11/4/19 | Berlin, Germany<br /> <br /> Web Audio Conference 2019 | 12/4/19 | Trondheim, Norway<br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Andrew Krug<br /> | Staff Security Engineer, Enterprise Information Security<br /> | IT MinIT<br /> | Remote, Via PreRecorded Video <br /> | No<br /> | n/a<br /> | [https://drive.google.com/file/d/1Opp0JiRvg7woq2CWVQJUXXGSc6WuycBZ/view?usp=sharing Video] [https://wiki.mozilla.org/IT/WeeklyMinIT MinIT Notes and Transcripts]<br /> |-<br /> | Asa Dotzler<br /> | Firefox Product Management<br /> | Firefox Browsers Weekly Update<br /> | MTV<br /> | no<br /> | n/a<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2019-04-29 2019-04-29]<br /> |-<br /> | Nathan Egge<br /> | Research Engineering Manager, Codecs<br /> | ET Weekly Update<br /> | Remote<br /> | no<br /> | n/a<br /> | [https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#April_29th.2C_2019 ET headlines]<br /> |-<br /> | Mike Hoye<br /> | I'm making friends on the internet.<br /> | Synchronous Messaging At Mozilla<br /> | MoTo<br /> | no<br /> | n/a<br /> | the #synchronicity channels on IRC and Slack.<br /> |-<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Their Name<br /> | Your Name<br /> | Intro location<br /> | Their Location<br /> | Their Role<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=User_talk:LeahPhelps&diff=1211208 2019-04-25T19:20:20Z

<p>Mhoye: Welcome!</p> <hr /> <div>'''Welcome to ''MozillaWiki''!'''<br /> We hope you will contribute much and well.<br /> You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br /> Again, welcome and have fun! [[User:Mhoye|mhoye]] ([[User talk:Mhoye|talk]]) 19:20, 25 April 2019 (UTC)</div>

Mhoye https://wiki.mozilla.org/index.php?title=User:LeahPhelps&diff=1211207 2019-04-25T19:20:20Z

<p>Mhoye: Creating user page for new user.</p> <hr /> <div>I need access to the account to update upcoming events/conference tickets available for Mozilla staff</div>

Mhoye https://wiki.mozilla.org/index.php?title=User_talk:Lclick&diff=1211198 2019-04-25T16:36:22Z

<p>Mhoye: Welcome!</p> <hr /> <div>'''Welcome to ''MozillaWiki''!'''<br /> We hope you will contribute much and well.<br /> You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br /> Again, welcome and have fun! [[User:Mhoye|mhoye]] ([[User talk:Mhoye|talk]]) 16:36, 25 April 2019 (UTC)</div>

Mhoye https://wiki.mozilla.org/index.php?title=User:Lclick&diff=1211197 2019-04-25T16:36:22Z

<p>Mhoye: Creating user page for new user.</p> <hr /> <div>As per chat with Justin -looking to get approval - I am working with Sandra Persing on Dev Sponsorship, Viewsource and her EU Roadshows doing the Event Production</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2019-04-08&diff=1210229 2019-04-08T17:19:18Z

<p>Mhoye: /* Speakers */</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2019-04-08 or anonymously at https://air.mozilla.org. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=xw5mtHRTDwU<br /> * join #airmozilla for backchannel discussion<br /> * Presenters only: Vidyo room &quot;Brownbags&quot;. Do '''not''' use this room if you're not planning to speak. <br /> {{conf|8600}}<br /> ** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> * The add-ons team would like to thank Zitronella for helping bring potentially malicious extensions to our attention by filing more than 30 blocklisting bugs over the last four weeks. Thank you for helping make our our ecosystem safe, Zitronella!<br /> <br /> * The Reps Council Spring 2019 elections voting has just started. Thanks to Felipe Do Espirito Santo, Irvin Chen, Luis A Sanchez, Mayur Patil, Prathamesh Chavan, Shahid Ali Farooqui, Vishal Chavan, Yuliana R Jimenez for running for the five slots. If you're a Rep, head over to [https://reps.mozilla.org/v/reps-council-elections-h1-2019-5-spots/ the Reps Portal] and cast your vote until April 15th. Q&amp;A from all candidates can be found on [https://discourse.mozilla.org/t/important-council-elections-spring-2019-nominee-q-a/37700 Discourse].<br /> <br /> * All of us here on the Developer Relations team would like to give a shout out to Mozilla Tech Speakers: Shagufta, Eugenio, Giannis, Trishul, and Rabimba who delivered talks this past week at various conferences and events around the globe. Additionally, we want to give a special shout out to two of our newest Tech Speakers: Marko and Indira - who delivered their first talks as official Mozilla Tech Speakers this past week. Thank you everyone for helping to spread your message about Mozilla and the Open Web!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * [[Add-ons/Community/Meetings|Add-ons Community Meeting]]<br /> ** 15:30 UTC / 8:30am PST | ACE Vidyo Room<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please reach out to Sandra Persing at spersing@mozilla.com for more details.<br /> <br /> '''[https://fitc.ca/event/to19/ FITC Toronto 2019]''' Gothenburg, Sweden | 2019-04-29 to 2019-05-01<br /> <br /> '''[http://www.writethedocs.org/conf/portland/2019/ Write the Docs 2019]''' Portland, Oregon, USA | 2019-05-19 to 2019-05-21<br /> <br /> '''[https://circlecitycon.com/ CircleCityCon 2019]''' Indianapolis, IN, USA | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://2019.jsconf.eu/ JSConfEU (and CSSConfEU)] ''' Berlin, Germany | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://layers.is Layers 2019]''' San Jose, CA, USA | 2019-06-03 to 2019-06-05<br /> <br /> '''[http://refactr.tech/index.html REFACTR.TECH 2019]''' Atlanta, GA | 2019-06-05 to 2019-06-07<br /> <br /> '''[https://cssday.nl/2019 CSS Day]''' Amsterdam, Netherlands | 2019-06-13 to 2019-06-14<br /> <br /> '''[http://codelandconf.com/ Codeland 2019]''' New York, NY, USA | 2019-07-22<br /> <br /> '''[https://braziljs.org/conf BrazilJS Conference]''' Porto Alegre, RS, Brazil | 2019-08-23 to 2019-08-24<br /> <br /> '''[https://ruhrjs.de/ RuhrJS 2019]''' Rotunde Bochum - Bochum Germany | 2019-10-05 to 2019-10-06<br /> <br /> '''[http://connect.tech/ CONNECT.TECH]''' Atlanta, GA, USA | 2019-10-16 to 2019-10-18<br /> <br /> '''[https://ntnu.edu/wac2019 Web Audio Conference 2019]''' Trondheim, Norway | 2019-12-04 to 2019-12-06<br /> <br /> <br /> '''Mozilla Sponsored Developer Events'''<br /> <br /> Mozilla sponsored developer events around the globe:<br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Amy Tsay &amp; Scott DeVaney<br /> | Add-ons Product Manager &amp; Editorial Manager<br /> | Add-ons in 2019, Recommended Extensions program<br /> | MTV &amp; SF<br /> | No<br /> | [https://docs.google.com/presentation/d/1Do9IDtV8dUrIMKVT7rmaxLh1GfqMRUqs0cWuNylsDnQ/edit doc]<br /> | [https://blog.mozilla.org/addons/2019/04/08/recommended-extensions-program-coming-soon/ blog post]<br /> |-<br /> | Asa Dotzler<br /> | Firefox Product Manager<br /> | Weekly Firefox Browsers Update<br /> | MTV<br /> | No<br /> | n/a<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2019-04-08 2019-04-08]<br /> |-<br /> | Andrew Krug<br /> | Staff Security Engineer, Enterprise Information Security<br /> | IT MinIT<br /> | Remote, Via PreRecorded Video <br /> | Please play video: https://drive.google.com/open?id=1mq0f5LWQK9WcOFJ_50zMcL-Wu19VFTn2<br /> | n/a<br /> | [https://drive.google.com/open?id=1mq0f5LWQK9WcOFJ_50zMcL-Wu19VFTn2 Video] [https://wiki.mozilla.org/IT/WeeklyMinIT MinIT Notes and Transcripts]<br /> |-<br /> | Emma Humphries<br /> | Bugmaster<br /> | Bug Types and Regression Fields<br /> | Remote, And recorded video<br /> | Yes<br /> | [https://drive.google.com/file/d/1v79RaDA3aXLxjNhXfDJ6vPmrmNW2qyyg/view Video]<br /> | [https://mozilla.github.io/bug-handling Bug Handling Documentation]<br /> |-<br /> | Mike Hoye<br /> | I make friends on the internet.<br /> | The future of IRC and synchronous messaging at Mozilla.<br /> | MoTo<br /> | No<br /> | -<br /> | Coming soon.<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> | Their Name<br /> | Your Name<br /> | Intro location<br /> | Their Location<br /> | Their Role<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Kelsey Whitthauer<br /> | Tara Robertson<br /> | Vancouver<br /> | Mountain View<br /> | Diversity and Inclusion Project Manager<br /> |-<br /> |-<br /> | Alissa Sobo<br /> | Michael Cooper<br /> | Portland<br /> | Portland<br /> | Services Engineering<br /> |-<br /> |-<br /> | Nhi Nguyen<br /> | Selena Deckelmann<br /> | Portland<br /> | Vancouver, BC<br /> | Networking Manager, Firefox Runtime<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2019-04-08&diff=1210227 2019-04-08T17:17:59Z

<p>Mhoye: /* Speakers */</p> <hr /> <div><br /> {{WeeklyUpdateNav}}<br /> * Every Monday @ 11:00am Pacific Time (19:00 UTC) <br /> * Watch at https://mzl.la/project-meeting-2019-04-08 or anonymously at https://air.mozilla.org. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=xw5mtHRTDwU<br /> * join #airmozilla for backchannel discussion<br /> * Presenters only: Vidyo room &quot;Brownbags&quot;. Do '''not''' use this room if you're not planning to speak. <br /> {{conf|8600}}<br /> ** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br /> <br /> __TOC__<br /> <br /> = Weekly Project Status Meeting Agenda =<br /> <br /> Items in this section will be shared during the live status meeting.<br /> <br /> == Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br /> * The add-ons team would like to thank Zitronella for helping bring potentially malicious extensions to our attention by filing more than 30 blocklisting bugs over the last four weeks. Thank you for helping make our our ecosystem safe, Zitronella!<br /> <br /> * The Reps Council Spring 2019 elections voting has just started. Thanks to Felipe Do Espirito Santo, Irvin Chen, Luis A Sanchez, Mayur Patil, Prathamesh Chavan, Shahid Ali Farooqui, Vishal Chavan, Yuliana R Jimenez for running for the five slots. If you're a Rep, head over to [https://reps.mozilla.org/v/reps-council-elections-h1-2019-5-spots/ the Reps Portal] and cast your vote until April 15th. Q&amp;A from all candidates can be found on [https://discourse.mozilla.org/t/important-council-elections-spring-2019-nominee-q-a/37700 Discourse].<br /> <br /> * All of us here on the Developer Relations team would like to give a shout out to Mozilla Tech Speakers: Shagufta, Eugenio, Giannis, Trishul, and Rabimba who delivered talks this past week at various conferences and events around the globe. Additionally, we want to give a special shout out to two of our newest Tech Speakers: Marko and Indira - who delivered their first talks as official Mozilla Tech Speakers this past week. Thank you everyone for helping to spread your message about Mozilla and the Open Web!<br /> <br /> == Upcoming Events ==<br /> <br /> === This Week ===<br /> <br /> === Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br /> <br /> === Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br /> <br /> === Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br /> * [[Add-ons/Community/Meetings|Add-ons Community Meeting]]<br /> ** 15:30 UTC / 8:30am PST | ACE Vidyo Room<br /> <br /> === Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br /> <br /> === Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br /> <br /> === Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br /> <br /> === Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br /> <br /> === Next Week ===<br /> <br /> === Later Events and Available Tickets ===<br /> '''Mozilla DevRel Complimentary Tickets'''<br /> <br /> Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please reach out to Sandra Persing at spersing@mozilla.com for more details.<br /> <br /> '''[https://fitc.ca/event/to19/ FITC Toronto 2019]''' Gothenburg, Sweden | 2019-04-29 to 2019-05-01<br /> <br /> '''[http://www.writethedocs.org/conf/portland/2019/ Write the Docs 2019]''' Portland, Oregon, USA | 2019-05-19 to 2019-05-21<br /> <br /> '''[https://circlecitycon.com/ CircleCityCon 2019]''' Indianapolis, IN, USA | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://2019.jsconf.eu/ JSConfEU (and CSSConfEU)] ''' Berlin, Germany | 2019-05-31 to 2019-06-02<br /> <br /> '''[https://layers.is Layers 2019]''' San Jose, CA, USA | 2019-06-03 to 2019-06-05<br /> <br /> '''[http://refactr.tech/index.html REFACTR.TECH 2019]''' Atlanta, GA | 2019-06-05 to 2019-06-07<br /> <br /> '''[https://cssday.nl/2019 CSS Day]''' Amsterdam, Netherlands | 2019-06-13 to 2019-06-14<br /> <br /> '''[http://codelandconf.com/ Codeland 2019]''' New York, NY, USA | 2019-07-22<br /> <br /> '''[https://braziljs.org/conf BrazilJS Conference]''' Porto Alegre, RS, Brazil | 2019-08-23 to 2019-08-24<br /> <br /> '''[https://ruhrjs.de/ RuhrJS 2019]''' Rotunde Bochum - Bochum Germany | 2019-10-05 to 2019-10-06<br /> <br /> '''[http://connect.tech/ CONNECT.TECH]''' Atlanta, GA, USA | 2019-10-16 to 2019-10-18<br /> <br /> '''[https://ntnu.edu/wac2019 Web Audio Conference 2019]''' Trondheim, Norway | 2019-12-04 to 2019-12-06<br /> <br /> <br /> '''Mozilla Sponsored Developer Events'''<br /> <br /> Mozilla sponsored developer events around the globe:<br /> <br /> == Speakers ==<br /> <br /> The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 &quot;widescreen&quot; format, please indicate in the &quot;Sharing&quot; column below.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! [https://mozillians.org/u/USERNAME Presenter]<br /> ! Title<br /> ! Topic<br /> ! Location<br /> ! Sharing<br /> ! Media<br /> ! More Details<br /> |-<br /> | Who Are You?<br /> | What Do You Do?<br /> | What are you going to talk about?<br /> | Where are you presenting from? (Moz Space, your house, space)<br /> | Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br /> | Links to slides or images you want displayed on screen<br /> | Link to where audience can find out more information<br /> |-<br /> | Amy Tsay &amp; Scott DeVaney<br /> | Add-ons Product Manager &amp; Editorial Manager<br /> | Add-ons in 2019, Recommended Extensions program<br /> | MTV &amp; SF<br /> | No<br /> | [https://docs.google.com/presentation/d/1Do9IDtV8dUrIMKVT7rmaxLh1GfqMRUqs0cWuNylsDnQ/edit doc]<br /> | [https://blog.mozilla.org/addons/2019/04/08/recommended-extensions-program-coming-soon/ blog post]<br /> |-<br /> | Asa Dotzler<br /> | Firefox Product Manager<br /> | Weekly Firefox Browsers Update<br /> | MTV<br /> | No<br /> | n/a<br /> | [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2019-04-08 2019-04-08]<br /> |-<br /> | Andrew Krug<br /> | Staff Security Engineer, Enterprise Information Security<br /> | IT MinIT<br /> | Remote, Via PreRecorded Video <br /> | Please play video: https://drive.google.com/open?id=1mq0f5LWQK9WcOFJ_50zMcL-Wu19VFTn2<br /> | n/a<br /> | [https://drive.google.com/open?id=1mq0f5LWQK9WcOFJ_50zMcL-Wu19VFTn2 Video] [https://wiki.mozilla.org/IT/WeeklyMinIT MinIT Notes and Transcripts]<br /> |-<br /> | Emma Humphries<br /> | Bugmaster<br /> | Bug Types and Regression Fields<br /> | Remote, And recorded video<br /> | Yes<br /> | [https://drive.google.com/file/d/1v79RaDA3aXLxjNhXfDJ6vPmrmNW2qyyg/view Video]<br /> | [https://mozilla.github.io/bug-handling Bug Handling Documentation]<br /> |-<br /> | Mike Hoye<br /> | Make friends on the internet.<br /> | The future of IRC and synchronous messaging at Mozilla.<br /> | MoTo<br /> | No<br /> | -<br /> | Coming soon.<br /> |}<br /> <br /> = Welcome! =<br /> <br /> Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br /> <br /> {| class=&quot;fullwidth-table wikitable&quot;<br /> |-<br /> ! ''Who is being introduced?''<br /> ! ''Who are you? (the introducer)''<br /> ! ''Where are you doing the introduction?''<br /> ! ''Where are they from?''<br /> ! ''How will they be part of Mozilla?''<br /> |-<br /> | Their Name<br /> | Your Name<br /> | Intro location<br /> | Their Location<br /> | Their Role<br /> |-<br /> &lt;!-- Insert new rows here --&gt;<br /> |-<br /> | Kelsey Whitthauer<br /> | Tara Robertson<br /> | Vancouver<br /> | Mountain View<br /> | Diversity and Inclusion Project Manager<br /> |-<br /> |-<br /> | Alissa Sobo<br /> | Michael Cooper<br /> | Portland<br /> | Portland<br /> | Services Engineering<br /> |-<br /> |-<br /> | Nhi Nguyen<br /> | Selena Deckelmann<br /> | Portland<br /> | Vancouver, BC<br /> | Networking Manager, Firefox Runtime<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Weekly Updates]]<br /> [[Category:Meeting Notes]]</div>

Mhoye https://wiki.mozilla.org/index.php?title=Community:SummerOfCode19&diff=1208530 2019-03-06T02:44:20Z

<p>Mhoye: Added the CPG</p> <hr /> <div>This is Mozilla's list of green-lit project proposals for the 2019 Google Summer of Code. <br /> <br /> &lt;b&gt;Are you a student looking to apply to GSoC with Mozilla?&lt;/b&gt; You're in the right place. This page lists all of our proposed [[SummerOfCode|Google Summer of Code]] projects. New suggestions can be made on [[Community:SummerOfCode19:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact mhoye or Florian for edits.<br /> <br /> If you're interested in participating in Mozilla's GSoC program, you can choose from the list below, '''but you do not have to'''. You can submit a proposal for your own idea. You should look at the [[Community:SummerOfCode19:Brainstorming|guidelines]], though, and discuss your ideas or application in the #introduction channel on IRC.Mozilla.org. This is important, as GSoC projects '''must have''' a supporting member of the Mozilla community to evaluate and mentor them, named in the application.<br /> <br /> Please bear in mind that a '''preexisting relationship with Mozilla is not a requirement for a successful GSOC proposal'''. While participating in Bugzilla is a good way to become familiar with how Mozilla works, &quot;spamming&quot; Bugzilla to establish your ''bona fides'' or improve your chances of a successful application has not historically been a successful approach. We're grateful for our volunteers' contributions, as always, but often that effort would be best put towards focusing on the proposals you are specifically interested in, and putting your effort into crafting an application for them specifically.<br /> <br /> ===Application Advice===<br /> <br /> You should do the following:<br /> <br /> * Talk to the mentor. Contact details are on this page; if all you have is a nickname, reach out to them on IRC.<br /> * Read the [https://flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide] and follow its advice.<br /> * Read [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ 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 [https://summerofcode.withgoogle.com/ the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]).<br /> * It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. Applying to more than that will seem like spam.<br /> * Participation in any Mozilla spaces, forums or events, including our GSOC projects, are subject to Mozilla's [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and you should read them carefully.<br /> <br /> Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:mhoye@mozilla.com Mike Hoye]. He will try and respond promptly and direct your questions to the right person. <br /> <br /> ===Project List===<br /> <br /> {| class=&quot;standard-table&quot; border=&quot;1&quot; style=&quot;border-collapse: collapse&quot;<br /> |-<br /> ! Title <br /> ! Details <br /> ! Skills Needed <br /> ! Reporter <br /> ! Mentor(s) <br /> ! Additional Comments<br /> |-<br /> | Improve Python in the browser<br /> | The [https://github.com/iodide-project/pyodide pyodide] project allows the Python scientific stack to run in the browser by compiling it to WebAssembly. Help make stuff run better and faster there.<br /> | Python and JavaScript. Can learn the WebAssembly parts as you go.<br /> | [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br /> | [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]<br /> | There are a number of specific projects we have in mind, but are open to other proposals that are within scope and seem practical within the timeframe. (1) Implement matplotlib's display on top of Web APIs (HTML5 Canvas, etc.) This would allow us to avoid shipping a whole separate rendering engine to the browser. (2) Build WebAssembly support into the conda packaging system to make it easier to distribute new compiled packages for Pyodide. (3) Make multi-dimensional arrays sharable between Python and Javascript. See Pyodide's [https://github.com/iodide-project/pyodide/issues list of issues] for additional ideas. About the mentor: Michael Droettboom is a Staff Data Engineer at Mozilla, and a former lead developer of matplotlib with years of experience building the Python scientific ecosystem.<br /> |-<br /> | ReSpec <br /> | [https://github.com/w3c/respec/ ReSpec] is a JS-based tool used to write W3C Specifications (Web Standards) that is widely used by the Web Standards Community. With 6+ years of development, it's heavily depended upon by the W3C community at large (of which Mozilla is an active participant). ReSpec's code is in need of some modernization, optimizations, and bug fixes - and we could use your help! In this project, you would have the opportunity to make ReSpec's UI more accessible, making it leaner and faster using distributed processing with Web Workers, and/or adding new features to make the lives of W3C spec Editor's better. <br /> | JavaScript, HTML, CSS. <br /> | [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br /> | [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]<br /> | ReSpec offers students the opportunity to work on a large code base that has extensive real world use and impact. The project offers students an extensive range of problems to tackle, from UI design, to concurrent processing (using Web Workers to do distributed text processing), dealing with accessibility and internationalization, writing and learning about unit and integration tests, security, code review, etc. - as well as exposure to the W3C and the web standards community, this project also aims at teaching students about how web standards are put together. To determine if this is a project you would like to be part of, see the [https://github.com/w3c/respec/issues/ list of issues] you could work on. It's a great opportunity to learn about all aspects of open source software development, but with the freedom to take on small to large challenges over the Summer (depending on your skill level and level of confidence). About the mentor: Marcos Caceres is a Staff Engineer at Mozilla who has been working on Web Standards for over a decade. Marcos is the lead maintainer of ReSpec. Marcos has extensive experience mentoring developers and has previously successfully mentor a GSO student. <br /> |-<br /> | Ship Public Suffix List (PSL) over Remote Settings<br /> | The list of public domain suffixes (DNS) is shipped with every release, with no way to update it on long term releases for example.<br /> Now that Remote Settings has become a solid solution to ship data, we could use it to publish updates of the PSL.<br /> The task consist in migrating the current client code to read from Remote Settings instead of a file, and implement a scheduled job (like Python) to push updates automatically (most likely compiled as a DAFSA file) <br /> | JavaScript and some Python basics <br /> | [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br /> | [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]<br /> | https://bugzilla.mozilla.org/show_bug.cgi?id=1083971<br /> |-<br /> | [https://github.com/marco-c/bugbug bugbug]<br /> | A platform for machine learning projects applied on Bugzilla, VCS and other software development data.<br /> | Python<br /> | [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br /> | [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)<br /> | The project will involve one or more of:<br /> i) building additional classifiers (e.g., to detect bugs with no steps to reproduce, or to suggest a developer to assign to a bug, and so on);<br /> <br /> ii) improving accuracy/precision/recall of the existing classifiers by implementing other machine learning techniques (e.g., by using convolutional neural networks or recurrent neural networks);<br /> <br /> iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better.<br /> |-<br /> | WebSocket Monitor<br /> | Support for WebSocket monitoring and inspection in Firefox DevTools.<br /> | JavaScript/React<br /> | [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br /> | [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]<br /> | This project aims at providing support for WebSocket monitoring and inspection in Firefox DevTools. The feature should be built on top of the existing Network panel UI and responsible for visualizing data sent through WebSocket connection (i.e. WS frames). The user should be able to use the UI to see as well as analyse the data (search, filter, etc.).<br /> * [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Detailed Project Description]<br /> |-<br /> | Helpful crash reporter<br /> | The crash reporter only allows users to send crash reports but in some cases it might help the user diagnose the crash and solve it on his/her own<br /> | C++, Javascript<br /> | [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br /> | [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto] <br /> | There's a few things that could be implemented:<br /> * A quick test of the memory owned by the crashed process (such as those in [http://www.memtest.org/ memtest86+]) might catch faulty memory, a common cause for crashes<br /> * The crash reporter client might try and validate Firefox files which can sometimes become corrupted (usually because of hardware issues). If they are it can prompt the user to re-install Firefox<br /> * Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers<br /> * For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla<br /> |-<br /> | Debugger Inline Variable Preview<br /> | When the Firefox DevTools debugger is paused, users can hover over variables to get a useful tooltip that details the variable's value at that time. While this popup is very informative, one valuable enhancement would be displaying relevant contextual variables values alongside the variable inline, alleviating the need for tooltips and allowing the user to more quickly get the information they need. The applicant will work alongside the Debugger's team to implement this feature based on UX mockups and be given space to share and implement ideas of their own.<br /> | Javascript<br /> | [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br /> | [https://mozillians.org/en-US/u/davidwalsh/ David Walsh] <br /> | <br /> |-<br /> | &lt;s&gt;GitHub Checks Support Improvements&lt;/s&gt;<br /> | (withdrawn)<br /> | <br /> | <br /> | <br /> | <br /> |-<br /> | Support GitHub Logins in Taskcluster<br /> | [https://github.com/taskcluster/taskcluster Taskcluster] currently supports logging in with Auth0, the Mozilla login system. We would like to make it useful outside of Mozilla, and most other users do their development on GitHub, making GitHub logins a good solution. This project would involve adding support for signing in with GitHub, as well as the more challenging task of assigning appropriate permissions to users based on the setup of their GitHub account.<br /> | Server-side JS<br /> | [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br /> | [https://mozillians.org/en-US/u/owlish/ Owlish], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell] <br /> | <br /> |-<br /> | Improve Webdriver support in Servo<br /> | [https://github.com/servo/servo/ Servo] currently supports a minimal subset of the [https://w3c.github.io/webdriver/ Webdriver standard]. We would like to improve Servo's support, and verify its correctness by passing a [https://github.com/web-platform-tests/wpt/tree/master/webdriver set of automated tests]. This project would involve writing Rust code to extend the webdriver server inside of Servo, as well as JavaScript and Python to support the [https://web-platform-tests.org/writing-tests/testdriver.html testdriver.js] testharness.<br /> | Familiarity with Python &amp; JavaScript; interest in learning Rust<br /> | [mailto:josh@joshmatthews.net Josh Bowman-Matthews] <br /> | [mailto:josh@joshmatthews.net Josh Bowman-Matthews]<br /> | [https://github.com/servo/servo/wiki/Support-Webdriver-based-tests-project Project description]<br /> |-<br /> | Support importing Instruments profiles in perf.html<br /> | [https://github.com/devtools-html/perf.html/ perf.html] visualizes performance data recorded from various performance analysis tools. It is a tool designed to consume performance profiles from Gecko Profiler but can visualize any profiler able to output JSON. It currently supports Gecko, Chrome and perf profile formats. Instruments is a performance analyzer that comes with Xcode. This project would involve adding support for Instruments profile import in perf.html.<br /> | Familiarity with JavaScript &amp; React<br /> | [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br /> | [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]<br /> | https://github.com/devtools-html/perf.html/issues/1138<br /> |-<br /> | Common Voice - WebAssembly MP3 Encoding<br /> | Currently Common Voice doesn’t support Safari, which is also why we have an iOS app. The only reason being the missing MediaRecorder API. It could be polyfilled (rebuilt in “userspace”) by compiling an MP3 encoder to WebAssembly. I’ve tried that a couple of times, but never had enough time to fix the opaque bugs happening in Safari. This could also be turned into its own library and would be a nice story overall of how WASM can help with WebCompat and missing APIs.<br /> | JavaScript<br /> | [https://mozillians.org/u/gweber/ Gregor Weber]<br /> | [https://mozillians.org/u/gweber/ Gregor Weber]<br /> | [https://github.com/mozilla/voice-web/issues/469 This GitHub issue] lines out some thoughts around how to implement it and you can find references to closed PRs which tried implementing it in various ways.<br /> |-<br /> | Common Voice - Voice Wave Avatar<br /> | We’d like our users to have unique(ish) avatars based either on the characteristics of their voice or a visualization of how their name (or an utterance of their choosing) is pronounced. It could also be a combination of the two ideas. We’re very open to explore this space together, though the a candidate should have some knowledge in sound theory.<br /> | JavaScript, Some knowledge of sound theory<br /> | [https://mozillians.org/u/gweber/ Gregor Weber]<br /> | [https://mozillians.org/u/gweber/ Gregor Weber]<br /> |-<br /> | Tab Manager menu in Firefox <br /> | This project will extend the tab overflow menu - which shows tabs not visible in the browser's tab strip - to allow management of all open tabs across all browser windows. The selected student will be working directly in the Firefox codebase to add functionality and new menu structures to make this easily accessible for end users. <br /> | JavaScript, CSS, and web experience<br /> | [https://mozillians.org/en-US/u/sfoster/ Sam Foster], [https://mozillians.org/en-US/u/bbell/ Bryan Bell]<br /> | [https://mozillians.org/en-US/u/sfoster/ Sam Foster]<br /> | We have [https://mozilla.invisionapp.com/share/4SNCEPDUEZ6#/screens UX mockups] for this feature, which could be broken into two phases. We also have a [https://bugzilla.mozilla.org/show_bug.cgi?id=1480542 bug on file], where discussion has begun. While working on this you will become very familiar with the Browser Toolbox, our own &quot;Inspector&quot; tool for the browser user-interface, as well as writing automated tests for the new feature you're adding. The existing tab overflow code lives in our [https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js browser-allTabsMenu.js] file, which will be the starting point for the new tab manager. You can look at this and the existing tab code to get an idea of how this currently works. <br /> -<br /> |-<br /> |-<br /> | Firefox Reader Redesign<br /> | The design of Firefox’s Reader Mode has languished behind as Quantum has implemented the new Photon Design System. The interface needs to be rebuilt using new visual and interaction styles to match the Photon Design System.<br /> | JavaScript, CSS, and web experience<br /> | [https://mozillians.org/en-US/u/awallin/ Abraham Wallin]<br /> | [https://mozillians.org/en-US/u/eeejay/ Eitan Isaacson]<br /> | [https://mozilla.invisionapp.com/share/87N9YQYCTJZ#/315073983_Reader_View_Redesign UX Mockups] for this feature are available with visual bugs have been reported [https://bugzilla.mozilla.org/show_bug.cgi?id=1187696 here] and [https://github.com/devtools-html/ux/issues/5 here]. Functional bugs and feature enhancements have been documented [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Areader-mode-has-issues here], [https://github.com/mozilla/readability/issues?q=is%3Aissue+is%3Aopen+label%3Ashould-be-readerable here], [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Areadability-algorithm&amp;list_id=14539703 here], and [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=comp%3Areader%20prod%3DToolkit%20whiteboard%3Aisreadable&amp;list_id=14539704 finally here]. The request is for an engineering student to implement the designs and tackle the queue of bugs/enhancements within the Firefox code base. Mentors will support with prioritization, design direction/assets, and technical guidance.<br /> <br /> <br /> |-<br /> | An Android file downloader designed for Emerging Markets<br /> | A lesson learned thanks to our UX team is in Emerging Markets the data plan is dynamic: in late nights we have the most affordable bandwidth. Here's the question: Why not schedule big files and videos and have them downloaded when you're sleeping? The mvp would be an App which we can send urls to. After receiving these urls the App either downloads it directly or defer it to late night. As there are more and more background restrictions enforced on new Android APIs, this should be a fun and challenging journey.<br /> <br /> The ultimate goal of this would be to embed this downloader in our browser for Emerging Markets, Firefox Lite. Firefox Lite is not satisfied with the current Android Download Manager in several ways: We'd like to give users the ability to pause/resume a download, we'd like to download a file directly to SDcard (opposed to download it to the main storage and move it into SDcard). That being said, please focus more on the reusablility of your App as a library than the UX/UI of the App itself. Afterall, GSOC is a coding project!<br /> <br /> We've also prepared an even more ambitious mission for those who want tough challenges: Design the app and make it dynamic deliverable. With aabs we can satisfy both light and heavy users by defaulting Android Download Manager as the download tool and prepare the aforementioned downloader dynamically so that Firefox Lite itself is still minimized in terms of disk size. Nevin and mTwTm are Android developers who can provide assistance to Android App and library design.<br /> | Android Java/Kotlin<br /> | [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)]<br /> | [https://github.com/mTwTm/ mTwTm(Teng-pao Yu)] (mTwTm@mozilla.com), [https://github.com/cnevinc/ Nevin Chen] (nevin@mozilla.com)<br /> | We're receiving requests for mockups already; thank you! However, to best give students the flexibility to design their own implementation we don't have these at least at this point. Nevertheless, to illustrate what might make a good proposal, we want you to imagine what would be a convenient way to schedule downloads. There are many ways we could do this: Copy-pasting download links, have the app opened whenever a link is clicked, or find a way to give other third-party apps access to your App's download queue. As we approach the project start date we expect to have this better laid-out, but we look forward to hearing your ideas.<br /> Also, we're utilizing the Mozilla Asia Product mail-list (https://groups.google.com/forum/#!forum/mozilla-asia-products) for discussions around this project. You might find some useful discussions there as well.<br /> |-<br /> | Toolkit for sandboxing third-parties libraries in Firefox<br /> | Firefox supports a long tail of infrequently used image and audio formats to<br /> support the occasional website that uses them. Each such format requires the<br /> Firefox decoder to use a new open source library for parsing and decoding.<br /> This, unfortunately, increases the attack surface of Firefox and as we saw in<br /> Pwn2Own 2018, Firefox was successfully exploited via a bugs in such libraries<br /> (libogg in this case).<br /> <br /> This project proposes to sandbox third-party libraries in Firefox by building a<br /> new software-fault isolation toolkit. Our tookit will build on the WebAssembly<br /> compiler to isolate libraries in Firefox. But, as part of this toolkit we will<br /> also develop and apply a library for safely interfacing with sandboxed libraries (and<br /> sanitizing data coming from them). with this toolkit we can ensure that any<br /> vulnerability in third-party libraries (e.g., libogg or libpng) cannot be used<br /> to be used to compromise Firefox.<br /> | C/C++, experience with WebAssembly<br /> | [https://github.com/EricRahm/ Eric Rahm] (erahm@mozilla.com)<br /> | [https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br /> | <br /> |-<br /> | Test automation our linting tools<br /> | We have a several linting tools running on Firefox code base, they currently don't have a test suite. <br /> The goal of this project is to make sure that tests are executed. We currently have a similar [https://bugzilla.mozilla.org/show_bug.cgi?id=1432410 test automation for static analyzer jobs]. The idea would be to extend (or replicate) this model for [https://searchfox.org/mozilla-central/source/tools/lint/ ./mach lint] (which run flake8, eslint, etc) and [https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/mach_commands.py#2327 ./mach clang-format]<br /> The bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1448008<br /> | Python<br /> | [https://github.com/sylvestre Sylvestre] (s@mozilla.com)<br /> | [https://github.com/abpostelnicu Andi Postelnicu] (andi@mozilla.com)<br /> | <br /> |-<br /> | Firefox Account Security Dashboard<br /> | Firefox Account administrators and users need an easily digestible view into the important events that have occurred on an account, providing a way to audit for irregularities.<br /> | JavaScript, HTML, CSS, MySQL<br /> | [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br /> | [https://mozillians.org/u/vbudhram/ Vijay Budhram], [https://mozillians.org/u/stomlinson/ Shane Tomlinson]<br /> | The Firefox Account platform tracks security information about an account, but does not surface this information in an easily consumable format. Users and administrators should be able to see a timeline of an account’s security related events, such as connecting devices, signing into services, changing or resetting passwords, and adding or removing 2FA. Each event in the timeline should include a timestamp, IP address, and location information when they occurred. <br /> <br /> This project would entail updating our security event API to ensure we track and expose the required data. The first phase is to build a script that consumes the API and pretty prints the timeline. The second phase is to provide a web interface for the security timeline.<br /> <br /> |-<br /> | Improving FastParquet<br /> | FastParquet is a Python library that needs improvement to how it writes the parquet file format <br /> | Python<br /> | [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br /> | [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br /> | [https://github.com/klahnakoski/mo-parquet/blob/dev/docs/StudentProject%202019.md Read more]<br /> <br /> |-<br /> | Faster Pyparsing<br /> | Pyparsing is a Python library that provides a DSL for language specification. It could use some optimization. <br /> | Python<br /> | [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br /> | [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br /> | [https://github.com/mozilla/moz-sql-parser/blob/dev/docs/Student%20Project%202019.md Read more]<br /> |-<br /> | TUID service improvments<br /> | The TUID service handles millions of requests daily from hundreds of machines. It must go faster, and be stabilized.<br /> | Python/Flask/Sqlite <br /> | [https://mozillians.org/en-US/u/ekyle/ Kyle Lahnakoski]<br /> | [mailto:gmierzwinski@mozilla.com Gregory Mierzwinski]<br /> | [https://github.com/mozilla/TUID/blob/dev/docs/Student%20Project%20190204.md Read more]<br /> <br /> |-<br /> | Firefox Source Docs Infrastructure<br /> | Improve the infrastructure underpinning Firefox's [https://firefox-source-docs.mozilla.org/ in-tree documentation].<br /> | Python, Sphinx, Rst<br /> | [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt]<br /> | [https://mozillians.org/en-US/u/ahal/ Andrew Halberstadt]<br /> | Writing docs for Firefox's in-tree [https://firefox-source-docs.mozilla.org/ source docs] is time consuming and difficult and the end result is difficult to navigate.<br /> <br /> With [https://developer.mozilla.org/en-US/ MDN] de-prioritizing build and workflow docs, we need a suitable replacement for all of Firefox's contribution and workflow documentation. The great advantage of documentation living in-tree, is that it can be updated along with the source. Unfortunately the current system to build and generate docs is difficult to write for, slow to build and generates poorly organized documentation. These factors discourage developers from creating or updating docs.<br /> <br /> This project aims to improve the documentation experience via static analysis tools (e.g hint when docs might need to be updated), enabling linters, faster build times, additional language support and well structured hierarchies. Help make documentation a bigger part of our developer's day to day workflow.<br /> |-<br /> | Improve FixMe<br /> | [http://fixme.ossn.club/ Improve FixMe], a tool for surfacing meaningful contribution opportunities to new contributors. This project started two years ago as a GSoC project and we are looking into adding more capabilities. The tool currently fetches issues only from GitHub and relays a lot into the tags project maintainers use in their repositories. We want to add gitlab support and come up with a more sophisticated way of identifying technologies and skills needed for new contributors <br /> | - Backend: Go, Buffalo, Postgresql. - Front-end: React, typescript, Redux<br /> | [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]<br /> | [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]<br /> | [https://github.com/ossn/fixme Link to] front-end source code, [https://github.com/ossn/fixme_backend link to backend] source code. [http://fixme.ossn.club/ FixMe tool in action]<br /> |-<br /> | Rust AV1 Encoder (rav1e) Project<br /> | Mozilla's rav1e Project [http://github.com/xiph/rav1e] is a clean room AV1 encoder implementation written in Rust. The goal is to create a production ready AV1 encoder for use with common internet use cases: Video-On-Demand (high latency), Live Streaming (some latency), Interactive Video Conferencing (low latency).<br /> |<br /> * C/C++<br /> * Rust<br /> * SIMD<br /> | [mailto:negge@mozilla.com Nathan Egge]<br /> | [mailto:negge@mozilla.com Nathan Egge]<br /> | We are looking for GSoC students to help us research and implement advanced encoding algorithms in rav1e. Areas of interest are:<br /> * Scene detection<br /> * Frame type assignment and ordering<br /> * Encoder complexity analysis and design of speed levels<br /> * Rate-distortion optimization algorithms<br /> * Parallelized encoding using Rust fearless concurrency<br /> * Chunked encoding<br /> |-<br /> | ..your next idea here!<br /> | some details<br /> | skills/language<br /> | reporter<br /> | mentor<br /> | comments</div>

Mhoye