Slashdot Mirror


Mozilla Announces Enterprise User Working Group

Lennie sends this quote from an announcement at the Mozilla blog: "Recently there has been a lot of discussion about enterprises and rapid releases. Online life is evolving faster than ever and it's imperative that Mozilla deliver improvements to the Web and to Firefox more quickly to reflect this. This has created challenges for IT departments that have to deliver lots of mission-critical applications through Firefox. Mozilla is fundamentally about people and we care about our users wherever they are. To this end, we are re-establishing a Mozilla Enterprise User Working Group as a place for enterprise developers, IT staff and Firefox developers to discuss the challenges, ideas and best practices for deploying Firefox in the enterprise."

14 of 156 comments (clear)

  1. LOL by Anonymous Coward · · Score: 3, Insightful
    1. Re:LOL by jojoba_oil · · Score: 4, Insightful

      Enterprise has never been (and I'll argue, shouldn't be) a focus of ours

      I wonder if that guy is still the community coordinator for marketing...

    2. Re:LOL by asa · · Score: 3, Informative

      "I wonder if that guy is still the community coordinator for marketing..."

      I'm not. I haven't been involved heavily in marketing since a year or so after I co-founded SpreadFirefox back in 2004. I'm currently the Director of the Firefox Desktop product.

      - A

  2. participants? by rbrausse · · Score: 3, Funny

    is Asa Dotzler part of this workgroup?

  3. In other words by OverlordQ · · Score: 4, Insightful

    To this end, we are re-establishing a Mozilla Enterprise User Working Group as a place for enterprise developers, IT staff and Firefox developers to discuss the challenges, ideas and best practices for deploying Firefox in the enterprise.

    In true Mozilla fashion, I'm sure that will mean "We'll pretend to listen while we continue to do whatever we want"

    --
    Your hair look like poop, Bob! - Wanker.
    1. Re:In other words by Bacon+Bits · · Score: 4, Funny

      In true Mozilla fashion, I'm sure that will mean "We'll pretend to listen while we continue to do whatever we want"

      See? FOSS software really is just as good as commercial closed-source software!

      --
      The road to tyranny has always been paved with claims of necessity.
    2. Re:In other words by QuantumRiff · · Score: 4, Insightful

      How long have people been begging for an MSI based installer, and some Group Policy support that is "official".. sure there are scripts that can hack GPO support in, and 3rd party builds of the MSI installer.. but people have been asking since Firefox 2...

      --

      What are we going to do tonight Brain?
    3. Re:In other words by jellomizer · · Score: 4, Insightful

      Yes, It sounds like their are doing a lot of crazy work where all they need to do is back track and go with a normal version numbers to fix the problem.

      Mozilla JUST ADMIT YOU WERE WRONG! and go back to what was working before. Being wrong isn't a sin that is how we all learn, if you are going to bull headed and just make a lot of extra work just to cover your mistake, so you can save face, is plain stupid.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  4. "Re-establishing" by dreemernj · · Score: 3, Interesting

    This was the story in 2007 when they first tried this: New Mozilla working group aims to simplify enterprise Firefox deployment

    --
    1 (short ton / firkin) = 89.1432354 slugs / keg
    1. Re:"Re-establishing" by rbrausse · · Score: 5, Informative

      in total three "meetings". and - history repeats itself - the same problems with Firefox in enterprise environments:

      * Packaging (MSI)
      * Settings Management (GPO)

      And the blog with the meeting notes is deleted. as I expected: This was a _really_ important project for Mozilla...

    2. Re:"Re-establishing" by pspmikek · · Score: 5, Informative

      The previous EWG was my effort and yes I believe it it failed because of a lack of interest by Mozilla.

      The old information is here:

      https://wiki.mozilla.org/Enterprise/Old

      And yeah, it is sad that the blog came down with the meeting notes.

      It looks like the wayback machine caught my back though

      http://web.archive.org/web/20080608175739/http://e2pt0.blogspot.com/2007/08/firefox-ewg-meeting-2.html

      At least for some posts.

  5. Hope 1 Expectations 0 by Darth_brooks · · Score: 4, Insightful

    I'll follow and contribute as much as I can, hoping that something changes, but having the cold expectation that nothing will. On the windows side, FF essentially needs three things:

    1. MSI for deployment.
    2. GPO management.
    3. Mozilla branding and support for the above, so I can automatically update the browser.

    That's the peanut butter and jelly for enterprise. I can get the first two from other people, why not you guys? Why it has taken this long to get to this point is beyond me. Seriously, the 'battles' between chrome, opera, and firefox are like watching soccer moms fight to the death over the last tickle me elmo at a Walmart when there's a toy store next door with aisles full of the same toy, cheaper. Seriously, do you guys want to keep scratching with each other over grandma's machine, or do you guys want people like me to push your product to 50 machines at once, and let 50 people *see and use* your browser, learn for themselves that it's better, and take it home with them?

    --
    There are some people that if they don't know, you can't tell 'em.
  6. The real plan? by mrjatsun · · Score: 3, Insightful

    o stop supporting enterprise deployments (by rapid release, no bug fixes only)
    o start an enterprise working group
    o profit! (charge for support)

  7. You don't need anything particularly fancy. by Millennium · · Score: 5, Insightful

    1) Throw the MCSEs a bone: give them their MSIs and GPOs. Alternatively, bless FrontMotion's MSI and GPO projects as the "official" ways to get these things for businesses that need them.

    2) From time to time (but no more frequently than once every two years), tag a release as Long-Term Support. This is exactly what it says on the tin: this release gets official support from Mozilla, including security fixes, until the next Long-Term Support release.

    3) Support for a non-LTS release is not dropped until there have been at least two major releases since then. Under the current situation, that means FF5 support would not be dropped until the release of FF7, which in turn would not be dropped until the release of FF9.

    I realize that long-term or even mid-term support is not sexy. Techies always want to live on the bleeding edge. But not every person or business is willing, or even able, to do that. They also need to be taken care of.