Mozilla brengt Firefox Developer Edition uit
Mozilla heeft een speciaal op webdevelopers gerichte versie van Firefox uitgebracht. De aangepaste browser bevat diverse tools die ontwikkelaars gebruiken om websites en webapps te ontwikkelen. Mozilla belooft de Firefox Developer Edition te blijven ...
The Content Services team is working to reframe how users are understood on the Internet: how content is presented to them, how they can signal what they are interested in, how they can take control of the kinds of adverts they are exposed to. As the Web evolves, these signals will be generated in two places by two actors: in the user’s client, at the user’s behest, or in the cloud, by a service or by a third party who seeks to know whatever it can about the user. We believe it is Mozilla’s place to ensure that the client empowers the user in this relationship and over time, think about how the cloud can play a role.
We’ve been working on an experimental feature that we think is super cool – which we’re calling the “Interest Dashboard” and today, we’ve releasing it as an experimental beta Firefox add-on. The team here is excited about the Interest Dashboard as it explores the advancement of content and the browser. The project has been led under the Product Management of Kevin Ghim and engineering leadership of Ed Lee in the Content Services team. The goal is to see how people consume the Web and try and classify it, and we have something we want to get testing and feedback on with this beta add-on..
How does it work?
You can download the experimental beta Interest Dashboard add-on here.
We believe that there are lots of ways that this add-on can benefit users – from new content discovery, to helping the user manage their own browsing behavior.
The ability to see how that time is spent, on which interests, and at what frequency and volume, will be fascinating for many users. Users will see how their content consumption is categorized and provide feedback directly into the Interest Dashboard. Ultimately, we can then start showing the user a more personalized content experience, on the user’s terms.
We also know that we have a lot of challenges ahead of us. We’d absolutely love your feedback after playing around with the add-on so please leave feedback in Bugzilla or in the comments section of this post. This is a foundational piece for for what we’re doing and we have to deliver value for ours users before we build on top of this.
There’s a lot of data science behind the classification system and we’re looking to make it better. he feature presents you with a number of views of your data and actions, but we want to know what you would find interesting.
The Interest Dashboard shows the user their activity and lets them gain insight from it – “what gets measured, gets managed”. In our case, the user of the Interest Dashboard will see all of the user’s browsing behavior and display it in a way the user can interact with. And if you use multiple instances of Firefox, across multiple desktops, or Firefox for Android, and you have connected all instances to a Firefox Account, you will see your data from all your browsing.
The Firefox Interest Dashboard add-on is unique in bringing this functionality directly to the user in their client, under their control. And unlike recommendation engines, the Firefox Interest Dashboard add-on will not be trying to stimulate you to remain engaged with a particular website, it will be a vehicle to allow the user to consciously express their own desires for what they want to browser to do.
So go download the Interest Dashboard add-on and see how much time each month you’re spending on watching kittens or funny videos.
Note: Most of the enhanced tiles changes landed during the 33 cycle. This explains why most of them does not show on this page.
- 65 changesets
- 119 files changed
- 2286 insertions
- 374 deletions
ExtensionOccurrences js18 cpp15 jsm11 h9 java7 css7 mn4 in4 c4 xml3 txt3 ini2 cc2 build2 xul1 sh1 inc1 dep1
ModuleOccurrences browser29 toolkit14 mobile14 security11 gfx11 netwerk6 widget4 media3 modules1 dom1 config1
List of changesets:Simone Bruno email@example.comBug 1058286 - Add in-tree manifests needed for tests. DONTBUILD a=NPOTB - 3f092c058c62 Ed Lee firstname.lastname@example.orgBug 1082051 - Enable enhanced tiles for desired locales on 33. r=ttaubert, a=sledru - 7dc8f5f9ad9e Ed Lee email@example.comBug 1081157 - "What is this page" link appears on "blank" version of about:newtab. r=ttaubert, a=sledru - d69a0e8a853d Nicolas Silva firstname.lastname@example.orgBug 1083071 - Add some old intel drivers to the blocklist. r=Bas a=sledru - d96967b7f22a Nicolas Silva email@example.comBug 1044975 - Don't crash if mapping D3D11 shader constant buffers fails. r=Bas a=sledru - 946f61c00aa0 Bas Schouten firstname.lastname@example.orgBug 1026893 - "crash in @0x0 | CContext::ID3D11DeviceContext1SetSamplers(ID3D11DeviceContext1, unsigned int, unsigned int, ID3D11SamplerState const*)". r=jmuizelaar a=sledru - b9e31f93e53c Nicolas Silva email@example.comBug 1083071 - Blacklist device family IntelGMAX4500HD drivers older than 7-19-2011 because of OMTC issues on Windows. r=Bas, a=sledru - b4f691bf543e Ryan VanderMeulen firstname.lastname@example.orgBug 1083071 - Change accidentally-used periods to commas. rs=nical, a=bustage - fc031fd29ac3 Ed Lee email@example.comBug 1075620 - Switch to GET for fetch to allow caching of links data from redirect. r=ttaubert, a=sledru - a7f2d0803533 Randell Jesup firstname.lastname@example.orgBug 1075640 - Don't return 0-length frames for decoding; add comments about loss handling. r=ehugg, a=sledru - be43cc1b2373 Ethan Hugg email@example.comBug 1075640 - Check for zero length frames in GMP H264 decode. r=jesup, a=sledru - 45dd53a5354b Irving Reid firstname.lastname@example.orgBug 1059674 - Use AsynchShutdown.blocker() for AddonManager provider shutdown. r=Unfocused, r=Yoric, r=Mossop, a=sledru - bda37eb8a921 Irving Reid email@example.comBug 1074135 - Callback after exceptions when calling async provider methods. r=Unfocused, r=Mossop, a=sledru - b3ce9237bb9a Irving Reid firstname.lastname@example.orgBug 1081702 - Check that callback parameters are defined before pushing onto result arrays. r=Mossop, a=sledru - f7b82b004588 Nicolas Silva email@example.comBug 1083071 - Backout the additional blacklist entries. r=jmuizelaar, a=sledru - e890ed642ccc Jeff Muizelaar firstname.lastname@example.orgBug 1083071. Disable D3D11 and D3D9 layers on broken drivers. r=bjacob, a=sledru - 1b2b105a4c54 Ryan VanderMeulen email@example.comBacked out changeset 1b2b105a4c54 (Bug 1083071) for Win7 mochitest-1 failures. - 77e045dd0f7c Jeff Muizelaar firstname.lastname@example.orgBug 1083071 - Disable D3D11 and D3D9 layers on broken drivers. r=bjacob, a=sledru - 3fdbf5e789d0 Benoit Jacob email@example.comBug 1083071 - Avoid touching D3D11 at all, even to test if it works, if D3D11 layers are blacklisted. r=Bas, r=jmuizelaar, a=sledru - e4f020cdef25 Ed Lee firstname.lastname@example.orgBug 1088729 - Only allow http(s) directory links. r=adw, a=sledru - 137b543a1ec4 Benoit Jacob email@example.comBug 1089413 - Only test resource sharing on d3d feature level >= 10. r=jmuizelaar, a=sledru - 9a8dc41a653e Justin Wood Callek@gmail.comNo Bug - Dummy commit to trigger jobs. r=robots a=people approved for CLOSED TREE by aliens. - bfeaec35449a Justin Wood Callek@gmail.comNo Bug - Dummy commit to trigger jobs. r=robots a=people approved for CLOSED TREE by aliens. - 0f740e9b92d5 Justin Wood Callek@gmail.comNo Bug - Dummy commit to trigger jobs. r=robots a=people approved for CLOSED TREE by aliens. - 506dbb9cb1c8 Justin Dolske firstname.lastname@example.orgMerge releases/mozilla-release and alder - 8a69f66b4e31 Justin Dolske email@example.comBug 1068290 - UI Tour: Add ability to highlight New Private Window icon in chrome. r=mattn - ea602704377d Justin Dolske firstname.lastname@example.orgBug 1072036 - UI Tour: Add ability to highlight new privacy button. r=mattn - 62fee88552f8 Justin Dolske email@example.comBug 1071238 - UI Tour: add ability to put a widget in the toolbar. r=mattn - f4c017d24f92 Blair McBride firstname.lastname@example.orgBug 1068284 - UI Tour: Add ability to highlight search provider in search menu. r=MattN - 4dc2af2e837c Gijs Kruitbosch email@example.comBug 1069300 - add a privacy/forget/panic button (includes fix for Bug 1074498), r=jaws, a=dolske - aea178b2ec0c Gijs Kruitbosch firstname.lastname@example.orgBug 1079869 - Fix closing forget panel by adding a closemenu=none attribute. r=jaws, a=sledru - 0de8444b8da0 Gijs Kruitbosch email@example.comBug 1077404 - subviewradio elements in panic button panel are elliptical and labels get borders, r=jaws - cc67ff387243 Justin Dolske firstname.lastname@example.orgBug 1076943 - forget icon has white border (non-transparent background). r=jaws a=dolske - 36221eb238be Gijs Kruitbosch email@example.comBug 1073607 - add magical pref system for panic button, r=jaws, a=dolske - 1599c644f54f Chris AtLee firstname.lastname@example.orgBug 1083853: adjust expected keys used for nightly-alder r=bhearsum - a752028423fd Justin Dolske email@example.comMerge releases/mozilla-release and alder - 3f594a5bacfc Justin Dolske firstname.lastname@example.orgBug 1088137 - Forget button can fail to clear cookies by running sanitizer too early. r=MattN - 860d5a053b5f Mark Hammond email@example.comBug 1077643 - Enable WhatsNew page in-product for 33.X anniversary - 1d7405a097b1 Justin Dolske firstname.lastname@example.orgBug 1089421 - Forget button should call more attention to it closing all tabs/windows. r=gijs, ui-r=phlsa - e0d4cbcae717 Gijs Kruitbosch email@example.comBug 1074520 - Use CSS instead of hacks to make the forget button lay out correctly. r=jaws, a=lmandel,dolske - c55d0a927772 Gijs Kruitbosch firstname.lastname@example.orgBug 1079222 - deny fullscreen from the forget button, r=dolske, a=dolske - 914bed88291e Justin Dolske email@example.comBug 1085330 - UITour: Highlight positioning breaks when icon target moves into "more tools" overflow panel. r=Unfocused - 48f2446e0b8b Gavin Sharp firstname.lastname@example.orgBug 1061736: add DuckDuckGo as a search engine option in Firefox. r=dolske - 0746f89a5aee Justin Dolske email@example.comBug 1077643 - followup to disable test that's now expected to fail. - 3e492d503e8d Justin Dolske firstname.lastname@example.orgMerge releases/mozilla-release and alder a=merge - 766b4b4fa7c7 Kai Engert email@example.comBug 1049435 - importing an RSA private key fails if p < q, upgrade to NSS 3.17.2, r=wtc, a=sledru - 8c16b644aaa7 Kai Engert Bug 1042889 - Cannot override secerrorcacertinvalid. r=dkeeler, a=sledru - efd4bca5ac0d Benoit Jacob firstname.lastname@example.orgBug 1088858 - Backport ANGLE fixes to make WebGL work on Windows in Firefox 33. r=jmuizelaar, a=sledru - d49ad0a834a8 Patrick McManus email@example.comBug 1088850 - Disable http/1 framing enforcement from Bug 237623. r=bagder, a=sledru - b4f797f3cd52 David Rajchenbach-Teller firstname.lastname@example.orgBug 1087674 - Handle XHR abort()/timeout and certificate errors more gracefully in GMPInstallmanager. r=gfritzsche, a=sledru - 0de6e2b5507a Richard Newman email@example.comBug 1090385 - More robust handling of external intents. r=snorp, a=sledru - 2c6590150a85 Richard Newman firstname.lastname@example.orgBug 1090385 - Follow-up: fix GeckoAppShell. a=bustage - f8bdafd5fac5 Richard Newman email@example.comBug 1090385 - Follow-up: fix GeckoApp. a=bustage - 13b6fd9ab7a1 Richard Newman firstname.lastname@example.orgBug 1090385 - Follow-up: fix yet more bustage in GeckoApp. a=bustage - 1316d20c2270 Bas Schouten email@example.comBug 1064864. Ensure the copying bounds are sane. r=jrmuizel a=sylvestre - 6e6d4a8dc162 Jonathan Watt firstname.lastname@example.orgBug 1076910 - Don't use gfxPlatform::GetPlatform() off the main thread. r=Bas, a=sledru - aa636b6addb1 Jonathan Watt email@example.comBug 1076910 - Add some error checks to gfxUtils::EncodeSourceSurface. r=Bas, a=sledru - 75c2f18b0020 Mark Finkle firstname.lastname@example.orgBug 883254 - Add the duckduckgo searchplugin. r=margaret, a=lmandel - 6233fa4970a4 Nick Alexander email@example.comBug 883254 - Add the duckduckgo searchplugin to certain locales. f=glandium, r=mfinkle, a=lmandel - 9b6e72bafd64 Nicolas Silva firstname.lastname@example.orgBug 1064107 - Ensure that gfxPlatform is initialized by the time we create the compositor. r=Bas, a=sledru - 204173cef30b Bas Schouten email@example.comBug 1093694 - Don't allow any graphics features when there's a driver version mismatch. r=jrmuizel, a=sledru - e1414483567c Benoit Jacob firstname.lastname@example.orgBug 1021265 - Regard d3d11 as broken with displaylink on versions <= 18.104.22.168484, and fall back to basic layers. r=jrmuizel, a=sledru - 7496596b3075 Benoit Jacob email@example.comBug 1093863 - Blacklist D3D on dual Intel/AMD not advertised as such in the registry. r=jrmuizel, a=lmandel - 8296918e9bdb Nick Alexander firstname.lastname@example.orgBug 883254 - Follow-up to add extra new line in JAR manifest. r=mfinkle, a=sledru - ff5068a4aa0c Nicolas SilvaBug 1089183 - Blacklist D2D on a range of ATI drivers that don't handle dxgi keyed mutex properly. r=bjacob, a=sledru - 818480839115
Mozilla voegt vergeetknop toe aan Firefox
Mozilla heeft Firefox-versie 33.1 gelanceerd. De update voegt een vergeetknop toe aan de webbrowser toe, waarmee je gemakkelijker dan voorheen je geschiedenis kunt wissen. Wanneer je op de vergeetknop drukt, worden je geschiedenis en cookies van ...
Nieuwe Firefox met vergeetknop en DuckDuckGo gelanceerdSecurity.nl
alle 2 nieuwsartikelen »
Mozilla haalt uit naar Android en iOS
De Mozilla-cto claimt dat dit komt door het gebrek aan transparantie, veroorzaakt door het propriëtaire karakter van beide besturingssystemen. Daarbij doelt hij in het geval van Android op de diverse Google-apps die niet opensource zijn, maar standaard ...
Mozilla Privacy Blog: Introducing Polaris Privacy Initiative to Accelerate User-focused Privacy Online
Today we are celebrating the 10th anniversary of Firefox and as a birthday present have lots of exciting new technologies for developers to try out.
Over the last 10 years Mozilla didn’t just build Firefox, we also helped build much of the Web that users experience today through Firefox and other browsers.
The Mozilla Project was created to wrestle control over the Web from Microsoft. Through its then dominant 98% browser market share with Internet Explorer 6, Microsoft had almost total control over the evolution of the Web. Mozilla didn’t tackle this situation merely through advocacy–telling the world why it is bad if a single corporation has disproportionate control over an ecosystem as important and central to our lives as the Web. Instead, we went to work to create a better, more powerful Web and a better, more powerful browser: Firefox. The competition and innovation Firefox brought to the Web has dramatically changed the open Web and browser landscape over the last 10 years.
Today, no single browser vendor has the same dominant market share Microsoft had. Users can choose from a number of browsers made by Microsoft, Google, Apple and of course Mozilla. The competition in the browser space is one of the clearest signs of the success of our mission over the last 10 years.
At Mozilla we don’t just build a consumer browser, we also build the Web itself. To overcome proprietary ecosystems the Web has to match or exceed the capabilities and performance of native platforms. Over the last 10 years we have pioneered many new Web technologies, and contributed to standardizing them.
Advancing Audio and Video
Audio and Video on the Web are also making big leaps forward with the help of Mozilla. We are one of the leading proponents of WebRTC, a new Web API for real-time communication via audio, video and data channels. Together with our long time partner Telefonica, we are bringing Firefox Hello, a WebRTC-based audio/video chat feature to Firefox soon. Firefox Hello allows people to communicate in real time without the need to download software or create an account.
Building out the Web
Our volunteer community continues to have a big role in advancing Firefox and the Web. Andre Natal from our Brazilian community has been contributing speech recognition functionality to Firefox and Firefox OS. This will allow users to interact with their desktop browsers as well as Firefox OS devices by simply using their voice. This Web Speech API is currently being added to our rendering engine Gecko.
Firefox Developer Edition
If you are a Web developer and excited to try out some of the technologies above, we have something special for you in celebration of our 10th anniversary. While we build the Web, it is developers who build the content and experiences the Web enables. In recognition of their efforts and our ongoing commitment to the Web developer community we are releasing a dedicated Firefox Developer Edition, made specifically for Web developers with many features that developers want enabled by default. The developer edition streamlines development workflow and adds new features that simplify the process of building for the entire Web, whether targeting mobile or desktop across many different platforms.
What the Future Holds
10 years ago, Mozilla started a long journey to set the Web free of Microsoft’s proprietary control, and today we have largely achieved that goal. The next phase of the struggle for an open Web is mobile where a new duopoly has arisen: iOS and Android. Just as we took on Microsoft 10 years ago with Firefox, we are looking to unseat Google’s and Apple’s dominance over the mobile space by creating a new smartphone OS that is built of the Web: Firefox OS. Since its launch last year Firefox OS has now spread to 24 countries all over the world, including our most recent launch in India. If you are using our Firefox OS developer phone, we are releasing a new developer build of Firefox OS 2.0 today.
We are also advancing the fundamental technologies of the Web through Servo and Rust. Servo is a new rendering engine for the next generation Web with advanced support for parallelism as well as improved security and reliability. We are able to accomplish this thanks to Rust, a new systems programming language which we have been building and which is gaining strong community support.
And, we have also started to explore the next frontier of the Web: Virtual Reality. We are pioneering new capabilities for VR on the Web and we are launching mozvr.com as a platform for technology demos and a place for developers to learn about how to bring VR experiences to the Web.
Filed under: Mozilla
My technical world changed a bit recently with a few events that directly impacted me or the activities of my company, Disruptive Innovations:
- Mozilla shows increasing signals that the future of XUL as a platform for embedders like my company is not bright. XULRunner has many users around the world but it's not part of the roadmap any more, unfortunately. I won't discuss here their corporate strategy. My applications BlueGriffon and BlueGriffon EPUB Edition being based on XULRunner and my business being largely based on them, it would be a bit foolish to avoid looking for an alternative...
- the two only potential solutions, Qt on one hand and AdobeAir on the other, do not satisfy me for the following reasons:
- Adobe Air is nothing near native,
- Qt is a big and powerful beast, hard to learn and master.
- Apple's Swift looks nice and powerful but cross-platform is not a word available in the Apple ecosystem.
- I have discovered Haxe. Haxe is an open source toolkit based on a modern, high level, strictly typed programming language, a cross-compiler, a complete cross-platform standard library and ways to access each platform's native capabilities. If you know ECMAScript and/or Java, you'll find Haxe fun and easy to master. I started playing with it and fell in love with its beauty, simplicity, and the large numbers of packages available.
In such cases, I take a few sheets of paper and start writing ideas. I have put a lot of ink on a dozen of originally blank pages and tested a few designs. I want, I need a very simple, flat learning curve way of writing standalone cross-platform native apps. And if the existing ecosystem can't give me such a tool, well, I do what I always do in such cases: I write my own... So I started writing my own environment for native desktop and mobile applications.
My requirements were the following ones:
- all UI specified in html5, of course, with the help of role attributes... Maybe I'll add a XUL-like language too just for migration purposes.
- UI styled by CSS, eh what did you expect?
- resulting native UI
- code in Haxe of course compiled to native!!! Assets not trivially readable like with JS...
- trivial embedding of Haxe-based gaming frameworks
- trivial embedding of a browser instance (Blink, Servo, etc...). When I say trivial, I really mean it. If you've played with CEF, you probably understand that this is not what I mean.
- no ugly hacks to deal with OSX menus or Windows icons.
- dynamic UI changes based on DOM manipulation just like in XUL
- very simple localization
- a "Hello world" button in a native window should be a one-minute thing. No big environment to install, no complex setup, no new IDE to learn. You know html5? Just put a <button> inside a new document's <body> in your favorite code editor, open a terminal and type "quaxebuild". Done, you have a native app in hands, ready for distribution.
The result will be Quaxe. Native desktop and mobile applications with native UI from html5 and Haxe.
I am glad to share with you the first demo screenshot below. The app was launched through a open bin/mac/MyFirstTest.app command line on OSX. Just to be very clear, there is NO BROWSER WINDOW in the screenshot below. The app is only a native resizable main frame containing a native button. It's specified in html5, you can access and modify its DOM but it's not your regular browser, there is no Blink, Gecko, Servo or any Web rendering engine inside. There is no common runtime either, à la Adobe Air. It's very, very lightweight despite of having to implement a xml parser, DOM4, a CSS parser, the whole CSS cascade and an OM for the widgetry.
As you can see above, it's already taking shape. If you're an investor and you're interested, please do not hesitate to contact me at your convenience. Writing native apps is going to be way cooler and simpler than it is now, that's a promise.
Last month I passed four years at Mozilla. At the time I joined there was a large influx into Mozilla Corporation as it went on a hiring spree, increasing the number of employees greatly.
For many years at Mozilla I had my head down, focused on delivering code and deadlines. Driven by my own imposter syndrome, I aimed to be as productive as possible. Hammering out code on Addons and then the Marketplace.
These days that feels less and less like a valuable role for me.
A few weeks ago I was looking at a chart in Mozillas intranet that shows how long you've been at Mozilla. For me it looks like this:
All it really means is that I'm old and I've been at Mozilla a while. Length of time at Mozilla doesn't really mean a whole lot, beyond that. What it did make me realise is that those group of employees who joined with me are becoming the elders of Mozilla. More than ever, we shape how Mozilla Corporation operates and help the culture.
It feels like I need to take on more responsibility for Mozilla and the way it operates. For example:
- making sure Mozilla takes the right direction
- calling out when Mozilla makes a mistake internally
- helping out when Mozilla does something wrong externally
- worrying about the mission and ensuring that we do things that focus on the mission
- ensuring people at Mozilla (including myself) are good to each other
I've seen these things be corrected within Mozilla, not by managers, but by the other employees who care about the organisation.
I've done that some times, but really not enough. Its easier to focus on some of lines of code, solve a problem and repeat. Now its time to put my head above the parapet more and take some shots.
We are the elders of Mozilla, time to start acting like it.
If this is on planet.mozilla.org, and so is a “content is password protected” post below it, I’m sorry.
The post is merely that way because its unfinished but I wanted to share it with a few others for early feedback.
I’ll delete this post, and unhide that one once things are ready. (Sorry for any confusion)
Ten years ago, tonight, this is what I was working on.
2-7pm PST, 22:00-03:00 GMT. That’s 22:00-03:00 on Tuesday night in Germany. In Japan, that’s 07:00-12:00 Wednesday morning.
Live webcast + text chat with key Mozilla people.
Yep, not only is it the 10 year anniversary of Firefox, it’s also 10 years since the inaugural Air Mozilla “broadcast”.
We’ve come a long way. So much more still to do :D
Oh hey, here’s another belated post from Sole! But at least it didn’t take me a full whole year to write ^_^
We hosted the first ever Firefox OS Bug Squash Party at Mozilla London (also known as MozLDN) last week, thanks to the initiative of Francisco and Guillaume that mostly brainstormed it all with support from Valentin Schmitt.
Francisco asked me on Friday to intro the event, and run through the basic security guidelines etc as I had done that before for other events that I had hosted at MozLDN (like ladieswhocode).
That was a great opportunity to show GIFs so I accepted enthusiastically!
Since this was going to be a somewhat long event we wanted to make sure no one misbehaved, so I made it VERY CLEAR what was right and what was wrong. I not only mentioned we had a code of conduct but also read it aloud (as it was reasonably short) and gave very explicit examples of “what NOT to do”. Then I also added it to the top of the etherpad we were using to coordinate and share content, so that even late comers could be aware of the “house rules”.
I’m particularly happy with how the code of conduct ended up looking so here is it—feel free to copy and use it in your own events:
***CODE OF CONDUCT***
Don’t be a jerk
This is a safe space
We’re here to learn and help each other
– Feel free to ask any questions
– No question is too silly
– Respect other people’s questions
– Respect other people’s background
– Don’t make assumptions—always ask
– If someone asks you to stop doing something… stop doing it!
– Sexist, racist, offensive comments/jokes/imagery
– Harassment of ANY kind
We’re building a community together
Good communities are made of diverse people
Anyone violating these rules will be sanctioned or expelled at our discretion
After going through the schedule it was time for Francisco’s epic Setting up the development environment session which was a good challenge for the WiFi network (Gaia is a huge project) and for those of us not familiar with Windows computers. Argh! (details are left to the imagination of the reader).
— GIF comedian (@supersole) November 1, 2014
Despite that we got pretty much everyone set up and ready to go just in time for lunch, so we decided to stop for lunch and continue afterwards with Guillaume’s session on how to run and debug Firefox OS apps using WebIDE.
— GIF comedian (@supersole) November 1, 2014
Wilson was also around and he brought this weird device hacked to be able to “DIY Dual SIM”:
DIY dual SIM phone pic.twitter.com/sobUJF2ThV
— GIF comedian (@supersole) November 1, 2014
(I think it was a Cloud FX phone?)
Also about that time Wilson got in touch with Leo, another Mozillian, who knew how to operate the A/V equipment and between my limited knowledge and Leo’s remote wisdom we managed to connect to the Mozilla Paris office, who were holding a similar event at the same time!
— GIF comedian (@supersole) November 1, 2014
Our space seemed a tad busier than theirs (we had ~35 people I think), so we joked a bit about that, but despite Paris having less people they ended up submitting more patches, teeheehee! So Dietrich named this Firefox OS Co-opetition! But I’m anticipating events…
The rest of Saturday was spent getting familiar with Gaia code, squashing more bugs, etc. At some point the first patches were ready, and Francisco took to the stage again to show how the process for code reviewing a patch worked, also how to run tests, ensure the patch actually fixes what it is meant to fix, etc.
— GIF comedian (@supersole) November 1, 2014
There was pizza a bit after that, and everyone was done for the day.Sunday
We weren’t too sure as to how many people would show up on Sunday but we still got a sizeable amount of attendees! There were more patches sent and bugs squashed. And also two presentations:
Marcia Knous explained how the QA process worked:
— GIF comedian (@supersole) November 2, 2014
And Zac spoke about automated tests:
— GIF comedian (@supersole) November 2, 2014
This slide was really cool: Best practices for reporting Firefox OS bugs!
— GIF comedian (@supersole) November 2, 2014
Transcribing it for easier referencing:
Bugzilla Best Practices
Typically included in a Bug report:
– Build ID and Base version used
– ADB Logcat while issue has been reproduced
– Video of the issue if it helps illustrate the problem
– Screenshot of the issue if it helps illustrate the problem
– Is the issue 100% reproducible?
For being our first Bug Squash Party, it went way smoother than we expected! It was a really nice continuation to MozFest–there were at least two attendees who joined the party because they had got a Flame at MozFest.
Setting up the dev environment was the longest part and it was a bit of a tedious bore–I wonder what can be done to simplify that–, but once that part was done, it was quite easy for people to get started since they were web developers already.
My personal opinion is that the explicitness with the Code of Conduct worked quite well, and I can say this with confidence because pretty much everyone behaved really well and respectfully, whereas some people that came afterwards and hadn’t been through our house rules behaved in ways that could have been “better”. From being politer with us to treating the rest of attendees with a bit more of respect.
We were also thinking that perhaps we should not let latecomers in, as they made us stop and start from the beginning to bring them up to speed, this being more of a workshop than a conference.
Finally, I’m sad to report that two of the test phones that we generously lent to attendees went missing. Maybe we’ll have to be less generous and trusting and ask for a proof of ID to be left with us in exchange for testing hardware. I would like to stress the point that these phones are work tools and stealing them prevents people from doing their work, and you should feel super bad for doing so, whomever you were.
Its been a while since I last blogged about “remoties”, but it continues to be a very popular topic! In addition to Twilio in February, I’ve given presentations at Automattic (best known for WordPress), RiotGames (twice) and Haas, UCBerkeley (twice), as well as smaller private discussions with several other companies.
You can get the slides in PDF format by clicking on the thumbnail of the first slide. (I’m happy to share the original very large keynote file, just let me know and we’ll figure out a way to share without hammering my poor website.)
Remoties are clearly something that people care deeply about. Geo-distributed teams are becoming more commonplace, and yet the challenges continue to be very real. The interest before each presentation is cautiously high, while the Q+A discussions during/afterwards are very engaged and lively. Every time, I find myself tweaking, honing and refining the presentation again and again… yet, the core principles remain the same:
- remoties / geo-distributed teams can be very effective, and can be sustained over time.
- remoties != compromise. In fact, a geo-distributed team means you can hire best-available, not “just” best-willing-to-relocate.
- easy to use, cheap, technologies work just fine if used correctly (maybe even better then expensive systems?)
- crisp, careful organization of human processes is essential
- in a geo-distributed team, *everyone* is a remotie, even people who happen to sit in an office. If you are remote from someone else, that makes you *both* remoties. Hence the working title “we are ALL remoties”.
Given how this topic impacts people’s jobs, and their lives, I’m not surprised by the passionate responses, and each time, the lively discussions encourage me to keep talking about this. As always, if you have any questions, suggestions or good/bad stories about working in a remote or geo-distributed teams, please let me know – I’d love to hear them.
ps: I noticed in my website logs that a lot of people were still downloading my original remoties slides, first posted in apr2012, even though I’d posted multiple revisions of the slides since. So, I’ve gone back and updated my earlier “remoties” blog posts to all point to these latest-and-greatest slides.