That Mozilla is a Corp owned by a not-for-profit isn't the real thing anymore (ie not what people may believe, not that they have any obligation beside following the rule of law) - it just frees the Corp from having to report to random share holders - instead, the Corp and the Org self-select a Board of directors that they report to.
At the end of the day, it's otherwise now similar to many corporations.
I don't think Mozilla can make meaningful impact in a world where it doesn't make products that internet users want to use. It would be a largely toothless advocacy organization at that point.
1. Do project managers, product managers, etc. count, or only real managers with teams reporting to them?
2. Do urinals count, or only real sit-down toilets?
/s
Of course that doesn't always mean more people going at the same time as some people don't like urinating so close to someone else so the second spot goes unused, and some of us prefer to sit for a no.1 anyway unless in a rush.
However, I just checked my queue and couldn't see any.
Just pocket money though.
And as a non-profit entity, could they retain some profit they have as investment or cash somewhere. In case some day they run into negatives they could use those as reserves?
But at the end of the day, Mozilla need some very serious management restructuring, starting from the very top end. Having been a Netscape user from over two decade ago, I finally left Firefox. And if you follow their decision, mailing list etc, you can feel how bureaucratic they are. Slow response to market changes, completely lack of ( actionable )vision, often having completely unrealistic target. Extreme inefficiency in development of its product. And these aren't my thoughts or comment only, their are many ex mozillian employees who felt the same. We all thought Mozilla should have been a great company achieving far then then they are today.
I think people simply aren't aware that all the major revenue associated with the NFL goes through specific teams, which are normal taxable corporations. Humorously, people also aren't aware that they gave up their tax exempt status, so I'm not sure that decision was worth it.
Acquisitions happen when the stakeholders (founders, employees, and investors) don't think they will get the level of return on investment they will be satisfied with.
Even if they DO decide to sell, the case you describe (on the verge of being successful but requires money to get to that point) sell at a disclosed amount. Undisclosed amount mostly means the investors and founders are not proud of the result so they would rather just keep it private.
That's not the case anymore with this merger though, right? Pocket will now cease to make actual money.
Mozilla Corporation is a for-profit, taxable entity. Here are their articles of incorporation: https://www.mozilla.org/en-US/foundation/documents/articles-.... It is itself a wholly owned subsidiary of Mozilla Foundation, which is the non-profit thing that people call "Mozilla". The Foundation is really just a holding company. The thing that people call "Mozilla" that does all of the work is The Corporation.
- Instead of shareholders, nonprofits have members. Members don't own the corporation (no one does) but control it insofar that they hire-and-fire its directors.
- Memberships normally can't be sold, and nonprofits have no equivalent to dividends.
- There are stronger conflict-of-interest protections, preventing officers from signing cheques to themselves or otherwise using the corporation's resources for their personal benefit - at least without someone else's approval.
A typical setup for nonprofits is to tie memberships to being a director, so that current board members choose their own successors. This is known as a "self-perpetuating board".
These things are hard or maybe impossible in a non-profit (IANAL/correct me if I'm wrong)
Non-profits can make surplus revenues over costs and retain them; they can't return profits to shareholders or other particular beneficiaries.
Certain classes of nonprofits are restricted from certain business activities, or limited to certain activities. E.g., charities (501c3 nonprofits) must be organized and operated exclusively for purposes on an list of charitable purposes.
Regional differences may be relevant here: in Canada, you can incorporate a nonprofit corporation and later apply for charity status (which restricts the company's possible activities in exchange for a 0% income tax rate) but it's completely optional.
In the US, on the other hand, to the best of my knowledge, one has to establish a for-profit entity first and then apply to the IRS to recognize it as a charity (which is a lengthy process). The words "charity" and "nonprofit" are interchangeable in the US for that reason.
If the concept of a non-charitable nonprofit exists in your jurisdiction, you can get the benefits of a nonprofit structure (ie. no owners) without restricting the company's activities, minus tax exemption and being able to issue tax receipts.
For context: I founded a non-charitable nonprofit in Canada; I'm not super familiar with the US side of things so I'm happy to be corrected.
The US works similarly. You incorporate as a nonprofit, but you have to separately apply for tax-exempt status afterwards. If you don't, you're a nonprofit without the benefits of being tax-exempt.
I don't understand why people are disappointed that Mozilla has stopped actively developing thunderbird - it means it's not going to change. There is an email client that you like, as is, and want to keep using, and you're annoyed because mozilla has promised not to change it?
https://www.mozilla.org/en-US/security/known-vulnerabilities...
The team that qualifies and does the release work for Thunderbird are volunteers. I believe that the builds are done on Mozilla hosted hardware.
The people who are making these complaints are disproportionately those who have no problem using Debian or Arch, so I don't think that's the crux of the issue for them.
Something is either being actively developed or it's dieing, there is no in between with software, there is no finished state.
I wish more pieces of software would get to the finished state and would slip into maintenance mode.
By the way - the IETF standardised an OAuth2 SASL mechanism (RFC 7628) a couple of years ago, no idea why GMail doesn't support it.
Basically, the only thing that is kind-of Gmail specific is the auth support (https://bugzilla.mozilla.org/show_bug.cgi?id=849540). If Gmail sometimes in future switches from OAuth2 to some other protocol, the client will have to be updated.
Yes, XUL is dead and Firefox is evolving into a Chrome substitute and while people have serious concerns about it, fact of the matter is that Chrome was designed for web apps and almost 9 years after its release Chrome is still the best browser available for web apps. Not sure how many people here remember Chrome's original goals, beautifully illustrated by their comic book announcement, but here's a refresher and try to count the problems that Firefox still has in 2017: https://www.google.com/googlebooks/chrome/index.html
In other words, Firefox is dying because users have been trained to expect security, stability, an interface free of crappy toolbars and extensions you can't uninstall, not to mention running long lived web apps. And while people on this forum will cry out for Vimperator or other poweruser extensions that 99.9% of the world have never heard about, it's undeniable that without evasive action Firefox will become a footnote in only a couple of years.
I'm also a Firefox user and I understand their move away from Thunderbird. For work I use Gmail, personal email is Fastmail, both have really good web interfaces. And while I try using email clients like Thunderbird, the web interfaces are simply good enough and always there. These are web apps btw and guess which browser is best for web apps? It's not Firefox ;-)
And for all I care Mozilla can kill every project they have, if that means Firefox continues to improve. Because it's still the only browser that cares about my freedoms.
I do use Thunderbird for offline backups, more because of the thought of losing important work email. But without combining it with an actual backup system, that's not actual backup, because IMAP does synchronization and messages deleted on the server translate to messages deleted on the client side as well. So I combine it with Arq Backup, which does daily uploads of everything on my laptop.
I do wonder whether using Thunderbird for backups is wise. I never recovered from a Thunderbird archive. Sometimes I'm thinking that a solution like OfflineIMAP or mbsync/isync might be better.
I'm also not sure of this, but that vision thing you link to is focused on the goals of the Foundation proper (excluding MoCo), which is not all of Mozilla, and many of the decisions fall out of that scope.
No. Thunderbird was built against something that the Mozilla foundation used to tout as the future of building software in general: XUL. And there also was a XULRunner which was to Gecko/Firefox what Electron is to Blink/Chrome: a way to develop native apps using the browser engine as a UI toolkit. The difference with electron is that it was built with more native-apps facilities, like spawning up Wizard dialogs: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Tu... All written in their XML.
It wasn't developed specifically for Thunderbird. Firefox is also built on top of the same technologies. XULRunner versions were released concurrently with new Firefox versions.
The reason why Thunderbird is a dead is because XUL is dead, or rather, will die soon. They are rewriting everything related to UI in Firefox and also terminating the traditional addon API which.. required XUL, in favor of Chrome's addon API.
Thunderbird is not the only notable app written in XUL beside Firefox. There's also Miro, Songbird, Google's adwords editor ( https://support.google.com/adwords/editor/answer/106323?hl=e... ) and many others.
Most software written in XUL has either been abandoned or going to die, anyway.
The old-school, heavy desktop apps seem to be so unbelievably light in comparison to current electron-based craziness. But I guess we deserve all the bloat for not being able to come up with sensible common API for desktop development :(
Unfortunately Mozilla failed to execute on that vision, leaving the field open for Electron and friends to emerge. Part of that failure was due to bad technological choices (RDF-XML was terrible), part to the unwieldy Mozilla legacy (the build system was notoriously byzantine) and part to them de-prioritizing anything that Firefox did not need. They had a working general-purpose JS-based UI runtime more than 15 years ago, and still the rise of nodeJS and html-based toolkits passed them by pretty spectacularly - because they had eyes only for Firefox and vanity projects like FFOS.
Additionally, XUL uses web tech, but it is not a standard and was never intended to be a standard (not even an informal specification exists AFAIK), so it's a stretch to say that Mozilla failed to execute on pushing XUL. What would the web gain by pushing it?
comex already named two highly popular ones (slack in particular can't be overlooked) but there are more. https://github.com/sindresorhus/awesome-electron
https://electron.atom.io/apps/
Outside of Slack, WhatsApp and Discord (see a pattern? pretty much all new chat apps are using it), I'm not sure if there's any other truly popular (among users) electron app, but among developers, electron definitely is popular and far more often used than XUL was. It's arguably more popular now for new apps than even toolkits like Qt and WxWidgets. People are writing, not one, but multiple competing implementations of things like.. unix terminal emulators in electron. These are not just webapps contained in chrome, they definitely need native access to local APIs. There's a frenzy among devs.
> so it's a stretch to say that Mozilla failed to execute on pushing XUL. What would the web gain by pushing it?
They didn't fail to "push it to the web". They failed to push it to app devs. They were rather enthusiastic at some point:
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/Th...
> Whether you need to migrate an existing web application to the desktop, are looking for a technology that will enable you to easily port your applications to multiple platforms, or want to integrate your own cool features into the browser, XUL warrants serious consideration.
And now they are arguably failing to push it to themselves as they're entirely abandoning it for Firefox and will rewrite the UI and extensions APIs to get rid of XUL.
Slack has a standalone app? I've only ever used the web version. What more does it do?
> Discord
Likewise, I never even realized Discord had a non-browser implementation.
I never even realized that WhatsApp had a non-mobile implementation.
> they definitely need native access to local APIs
Which ones?
> And now they are arguably failing to push it to themselves
Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?
But that's exactly how Electron and friends got popular: they allow for web-first development. Desktop support is a bonus for people who need it.
When Mozilla started working on XUL, the future of the web looked a lot like XML and fat clients. Applications would be built by desktop developers targeting the desktop in a way that would allow for the web to integrate in the background. They wanted to bring the web to the desktop, woo-hoo!
As it turns out, the opposite workflow won: applications are now built by web developers targeting the web, in a way that allows for desktops to come onboard where required. In this scenario, XUL is just too complicated for people who simply need "a web view with a couple of extra APIs". This is still "bringing the web to the desktop", the fundamental role of the runtime is exactly the same; but the paradigm is opposite to what Mozilla had envisioned.
> They're rewriting their UI using CSS/HTML/JS because this is feasible today
XULRunner/Gecko was already built on CSS and JS, but it lived in a desktop paradigm of pseudo-native widgets - because HTML interfaces were terrible back then. It wasn't even a performance issue, but rather that everything was a page refresh because nobody knew any better. AJAX had not been formalized, and XMLHttpRequest was used (guess what) to pull actual XML. HTML4 was considered a hack that was supposed to eventually go away. It wasn't a "this is not possible today" problem, but rather "why would anyone want that?". Already there were lots of arguments on whether JS was "good enough" for desktop development, whether CSS was too verbose, and so on...
> why would Mozilla want to retain XUL
XUL is battle-tested to a different level, having survived almost 20 years, and it's a better option for pure-desktop development than web views. If Mozilla had paid more attention to its evolution, rather than going on quixotic adventures like FFOS, maybe they could have competed with Electron-style apps. Alas, now it's probably too late.
Maybe I'm just an old fuddy-duddy (I'm in my 20s, jfc), but I don't see how Electron's popularity is considered a given. I know plenty of people who use the given services, but none who use the desktop interfaces. VS Code is the only Electron app that I've ever seen used in the wild. Am I just hanging in the wrong crowds? Which ones should I be looking at, if so?
> It wasn't a "this is not possible today" problem
Hence "feasible" rather than "possible". :P (And conspicuously not "easy" rather than "feasible", either...)
> maybe they could have competed with Electron-style apps
I sound like a broken record by now, but I still don't see what people think Mozilla has to gain by offering a native GUI framework that people have already proven they don't want. And frankly, I think FirefoxOS, while ill-fated, was at least audacious. :P
Just to note: Atom is the original Electron app. I assume you've seen more people use that than Code.
Maybe for you, definitely not for me. Most of the applications I use daily are desktop ones and I'll refuse to install an electron one unless I have to.
Chew up a bunch of RAM and glitch display compositing if my experience is typical.
Can't give an answer on slack, as it's not something I use (and I wouldn't use any of the three services if I had a choice, but you don't get to make choices for entire communities as an individual and chat apps are about communities..), but I can say something about discord.
Custom keybindings, ability to do things like push to talk while you're in game, general integration with your OS desktop features (systemtray, native OS notifications), GUI that can overlay over your full-screen window ( like this: https://youtu.be/aVQyk_GX7aE?t=98 ) and probably other features I haven't paid attention to.
> I never even realized that WhatsApp had a non-mobile implementation.
http://www.theverge.com/2016/5/10/11653606/whatsapp-mac-wind...
Released in May, 2016.. and the webapp launched in 2015.
> Which ones?
Are you seriously asking that of terminal emulators that are supposed to be drop-in replacement for iTerm or Gnome Terminal and whatever else? how do you think your bash scripts can operate without breaking on your local data in a webapp without added native calls? I feel like I'm getting trolled here.
> Er, the whole point of Mozilla is to champion standards-based web tech. They're rewriting their UI using CSS/HTML/JS because this is feasible today, whereas it wasn't in 2005. So I ask again, why would Mozilla want to retain XUL instead of making web technologies more powerful?
So a great deal of selective quoting up till here while acting sassy and not paying attention to what was quoted to support the point yet still asking the question?
Why would they retain a competitive edge when other platforms like electron are attracting all the developers to enhance their application with native access goodness, why indeed.
I'll quote it again.
> Whether you need to migrate an existing web application to the desktop [...] or want to integrate your own cool features into the browser, XUL warrants serious consideration.
Is what Electron and Chrome actually do for people now, successfully, in droves and was an aspiration they had before. As for what is feasible now that wasn't before.. electron is not going away any time soon and webapps haven't replaced native. Even more so on mobile platforms, as 90% websites are begging you to install the app with full screen popups.
Yes, because the question isn't "how is this useful", it's "how is it in Mozilla's best interest to invest in this?" Mozilla came up with XUL because they wanted a cross-platform way to develop a large graphical application, and given that they're an open source organization they figured they might as well try to popularize the framework to hopefully get some volunteer contributions to the codebase. But XUL was never an end, only a means to an end, and the technology itself no longer has any strategic advantage.
As for "failing to execute" on taking over the world of desktop apps with XUL, I don't think Mozilla will lose any sleep over it. The secret sauce to Electron isn't Chromium, it's Node.js. We can say that Mozilla failed to execute the opportunity to popularize server-side Javascript first... but that's Rhino was for, and really, nobody in 2005 would have foreseen that developers would eventually want to write their backends in Javascript. :P
Be careful with generalizations, I am surely not part of that list and know quite a few others that want their computers Electron-free.
ie: They have a simple 404 page instead of some novelty page with funny text and a random webm playing in the background
...though I don't know why anyone would care about slow 404 pages either, given that they should be rarely visited and quickly left.
I always thought Mozilla should have built a Linux distribution (or rather, forked debian like everyone else ha!) and implemented their Firefox UI kit (Gecko right? I'm not as familiar.) and made a Front end for it that was smooth and easy to build apps for using web technologies, but could still run native *nix apps via debion packages.
I believe that now as much as I did when I was younger, but the itme for desktop OSs may have passed.
It would have been a hit I think. Well designed, well maintained, well documented. At least in my starry eyed version of this universe where unicorns exist
It does not seem like the right place to invest to continue having relevance in the marketplace.
I see that with my colleagues, who have Gmail (Gapps for domains) in one tab and OWA in another... instead of using a mail client with unified mailbox and not having tp look after which account has the message.
Yes, Apple Mail.app user here, who is not going to switch to webapp mail anytime soon.
tl;dr: I think Mozilla has actually treated Thunderbird fairly well (but not quite as well as I'd like).
Thunderbird has been difficult for Mozilla to support for a while. In many ways, Thunderbird is only in as good a spot as it is because of people at Mozilla who still care about Thunderbird. There are lots of Gecko features that are used by Firefox and Thunderbird, and often, Gecko devs who make breaking changes to something Thunderbird uses will - if not fix the bug - at least alert the Thunderbird team of the breakage and point them in the right direction to fix it. They're also willing to support (some) stuff that only benefits Thunderbird, especially in the text editor. This can be hard for both teams though, like when Mozilla made huge changes to the Firefox build system; since Thunderbird imports the entire Firefox source tree, Thunderbird had to keep up or be unable to build.
As you can imagine, these difficulties will only be magnified by the (slow) move away from XUL. Worse, Thunderbird's codebase is pretty crufty and full of decisions that last seemed good over a decade ago (e.g. libmime's decision to create its own C-based object system instead of using C++ like the rest of Gecko[1]). It would take a lot of work to make the codebase not suck, and I'm not sure Thunderbird has ever had enough paid staff to do that in a reasonable timeframe. These architectural issues are the reason that message tabs in Thunderbird aren't actually multiplexed: every time you open a message tab, it actually just rearranges the elements from the single instance of the 3-pane layout to make it look right. (That's why scroll position in message tabs isn't preserved when you switch tabs.)
Thunderbird has also has significant difficulties finding a way to make money. Those who remember the Mozilla Messaging days (and the subsequent merge back into MoCo) might recall how that's when the team pushed for features like "Get a New Mail Account" (which has partnered mail providers who could sell users a fancy email address), "FileLink" (which has partners providing file hosting), and even a planned effort to do like Firefox and make money from search referrals (this fell through for some fairly strange partnership issues that I'm not sure I can talk about).
However, despite their general desire to discontinue financial support for Thunderbird, Mozilla (the Foundation, I believe) has opened up donations specifically for Thunderbird[2] which, as I understand it, gave the Thunderbird Council the ability to hire the first paid engineer on Thunderbird in several years[3]. In addition, Mozilla has worked to help Thunderbird find a new long-term home and has provided infrastructure support when they really don't need to do either.
While I think Mozilla should place a greater focus on email, I'm not sure Thunderbird is the best way to go about that, especially as Mozilla moves away from XUL. With the rise of Electron/Positron, something like glodastrophe[4] (based on the ill-fated Firefox OS email app) might have a better long-term outlook. However, trying to replicate all (or even most) of Thunderbird's features in a new application would be a huge effort and it's unclear whether the app would be popular enough to make all that effort worthwhile; I expect Mozilla would want to feel confident that they could use such an app to influence email/messaging standards.
I don't know what's going to happen in the long run, but as a Mozilla employee who started out working on Thunderbird, I still have a special place in my heart for it. I hope that one day Mozilla will be willing to revisit email, but it might take a while.
[1] https://dxr.mozilla.org/comm-central/source/mailnews/mime/sr... [2] https://donate.mozilla.org/en-US/thunderbird/ [3] https://mail.mozilla.org/pipermail/tb-planning/2016-December... [4] https://github.com/asutherland/glodastrophe
https://github.com/nylas/nylas-mail'
(I work at Nylas)
I mean, what is wrong with bookmarks and sharing links? Firefox can even send tabs to other computers I got linked via ff sync.
Iterate on a bad idea, give it a social spin, and voilà! You have a sellable startup. Except you should not buy that.
Pocket provides multi-platform access. And multi-browser access -- doesn't matter if I'm on Firefox, Chrome, Safari, IE, whatevs, I can pull up Pocket.
Pocket strips all of today's utterly fucked, utterly useless, utterly counterproductive Web design. I cannot emphasize too much: Web design isn't the solution, Web design is the problem.
Offline reading. Pocket articles (via app) can be read when disconnected.
Tags. You can create, and cross-reference, tags between articles.
Scale. I've got ~3k - 4k articles on Pocket. Possibly more. (I'll get to that.) They're related to ongoing research, and the ability to find, classify, and relocate large amounts of material is useful.
Whilst Pocket doesn't have a ratings or workflow-related management, I've somewhat created these. A set of tags that relates to quality (rated 0 - 5, low to high, where 0 indicates negative information, 5 indicates a foundational document -- most content is a 2 or 3, and that's rating high. Books and scientific papers generally earn a '4': definitive or clarifying, though generally not foundational.
For workflow, I'm largely working with "readme" (a reminder to go back and read closely), and a set of tags related to specific writing projects. I need to come up with a more useful system.
Pocket also ... sort of and/or sometimes ... allows for full-text search within documents. This may have been a promotional-only feature.
Given that the Web as a whole is approaching uselessness under scope of search, the ability to look through a set of documents I've already at least partially vetted is tremendously useful.
There's a whole slew of things Pocket doesn't do, which I'll address in a top-level comment. I've shared these with the firm, though I've seen little or no progress on any of them in ages.
This desperately needs adding to the UI and tools.
... and yet this thread and every other Mozilla apologist thread is always filled with folks who suggest that it's no big deal to assume an always-on, always-available network connection.
When I get home, I take out my Kobo eReader, which has Pocket built-in. It's very nice to read articles on an eInk display, without the distractions of an iPad or a computer.
It's HARD.
Don't blame them from not being the perfect champion we used to idealize. They are doing everything they can.
I'm all for them killing it.
Why would it be slow? I can only type so fast and sending/receiving mail is mostly dependent on the connectivity, not on the software.
I have a need for more people to repeat the same process. There's zero chance I'll be asking them to download TB.
This means depending on your storage configuration and how you use folders, potentially writing 100MB, 1G, 10G, etc. back to disk on folder content change.
For batch processing though, I use the CLI tools - thunderbird is view/compose only (procmail/formail/archivemail/offlineimap,etc)
I was hitting performance probs on bigger folders, and setup some more strict archiving to archive older mails to subfolders/zap offline using an 'archivemail' job, etc, and the problem went away, with TB being quite snappy.
as I understand it there was some effort to support 1-file-per-email, which might be an option now, but this has it's problems too.
Outlook has it's PST corruption hell...
Basically, in my opinion, email is a pain, each client shows it differently, though I am admittedly not up to speed on Opera Mail.
You seem to be attempting to address just the slowness of my complain and not its overall awfulness. Start-up time, loading each email; I've never seen it work very fast it always has that android-like lag throughout the entire thing. It also doesn't feel native to whatever OS you're using it in almost like using a Swing app.
The UX is just awful.
So if you think Thunderbird should be killed, what do you suggest as a replacement? It needs to be free, and run on Windows for my company to use it.
I suppose I'll have to learn to live with mutt eventually.
Mutt is the only way I can keep up with my mail volume. The only time the UI doesn't react instantly is when it loads huge mailboxes. And it still does that faster than I've seen graphical clients load the same mailbox.
Add to that pretty much infinite customization, and it does indeed suck less.
If you have to deal with large amounts of mail for pretty much whatever reason, you can do it faster with mutt than with any other client I've ever used. Yes, there is a learning curve. It isn't a vim-style learning curve, but it is there. But if you're considering a command line MUA at all, you can handle it.
There's a bunch of config tweaks that are supposed to help but so far they haven't.
Also, sometimes it'll just not find certain messages. That also means it's time to clear out and rebuild indexes.
This has been my experience every time I use thunderbird, over many years. I'm not sure what it is about my mailbox that makes me see these issues when others don't.
It's a good program but could use some maintenance loving.
If you like thunderbird theres postbox developed from thunderbird
Vivaldi browser (unofficial Opera successor) is working on an HTML5 powered email app, though will it be open source?
On Android there is open source K9Mail app but it's pretty old fashion, no conversation view.
I envision a new lean Mozilla browser (like Firefox was to Mozilla Suite back then) based on Rust powered Servo-HTML-engine and a HTML based UI. Additionally an email app addon would fit in my vision.
Mozilla doesn't have the resources to continue with Thunderbird.
I am increasingly baffled by their decisions and how they relate to the strategic plans [0] they've been producing for a while. Despite the worthy words in their plan they seem to have no sense of direction. That saddens me.
That said I'm happier having Pocket as an open source part of Mozilla/Firefox than a surprise integration of a commercial app.
[0] https://wiki.mozilla.org/MoFo_2020