MDN Web Docs
Ads on MDN #335
-
|
https://developer.mozilla.org/en-US/advertising Just adding this as pointer now, as I thought it would have been largely communicated by now. Also creating a thread for the "occasion" |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
|
Hey @SphinxKnight, thank you for stating the thread. Do you or anyone else from the community have any questions about this topic? |
Beta Was this translation helpful? Give feedback.
-
|
Disclaimer: it will soon be 10 years I contribute to MDN, esp. localizing its content in French. What follows is my opinion only and does not constitute a statement for the MDN l10n-fr community. This content is also hosted on https://gist.github.com/SphinxKnight/f8d86b6bdc2910719ba3b1476ac09910 Ethics & TransparencyTransparencyThere has been 0 announcements to the public nor to the community. Here is the 8th principle of the Mozilla Manifesto for anyone interested to read: "Transparent community-based processes promote participation, accountability and trust." I have since seen several messages from my end (without actively looking for them) "was there a blog post or an annoucement?". mdn/yari#8213 has no rationale nor explanation. In my mind "open source" is more than just "share source code on GitHub and deal with it". It would be nice for yari to be exemplary in terms of intent/transparency in order to build trust. A few weeks ago (and before ads inclusion), a roadmap with OWD was advertised: no mention of ads in the blog post nor in the tracking GH view. On the other hand, this roadmap is advertised right from https://developer.mozilla.org/en-US/advertising. Is this roadmap a means to an end (generating revenue) or the contrary? To balance this, I strongly hope there will be a report at the end of the six weeks of this "experiment" (29th of March) and that any continuation will not be made in silence by default. Ethics & other commonsOn https://www.kevel.com/, we can read on the front page "Bypass ad blockers with ad server APIs" which, to me, does not align with "user respect". On the other hand, neither Wikipedia nor OpenStreetMap have ads while those noble projects:
Mozilla also has another "common" project that I know of: Common Voice. As far as I understand, this project is lead by Mozilla Foundation (whereas MDN is lead by Mozilla Corporation): would/should/could MDN switch to MoFo governance? Accountability & distributionContrary to previous MDN Plus features, this "feature" affects every reader on MDN. For other features, it was sensible for Mozilla to collect the corresponding revenue as they were the sole creators and maintainers of MDN Plus. Since ads affect every single page (whether English or localized, whether written by a MoCo employee, an OWD member, or a volunteer): what is the plan to distribute the revenue generated by the ads among the diverse community writing them? For instance, in the past, 40% of MDN traffic was generated from non-English content. Does that mean that Mozilla will "invest" 40% (minus a margin for hosting/managing the platform) of ads revenue to maintaining localization tooling/communities for MDN? A similar question could be asked about the OWD "share". EfficiencyI have no statistics regarding the developer population, but I would tend to think that, as most of them are tech-savvy, they have an ad blocker installed (this question could have been asked beforehand on Matrix/Discord). If I understand it correctly: blocking the ads would block the revenue. Moreover:
In regards to all of this, I would not bet that much on ads and do not quite understand Mozilla strategy here. ProspectiveI can't help but ask those bleak questions.
References |
Beta Was this translation helpful? Give feedback.
-
First of all, thank you for taking the time to provide feedback. We also want to thank you, and our wider community, for all your support and contributions.
In general, Mozilla does not do outreach for experiments on our products. This is partially related to limited resources and the high number of experiments across Mozilla, and partially because we do not want to focus people’s attention on the experiment but instead see how it performs on its own. This is why your feedback is so valuable. We added a page on MDN Web Docs, linked from the display ad, where we explained the why and how of advertising on MDN. We will review the experiment results at the end of March, and based on this, we will share the next steps. At that point, if there is a launch plan, it will involve widely communicating the why, how, and other relevant details.
We cannot speak directly to Kevel’s marketing copy decisions. What we can do is explain how we implemented ads. We are partnering with Kevel because they allow us to make privacy-compliant ads without sharing user data. The ads are served based on the page’s context and not through user tracking. We use country data, which is done on our CDN and not shared with any third party. We use our own ads server, and even that one does not get the IP of the user, only the country code. To get a little more technical 😊, we use an IP range and not the user’s specific IP address. This was custom work done by engineering to protect user privacy further. Also, one thing to note is that, as you later mention, if you have uBlock installed with EasyList, ads on MDN Web Docs are indeed blocked.
MDN Web Docs is part of the Mozilla corporation and incurs costs that Mozilla has covered for the past 17 years. Mozilla recognizes the value of MDN Web Docs for the wider web developer community. We all have MDN’s future at heart and want to ensure that the project will continue to serve web developers worldwide for many years to come. Mozilla, as a company, has a long-standing goal of diversifying its revenue streams. This will involve experimenting in different areas, and success in that goal should ultimately strengthen Mozilla and its mission. A delicate balance must be struck here, so we rely on our community of readers and contributors to help guide us along this path. As with most things, we will not always agree on everything, but we want to ensure the balance does not tip too much in either direction.
Our focus is to continually make MDN better - that is why we have a fully scoped roadmap with pure MDN product improvements out there that we are committed to delivering by the end of the year. Ideally, this impacts our investment in our relationship with partners and the community. There are active conversations about improving our tooling and ways in which we support our partners and community.
We believe that advertising can be effective and is a major part of how the internet is financed today. We do our best to display ads that we believe are relevant in context and come from companies that align with Mozilla’s vision and values. We do not track or share personal information, and we do believe this could be a great option for sustaining MDN moving forward without sacrificing user experience on the site.
MDN Web Docs is a collective effort, and we believe that will always be true. OWD is one of our closest partners, together with the Product Advisory Board. There are also many individual contributors (like yourself) who are invaluable to the project. Mozilla has been continuously investing in MDN for the last 17 years, we are committed to the project, and to answer your specific question, we have no intention to let OWD or anyone else ‘run’ MDN in the near future.
As mentioned earlier, Mozilla Corporation plans to continue to invest in and host MDN.
As mentioned before, not something we are actively pursuing at the moment, but we thank you for the suggestion.
As an open-source project, and with the licenses chosen, we are aware that anyone is able to fork the MDN Web Docs project and start it under a different name, brand, business, and contribution model. We hope the community we have built over the past 17+ years will stick around and help ensure that the current MDN Web Docs keep getting better for everyone. Thank you again for your thoughtful feedback. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like this is not an experiment anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @SphinxKnight, here is a summary of what we talked about in the community call. Thanks to those who could attend. Apologies that it took so long to post this. There is a lot going on at the moment. Hermina talked about the ads experiment. The ads experiment was a success, and ads will continue on MDN. Florian (Engineering team) demonstrated a new code playground that is being worked on. Dipika (Content team) provided some highlights of the work that the content team has been doing, such as the improvements to the RegExp pages, new guidelines for the “See also” section of our pages, and the addition of new examples to the CSS color function page. We ended by announcing that the MDN Web Docs blog will be launched on 1 May this year. The blog will be used to publish articles that demonstrate how multiple open web technologies are used to build websites and apps. Through the blog, we will also provide regular updates on what the MDN Web Docs team has been working on, including updates from the engineering team., The Community Spotlight contributors will now be featured here. The blog will also be used to feature sponsored content. We have strict guidelines around sponsored content. It will be clearly identified as such, the content provided by the partner has to be valuable to our readers by itself, but also, the service promoted needs to make sense for our readers. We also announced that we are working on a project called the MDN Web Docs sustainability initiative. This initiative is our way to support and give back to the maintainers and open-source projects that MDN Web Docs relies on. We will also support not-for-profit organizations focused on empowering underrepresented people in tech, such as Women Who Code, and educational projects like freeCodeCamp. What this support will look like is not decided as we need to speak with these people and organizations to understand how this initiative can be the most effective for them. |
Beta Was this translation helpful? Give feedback.
-
|
There was a question on Discord:
Yes, it will be at https://developer.mozilla.org/blog but the content will not be part of mdn/content. The MDN team does not own Hacks, and it is used for other updates that are unrelated to MDN. We wanted to create a space that is specifically focused on MDN and what we, the community, and our partners do. As mentioned in the update, we also want to use the blog to provide other value-added content through sponsored content, which would not be possible on Hacks. |
Beta Was this translation helpful? Give feedback.
Hey @SphinxKnight, here is a summary of what we talked about in the community call. Thanks to those who could attend.
Apologies that it took so long to post this. There is a lot going on at the moment.
Hermina talked about the ads experiment. The ads experiment was a success, and ads will continue on MDN. Florian (Engineering team) demonstrated a new code playground that is being worked on. Dipika (Content team) provided some highlights of the work that the content team has been doing, such as the improvements to the RegExp pages, new guidelines for the “See also” section of our pages, and the addition of new examples to the CSS color function page.
We ended by announcing that the MDN Web…