Slashdot Mirror


Dotgnu Coding Competition

Honestly writes "Apparently DotGNU seems to be offering more than the 'warm fuzzy feeling' to its contributors. Somebody has funded about $4500 worth of prizes for code contributions. The developers have confirmed that the $$$ is in FSF Hands (good hands, I suppose). Here is the split up of prizes. It's almost strange to earn money writing open source. Especially when you're not even employed by dotgnu. Anyway all I can say is ,I like it. It's ideal for a grad student with lots of free time. But hardly anyone seems to have seen the Newsforge posts (except maybe me)."

132 comments

  1. fp by Pompatus · · Score: 5, Funny

    It's ideal for a grad student with lots of free time.

    Never been to grad school, huh?

    --

    ----
    Squirrel ... It's not just for breakfast anymore
    1. Re:fp by s20451 · · Score: 2, Informative

      It's the Saturday of a long weekend, and as a grad student I'm spending my copious free time ... in the lab.

      --
      Toronto-area transit rider? Rate your ride.
    2. Re:fp by zCyl · · Score: 2, Interesting

      Some days I think Slashdot needs a +10, Insightful...

    3. Re:fp by Anonymous Coward · · Score: 2, Funny

      Life of a grad student:

      Year 0: "I will be an agent of change."
      Year 0.5: "Holy S@#&! Quals!"
      Year 1.0: Finished recovering from Quals
      Year 2.0: Hmm, no results.
      Year 3.0: Still nothin'. Do prelim anyway.
      Year 4.0: Realize that for project to succeed, 2 laws of thermodynamics must be violated.
      Year 5.0: Finally convince advisor of above
      Year 6.0: Surf web, drink coffee, contemplate navel. No longer bitter - now at peace.
      Year 7.0: Realize you're almost 30 and still in school. Realize you still don't have a feasable project. Bitterness returns.
      Year 7.0001: Job search begins.
      Year 7.5: Find job. Discover "friends" from undergrad who went straight to work will be boss's boss.
      Year 7.6: Define project, perform experiments, analyzing results, writing paper(s). Only productive time in grad school
      Year 7.7: Look for 5 faculty members willing to sit in a room with you and each other for 3 solid hours.
      Year 8.0: Committee finally assembled. Defense occurrs. Sum up 8 years with 20 minute talk. Listen to useful advice on project you'll never think about or work on again. Stand outside door for 20 minutes pacing nervously while committee discusses weekend plans, daycare options, new italian restaurant on west side. "You've passed! Now pay us $1000 to get 10 bound copies of your thesis made plus the microfilm charge or else you won't officially be awarded a diploma."

    4. Re:fp by tetrode · · Score: 1

      I understand that you've never had a job?

  2. If... by Spoticus · · Score: 2, Funny

    RMS wins, you know it's fixed ;-)

    1. Re:If... by wik · · Score: 5, Funny

      Little do you know, but the real prize is RMS coming to your front door with the FSF Source Patrol van, carrying an oversized copy of the GPL.

      --
      / \
      \ / ASCII ribbon campaign for peace
      x
      / \
    2. Re:If... by Anonymous Coward · · Score: 0

      After the second time this happened to me, I got a dog.

    3. Re:If... by God!+Awful+2 · · Score: 1


      Little do you know, but the real prize is RMS coming to your front door with the FSF Source Patrol van, carrying an oversized copy of the GPL.

      That would be funny... especially if you lived in Norway or something. "Hi, this is Richard Stallman. I just spent 15 hours and $5,000 travelling across the world to give you this $300 check."

      Seriously... the top prize is $2,000. A decent programmer makes that in a week. This contest is lame.

      -a

    4. Re:If... by pyrrhonist · · Score: 2, Funny
      A decent programmer makes that in a week.

      No, several thousand Indians make that decent programmer's salary in a week.

      --
      Show me on the doll where his noodly appendage touched you.
    5. Re:If... by Anonymous Coward · · Score: 0

      No, several thousand Indians make that decent programmer's salary in a week.

      Only if you overpay them.

    6. Re:If... by Anonymous Coward · · Score: 0

      You're lame. Go back to your X-Box and leave the hacking to the hackers.

  3. Grad students, free time? by Anonymous Coward · · Score: 1, Insightful

    Ideal for grad students with lots of free time . Umm....what planet are you from?

  4. Thanks for spoiling it! by Lord+of+the+Fries · · Score: 5, Funny

    "But hardly anyone seems to have seen the Newsforge posts (except maybe me)."

    Oh great! So much for the easy win for the few of us that did know about it. :/

    --
    One man's pink plane is another man's blue plane.
  5. System.Windows.Forms by rf0 · · Score: 1, Interesting

    You have to wonder how many hidden calls there are? I'm sure at least on major one will be hidden making this all nice and hard

    Rus

    1. Re:System.Windows.Forms by Anonymous Coward · · Score: 2, Informative

      It doesn't matter how many "hidden" (they're not hidden - use ildsasm) calls there are. You're making your own implementation.

    2. Re:System.Windows.Forms by MagPulse · · Score: 1

      What the OP probably meant to say is that the "perfect" Windows.Forms implementation will need to reproduce all the bugs and quirks that the MS one has, and then fix them when MS does.

    3. Re:System.Windows.Forms by Burb · · Score: 1
      "All the bugs and quirks"

      OK, I'll bite. Name three.

      --

    4. Re:System.Windows.Forms by Burb · · Score: 1
      Damn, my bluff has been called.

      Mind you, I would categorise these as bugs (i.e. things the windows app should do but doesnt), not features (quirky features that we have to replicate to get compatibility). I think that Portable.NET, or Mono, or whatever should certainly strive to be reasonably quirk-compliant but not bug compliant.

      --

  6. Bribes... by Anonymous Coward · · Score: 0

    don't take them lightly.

    1. Re:Bribes... by BiggerIsBetter · · Score: 1

      don't take them lightly.

      Don't take them at all has always been my motto.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  7. ideal for grad students by Anonymous Coward · · Score: 0

    dude, where do you go to grad school?

    1. Re:ideal for grad students by Anonymous Coward · · Score: 0

      Maybe it should be rephrased to "CS undergrads who are going to Sociology grad school"

  8. No you're not. by FreeLinux · · Score: 3, Funny

    You're posting on Slashdot, just like you do during the "busy" week.

    1. Re:No you're not. by s20451 · · Score: 1

      I'll be sure to make a note of that and have someone dock my "pay".

      --
      Toronto-area transit rider? Rate your ride.
  9. What about Mono by joeykiller · · Score: 3, Interesting

    How does this differ from mono? It seems to me as the two projects are trying to achieve the same things. If that's the case, why have two projects at all? Why not merge the two efforts? I guess somebody here knows why.

    1. Re:What about Mono by Plix · · Score: 4, Informative
    2. Re:What about Mono by Anonymous Coward · · Score: 0


      programmers re-inventing the wheel ? say it aint so, next you will be telling me wordprocessors are 600mb big

    3. Re:What about Mono by qtp · · Score: 4, Insightful

      why have two projects at all?

      Perhaps, because different projects might come up with different implementations that have strenths that the others might not.

      Sometimes a parallel effort is needed in order that different approaches to the same problems get to be explored fully.

      Because it is sometimes better to fork a project, not because one approach is "wrong" but because another is equally good.

      Because it might be better to merge to separate efforts later when both have more mature codebases.

      Because having two separate projects nmight enable the coders to more easily see alternative methods that neither effort would have thought of without the other.

      Because there is more than one way to do it.

      --
      Read, L
    4. Re:What about Mono by Anonymous Coward · · Score: 0

      why have two projects at all?

      It's a big wall, so let them both have at it!

    5. Re:What about Mono by Anonymous Coward · · Score: 2, Informative


      An advanced native-code compilation engine: Both just-in-time compilation (JIT) and pre-compilation of CIL bytecodes into native code are supported.


      Portable.net uses an advanced unrolling interpreter which gives it up to 60% the speed of a real JIT and makes it much easier to port than the mono JIT. It only took a week to port the unroller to arm processors.

      In the future Portable .net will have a full jit as well as the portable unrolling interpreter (which is much faster than mono's interpreter).


      A foundation for code optimization: The new code generator in Mono builds on the experience of our first JIT engine, and enables us to implement various advanced compiler optimization tricks. With an SSA-framework, plenty of new optimizations are possible.
      The current list of optimizations are: Peephole postpass, Branch optimizations, Inline method calls, Constant folding, Constant propagation, Copy propagation, Dead code elimination, Linear scan global reg allocation, Conditional moves, Emit per-domain code, Instruction scheduling, Intrinsic method implementations, Tail recursion and tail calls, Loop related optimizations, Fast x86 FP compares, Leaf procedures optimizations


      That's only unique cause Mono currently has a JIT. It's not unique to the Mono project.

      A self-hosting C# compiler written in C#, which is clean, easy to maintain.


      Focus on the .NET Framework: we are tracking down the .NET Framework API definition, as we believe it is the API people will be most familiar with.


      And the API that is the most poorly designed (when compared to OO libraries like Java).


      A multi-platform runtime engine: both a JIT engine and an interpreter exist. The JIT engine runs currently on x86 systems, while the interpreter works on SPARC, StrongARM, s390 and PowerPC systems.
      Our new compilation engine is being ported to the PowerPC.


      Now the wording of this paragraph is designed to decieve. The first part talks about a multi-platform runtime engine which is infact not unique to mono. In reality, portable.net runs on far more platforms than mono. The second part just goes on to talk about how the new compilation is going to be ported to PowerPC.


      Supports Linux, BSD, Windows and Solaris at this point.


      Portable.Net supports Linux, BSD, Windows, OSX, and more. In fact, all you need is a C compiler -- you can even compile portable.net with Visual C++ (try doing that with mono).


      The JIT engine is written using a portable instruction selector which not only generates good code but is also the foundation to re-target the JIT engine to other systems.


      More about the JIT. All of this "amazing" stuff is pretty standard for a JITs.


      Full support for remoting in the runtime.


      I'll give them that.


      The C# compiler, the JIT engine and the class libraries are mature enough that the whole system has been self-hosting since April 2002. This means that we develop Mono completely with itself at this point.
      By forcing ourselves to use our own code to develop our tools, we bug fix problems rapidly, and the system is overall more robust and tested than if we did not.


      That's not unique to mono either.


      We have a great community of developers, without which Mono would not be possible.
      In general, Mono is more mature and complete since it has been used to develop itself, which is a


      And so does portable.net. Too many mono developers are newbie or ex VB programmers which makes *a lot* of the code in mono extremely ugly hacks.

    6. Re:What about Mono by Laconian · · Score: 1

      That's great, but we're dealing with a limited number of skilled programmers. If there were unlimited resources, a parallel approach might work better.

      But why fork a project needlessly when combined efforts could produce a product that is ultimately more intuitive and polished than two rough apps that waste twice the time for twice the learning curve?

      I apologize for the run-on sentence.

    7. Re:What about Mono by qtp · · Score: 1

      but we're dealing with a limited number of skilled programmers.

      Open Source is not a corporation, nor is it a (managed) Democracy. It is, howerver a volunteer effort where programmers are permitted to put thier efforts behind whicheber effort they see fit, for whatever reason.

      But why fork a project needlessly when combined efforts could produce a product that is ultimately more intuitive and polished than two rough apps that waste twice the time for twice the learning curve?

      It is more likely that a single effort will produce a non-intuitive and unpolished implementation than two seperate efforts.

      As for wasting "twice the time", if one effort finds itself committed to the wrong approach, then the rest of the community will be thankful that the other does exist. See the Mythical Man Month to understand why more programmers working on a single project does not necessarily mean that the project will turn out better or be ready quicker.

      I'm not really certain that "intuitiveness" is at stake here. IMHO, the most important aspect of the .net spec is the network transparancy, not the particular user interface. If it is possible to implement the network layer without tying it to a particular user interface or Desktop environment, then that is what should be done. (IIRC, .net does some of what Gnome was originally intended to do as a "network object model environment". Too bad Gnome spent so much time attempting to be "Windows, but better" that Microsoft beat them to the punch on the "network object" spec.)

      I do like some of what Ximian has done, but not enough to change my mind about accepting any argument for a "default desktop environment". Neither Gnome nor KDE has shown me that thier way is superior to designing apps that are not tied to any particular "desktop" or window manager.

      --
      Read, L
  10. Not the only one by jaaron · · Score: 0, Redundant

    I'm sure I'm not the only one with this question:

    What's the difference between gotGnu and Ximian's Mono project?

    I've googled for some details, but I'm not .NET literate enough to really distinguish the two. Anyone want to give a short explanation of the differences? Thanks.

    --
    Who said Freedom was Fair?
  11. sample of code by lethalwp · · Score: 1

    here is a link to a sample code that should be "finally" supported?

    http://savannah.gnu.org/cgi-bin/viewcvs/dotgnu-p ne t/pnetlib/samples/FormsHello.cs?rev=HEAD&content-t %20ype=text/vnd.viewcvs-markup

    (remove the space %20) that /. introduces

    1. Re:sample of code by Anonymous Coward · · Score: 0
  12. Because by Anonymous Coward · · Score: 2, Insightful

    Each project is sure that their way is the only "sane" way to go about it. Each project looks down at the other with disdane, simply for being different.

    It's the same reason that there are now ~300 MP3 player projects on SourceForge.

  13. Dyslexia??? by jpetts · · Score: 4, Funny

    I read that title as Donut Coding Competition!

    --
    Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
  14. Dotgnu? You Spelled Doughnut Wrong! by Anonymous Coward · · Score: 0

    Rats! Bung!

  15. Re: "It's almost strange to be earning money..." by JessLeah · · Score: 2, Insightful

    As much as I love Open-Source/Free Software, it IS very very hard to make a living making it. I'm not talking about writing code for an employer, and then getting permission to release it; I'm talking about actually making your living DIRECTLY off of making, releasing and "selling" open source/free software, a la Red Hat (who just recently turned a profit for the first time). I'd love to hear some more stories from people who've actually made money by coding OSS/FS.

  16. What about this Malloc routine.. by adeyadey · · Score: 5, Funny

    What about this Malloc routine I've just written?
    Do I get a prize?

    Darl McBride

    --
    "You lied to me! There is a Swansea!"
    1. Re:What about this Malloc routine.. by Anonymous Coward · · Score: 0

      You now owe me a new glass of Pepsi and a new monitor. :)

    2. Re:What about this Malloc routine.. by Anonymous Coward · · Score: 0

      I'll pay you my own way now, you sexy Mormon plum.
      - The Giver

  17. pgp key? by molo · · Score: 2, Interesting

    That message is signed with a pgp key. However, the key doesn't seem to be available on the public key servers, so how can we validate the message?

    If anyone has DSA key 0x7525EC32, please speak up.

    -molo

    --
    Using your sig line to advertise for friends is lame.
    1. Re:pgp key? by nuntius · · Score: 1

      Gimme some time; I'm generating one to match that message. ;)

    2. Re:pgp key? by daserver · · Score: 3, Funny

      Is this a new version of "Will the real slim shady please stand up"? Sorry couldn't resist.

    3. Re:pgp key? by Anonymous Coward · · Score: 1, Funny

      I'm 0x7525EC32
      yes I'm the real 0x7525EC32
      all you other 0x7525EC32
      are just 0xDEADBEEF
      so won't the real 0x7525EC32
      please..sign your public key..
      please sign your..no, I think I lost the rhythm of this thing long ago.

  18. Not so strange. by jtalkington · · Score: 5, Insightful

    It's almost strange to earn money writing open source.

    No, it's not. Linus, RMS, AC, BP, among many others have been getting paid to write free software for years.
    Part of the stigma associated with OSS is that since it's associated with "volunteers," it is considered hobby level. Lots of people get paid to work on OSS, and ever increasing large software companies (e.g. IBM and Apple) have staff members working exclusively on OSS.

    1. Re:Not so strange. by stratjakt · · Score: 0, Troll

      Linus doesnt get paid to write free software. He writes VLIW shit for Transmeta last I heard, and I dont believe any of that is Free.

      Even Mr Lunix needs a real job to pay the bills.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:Not so strange. by Anonymous Coward · · Score: 0

      i belive RMS earned his cash through HP no ? yeah well known for their free software are they ? not

      get real, people need to earn a living or have you bought the GNU branding initative too ?

    3. Re:Not so strange. by r00zky · · Score: 2, Informative

      He's no longer working for Transmeta.
      He's getting paid to write the kernel, paid by OSDL, more info here.

      --
      I'm a chainsmokin' alcoholic sociopath, so-ci-o-path
    4. Re:Not so strange. by Anonymous Coward · · Score: 0

      Yup. They fired about 8 other people right before they hired him as well. Mostly kernel developers with 20+ years writing Unix kernels (Dynix, Dynix/PTX, BSD, and Linux).

    5. Re:Not so strange. by Jah-Wren+Ryel · · Score: 1

      Duh. RMS "earned his cash" through contract development of free software. Somebody wanted a new feature added to Emacs or a port of gcc to a new arch, they'd hire RMS. He'd get paid (handsomely), they'd get what they needed and we'd get the improvements in the Free software.

      I don't know one way or the other, but nowadays I bet RMS makes more money from speaking engagements than he does from contract work. Just a guess though.

      --
      When information is power, privacy is freedom.
    6. Re:Not so strange. by Anonymous Coward · · Score: 0

      RMS, AC, BP, among many others have been getting paid to write free software for years. Actally, i havent gotten paid a cent.

  19. $300 per prize - is it too little ? by leoaugust · · Score: 4, Interesting

    Besides the chance of winning one of fifteen monetary prizes totalling US$ 4500

    Though it is good start that there is some money, but what comes to my mind is why so little ... 15 prizes averaging $ 300 each

    • that is about 8.5 hours of a coder worth $ 35 an hour
    • or 1 week (20 hours) of a grad students time ....
    • or 2 weeks (40 - 60 hours) of a coder in India's time
    • or 4 hours of a coder worth $ 75 an hour

    I wonder why doesn't some philanthropist wanting to donate to charity or some rich guy wanting to support Linux just give a couple of hundred thousand dollars, or may be a few millions, in prize money - so that it can support a critical mass of programmers that can devote a decent amount of time ..... rather than the tens of hours that are "economically feasible" now ....

    I know ... linux is not about money and all .... but still ... why couldn't it be ... everyone does not have to pay - just those people wanting it very badly have to pay while the rest get a free ride so that society as a whole benefits ...

    and seriously - this is not meant to be flamebait ...

    --
    To see a world in a grain of sand, and then to step back and see the beach where the sand lies ...
    1. Re:$300 per prize - is it too little ? by Anonymous Coward · · Score: 0


      see linux is a charity project, not a buisness

    2. Re:$300 per prize - is it too little ? by Cthefuture · · Score: 2, Insightful

      I was thinking the same thing. The top prize is $2000. Over four months that's less than $3 an hour. And that's if you win. Screw that.

      Now sure, some people would just do it for the hell of it. However, if they are expecting quality code, it probably isn't going to happen. Anyone with any talent is going to pass this over.

      Quite lame.

      --
      The ratio of people to cake is too big
    3. Re:$300 per prize - is it too little ? by rhysweatherley · · Score: 4, Insightful

      It's a prize, not a wage.

    4. Re:$300 per prize - is it too little ? by God!+Awful+2 · · Score: 1


      I wonder why doesn't some philanthropist wanting to donate to charity or some rich guy wanting to support Linux just give a couple of hundred thousand dollars, or may be a few millions, in prize money - so that it can support a critical mass of programmers that can devote a decent amount of time

      It's common sense. Most people with $1 million to spare didn't get rich by giving their money away. Also, very few of them got rich by giving away their product for free.

      -a

    5. Re:$300 per prize - is it too little ? by Daniel+Phillips · · Score: 1

      I was thinking the same thing. The top prize is $2000. Over four months that's less than $3 an hour. And that's if you win. Screw that.

      I estimate that for over half the world's population, it's over half a year's per-capita income. (Per capita GDP by country here. )

      While you are unlikely to do this purely for the money you live in a rich, industrialized country, for you, the resume item is easily worth the effort. And what the heck, even if you don't win, you are going to learn enough to make it worthwhile.

      --
      Have you got your LWN subscription yet?
    6. Re:$300 per prize - is it too little ? by Anonymous Coward · · Score: 0

      It's not about the money. Go back to your X-Box; this isn't the game for you.

  20. Re: "It's almost strange to be earning money..." by Anonymous Coward · · Score: 0

    Interesting, I've the opposite problem. I'd be willing to spend some money, but would hate it if it ended up in the pockets of someone who just continued with what he was already doing. I mean, I want my money to get an extra mile. For example, I'd like to see OpenOffice for Mac OS X finished a little earlier. I'd be willing to spend a little money on that.

  21. Thus Anna and the other girls learned even more by Anonymous Coward · · Score: 0

    Bad boy.

  22. you donate... by Thinkit3 · · Score: 1

    Look anywhere and you'll see paypal donating links. Who needs a philanthropist? Lots of individuals can do this. I've donated to xiph and mozilla.

    --
    -Libertarian secular transhumanist
  23. "Competition"? by wcdw · · Score: 1, Redundant

    Sounds more like using reverse psychology to get people to work for slave wages.

    Or perhaps I was just put off by the #irc and pnetlib contribution requirements....

    --
    If you're not living on the edge, you're just taking up space!
    1. Re:"Competition"? by Anonymous Coward · · Score: 0

      I think this competition is aimed for the people who would code anyway, but now is encouraged to work a little faster.

      Another advantage is that this competition will perhaps be good PR

  24. Did you say rats? by Anonymous Coward · · Score: 0

    Look - we get them dirty FSF rats! By the bye, why do you think he said "good hands, I suppose"? Maybe we're all going to get a little jerk from da boys? Hand(coding)jobs for everyone! Yay!

  25. DotGNU/GNU by SuperBanana · · Score: 0, Troll
    Apparently DotGNU seems to be offering more than the 'warm fuzzy feeling' to its contributors.

    That's DotGNU/GNU you insensitive clod!

    So much for the warm fuzzy feelings.

    1. Re:DotGNU/GNU by SuperBanana · · Score: 0, Offtopic
      (Score:-1, Troll)

      DUDES. It's a JOKE. Oh well, serves me right for posting during labor day weekened, when the lusers are the only people around.

      Oh wait...

  26. That's better than.. by SuperBanana · · Score: 1
    I read that title as Donut Coding Competition!

    That's better than the Dognut Counting Competition...

  27. Re: "It's almost strange to be earning money..." by Renegade+Lisp · · Score: 1

    I call myself a "free software consultant", and I am making a considerable fraction of my income writing free software. I am paid by companies who use free software, and who want me to enhance it with new features. The other part of my income is teaching seminars in the J2EE field, and doing regular consulting work, usually with an emphasis on free software solutions. From my personal experience, I can say there are lots of opportunities if you really want to work in this field, and put the emphasis on free software.

  28. PNET vs Mono by Anonymous Coward · · Score: 4, Informative

    Basically Mono's FAQ trashes DotGNU and Mono at every chance. Miguel and the Mono crew has had a smear campaign against DotGNU since day one.

    DotGNU in the past has tried to cooperate and initiated talks in sharing resources, but this didn't go well with Mono.

    The true difference between Portable.NET and Mono is Portable.NET has chosen different technical decisions.

    #1: The compiler is written in C/C++ not C# itself, so it doesn't have the chicken or the egg problem. Mono's CVS is very difficult to get a handle of because of this. PNET's compiler is about 3x as fast as Mono's.

    #2: The topic at hand, winforms.. PNET's winforms only dependancy is X, which means their winforms work on handhelds, osx, etc. Very portable. Mono's requires Wine, not very portable to say the least.

    Thats a rough quick sum.

    1. Re:PNET vs Mono by krumms · · Score: 1

      Basically Mono's FAQ trashes DotGNU and Mono at every chance.

      They trash their own software??? Harsh! :P

  29. License? by DickBreath · · Score: 3, Interesting
    Can DotGNU be used by a developer who wants to put their own work into making a web based, for pay application, that is closed source, but using DotGNU's tools and platform?

    I love free software and open source, use them, advocate them, and even write some small time stuff and license it LGPL. During the day, I work for a company that develops and sells a software program.

    Here is a quote from the FAQ of DotGNU's Vision for WebServices .

    Am I obligated to give away my webservice source code?

    You are not automatically obligated to distribute your source code, and you are certainly not obligated to just give it away. However, if you sell webservice services, then your customers will expect that you make them the "owner of the data" which the webservice uses, and depending on the exact circumstances that may indirectly give these customers a right to get the source code upon request. Here are the details:

    If you provide a webservice using a GPL'd webservice program (which you may have modified), then the "owner of the data" will be able to obtain the webservices programs under the terms of the GNU GPL, and this implies in particular that they will have a right to get the source code of the exact version of the program which you're using. The terms of the GNU GPL also require you to make a written promise to this "owner of the data" that you will be willing to provide the source code upon request. This ensures that the "owner of the data" will know about this right to the source code.

    The "owner of the data" is typically a paying customer, and the fact that the customer has a right to get the source code increases the value of the service you provide. Therefore you will be able to charge a higher price and/or close more sales.

    You can use the DotGNU development tools to program your own webservices (instead of just modifying the webservice programs which are distributed with DotGNU, or which others have made available under the GNU GPL) and then your are not required to make source code for these webservices available to the customer who is the "owner of the data". However, even in these situations where you are not required to make the source code available to your customers, we strongly encourage you to provide the source code to your customers under the terms of the GNU GPL anyway. We believe that this is ethically the right thing to do, and that it will be good for your business.

    Now I thought the GPL would not prevent this sort of thing? Now I'm really confused.

    I'm sure glad that GNU thinks they know what would be good for my employer's business and that my employer should charege more for their program (which is for schools).

    I thought I had a good solid understanding of the GPL . I've taken the GPL quiz , read the GPL Faq before.

    I thought the GPL only applied to copying and distribution of a program or derrived work. Not to running it privately on my own web site.

    If I distribute my proprietary program, along side a DotGNU program / platform that executes it, I would not think that my program comes under the scope of the GPL.

    If I do NOT distribute my proprietary program, but merely run it at my site, and merely sell it as a service, then I was definitely under the impression that the GPL did not apply since no distribution takes place.

    Still, back to the case where I distribute my program, and a seperate DotGNU program to run it, then I would not think that my program comes under the scope of the GPL.

    Maybe I had better just stay completely away from DotGNU. Stick with Apache and various Java tools instead.

    Just a side note about the customer having their data he

    --

    I'll see your senator, and I'll raise you two judges.
    1. Re:License? by Malcontent · · Score: 1

      The dotGNU web services license seems to be a superset of the GPL. I don't think the GPL forces you to distribute web services code.

      --

      War is necrophilia.

  30. Only for the incrowd? by mikiN · · Score: 1
    Reading the announcement, one passage struck me as odd:

    2. At least one of your code contributions (a new file or a
    modification of an existing file) must have been accepted
    into the pnetlib System.Windows.Forms codebase.

    Does this mean that only those who already have had code accepted into the codebase can enter the competition? Or am I mixing up verb tenses (passive present perfect, passive future perfect) here?

    --
    The Hacker's Guide To The Kernel: Don't panic()!
    1. Re:Only for the incrowd? by Anonymous Coward · · Score: 1, Informative

      No, the passage means the following:
      If you are hacking on System.Windows.Forms at least one of your code contributions needs to get accepted into the official pnetlib so that you are considered as a participant.

      The contest - of course - isn't restricted to people who already contributed something.

  31. Re: "It's almost strange to be earning money..." by Renegade+Lisp · · Score: 1
    For example, I'd like to see OpenOffice for Mac OS X finished a little earlier. I'd be willing to spend a little money on that.
    I'm sure there are lots of people who feel the same about this or the other feature or port. It would be great if there was an infrastructure where people could donate money and programmers could take up work that these people wanted, the results being released as free software. It would be a great way of making a living with the stuff that we like doing.

    I therefore don't understand your point that "I'd be willing to spend some money, but would hate it if it ended up in the pockets of someone who just continued with what he was already doing." -- I think that's the best way to spend your money, because it's gonna support the work of someone who is in it not just for the money. But sometimes, it does take money to pay the bills...

    Seriously, I think I understand your point that you actually want your feature to be given priority. But you could make contracts to guarantee that, set deadlines, and what have you.

  32. Speaking of dotgnu/.NET.... by tcopeland · · Score: 1

    ...there's a Ruby to .NET bridge over on RubyForge.

    Not sure how much effort it would be to get it working with dotgnu as well... maybe it wouldn't be too bad since much of the connector code appears to be in lib/dotnet/bridge.rb. Lots of C# code in there, though.

  33. Abe's Oddesy by Anonymous Coward · · Score: 0

    Anyone else reminded of the displays on the back wall of the game that said:

    "Work Hard, Die Young, Win Valuable Prizes!"

  34. Standard comment #346 by UserAlreadyExists · · Score: 2, Insightful

    I wouldn't support such a project. If you try to copy MS, you'll always be behind. Reverse engineering takes a lot of time and it's a moving target, since they can change .NET at will. Look at GNU Classpath (Java reimplementation): they're way behind.

    In these cases I think it's better to create a project that offers the same general functionality, but in a distinctive, better way.

    If only I wasn't so lazy...

    --
    "Screw causalilty!" -- Prof. Farnsworth
    1. Re:Standard comment #346 by lederhosen · · Score: 1

      I think Classpath is easyer because of that
      Java was designed to be portable. .Net with
      winforms is not.

      Allthough Swing is not ported much of the
      "usual" 1.2 API is. For example Eclipse
      now runs compiled with gcj.

    2. Re:Standard comment #346 by chochos · · Score: 1

      Supposedly it's not reverse engineering; they're implementing everything according to the ECMA spec.

    3. Re:Standard comment #346 by UserAlreadyExists · · Score: 1

      Yeah, but who writes the spec?

      --
      "Screw causalilty!" -- Prof. Farnsworth
  35. stay away from all of them for now by penguin7of9 · · Score: 3, Interesting

    Maybe I had better just stay completely away from DotGNU. Stick with Apache and various Java tools instead.

    The Apache license is fine, but Java doesn't look like a big win to me. While Sun keeps proclaiming that the platform is open, in reality, large parts of the platform only exist as Sun proprietary code. Even if someone managed to reimplement them, Sun controls the compatibility tests and they can shoot down any implementation they don't like.

    At this point, I'd not get involved with any of Java, PNET, or .NET--the one thing all of them seem to agree on is that they want to entangle users in a web of intellectual property. Well, actually there is another thing that they seem to agree on: all of them want to run your code in a bloated runtime that's slow to start up. Mono seems to have the most straightforward license of the bunch, but even Mono is at risk of patent infringement claims from Microsoft.

    Just wait for the dust to settle and for Sun and Microsoft to come to their senses with their outrageous intellectual property claims. Until then, you have plenty of other options--there is nothing technically new in any of those platforms.

    1. Re:stay away from all of them for now by DickBreath · · Score: 2, Interesting

      Java doesn't look like a big win to me. While Sun keeps proclaiming that the platform is open, in reality, large parts of the platform only exist as Sun proprietary code

      Obviously, because I study the licenses before even proposing development, I would be considering such things.

      Open source implementations of Java are on the horizon. Today, commercial Java runtimes are available from multiple vendors, so you are not likely to have one single vendor treat you badly.

      It is not impossible that Sun could lose control of the standard once multiple mature Java implementations are around. What the rest of the industry does could become a de facto standard. Sort of how the PC architecture hasn't been dictated by IBM for a very long time. Or how modem command sets were no longer dictaged by Hayes. I'm sure there are other examples.

      So whether Sun sets the standards in practice or not (in the event of multiple mature open source implementations) would really depend on how good the standards are, and on how nicely they play.


      Java doesn't look like a big win to me. While Sun keeps proclaiming that the platform is open, in reality, large parts of the platform only exist as Sun proprietary code

      It has the drawback you point out. It also is not as mature in some sense as Java. If the evolution of Mono fits my schedule, it might be the thing to use.

      --

      I'll see your senator, and I'll raise you two judges.
    2. Re:stay away from all of them for now by penguin7of9 · · Score: 1

      Open source implementations of Java are on the horizon.

      It is unclear, however, whether those violate Sun intellectual property. If you check the USPTO web site, you'll see that Sun has numerous patents on key Java technologies, including the basic type verification algorithm.

      Furthermore, even when you just download the documentation from Sun's web site, you accept a license that prohibits you from distributing any implementation of the code that has not passed Sun's conformance tests, and it imposes other restrictions on you (probably incompatible with the GPL).

      So, while people are working on open source implementations of the Java platform, the more compatible they become with Sun Java, the more they risk annoying Sun sufficiently into shutting them down.

      Today, commercial Java runtimes are available from multiple vendors, so you are not likely to have one single vendor treat you badly.

      I'm less concerned about a vendor treating me badly and more about the future of the Java platform. From a practical point of view, as long as other vendors base their implementations on Sun's, they will tend to incorporate Sun's technical mistakes into their own implementations. Sun's latest screw-up is to try to implement Java2D on top of OpenGL--that's just a substandard approach and simply will not work well on Linux.

      From a legal point of view, between the extensive and intricate "community licenses" (which define just about anything as a "derived work"), Sun's extensive patent portfolio, and Sun's contractual agreements with Apple and IBM, the possibility of a free and clear Java implementation seems extremely remote.

      Unless Sun actually changes their licenses, I don't think there will ever be an open source Java implementation without a legal shadow over it. At best, Sun may tolerate open source Java implementations--but perhaps only until they hit hard times and their management changes.

  36. Neither have some others... by Anonymous Coward · · Score: 0

    http://www.spectacle.org/0203/sims.html

  37. I beg to differ by jpmorgan · · Score: 3, Informative
    DotGNU in the past has tried to cooperate and initiated talks in sharing resources, but this didn't go well with Mono.

    I was involved in that argument. If I recall correctly, it was a Rhys Weatherly and some others demanding that the Mono be placed under the DotGNU steering committee and that everybody work on their project instead. Of course, at the time it was quite obvious that DotGNU was mostly ideologues who were obsessed with 'defeating Microsoft' through some embrace and extend tactics, whereas most of the Mono hackers were fairly pragmatic about the whole issue: 'This is pretty cool! I'd love to see an implementation of this in Linux!'. Most of the people who weren't turned off by the downright abrasiveness of Rhys were turned off by the zealous ideology.

    As for bad-mouthing, the only thing the Mono FAQ says about Portable.NET as opposed to Mono is that it the runtime (and compiler) are much less tested. Ximian claims that by developing the compiler and most of the rest of Mono in C#, the whole toolchain has been given a much more rigourous workout than Portable.NET.

    In fact, I'd say the badmouthing has been much more in the other direction: there used to be a page around on the DotGNU website (not sure if it's still there) badmouthing Mono. None of the claims had any substance. For example, it claimed that Mono was on shaky legal grounds with regards to hidden Microsoft patents, which may perhaps be true. However, Portable.NET/DotGNU isn't safe from those legal threats either. Further, while Mono was developed from the ECMA (and now ISO) specifications, Portable.NET was initially developed by reverse engineering Microsoft's .NET implementation (without any clean-room engineering), putting it at risk of copyright infringement claims as well as patent claims. This was also part of the reason why there was little interest from Mono in merging the class libraries.

    I suspect things are probably more civil these days. Cooler heads usually prevail in the end.

    As for your other claims....

    #1: The compiler is written in C/C++ not C# itself, so it doesn't have the chicken or the egg problem. Mono's CVS is very difficult to get a handle of because of this. PNET's compiler is about 3x as fast as Mono's.

    Mono's CVS is easy to handle. It is distributed with a partial prebuilt toolchain, that is then used to build the entire toolchain. It's all MSIL, so there are no platform portability issues. It is also standard practice to write a compiler in its own language.

    #2: The topic at hand, winforms.. PNET's winforms only dependancy is X, which means their winforms work on handhelds, osx, etc. Very portable. Mono's requires Wine, not very portable to say the least.

    WinForms contains a number of window-isms, which the Wine project have already implemented. Reimplementing winelib seems silly and a waste of energy. I can't imagine it'd be appreciably harder to port Mono's WinForms implementation across platforms had it been written from scratch than it would be to port winelib itself. And if winelib gets ported, people other than Mono users and developers can benefit from that work.

    Anyway, just my $0.02.

    1. Re:I beg to differ by Anonymous Coward · · Score: 0

      I was involved in that argument. If I recall correctly, it was a Rhys Weatherly and some others demanding that the Mono be placed under the DotGNU steering committee and that everybody work on their project instead. Of course, at the time it was quite obvious that DotGNU was mostly ideologues who were obsessed with 'defeating Microsoft' through some embrace and extend tactics, whereas most of the Mono hackers were fairly pragmatic about the whole issue: 'This is pretty cool! I'd love to see an implementation of this in Linux!'. Most of the people who weren't turned off by the downright abrasiveness of Rhys were turned off by the zealous ideology.

      At that time, there was no Mono, and Portable.NET was not yet a part of the DotGNU project, so obviously you're either lying or your memory is severely flawed. Also, while part of the reasoning behind starting Portable.NET was to counter the MS .NET initiative, the rest was "This is pretty cool! I'd love to see an implementation of this in" followed by every OS imaginable; that's why it's called _Portable_ .NET. Mono may mean monkey in spanish but it also means single or one in english, which is appropriate considering how little attention is given to platforms other than x86 GNU/Linux.

      As for bad-mouthing, the only thing the Mono FAQ says about Portable.NET as opposed to Mono is that it the runtime (and compiler) are much less tested. Ximian claims that by developing the compiler and most of the rest of Mono in C#, the whole toolchain has been given a much more rigourous workout than Portable.NET.

      No, it says "It is easier to describe what is unique about Mono:" and then goes into a list of things that mono supposedly has that pnet does not, but which is really not the case. The mono JIT, granted, is unique since the pnet hackers won't begin work on their own JIT until after the DotGNU 0.1 release (later this month or early next month). Pnet does have native unrollers which can _portably_ achieve a high level of JIT efficiency (unrollers are capable of doing everything a JIT can except the trampoline parts, but can be developed incrementally, unlike JITs) and the pnet "interpreter" doesn't interpret IL, which is inefficient, but instead interprets CVM which IL is converted to in linear time during verification. The Mono FAQ fails to list these genuine design differences and instead tries to make it appear that pnet lacks various things it does not. I especially like the "We have a great community of developers, without which Mono would not be possible." comparison point. Implying that pnet doesn't have a great community of developers (albeit a much smaller one thanks to the constant flameage from monophiles) is just plain bs. And just because the pnet compiler isn't written in C# (chicken and egg problems should be left to chefs) doesn't mean it's immature and untested. Pnet does have to compile its own class libraries and those are in turn used by other parts of DotGNU as well as by independant hackers. And if you want to talk about having a "big motivator" for correctness and maturity, try getting flamed non-stop by the competition.

      In fact, I'd say the badmouthing has been much more in the other direction: there used to be a page around on the DotGNU website (not sure if it's still there) badmouthing Mono. None of the claims had any substance. For example, it claimed that Mono was on shaky legal grounds with regards to hidden Microsoft patents, which may perhaps be true. However, Portable.NET/DotGNU isn't safe from those legal threats either. Further, while Mono was developed from the ECMA (and now ISO) specifications, Portable.NET was initially developed by reverse engineering Microsoft's .NET implementation (without any clean-room engineering), putting it at risk of copyright infringement claims as well as patent claims. This was also part of the reason why there was little interest from Mono in m

    2. Re:I beg to differ by TummyX · · Score: 2, Insightful


      WinForms contains a number of window-isms, which the Wine project have already implemented. Reimplementing winelib seems silly and a waste of energy. I can't imagine it'd be appreciably harder to port Mono's WinForms implementation across platforms had it been written from scratch than it would be to port winelib itself. And if winelib gets ported, people other than Mono users and developers can benefit from that work.


      WTF!? WinForms is based on windows controls but that doesn't mean you need an implementation of the entire windows API to implement them. The windows controls themselves can be written in pure C#. The only native part you need is the System.Drawing APIs which can be implemented different for different platforms. There is absolutely no need to have the entire windows API to implement a few basic controls. Also, I'd love to see how they plan on getting winlib + mono small enough to work comfortably on an iPaq.

  38. Re: "It's almost strange to be earning money..." by Anonymous Coward · · Score: 0
    Perhaps the most common way is to actually write the Open Source stuff, and then make your living by:
    • Writing book(s) about things you wrote.
    • Speaking in conferences about things you wrote.
    • Working as consultant specializing in things you wrote.

    I would say these are much more common (and more likely succeed) approaches than trying to directly sell things you wrote (not that that wasn't possible; it's just harder).

  39. Imagine... by Anonymous Coward · · Score: 0

    a beowolf cluster of competitors...

  40. The /. effect by Flingles · · Score: 1

    But hardly anyone seems to have seen the Newsforge posts (except maybe me)

    Not anymore!
    /idiot>

    --
    Karma: -2^0.5 . Mainly due to the imbibing of dihydrogen monoxide
  41. Popularity Contest by drinkypoo · · Score: 1

    The contributions will be judged considering not only the quantity and quality of the contributed code, but taking in consideration also how well the competition participants use the #dotgnu irc channel, the mailing lists and the wiki for coordinating their coding efforts, and for helping newcomers with getting started.

    Okay helping newcomers get started, that's fine, but shouldn't we be judging people primarily on their ability to write code that's useful and easy to read, understand, and extend? I don't think it's reasonable to judge people on their social skills beyond a certain point. (People too abrasive to collaborate with, for example, are reasonably disqualified unless they single-handledly write the whole damn show.)

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  42. Pfffff by Laconian · · Score: 0, Troll

    Look at those paltry prizes. Even if I was the 1337est programmer on Earth, I still wouldn't quit my day job for Open Sores. Add another zero to the end and let's talk. Or three. Or six. $2000.000000! Now we're talking.

    1. Re:Pfffff by Anonymous Coward · · Score: 0

      WELL... Adding 6 zeros to the end just increase your resolution of certainty that it is 2000$ to the nearest six decimals. "Yep! I am CERTAIN that is 2000$ sitting on the table - counted it 3 times. There are no .000001 dollars sneaking in." You really want to make sure the decimal point gives moved to REALLY get some real talking done. Tah!

    2. Re:Pfffff by Laconian · · Score: 1

      Definitely. And when people ask how much your salary is, just tell them seven figures no matter much. Pad zeroes at the front when necessary. You're an instant sensation!

  43. Hint on Windows.Forms by Anonymous Coward · · Score: 0

    Port the SWT library to .net, use the same SWT code from Java.

  44. Wine? by Ed+Avis · · Score: 1

    The article says that the competition is to implement the System.Windows.Forms libraries. But I thought Miguel was doing some work to use Wine to implement this, since System.Windows.Forms (in true Microsoft style) is just a thin wrapper around the Win32 API.

    Oh wait, that's Mono, not dotgnu. But why can't dotgnu do the same thing?

    Or the other work that Mono is doing, a pure C# implementation of System.Windows.Forms using GTK#, why can't dotgnu use that? I thought this .net stuff was meant to be portable and compatible and stuff?

    --
    -- Ed Avis ed@membled.com
    1. Re:Wine? by chochos · · Score: 2, Informative

      DotGNU is trying to implement System.Windows.Forms using only X instead of Wine or GTK#. This should result in greater portability. So they're writing all the gadgets from scratch, in C#. It's slower than using Wine but right now I can build PNET completely on OSX, and I can't still get Mono to work on OSX and even if I did it would only be for command-line and ASP stuff, no GUI available because I can't use Wine on OSX.

  45. Re: "It's almost strange to be earning money..." by Anonymous Coward · · Score: 0

    Yes, but just because you are a good programmer, doesn't make you a good writer/speaker.

  46. Re: "It's almost strange to be earning money..." by Daniel+Phillips · · Score: 1

    As much as I love Open-Source/Free Software, it IS very very hard to make a living making it. I'm not talking about writing code for an employer, and then getting permission to release it; I'm talking about actually making your living DIRECTLY off of making, releasing and "selling" open source/free software, a la Red Hat (who just recently turned a profit for the first time). I'd love to hear some more stories from people who've actually made money by coding OSS/FS.

    Practically all the core Linux and BSD contributors are paid full-time to hack on Free, open source code, sometimes with proprietary coding/design work also as a job duty, in many cases not.

    This trend really started at the height of the Dot-bubble, and many thought it would end with it as well, but surprise, it didn't. There was a lot of job-changing to be sure, but nobody who could hack the kernel stayed without a patron for long. Reason: this stuff is strategic, and getting more so.

    It's not just kernel work either. For example, being a member of the Samba team is pretty much a ticket to full employment. There are dozens of high profile projects in the same category. And finally, any FOSS credits on your resume are money in the bank.

    --
    Have you got your LWN subscription yet?
  47. MonoDotGNUcleosis? by smittyoneeach · · Score: 1

    Parrot will _own_ them both.

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  48. Here is a copy of DSA key 0x7525EC32: by bizcoach · · Score: 1

    Here you go:

    -----BEGIN PGP PUBLIC KEY BLOCK-----
    Version: GnuPG v1.2.2 (GNU/Linux)

    mQGiBD9AEc8RBAC0LUbRgcVpiR5GhIN3yxSHcFIgdnm4s8rj d6 wWqT9/8ATBnk/+
    MzveHn6TDv1s3GU1eWdzJtMuWSJ3LJkUEo pbTGcpMTqDqE53D/ 7WAAtteEqN7JpG
    j2MfjFhGmIp7mvOEK8tPCxwGtUESyJ+ZZ2 2CGdOR3bB91TwMua hXl9lz4wCg8n6G
    eNzxN/pStiOPdmPzYhwuhrsEAJY7bS6YWS yHMV3Tnr3CFWZWlb If60/ew0TZm3Q2 /WD7PUonQg2qPb0DAg7vNjNCf0TPjtWlSBullQQ7hYniiyI0XQ 7fy6ffBedTdsdn
    SieyePuVXaAXvklErnPisBnMo+4HmNV9nf 33DYgsx0imnh/QSc rmqkFX72QI96Fz
    ChdOA/9lXHoZHVCTmJnr18SVkxrwuh8Vdx m4xOkcMLxT6mSPp/ VhTb7D/5T2bgBW
    NY/1nqvV3oLIFH8L8ngk96lbYikIBr7GrW hbzRznkFtQtEy8eK sEysxkuMIxL0c9
    iNt5tWamuVZR66Mabbcu97ChFXIRkSqMs8 uGK9WkWxWsYT9Nd7 Q4Tm9yYmVydCBC
    b2xsb3cgKERvdEdOVSBwcm9qZWN0IGZvdW 5kZXIpIDxuYkBmcm VlZG9tLmJpej6I
    WwQTEQIAGwUCP0ARzwYLCQgHAwIDFQIDAx YCAQIeAQIXgAAKCR ChghW9dSXsMvar
    AKDqy4NAQruhZYB2JxEFW9gnGoQi3gCg59 ex4OoX4BP81JgazH K6YepWJxa5AQ0E
    P0AR0RAEAJaNsiJ0Es+fyCylDyCFvggJ4g aNhHjs5oTxYdfA2y QqKFWb2yTqW7LX
    h6OrrPZPUS37gkQdG+OlQNJ88YZqhS5jiD yPeWb2tUXRs6f/Cz EmVHe8iB3b3pYq
    5nonJhUvGaMJuNS9r1kluJUdFOSZGOLm4K Asjs5Nu7s2Y8+9bK YXAAURA/9nGQYJ
    MxnRl7Av2WAjoef1YV3FCnJ/BGOLTv/rWA NIDKJSJ+xNI//tHk TdA7/cTI/oxrlO
    CEnZLBTpB/jQhwLdHoNLkZ+R5YKIIp2XiA wnUSQq0FM+b6ZUD0 lW87EdKb71DUte
    TL5oUhi8d9Hg79+XIVyFbav+gCmAhiI/3P nUMIhGBBgRAgAGBQ I/QBHRAAoJEKGC
    Fb11Jewy1CAAn1Yfkp0xhB5qQgh5U/37mO jkjOqLAJ9fbHcY5y TB7FFdXbUMlC9M
    ucsqOQ==
    =CsUb
    -----END PGP PUBLIC KEY BLOCK-----

    Alas, this key is only self-signed so right now the fact that the announcement is GnuPG-signed doesn't help too much to ensure its authenticity.

    If you have a GnuPG key which is well-connected to the web of trust, I'd appreciate if you could make a phone call to verify the fingerprint and then sign the key. There is only one family named "Bollow" in Switzerland, therefore it's easy to find my private telephone number e.g. at http://tel.search.ch ... my office telephone number is also easy to find, it's in the .sig of most of my postings on the DotGNU developers mailing list. The timezone is UTC+2, please don't call the private number in the middle of the night. Calling the office number at any time, day or night, is ok (there's an answering machine).

    Greetings,
    Norbert.

  49. No, you weren't involved by bizcoach · · Score: 4, Interesting

    No, you weren't involved in any of the three attempts to establish cooperation
    with Mono.

    The first attempt was made by the DotGNU coreteam and the
    Free Software Foundation, privately, immediately after the existence of the
    Mono project had become public knowledge (that was in early July 2001).

    You must be referring to the second of these attepts, which was not initiated
    by the DotGNU project but by a third party (Martin Coxall)... making Mono part
    of DotGNU was his idea, not ours... both Miguel (the Mono project leader) and
    I posted in the thread which resulted from this proposal, and I got upset about some
    of Miguel's comments, but in retrospect I think it's very understandable that
    the Mono folks were not interested in talking about cooperation in the context
    of such a proposal.

    In April 2002, we made a third attempt to establish cooperation with Mono.
    This attempt was much more promising than the earlier two, and it has involved
    offering a sizeable chunk of pnetlib I18N code to Mono under the X11 license,
    which they have integrated into their class library.

    DotGNU is still open to discussing any mutually beneficial ways of cooperation.
    For example, some parts of the class library could be developed jointly, using
    a neutral cvs server. We have proposed this to the Mono project multiple
    times, so far it seems that the Mono folks are not interested in this kind of
    cooperation. The I18N code which was integrated into the Mono libs forked
    immediately, so that doesn't count as a mutually beneficial form of
    cooperation.

    Your claim about DotGNU Portable.NET being "at risk of copyright infringement
    claims" is totally false. Our procedures have been carefully checked and
    declared ok by a competent lawyer (Eben Moglen, professor of law and legal
    history at Columbia Law School). I do know however what discussion you
    probably remember. Here is how it went: I asked whether Mono has proper
    procedures for reverse engineering (in hindsight I regret having asked
    this question publicly, I now think it would have been much more appropriate
    to ask this kind of question privately), and Miguel replied that the Mono
    project doesn't have the resources for that, and he added a verbal attack
    against the procedures used by Rhys in the early days of the Portable.NET
    project. You really shouldn't be concerned about what Miguel wrote about
    Portable.NET in that message. First of all, reverse engineering for purposes
    of interoperability is always legal in the country where that work was done.
    (EULA clauses that forbid it are legally null and void in that country.)
    Secondly, the early versions of Portable.NET achieved interoperability in a
    manner that (in the judgement of Eben Moglen) would not have violated the terms
    of the anti-reverse-engineering clause even if that clause wasn't irrelevant
    anyway. (We had not informed Miguel about the details. Why should we? He
    never asked.) Thirdly, the code to which these concerns applied has long since
    been rewritten for technical reasons anyway.

    Nota bene, both projects, Mono and Portable.NET, want to be compatible with
    much more than just with what is described in the ECMA specs. So there is
    reason to be careful. I can assure you that I've been working hard behind the
    scenes of the DotGNU project to make sure that we're as careful as we
    reasonably can be.

    I don't know what you mean with the claim "there used to be a page around on
    the DotGNU website (not sure if it's still there) badmouthing Mono." I
    maintain the DotGNU website and I'm sure that we have never had any such
    page. The DotGNU website moved to the Savannah CVS system on July 10, 2001
    and all versions of all website files since then can still be reviewed at
    http://savannah.gnu.org/cgi-bin/viewcvs/projec ts/d otgnu/?cvsroot=www.gnu.org
    Since that website move was just one day after the initial public announcement
    of the Mono project, if your claim was true, the evidence should be there. I
    challenge you to check your claim against the available public record.

    Greetings,
    Norbert.

    1. Re:No, you weren't involved by miguel · · Score: 2, Informative

      Well, a few corrections.

      Phase 1: DotGNU and Mono announced on the same day by the FSF. Mono to work on the framework, DotGNU to do the more undefined parts of .NET. Whatever that meant.

      At this point cooperation was not possible, because it turned out the DotGNU team wanted to invent a new virtual machine that supported Java and .NET at the same time. I could see this as interesting research, but not something I particularly cared about.

      Then we were asked something like `you will work with us better than with proprietary companies'. This is ridiculous in that you cant make this kind of promises. Specially with a team of people (the DotGnu) who had no track record of writing anything of large scale. So to us, a relatively experienced team of developers, being told this by a team of self-appointed "core team" of unexperienced people was a non-starter.

      Phase 2: Portable.NET bends over and accepts every wacky idea of DotGNUers. The idea here is that Portable.NET had to please the desires of the dotgnu kids, so a promise to support JVM binaries at the same time and generating code for both was made. They got this working to some extent, but again, its slow, untested, and very broken.

      Phase 3: the code donation. Mono received under the terms of the MIT X11 license, a copy of the I18N code. A pretty small chunk of code, and lots of data files that come from the IBM ICU library (about 4k lines of code, plus 46k of data files).

      This was the beginning of cooperation.

      The cooperation did not last long, because even when we submitted fixes to them, and pointed them to new codecs, they decided to change the license of their code to GNU GPL, because they felt cooperation with us was useless.

      Licensing:

      We use the more liberal MIT X11 code, which they have liberally integrated into their code base, but since we are commited to eliminate any potential licensing problem that a proprietary software developer might have with Mono, we will not use the GNU GPL or GNU LGPL in our libraries.

      We could not use PNet's code for two reasons: we just plain dont like the coding style (coming from the Linux/Gnome coding conventions), and second the reverse engineering that was done in Australia (what Norbert claims is ok) would put anyone distributing the software in the US under a potentially interesting legal situation.

      It is our responsability to the contributors of Mono who have devoted tons of hours to it, and to the users to make sure that there is not the slightest potential legal problem with the code that would make their contribution useless. We dont want anyone FUDing in the future like its being done with SCO. So we had to have more strict legal procedures.

      For instance, we recommended people not to look at Rotor source code until we had the equivalent Rotor functionality implemented. Pnet follows a different approach: read Rotor, and do a new implementation of it. Might be better for interop, but I sleep better at night :-)

      Miguel.

  50. Re:DotGNU Control Freaks by mdupont · · Score: 1

    I think your right.

    I posted over 57 bug reports to the project, yet they are discounted. Even if 99% fixed.

    Rhys is discriminating against honest help, and I find that he is driving away help. Now they would rather buy help!?

    In any case, now they are trying to use Intellectual property law against would be contributors that they have decided to ban.

    I think that they have forgotten about the principles of free software.

    mike

    --
    Introspection is the key to understanding