Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Mozilla The Internet

Firefox Developer on Recruitment Policy 300

wikinerd writes "A Firefox developer talks about the project's controversial invitation-only developer recruitment policy and explains why Firefox will never grow up."
This discussion has been archived. No new comments can be posted.

Firefox Developer on Recruitment Policy

Comments Filter:
  • by Gopal.V ( 532678 ) on Monday January 31, 2005 @06:11AM (#11526864) Homepage Journal
    As much as I agree on granting commit access to anyone worthy of it .. I absolutely do not like the XFree86 way of "We take only patches" kind of elite bastards (Linus comes close to pissing me off, but he manages to show the other side as well on a few good days).

    Hopefully firefox will not go into that Elitist arena which blocks out young developers...

    All that said, I had to work for 3 months almost full time to get commit access on what I work on . But we've had a guy who would steam roll the patch database with useless patches and report all kinds of pedantic bugs to pester us into giving commit access (and for his notice, that doesn't get you anywhere).

    A single strategy doesn't work for all types :)
  • by Ezza ( 413609 ) on Monday January 31, 2005 @06:13AM (#11526875)
    is that ANYONE can contribute to a project.

    Only if the developers think you're good enough of course.

  • by lachlan76 ( 770870 ) on Monday January 31, 2005 @06:17AM (#11526885)
    Well, obviously you don't have to be on the team to work for the team. But who wants to work for someone that isn't going to treat them as part of the same team?

    Well they're not gonna give every single person out there commit access to the repository, are they? If you want to be able to directly change a section of the code, you need to prove your abilities. Which is fair enough.
  • by puke76 ( 775195 ) on Monday January 31, 2005 @06:22AM (#11526900) Homepage
    When Firefox developers won't fix important issues [mozilla.org] that would improve browser acceptance in areas like internet cafes, kiosks etc, you have to wonder. What company wants a browser that you can't lock down?
  • What about plugins? (Score:3, Interesting)

    by InterStellaArtois ( 808931 ) on Monday January 31, 2005 @06:39AM (#11526942) Homepage
    Well, if you really want to work on Firefox but can't get a look in, there's always plugins. I know, it doesn't solve the issues here but it would be a start for a keen young developer who needs to build credibility.

    Not sure if plugins are included in this apparently elitist policy - I can't RTFA because it's slashdotted naturally.

  • Well, although I disagree with the developers not accepting many patches, this is not one of them. Anything that most people do not need is supposed to be an extension in order to stop bloat--that's why Firefox is so much better than Mozilla; this falls into that category as only a select few machines run by an even more select few of (hopefully technically knowledgable) indivduals would need this.

    The extension system is integrated into Firefox and designed to be used. The real problem with the Kiosk mode is that that extension looks like it hasn't been kept up-to-date/has ceased development.

    In the future (maybe 1.1), I think the Firefox developers will probably include the most popular extensions in the Firefox installer to make it even easier to do additional stuff like this.
  • by DingerX ( 847589 ) on Monday January 31, 2005 @06:58AM (#11526988) Journal
    Well Tex, code ain't big enough for the ten thousand of us.

    Openness, huh?
    I always thought open source meant the source was free to be used, modified, imnproved and adapted. It does not, to my recollection, mean that those maintaining a given heap o' code have to take "all comers", or even have to have a formal mechanism in place to consider adding to their number.
    I don't know what kinds of projects y'all work on, but where I come from, when someone comes up asking to join a project, or asks for collaboration, in the name of "The community", "the open source ideal", or other high-falutin' sounds, it usually boils down to one of a series of options:
    A) Can you give me lessons?
    B) Can you spend time working on my project?
    C) Can I boost my own social position by claiming to work for you guys?

    If you have the luxury of an abundance of people who want to work on your free project, you pick the ones who are most capable of doing work with the least amount of management. Going through a list of submitted applications is not the most efficient way to do this. You find who's doing good work, and talk them into working for you.

    If someone has a brilliant vision for OSS, that person is usually better served realizing that vision in a dedicate project. Giants on the shoulders of dwarves.
  • Open Source? (Score:5, Interesting)

    by vcv ( 526771 ) on Monday January 31, 2005 @07:12AM (#11527022)
    Firefox is open source, so anyone can contribute. And the open-source is fully of great talents, right?

    Why then, after 5 (almost 6) years, is the outline property in CSS not supported? Why is there no one able to fully implement this? Yes, I know about -moz-outline, but it's -moz-outline because they don't trust their own code enough after 5 years.

    https://bugzilla.mozilla.org/show_bug.cgi?id=6647
  • pet peeve (Score:5, Interesting)

    by Anonymous Coward on Monday January 31, 2005 @07:20AM (#11527041)
    My pet peeve is how the developers won't fix autocomplete so it does not remember credit card numbers.

    It's bug 188285. Have a look if you're interested.
  • Comment removed (Score:5, Interesting)

    by account_deleted ( 4530225 ) on Monday January 31, 2005 @07:53AM (#11527130)
    Comment removed based on user account deletion
  • by mcsmurf ( 757095 ) on Monday January 31, 2005 @08:58AM (#11527295) Homepage
    Why does the link to his blog redirect to Wikipedia?
  • by raahul_da_man ( 469058 ) on Monday January 31, 2005 @09:06AM (#11527319)
    Oh I see. The Mozilla developers are supposed to learn lessons on openness from BSD? What kind of troll are you?

    Did you miss the OpenBSD forking because the rest of the previous BSD team ..Net? Open? could not get along with Theo De Raadt. These are the same BSD's that pride themselves on its elitist policy of only accepting patches from the core group.

    http://www.netbsd.org/People/core.html

    I humbly submit that no one needs to learn anything from the BSD process. Next time, don't make such clueless statements. On Slashdot, people who know the history of Unix are a dime a dozen.

    In fact, if you knew anything about the BSD approach, you would realize that the Firefox group seems to be approaching the exact same level of arrogance. I only hope we don't end up with three pointless forks..Open Firefox anyone? The pointless infighting and forking of BSD was the reason they were hasbeens instead of competition to Linux.
  • Re:Other groups (Score:4, Interesting)

    by malkavian ( 9512 ) on Monday January 31, 2005 @09:25AM (#11527401)
    I think you hit the nail on the head with your comment.
    After all, not everyone in Debian are the smartest coder.
    Firefox actually want the 'smartest coders' that work with their codebase.
    While it is certainly elitist, it makes sure that only the elite (dedication plus skill) get to work on their branch of the browser. If that ends up making it work faster, more robustly and more efficiently, then all to the better.
    A small team of highly skilled individuals can often achieve more than a large pool of medium skilled people, and usually far more than a huge team of mediocrely skilled people.
    Everyone they compete with (corporate entities, such as MS and Opera) is pretty much guaranteed to be elitist (they'll hire the best coders and designers they can at interview), so why shouldn't the firefox team?
    Of course, as has been noted, if you think you can do better with your choice of team recruitment, then fork the project, and see which one survives.
  • Word and Deed (Score:2, Interesting)

    by tezza ( 539307 ) on Monday January 31, 2005 @10:15AM (#11527672)
    Wow. Only 'Hubris' [reference.com] even comes close to describing how arrogant this guy comes across.

    People sometimes ask why we work on Firefox for free. It gets hard to keep a straight face at work. Give me another project that touches the lives of millions of people worldwide and still has public codenames like The Ocho which get published in the media.

    --------

    I find it hard to keep my lunch down when I read such self-aggrandising bullshit.

    Then they lock out other developers so they can't fucking choose a fucking codename just in case it dilutes their moment in the media spotlight.

    So they seem arrogant both in word and deed.

  • Re:Open Source? (Score:1, Interesting)

    by Anonymous Coward on Monday January 31, 2005 @10:17AM (#11527687)
    How about, If it bugs you don't use it. I really hate that lame ass cop-out. FF is not so cool that everyone who finds out that it has bugs, that it crashes, and that it's missing functionality needs to become a programmer and fix the bugs themselves. Especially when there are other free browsers out there that don't have a problem rendering websites and not crashing. I can do my online banking with Netscape and IE, I can't with FF. That to me is part of basic functionality. The last thing in the world I would ever do is write up some code for FF to fix their problem, precisely because it's not my problem.

    I'm starting to believe that some people view the OSS movement as an excuse to be lazy. Why bother writing decent code if you can just bullshit everyone else into doing it for you? Of course there are lazy assholes in every crowd that make the whole group look bad.

    FF has been way too overhyped and now it can't live up to it's expectations. It is a new fledgling browser with minimal functionality and minimal stability. It is nowhere near a replacement or competitor for IE, Opera, or Netscape. Honestly I don't think it was anywhere near ready for a full page NYT ad, especially if I can't do my online banking with it.
  • Debian (Score:1, Interesting)

    by Anonymous Coward on Monday January 31, 2005 @10:23AM (#11527735)
    Debian as a whole isn't bureaucratic, but the new maintainer process sure is. Did you see that page about joining Debian? Between applicants, front desks, sponsors, committees and tests... yuck. Those guys even rejected Norm Walsh as a Debian maintainer.
  • Re:Word and Deed (Score:3, Interesting)

    by photon317 ( 208409 ) on Monday January 31, 2005 @11:52AM (#11528653)
    "We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris."

    -- LarryWall, ProgrammingPerl (1st edition), O'Reilly & Associates

    In the second edition of the book (which sports not only LarryWall as author, but also Tom Christiansen and Randal L. Schwartz as co-authors), there is a glossary which has pithy definitions for each of these terms:

    Laziness
    The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer, Also hence, this book. See also impatience and hubris. (p.609)

    Impatience
    The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer. See also laziness and hubris. (p.608)

    Hubris
    Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. See also laziness and impatience. (p.607)
  • by shaitand ( 626655 ) on Monday January 31, 2005 @12:19PM (#11528961) Journal
    If Slashdot's HTML cannot pass the validator then Slashdot's HTML that is also bugged. Incompatability with the standards is a bug, not an oops.
  • Re:obligatory link (Score:3, Interesting)

    by snorklewacker ( 836663 ) on Monday January 31, 2005 @01:32PM (#11529735)
    > But it is unethical to post such a link under your own username rather than anonymous... this way, it's kinda karma whoring,

    What the hell is WRONG with a community where the basic CONCEPT of "karma whoring" can be regarded as a "bad thing". Yes, some people copy and paste an entire article for some moronic moderator to pump them up to +5, but ...

    argh, I can't even express it adequately ...

    It's just karma. It's a little point scale. It does not validate your existence. Stop putting so bloody much importance on it.

    criminy. end rant.

  • Comment removed (Score:3, Interesting)

    by account_deleted ( 4530225 ) on Monday January 31, 2005 @02:05PM (#11530183)
    Comment removed based on user account deletion
  • by dnoyeb ( 547705 ) on Monday January 31, 2005 @03:24PM (#11530995) Homepage Journal
    Yep, that is how I have worked on every open project so far. I see enough bugs with a particular function and complain on bugzilla. End up in small debate about the issue in bugzilla. Offer my time if he/she will explain how to setup a build environment. I do, fix the bug, and send in the patch file to the developer on bugzilla.

    Then the next bug I simply file the report, ask if its valid, and if so submit the patch to bugzilla again. Once this happens a few times it becomes more time consuming to manage my contributions than to let me contribute directly, and I usually get requested to commit directly to cvs. I actually prefer not to have that burdeon/responsibility :P
  • by codemachine ( 245871 ) on Monday January 31, 2005 @05:43PM (#11532867)
    Created due to licensing, but heavily adopted due to people being fed up with XFree86.

    The Cygwin folks already had to fork XFree because of the orgainization's refusal to accept patches. And Cygwin was far from being the only ones annoyed with XFree. It was just easier for distros to stick with XFree instead of maintaining their own, and causing a political mess.

    The license change was merely the last straw, and was very indicative of how XFree operated. By unilaterally changing the license, then refusing to work with the people who ship their product on fixing it, they showed an even higher level of elitism than before. By this time there was a large enough group X11 developers that were doing great work, but not part of XFree (mainly Keith Packard), that the distros had somewhere else to turn.

    So it was more than a simple license change I'm afraid. They kept some of the best developers doing the most innovative work outside of the group, and alienated the very people who distributed their product. Their own elitism made them completely irrelivant in the development of X11, which was supposed to be the entire purpose for XFree's existance.

    It is not impossible that this could happen to Firefox too, but right now they are the main drivers in the browser market, and generally are keeping their use base happy. No reason to worry quite yet.

Always try to do things in chronological order; it's less confusing that way.

Working...