main mozilla tech

We have an important story to tell!

Hey @flod (and Giacomo!)! You touched interesting topics in your latest post, and when I started crafting my comment it got so lengthy, I decided to use my platform to deliver it. Blog-to-blog discussion style! 馃檪

I’ll try to respond, but please, bare in mind, that that’s my personal opinion, nothing official.

You started by pointing out a set of efforts that you either find of questionable value or not “leader” style. Things like Fx UI direction, multiprocessing, Jetpack or Personas.

In particular, you focused on two dimensions:

  1. Are those efforts unique? Innovative? Or do we chase others?
  2. Are those efforts valuable elements that fit into Mozilla Manifesto vision

You question both, and I believe you have all the rights on Earth to do so. We may disagree, but we should talk about this, and I find the fact that you express your concerns in public a good sign of the health of our ecosystem.

So, down to some points you raised. I humbly disagree with your notion of “cloning Chrome”. I believe it is a cognitive impairment that we so easily (we – I mean, most Mozillians I know) buy – this concept of “fresh Chrome”. Chrome is great! But it is not “innovative” in a sense many people talk about it. We just so easily take for granted a lot of inventions we brought to the world, and Chrome, yes, they just looked at Firefox and learned from us. That is just awesome, but that’s what they did!

Once again, Google is looking at an open source project and learns from them how to build a web browser. No, wait! Google, Microsoft and Apple are doing it. Now, how awesome it is? Think of all those things that Firefox brought to the browser landscape since its 1.0 version and notice how many of those innovations are now in IE8, Safari and Chrome.

They also have brilliant developers and *just* bringing all the values of Firefox would be a waste of time, so they, among other things, got a free ride of fixing things we struggled with. And now it is our time to fix those, and there’s nothing unhealthy in this. What would be, in my opinion, unhealthy, is to pretend we don’t see them, and defending our approach as “the right one” (remember Bill Gates first comments on Firefox 1.0?).

Ability to go multi-process is important. Majority of perceived performance improvements that Chrome has (and Fx 3.5/3.6 brought) come from two things: tricking user’s eyes – show him UI 200 ms before its usable – and putting expensive elements off the main thread. (I’m sure that performance team will be able to explain that better). The fact that you have to restart your browser when you install extension is a UX bug. No user expects it or wants it. It does not bring any value and the only reason we have it is a technical limitation.

For years we raised the bar of how the web browser should work. We set the standards in many areas. Opera set some, Safari set some, IE set some as well. Now Chrome set some standards and we just have to match them, possibly using extelligence of our brilliant dev team to push it further and innovate (Jetpack team is far from just fixing issues, they aim for bringing extensions to a new level, and they should be aiming for nothing less than that!). No reason to be worried, we make a great web browser better and it would be unwise to ask our users to trade those nice features for ability to use browser with Mozilla values. Why not give them the best of both?

Personas is an interesting project. I remember my initial feelings when I encountered Personas were much of “eee, nothing interesting”. I considered it to be a minor feature. I recognized that I’m not a target audience (neither you are, I think). But on the day of Fx 3.6 launch I got my lesson when I received amazing amount of feedback from my non-geek friends precisely about Personas and how this project resonated with them. It was amazing for me how emotional people got about “missing Real Madrid Persona, but you have Barcelona one!” or “the pink one is soooo cute” or “my browser is so much more personal now, when my you-name-it favorite actor/actress or symbol of my subculture is here”. Look at the amount of Personas created by people in such a short time! It is an amazing project and only now I see how it fits into Mozilla mission and vibe.

UI on the other hand is a much more complex thing, cause it is related to personal taste and fashion (and fashion itself is, from sociologist point of view a bizarre phenomena of human culture). But imo it all boils down to a simple aspect of cyclical changes. Windows 7 brought new UI, IE8 followed. Chrome followed IE8, Opera followed IE8 or Chrome or both, we’re following W7 or IE8 or Chrome or Opera – you call it. People expect browser to match the visual style of their operating system and Windows 7 is going to be the OS of choice for the vast majority of the world which, in result, will set the UI standard for the OS and apps for quite a some time. We can like it or hate it, but that’s going to happen, and Firefox on Windows should imo fit the OS style. What we will do beyond that is the major issue, and I believe our UI team is trying to come out with the value on top of that. Basing on past experience, I’m sure they’ll do a great job and we’ll see others learning from us. That’s how it works here. Would you prefer vendors to ignore each others accomplishments or deny them?

I disagree with you on your perspective of mobile world. I, for one, wait for Fennec on Android and I know a lot of people who do. I’m excited to think of how we can fit Firefox experience into Windows Mobile 7 and I’m sure it’ll be an exciting journey. Mozilla Messaging is going to generate projects related to forms of communication and I find this topic to be extremely important, so I have no worry about sustainability of it. Our embedding story is nothing to be proud of, but maybe it was a trade-off we had to do in order to achieve what we aimed for. I share your concerns here, and I see many of the platform team people discuss what we can do in order to make it better.

I see Mozilla pretty much self-aware of many of the issues you raised and diversified internally enough to have people raising concerns internally and open enough to have a ground to talk about them – your post is a part of it.

Bottom line

