PUBLIC MARKS from user karlcow with tag mozilla

The Community Marketing Guide is a resource for members of the Mozilla community who are interested in getting involved and in helping to promote the Mozilla project in their locale. We hope the guide helps Mozillians identify activities they wish to undertake and point them to the resources that are already available to the community. The guide is of course a work in progress and will be regularly updated, so your feedback to help improve it is always welcome.

This document reflects the current Bespin Server API, as implemented by the Python backend.

HTML5: The Markup Language is a useful document, and makes for interesting reading. It’s status, however, remains controversial (normative or merely informative?). Time will tell, of course, how specifications bloom.

Last but not least, last time I checked Mozilla Labs' name contained the word "Labs". In general, labs are here to make experiments, things that don't seem ordinary or even reasonable, labs are here to pave the future, not do what all others are doing too.

This visualization is a concept for the LizardFeeder and it’s built with jQuery and SVG plugin. Code is a mess, so I’ll post only some (retouched) screenshots.

This would be unheard of anywhere else in the world where Google and Yahoo are the fiercest of competitors. However in Korea, where Naver is the market leader (75% market share), and Daum second, Google and Yahoo are not relevant for most Korean web users (with perhaps the exception of Flickr, which is available in Hangul, and YouTube.)

The goal is to get consensus on a document that improves life for cross-browser web authors as soon as possible, without spending time on features that only apply to small portions of the market, proprietary devices, wrappers for patent-encumbered media players, and other products of closed development processes.

“localising” amounts to far more than translating.

One of the school’s most significant contributions to Mozilla’s Firefox project was developed last year by a recent Seneca computer studies graduate Andrew Smith. He helped implement support for a new image format, the Animated PNG (APNG), which overcomes the technical limitations of animated GIFs.

To do this, future versions of Firefox plan on supporting the new W3C Geolocation Specification, which adds the native ability for Web sites to request, and you to optionally grant access to, your location.

It was September 2006 when Mozilla Corporation CTO Brendan Eich removed Ben Matthew Goodger as owner of the Firefox project and placed Mike Connor at the helm. Goodger was first demoted to “peer” status, and from there he officially removed himself from all leadership positions throughout the Mozilla project.

command is an exploration of using Friend of a Friend (FOAF) data to provide more context about the currently viewed page. It can be installed within Mozilla Ubiquity, a Mozilla Labs project.

Snowl is an experiment to answer that question. It’s a prototype Firefox extension that integrates messaging into the browser

Aurora is a concept video presenting one possible future user experience for the Web, created by Adaptive Path as part of the Mozilla Labs concept browser series. Aurora explores new ways people could interact with the Web in the future based on projected technological trends and real-world scenarios.

1. Focus work on ES3.1 with full collaboration of all parties, and target two interoperable implementations by early next year. 2. Collaborate on the next step beyond ES3.1, which will include syntactic extensions but which will be more modest than ES4 in both semantic and syntactic innovation.

Mozilla paid the way for everyone who attended

But I also think that if all we have are people “like me”, the open internet is at risk. It’s at risk because the better technology doesn’t always win.

Busy indeed. So busy, they were dead. As one of his positive stats for the day, Kim notes that there were over 500 news items covering the launch, which is true. Too bad a fair number of those stories were focusing on the server outage. This incredible PR spin on the day makes it clear that mozilla.org fumbled the ball twice yesterday: once in failing to provide adequate hosting for the event, and again when they failed to fess up to the problem and instead gloss over it with some ra-ra-aren't-we-doing-great blathering.

Lately, I've seen some people criticize Mozilla because a particular bug (often a request for a new feature) that they care a lot about hasn't been fixed, on the basis that the bug was filed some number of years ago (generally more than five). I think this line of criticism is undeserved and seriously misguided. People who make this argument are, effectively, criticizing us for our openness.

Internet Explorer 4 introduced the document.all DOM (document object model) to allow access to the various parts of the web page. Soon after that the standard DOM method getElementById was introduced and is therefore available in all version 5 browsers. This means that the document.all references are only needed to support IE4.

We're not planning to cram a bunch of Fixes into Firefox 3 since it's almost ready, and cramming features in at the last minute risks hurting other Web standards support or hurting some of the other things that make Firefox a great browser.

oui. un discours réaliste (bien que nouveau) qui prend en compte tout le contexte. Cela me rappelle une anecdote d'une amie. Au Canada, elle pratiquait le karaté. À la fin de chaque année, elle était préparée pour passer l'examen des ceintures. Au Japon, elle a repris les cours à zéro. Le maître propose enseigne la technique et la philosophie du karaté et les individus ne se présentent à l'examen que quand ils sont prêts. C'est toute la différence entre passer le test Acid 3 avec hack ou pas, et implémenter sérieusement la technologie en étant sur de ce que l'on fait. Et je trouve, dans ce cas ci, la démarche de Mozilla et son changement de discours plutôt bien.

Regarder les communautés évoluer est toujours intéressant. Que ce soit celles du w3c ou ailleurs. Complexe. Y participer, c'est accepté d'avoir les mains sales ou alors on est un sombre ignare idéaliste.

projet Mozilla se focalise sur la sortie prochaine de la version 3 finale. En effet, ce qui compte pour Firefox actuellement, c'est de se concentrer sur les bogues bloquants pour obtenir un produit le plus stable possible[1]. […]C'est tout à fait ça : ces tests ne sont pas équitables, mais ils sont mieux que rien.