> Charge for access to MDN, structure the legal particulars so that revenue goes to pay the tech writing staff, covers operating costs, and provides the excess

> Charge for access to MDN, structure the legal particulars so that revenue goes to pay the tech writing staff, covers operating costs, and provides the excess to the Mozilla Foundation. Use the resulting goodwill and attention as a lead generation mechanism for whatever other projects Mozilla tries to create and charge for. This doesn't sit very well with me, as someone who has written a few security-related articles on MDN and generally tries to contribute to e.g. the compat-data repository as I get time. I'm motivated, just as I would be with an OSS PR, by the work being high quality and freely accessible to all. It's a wiki. Anyone can help contribute. Do the professional technical writers do an excellent job as changes land in Firefox? Yes. Is it fair to charge for access to contributions that both the paid technical writers and the community have contributed under the impression that this is a free resource in the public domain? I'm not sure. Is there a middle ground whereby we can still fund hosting/maintenance/professional technical writing but give access to a) folks who perhaps otherwise wouldn't have the means to pay for the documentation and b) folks who've contributed to the resource? Perhaps.