But ultimately I believe your concerns would be all valid if that would be all that is happening in the Mozilla project. If the whole community would work on either Personas, or marketing or UI. But is it? Do you really feel that those elements you describe represent, as you wrote “Mozilla project as a whole“?

I see Mozilla as a meta-project that’s involved in a huge number of projects that touch amazing variety of issues, and it is very hard to nail it down to one or two and call that “representative” for the community.

No matter what you think of Personas, I don’t think you can say that this effort matches what Mozilla is doing with Drumbeat, Bespin, Raindrop or Weave. No matter if you find Jetpack valuable, I hope you did not get lured by press foretelling the end of extensions as we know them. Can you name an example of a project that generated tons of thousands of dependencies and was irresponsibly killed by Mozilla? Have we ever done something like that? Then, do you really think we will do this?

We generate amazing amount of projects of very different kinds. Globally, our community is very diversified and in different points of their journey. Some communities need more marketing, UK, Korea, Sweden? Some, like Italy, Poland, Germany, may have enough internal marketing to consider Mozilla global marketing effort focused on promoting Firefox useless for them or even “too much”. We, Mozillians who live in those countries should act as a membrane which adjusts the signal, and gives feedback to our fellow Mozillians worldwide about what we need, and what we don’t. Poland has 52% of market share, and we need things like developers community or foundation-like efforts to use the potential are trust we generated over years as a platform to bring Mozilla values further, so we work with Mitchell, Mozilla Foundation and from time to time I try to get Paul Rouget’s attention 馃槈 At the same time, PR and marketing wise, we work with Polish PR agency, Barbara and others to balance the amount of press we generate to avoid wasting time to convince the convinced ones. That’s just adjusting. I believe that we should do that much more often in many countries which just are ready for different aspects of Mozilla project to stimulate and energize Mozillians.

Example? Here you are. You think we focus too much on marketing sites? Well, then you focus on other aspects! I believe that the concept of “we have to localize all websites to all languages” is not sustainable anymore. We will generate more websites/webapps, and our local communities will decide which ones to promote locally. We don’t have to have everything localize everywhere and that’s a great power you have to adjust the signal to your locale. Mozilla should make sure all websites/webapps/apps are localizable and let community decide which ones to localize. Focus on the ones that are most important for you!

We have so many projects to pick from! Of different kinds, using different techniques to address different aspects of the common value set expressed in Mozilla Manifesto. They’re also diverse in a way you think about them.

Some of them are truly unique and experimental, and massive – think of our JIT approach (it took a ride from MtV to SF airport for Taras to explain to my what is so different in our JIT approach but now I’m proud of what we’re aiming for), think of L20n, think of Ubiquity,聽 Bespin, Raindrop or Drumbeat.

Some of them, are application of Mozilla-way onto existing concepts. Weave is not innovative because it allows sharing data. But it brought privacy to the picture. SUMO is not the very first support platform ever, but the way we approach the concept of support is innovative and “Mozillian”. Our Metrics team is not the only metrics team in the world, but they do hell a lot of innovation on making their work public and open to contribution which is pretty unique. We may not be the first project ever to have marketing team, but we approach marketing and PR in a unique and innovative way.

Some of them are just a catch-up game and that’s also not bad. We have 350 million users, if someone brought a good idea to the world of web browsers and we can just make sure that 350 million Internet users may use Internet safer, easier and better then I find it pretty important thing to do and I definitely expect such actions from other vendors. (think: partial upgrades)

Ultimately, many of them are a mix of the ones above and as long as we are able to generate new projects that resonate with what people find important on the Internet, I think Mozilla makes an impact and has a bright future that we, including you and me, have to shape.

main mozilla po polsku tech

Mozilla, wolno艣膰 i h.264

Uwaga: poni偶szy tekst, to moja prywatna opinia, jako cz艂onka projektu Mozilla.

W tym tygodniu nast膮pi艂 wa偶ny moment w historii rozwoju WWW. Youtube i Vimeo og艂osi艂y plany odej艣cia od technologii Flash na rzecz standardu HTML5.

Kawa艂ek historii

Blisko rok temu, Mozilla og艂osi艂a wprowadzenie tagu <video/> i rozpocz臋艂a promowanie go, jako alternatywy dla zamkni臋tych wtyczek.

Wiele os贸b wtedy krytykowa艂o t臋 decyzj臋. Zwracano uwag臋, 偶e nikt inny tego nie wprowadza, 偶e HTML5 to jeszcze nie jest standard, 偶e Ogg/Theora, kodek, kt贸rego u偶ywamy, nie jest wystarczaj膮co szybki oraz, 偶e jest za p贸藕no, nikt nie zrezygnuje z zamkni臋tych wtyczek dla otwartego standardu. Ta krytyka nie by艂a bezpodstawna. Wszystkie powy偶sze punkty by艂y prawdziwe.

To, 偶e dzi艣 rozmawiamy o tym z tak odmiennego punktu widzenia pokazuje tylko jak szybko nast臋puj膮 dzi艣 zmiany w 艣wiecie standard贸w w por贸wnaniu do, np. czasu jaki zaj臋艂o wprowadzanie standardu CSS2. To ogromny sukces ca艂ej spo艂eczno艣ci skupionej wok贸艂 WWW i wierz臋, 偶e Mozilla mia艂a w tym decyduj膮c膮 rol臋.

Wracaj膮c do tematu, dzi艣 mamy trzy wa偶ne silniki obs艂uguj膮ce <video/> – Presto (Opera), Webkit (Safari, Chrome) i Gecko (Firefox, Camino, Seamonkey, Flock). Mamy rosn膮c膮 liczb臋 stron, kt贸re korzystaj膮 z tego standardu i rosn膮c膮 liczb臋 u偶ytkownik贸w, kt贸rzy korzystaj膮 z przegl膮darki kt贸ra je obs艂uguje. (W Polsce oko艂o 50% u偶ytkownik贸w Internetu).

Niestety, Chrome i Safari zdecydowa艂y si臋 wspiera膰 wideo obs艂uguj膮c jedynie kodek o nazwie h.264, kt贸ry jest zamkni臋ty i trzeba za niego zap艂aci膰. Mozilla uwa偶a, 偶e taki krok jest szkodliwy dla rozwoju Internetu i stoi w sprzeczno艣ci z Manifestem Mozilli i w efekcie nowe platformy Vimeo i Youtube nie mog膮 by膰 wykorzystywane przez Firefoksa.

Wierzymy, 偶e znajdziemy porozumienie, ale na razie sytuacja jest trudna. W tym po艣cie postaram si臋 wyt艂umaczy膰, dlaczego Mozilla uznaje H.264 za z艂y kodek dla Internetu.

main mozilla po polsku tech

Firefox 3.6 wydany!

A jednak, myli艂em si臋.

Dwie godziny przed czasem, Firefox 3.6 zosta艂 wydany!

Wi臋cej informacji.

Dzi臋kujemy ca艂ej spo艂eczno艣ci Mozilli pracuj膮cej nad tym! 馃檪

main mozilla po polsku tech

Firefox 3.6 ju偶 dzisiaj, o 19:30 czasu polskiego

Taaak… P贸艂 roku po wydaniu Firefoksa 3.5, ju偶 dzisiaj, o 19:30 czasu polskiego Mozilla wyda nast臋pn膮 wersj臋 swojego flagowego produktu – Firefoksa.

Czas w Internecie przyspiesza. Kiedy艣 rok mi臋dzy wydaniami by艂 OK, teraz p贸艂 roku to ju偶 stanowczo za d艂ugo oczekiwania, zatem wszyscy w projekcie mamy poczucie, 偶e na finalne 3.6 czekalismy d艂ugo.

Z drugiej strony. Cierpliwo艣膰 u偶ytkownik贸w spada. Kiedy艣 byli gotowi czeka膰 na swoje BBSy czy pierwsze strony po kilka minut na modemach 36kbps. Dzi艣 narzekamy na kilkumegabitowe 艂膮cza. Podobnie z przegl膮darkami. Cho膰 ka偶da, absolutnie ka偶da wersja ka偶dej przegl膮darki na rynku jest szybsza z wersji na wersj臋, po kilku miesi膮cach staje si臋 ju偶 “za wolna”.

Firefox 3.6 nie jest wyj膮tkiem, szybszy o 20% od Firefoksa 3.5 sprawia, 偶e Firefox 2.0, w 2006 roku demon pr臋dko艣ci, wygl膮da dzi艣 na okrutnie powolnego (mimo, 偶e przecie偶 moc obliczeniowa domowych komputer贸w wzros艂a kilkakrotnie!).聽 Dzi艣 wszystkie przegl膮darki walcz膮 o u艂amki sekund, cho膰 zbli偶amy si臋 do granicy mo偶liwo艣ci sprz臋tu.

Poza pr臋dko艣ci膮, Firefox 3.6 to tak偶e Personas, mn贸stwo fajnych rzeczy dla autor贸w stron, mechanizm pilnuj膮cy aktualno艣ci wtyczek i inne.

Marek St臋pie艅 i ca艂e pracowa艂o oczywi艣cie nad przygotowaniem polskiej lokalizacji, kt贸ra mam nadziej臋 jak zawsze stanowi膰 b臋dzie mocny punkt programu 馃檪

p.s. Tak. O 19:30. Mike Beltzner jest bardzo, bardzo skrupulatny. Punkt 19:30 w Polsce. Ani minuty, sekundy, godziny wcze艣niej. Wszystko co pojawi si臋 wcze艣niej mo偶e si臋 zmieni膰. Chcesz wcze艣niej? Mo偶esz pobra膰 nocn膮 kompilacj臋 – ale gwarancj臋 jako艣ci i wsparcie dajemy na finalne wydanie Firefoksa 3.6, kt贸re pojawi si臋 o 19:30 o czym i Mozilla nie zapomn膮 zakomunikowa膰.

main mozilla tech

The world stands on its head

Unrelated opening
Every one of us has those moments when you find yourself old. Even teenagers do, when their younger friends teach them how to use the latest hype du jour on the Internet. I, for one, feel profanely old today, and kind of hardly accepting the reality of the approaching “middle age” thing.

“It’s rare that you see an artist in his 30s or 40s able to really contribute something amazing.” said Steve Jobs. Thanks Steve…

But that was not supposed to be about me becoming 26. It was supposed to be about another miracle that nobody expected to ever happen. Or at least, I’m still genuinely surprised whenever I see the dream of yesterday becoming reality of today.

So, maybe for many of you it will not come as anything striking, kind of聽 “yea, Poland has always had good community and Firefox market share is above average”, but for me it’s an impossible coming real.

Down to the point just published another round of their browser stats for Poland. According to those, Chrome just passed 3% of market share in Poland. It is a real deal. I remember Firefox having 3% – in December 2004, month after 1.0 release, after 6 years of work, Mozilla based browser reached 3% of market share. But that’s not only that! Opera just week ago gained a point and reached 10% of market share in Poland! I remember it – May 2005 – Firefox 1.x at 10.2%.

And having that, we have also Firefox breaking 52% of market share in Poland! 52% is the high and it is clearly an outstanding result that heavily influences the way we should think about Internet in Poland. It’s an amazing award from the users to the Mozilla project and, especially, a group of people in the team and those working on community forum.

In result of all of this, Internet Explorer in Poland, the one web browser that dictated, for over 10 years, how the web looks like, ten years in which the Internet has been shaping up, this web browser has now only 33.38% of market share. One third. Vox populi at its best.

We have 2/3 of users using modern web browsers, and if we add IE8 here, it gets to 3/4, 75% of users. IE6 is used by less than 9% of users and it means that, for example, just by watching the stats, companies will do better by investing in making sure their website works with Opera than checking it in IE6!

Hard to express this feeling. It’s amazing that we can see modern browsers not cannibalizing each other, but sharing the market share gains.

Wake up, revisit the web today, it’s party time!
Think of what’s possible because of that. We have the Web today that means something different for the users and web authors. They can slowly start to ignore IE6, and that is a real deal for everyone who does the web hacking. Users can utilize the powerful webtools, banks can invest in reach online banking, people are also free to choose their operating system because their online experience wont degrade because of that. People can choose out of four major web browsers that are in a healthy competition or they can choose from one of the less mainstream, but still high quality ones like K-Meleon, Camino, Seamonkey, Arora, Epiphany… Over 52% of Polish internet users can change how the websites look via extensions, and how their browser works and what they see via adblocks, flashblocks and others. They can influence their experience and by vast majority they chose their web browser by themselves, understanding what they are doing and knowing that they have a choice now.

I’m pretty sure that this is true not only for Poland, but for other countries. Hungary, where Firefox is at 52%. Latvia with Firefox at 50%,聽 Bulgaria, where Firefox is above 45% and just passing by IE. Ukraine where Opera has 34% and Firefox has 26%… and I’m still talking about just one region, while the rest of Europe is going through the similar process.

Five years after Firefox 1.0 has been released, we have a different web. The web which has new challenges and opportunities. We have to raise to them and I believe that the next 5 years is going to be super exciting!

main mozilla po polsku tech

Firefox 3.5 wydany!

W nawi膮zaniu do poprzeniego wpisu… To ju偶 oficjalne! Firefox 3.5 jest ju偶 publicznie dost臋pny, przetestowany i stabilny!

20090630_firefox_3.5fZapraszam do pobrania i zapoznania si臋 z informacjami o wydaniu oraz do obejrzenia statystyk pobierania na 偶ywo, a jutro, o 20:50 polskiego czasu nast膮pi Shiretoko Shock Weave – moment w kt贸rym ca艂a spo艂eczno艣膰 Mozilli w jednym momencie poinformuje na sieciach spo艂eczno艣ciowych o tym wydaniu 馃檪

Chcia艂bym przy okazji nieskromnie zwr贸ci膰 uwag臋 czytelnik贸w na niesamowit膮 robot臋 jak膮 wykonuje w Polsce zesp贸艂, a w szczeg贸lno艣ci lider zespo艂u – Hubert Gajewski oraz lider lokalizacji Firefoksa – Marek St臋pie艅. To dzi臋ki tej pracy polska lokalizacja jest tak wysokiej jako艣ci! 馃檪

main mozilla po polsku tech

Dzieje si臋!

Ca艂e szcze艣cie, 偶e doczekali艣my si臋 czas贸w, gdy o tym co dzieje si臋 w projektach Internetowych informuj膮 media mainstreemowe, portale spo艂eczno艣ciowe, mikroblogi, a nawet mozillowo-zorientowany foxinews. Szcz臋艣cie, bo gdyby kto艣 chcia艂 s膮dzi膰 o aktywno艣ci projektu po planecie MozilliPL, to trudno by艂oby si臋 czego艣 dowiedzie膰.

Sam mam niestety ma艂o czasu (tak, tak, sesja…), ale spr贸buj臋 w telegraficznym skr贸cie, w losowej kolejno艣ci, opisa膰 kilka temat贸w dla zainteresowanych:

  • Wydanie Firefoksa 3.5 zbli偶a si臋 wielkimi krokami. Tym razem, w odr贸偶nieniu od naszej tradycji, chcieliby艣my, aby wydanie RC faktycznie by艂o kandydatem na wersje finaln膮. Koniec z wydawaniem RC1 i planowaniem trzech nast臋pnych r贸wnocze艣nie… Jak co艣 jest kandydatem na wydanie, to ma by膰 gotowe. Dlatego Mike (Beltzner) i Mike (Shaver) bardzo powa偶nie uparli si臋, 偶e nie b臋dzie RC2. No, chyba, 偶e niebo spadnie nam na g艂owy.
  • Nowy A w nim – 艂atwiejsza nawigacja, wygodniejsze zarz膮dzanie i nowa funkcja – Kolekcje – kt贸ra umo偶liwia tworzenie w艂asnych zestaw贸w rozszerze艅 i motyw贸w. W przysz艂o艣ci mamy nadziej臋 zaoferowa膰 Ci mo偶liwo艣膰 spakowania takiej kolekcji i wydania jako w艂asnego Firefoksa.
  • Projekt – przez 35 dni zostanie zaprezentowanych 35 nowych funkcji dla webmaster贸w, kt贸re pojawi膮 si臋 w przegl膮darkach nowej generacji – Firefoksie 3.5, nast臋pnej Operze, Safari i Chrome.
  • Thunderbird 3.0beta3 zbli偶a si臋. Zosta艂a jedna du偶a rzecz (globalne wyszukiwanie), kt贸ra powinna wyl膮dowa膰 w ci膮gu tygodnia i potem ju偶 przygotowania do wydania.
  • Trwaj膮 prace nad Firefoksem 3.0.12. Tradycyjnie, kilka poprawek wydajno艣ci, kilka bezpiecze艅stwa i kilka b艂臋d贸w zwyk艂ych.
  • Zesp贸艂 przygotowa艂 polskie t艂umaczenie Poradnika Recenzenta do Firefoksa 3.5. B臋dzie to ma艂a ksi膮偶eczka z opisem nowych technologii i funkcji jakie b臋d膮 dost臋pne dla autor贸w stron WWW i u偶ytkownik贸w wraz z nowym Firefoksem.
  • Zacz臋艂y si臋 przygotowania do planowanego na wrzesie艅 Tygodnia Mozilli (po angielsku – Mozilla Service Week, ale niestety brzydko brzmi t艂umaczenie dos艂owne). B臋dzie to kampania troch臋 podobna do bank贸w czasu – chcemy zach臋ci膰 ludzi posiadaj膮cych zdolno艣ci techniczne do pomagania osobom mniej uzdolnionym i potrzebuj膮cym pomocy. W ramach tej kampanii b臋dziemy szuka膰 ch臋tnych do prowadzenia wyk艂ad贸w na temat obs艂ugi Internetu, osoby chc膮ce pom贸c z konfiguracj膮 Internetu, lub w inny spos贸b pom贸c bli藕niemu. 馃檪
  • Pierwsze prace nad Firefox.Next – tutaj zidentyfikowali艣my 35 b艂臋d贸w, kt贸rych rozwi膮zanie sprawi, 偶e Firefox b臋dzie reagowa艂 szybciej przez co poprawi si臋 wra偶enie z interakcji z przegl膮dark膮. B艂臋dy takie oznaczamy TSnap. W przysz艂ym tygodniu w trunku wyl膮duje Canvas3D, a zesp贸艂 odpowiedzialny za layout zacz膮艂 prace nad XBL2. O innych planach na Firefox.Next mo偶na przeczyta膰 na Wiki.
  • Seamonkey 2.0b1 powinno wyj艣膰 w ci膮gu tygodnia.
  • Microsoft wst臋pnie og艂osi艂, 偶e zamierza wyda膰 Windows 7 bez IE w Europie. Bardzo trudno okresli膰, czy to jest w艂a艣ciwy ruch. Mitchell 艣wietnie podsumowa艂a (jeszcze przed t膮 decyzj膮) jak ten dylemat wygl膮da z naszej strony. Ja mam bardzo mieszane odczucia. Nie do ko艅ca rozumiem co Microsoft zdecydowa艂 tak naprawde (co dok艂adne oznacza “we will offer it separately”?) i mam powa偶ne w膮tpliwo艣ci, czy wydawanie w 2009 roku systemu operacyjnego bez przegl膮darki jest dobre dla u偶ytkownik贸w.
  • JestPack to nowy projekt z Mozilla Labs b臋d膮cy kontynuacj膮 idei projektu FUEL – budowania 艂atwych klock贸w z kt贸rych mo偶na tworzy膰 rozszerzenia. JetPack pozwala tworzy膰 rozszerzenia korzystaj膮c wy艂膮cznie ze znajomo艣ci technologii webowych – HTML, JS, CSS.
  • Projekt Personas – rozszerzenia pozwalaj膮cego na 艂atwe zmienianie motyw贸w Firefoksa bije rekordy popularno艣ci. Nigdy nie s膮dzi艂em, 偶e co艣 mo偶e przebi膰 popularno艣膰 AdBlocka 馃槈
  • Projekt Weave rozwija Mozillowe podej艣cie do “chmury” pozwalaj膮c synchronizowa膰 swoje dane z przegl膮darki mi臋dzy komputerami, ale w spos贸b zaszyfrowany, tak, aby ten kto hostuje serwer Weave nie mia艂 dostepu do Twoich danych. W ostatniej wersji pierwsze eksperymenty z OpenID.
  • Bespin to z kolei edytor w “chmurze” – dostepny przez stron臋 WWW edytor kodu, kt贸ry pozwala pracowa膰 nad projektem w grupie ludzi, a swoje projekty mie膰 dost臋pne z ka偶dej maszyny bez potrzeby przygotowywania 艣rodowiska.
  • Kampania FastestFirefox zbiera filmiki ludzi robi膮cych to co umiej膮 najszybciej. Chcemy zebra膰 je razem i stworzy膰 kompilacj臋 ludzkich pasji zwi膮zanych z szybko艣ci膮, ci膮gle pracuj膮cych by by膰 jeszcze szybszym – tak jak spo艂eczno艣膰 pracuj膮ca nad Firefoksem pracuje, by ka偶dy kolejny Firefox by艂 szybszy.
  • Wydali艣my wersj臋 0.5 i 0.5.1 biblioteki do lokalizacji Silme. Adrian wraz z zespo艂em oraz Romi pracuj膮 teraz nad dwoma projektami korzystaj膮cymi z Silme. Projekt Adriana nazywa si臋 Koala i b臋dzie rozszerzeniem do lokalizacji do Komodo, a projekt Romiego to pr贸ba po艂膮czenia Silme z Narro.

Tak wi臋c, dzieje si臋!

Staramy si臋 jak najwi臋cej z tego przenie艣膰 do Polski, ale brakuje nam r膮k do pracy. Je艣li jeste艣 zainteresowany/a pomoc膮, to szukamy na pewno ch臋tnych do pomocy z:

  • SUMO. to strona z artyku艂ami do pomocy osobom u偶ywaj膮cym Firefoksa. GmbH (mwawoczny at aviary dot pl) ch臋tnie przyjmie pomoc 馃檪
  • Eventy. Chcemy zorganizowa膰 kilka spotka艅 na temat technologii Web w Polsce. Szukamy os贸b ch臋tnych do organizaci MozCamp贸w, lub innej formy spotka艅. Dzieje si臋 du偶o, jest o czym rozmawia膰 馃檪
  • I jak zawsze, mamy wakaty dla ch臋tnych do t艂umaczenia. szuka t艂umaczy, bo projekt贸w nam si臋 zrobi艂o co nie miara. Pami臋taj jednak, zanim wy艣lesz zg艂oszenie, t艂umaczenia to odpowiedzialna praca. A my chcemy by膰 w tym najlepsi. 馃檪
  • Z tego co wiem, nikt nie t艂umaczy – je艣li kto艣 jest zainteresowany, to z ch臋ci膮 pomog臋 z organizacj膮 tego 馃檪

main mozilla po polsku tech

Samo艣wiadomo艣膰 przegl膮darkowa – living on the edge

S膮 takie dni kiedy cz艂owiek musi spojrze膰 sobie prosto w oczy i przyzna膰 si臋, sam przed sob膮, jak u偶ywa przegl膮darek.

browser geek

taka ju偶 pewnie natura tego co robi臋, ale mam… sporo… przegl膮darek. Ile pytasz? No… jakby to…

iCab, Opera 10a, Amaya 11.1, Camino 2.0b2, Seamonkey 2.0 nightly, Flock 2.1 nightly, Firefox trunk nightly, Fennec nightly, WebKit nightly, Shiira, Arora nightly, Chromium nightly, Safari 4 alpha…Czy to normalne panie doktorze?

Co ciekawe, w艂a艣ciwe wszystkie obs艂uguj膮 nowoczesne standardy (tylko Amaya jako艣 tak inaczej聽 ;)), wszystkie s膮 szybkie rozwijaj膮 si臋 dynamicznie i ka偶da posiada jakie艣 unikalne cechy, kt贸rych nie ma inna.


Podstawow膮 przegl膮dark膮 jest dla mnie Firefox, aktualnie u偶ywam czego艣 co nazywa si臋 Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090306 Minefield/3.2a1pre ale pewnie zmieni nazw臋 w zwi膮zku z planowan膮 zmian膮 Fx 3.1 na 3.5.

Powy偶sze daje mi du偶o mi艂ych udogodnie艅 i powod贸w do dumy (jak ostatnie nowo艣ci w TraceMonkey, interfejsy do <video/>, acid3 na 94% etc.) , ale skutkiem ubocznym jest ograniczona mo偶liwo艣膰 korzystania z rozszerze艅.

To czyni mnie ma艂o aktywnym ich u偶ytkownikiem, i jak na browser geeka, plasuj臋 si臋 pewnie na do艣膰 dalekiej pozycji z moimi 4 rozszerzeniami:

  • Ubiquity – na razie to dla mnie troche jak gesty myszy. Wiem, 偶e s膮 przydatne, ale ci膮gle zapominam korzysta膰. Jak sobie przypomne, to pomaga 馃檪
  • Weave – d艂ugo u偶ywa艂em jedynie eksperymentalnie ale od powrotu do domu mam desktop i laptop (i na obu r贸偶ne systemy) wi臋c zacz膮艂em korzysta膰 masowo.
  • Firebug – zmienia spos贸b tworzenia stron
  • About:tab – najnowsze nabytek. Eksperyment w stron臋 rozwi膮za艅 z Opery, Chrome i Safari ale w po艂膮czeniu z podej艣ciem znanym z Ubiquity

Du偶o? Ma艂o? Nie wiem… oczywi艣cie wszystkie w wersji nightly.

Jednym z ciekawych efekt贸w takiego u偶ywania przegl膮darek (i nie tylko, testuje MacOS Snow Leopard, KDE4.3, Android nightly, Thunderbirda 3 nightly, Ubuntu 9.04, Windows 7…) jest to, 偶e wszystko wydaje mi si臋 stare. Kumpela u偶ywa “najnowszej” wersji? heh… Firefox 3? Heh… Ubuntu 8.10? Heh… wszystko jakie艣 takie

stare? 馃檪

Ten typ tak ma. Ale jakby kto艣 szuka艂 czego艣 do potestowania to polecam eksperyment z About:Tab.

main mozilla po polsku tech

Du偶o si臋 dzieje

Zbli偶aj膮ce si臋 wydanie Firefoksa 3.1 jest najciekawszym w mojej historii… Troszeczk臋 przypomina wydanie Fx 1.5. Stoimy na stabilnej, szybkiej nowoczesnej platformie jak膮 jest Gecko 1.9 i mo偶emy si臋 skupi膰 na tych drobnych detalach i mi艂ych dodatkach, kt贸re sprawiaj膮, 偶e korzystanie z sieci jest przyjemne.

Zatem w por贸wnaniu z ogromem zmian jakie wprowadzi艂 Fx 3.0, wersja 3.1 b臋dzie zmian膮 znacznie bardziej ewolucyjn膮 i spokojn膮, co nie znaczy, 偶e niepotrzebn膮 馃檪

Prawid艂owa obs艂uga profili kolor贸w ICC, media queries, d艂ugo oczekiwany text-shadow,聽 niezwykle wa偶na dla przysz艂o艣ci otwartego Internetu obs艂uga znacznik贸w <audio/> i <video/>, querySelector,聽 ustandaryzowany Drag&Drop, API do geolokacji, przeci膮ganie kart pomi臋dzy oknami, autotagowanie zak艂adek, znacz膮ce przyspieszenie aplikacji webowych i samego Firefoksa dzi臋ki Tracemonkey… a to tylko czubek g贸ry lodowej, zapraszam do poczytania Fx3.1 dla programist贸w, i Fx 3.1 draft plan.

Cz臋艣膰 to usprawienienia widoczne go艂ym okiem, inne dadz膮 nowe mo偶liwo艣ci autorom stron i autorom rozszerze艅, wszystkie s膮 “spokojne”. Nie wiem jak to inaczej opisa膰, ale nie ma tu wielkich, ryzykownych zmian (mo偶e poza API do pobierania zdalnych czcionek), du偶ych przeobra偶e艅 interfejsu czy ogromnych przetasowa艅 w g艂贸wnych elementach silnika.

Dwa ciekawe elementy, kt贸re spokojnie ewoluuj膮 w Fx3.1 to obs艂uga standard贸w i dodatkowe interfejsy do zarz膮dzania sesjami i prywatno艣ci膮 sesji. I to z tym zwi膮zane s膮 dwa poni偶sze screeny:

Session restore updated
Session restore updated
Acid 3 w fx3.1 nightly
Acid 3 w fx3.1 nightly

Pierwszy pokazuje nowe mo偶liwo艣ci podczas przywracania sesji, drugi to aktualizacja stanu ACID3 w Firefoksie. Te 93% to to co ju偶 wyl膮dowa艂o w g艂贸wnym repozytorium, bo istniej膮 te偶 patche poprawiaj膮ce wszystkie pozosta艂e b艂臋dy, ale nie zosta艂y jeszcze w艂膮czone do g艂贸wnej ga艂臋zi. Z tego co pisa艂 Dbaron, prawdopodobnie na wydanie Fx3.1 uda si臋 podnie艣膰 to do 98%.

Czemu nie 100%? Nie ma powodu do po艣piechu. Acid3, jak ju偶 wielokrotnie pisa艂o wiele os贸b, jest testem do艣膰 “abstrakcyjnym” w tym sensie, 偶e nie testuje najpopularniejszych element贸w standard贸w, tylko w艂a艣nie te, kt贸re nie dzia艂aj膮 np. w Fx. Spe艂nienie wymaga艅 testu ma sens tylko w贸wczas gdy jest elementem prac nad og贸lnym poprawieniem obs艂ugi standard贸w, a nie gdy jest sztucznym pompowaniem zmian, aby tylko zapewni膰 sobie “setk臋” w jakim艣 testowym buildzie, kt贸ry nigdy nie zostanie wydany i wywala si臋 na wszystkim poza testem Acid 3.

To oczywi艣cie nie wszystko, uwa偶ni obsewatorzy planety Mozilli z pewno艣ci膮 zauwa偶yli prac臋 ekipy od Ux nad poprawkami u偶yteczno艣ci, nie wspominaj膮c ju偶 o setkach poprawionych b艂臋d贸w.

W tym samym czasie grupa z labs pracuje nad nowymi wersjami Ubiquity, Weave czy Prism, Mozilla Messaging eksperymentuje z UI i pracuje nad wydaniem Thunderbirda 3, a zesp贸艂 z Mozilla Mobile szykuje si臋 na wydanie Fenneca 1.0.

Ach, zapomnia艂bym, 偶e tak偶e teraz, inna grupa, pod wodz膮 Brendana Eicha, pracuje nad Mozill膮 2 – now膮 wersj膮 platformy, kt贸ra wprowadzi naprawde ogromne zmiany w funkcjonowanie Gecko, a w艣r贸d zakresu prac Gecko 2.0 pojawiaj膮 si臋 takie rzeczy jak wsparcie dla animacji 3D – SVG, Canvas 3D, nowy standard lokalizacji – L20n, instalacja rozszerze艅 bez restartu, Compositor – nowy system prezentacji uk艂adu strony i wiele innych…

Je艣li jednak tego jest Ci ma艂o, masz poczucie niedosytu, albo uznajesz, 偶e Mozilla to co艣 wi臋cej ni偶 grupa programist贸w i ich kod, to… masz absolutn膮 racj臋 Mozilla Foundation oraz Mozilla Europe pracuj膮 nad projektem o nazwie “2010 Goals“, kt贸ry ma za zadanie zdefiniowa膰 rol臋 Mozilli jako aktywatora i uczestnika dyskusji na temat rozwoju Internetu w takich dziedzinach jak edukacja, dost臋p w najgorzej zinformatyzowanych regionach 艣wiata, czy otwieranie rynku mobilnego tak jak zrobili艣my to z WWW dzi臋ki Firefoksowi.

Je艣li masz ochot臋 co艣 porobi膰, rozwija膰 si臋 pomagaj膮c w realizacji naszej misji, to otwieramy w艂a艣nie dla Ciebie nowy portal –, kt贸ry ma na celu pom贸c Ci odnale藕膰 si臋 na pocz膮tku swojej przygody z Mozill膮. Du偶o si臋 dzieje i jest mn贸stwo miejsca dla Ciebie 馃檪

mozilla tech

[RFC] Mozilla Community Theme

We’re listening to you and we’re excited about your ideas 馃檪

Some time ago, Sta艣 and Seth started a survey program to get an idea on what You feel about Mozilla. And in the very first survey they led, the very most commonly requested support from Mozilla was to provide Mozilla website template for community sites.

We were not surprised to see this in the survey results because it has been something that many of us have been considering a long time.聽 How could we find creative ways to support all of our Mozilla contributors?聽 How can we make life easier for everyone?聽 We have all levels of communities, from large to small and new to old.聽 Many do not have all the resources needed to create this on their own.

That’s exactly how Mozilla Community Sites project started. We’re going to work on customization of several commonly used community webtools to make it easy to set up and deploy a website for your community. If a contributor community chooses to use the tools provided, they can get a site up and running that looks like a Mozilla Community project website, with several features built in specific that do not requiring mastering PHP/MySQL etc. (but if you want, feel free to support us with your skills :)).

The tool presents several commonly used webtools like Drupal, WordPress, phpBB/punBB, PlanetPlanet etc. and prepare them to be ready to start in the Mozilla community environment. We’re planning to offer two kinds of websites:

  • powerful and highly customizable website using Drupal CMS
  • smaller, easier to deploy and less interactive based on WordPress.

We want these sites to easily feed from Mozilla Developer Center, SUMO, QMO and list latest stable releases in your language.

We also intend to use Single Sign On, OpenID, and other features to improve integration.

One featured below is a much requested Mozilla Community Theme.

From the survey, we gathered that people wanted a theme that clearly indicated that websie was part of the Mozilla Project, while at the same time not an effort from the Mozilla Corporation or Foundation.

We worked with designers to help us create something that had a feel somewhere close to the Corporation and Foundation sites, but still unique and different.

And today, I’d like to present you the draft and ask for you feedback on it!

Below is the screenshot of how the website could look like.

Main Community Website 2
Main Community Website Draft
Main Community Website 3
Main Community Website Draft
Main Community Website 4
Main Community Website Draft

The content presented on the screenshots above is of course just an example. Website maintainer will decide what to present there.

Also, the theme is not obligatory to anyone. It’ll be just an option you can use while preparing your website. We appreciate and respect how our communities are independent.

We will also provide you a special Guidelines that will help you customize the template according to your needs (changing colors – green, orange, blue etc., backgrounds, etc.). These guidelines are intended to make it easier to modify the template if you want to skin another webtool from outside of our list with this theme while still maintaining quality.

Just to be clear, with this tool you will be able to select the following:

  • components you want to display (top header, header bar, left, right panels, etc.).
  • colors to use (Guidelines will provide a list of color pallets that fits the theme well)
  • ideas to put in the background (maybe something specific to your community – Eiffel tower in the header background?)
  • community logo.

We will suggest you to follow those Guidelines, but if you want to go beyond, feel free!

Oh, and… the theme will be, of course, open sourced 馃檪

So, now, that we spent some time with designers on this, we need your feedback before going any further. We need to know what you think, would it fit your community if you lead one, which kind of community does this mockup fit, what could be improved to fit others, what can we do better and what is missing. It’s especially crucial to find out what’s missing to make sure it’ll be covered with the final version. Please, focus on clear, productive feedback. Thanks! 馃檪