Slashdot Mirror

We want the agreement to accomplish three things:

1. Stipulate that the code is being released to the project under the project's license (for our project this is the Apache License).
2. Ensure that the contributor has permission to release the intellectual property to the project, including any necessary permission from their employer.
3. Make sure that the contributor does not apply for patents for the code that they're submitting.

1. Do you see legal value in this sort of agreement?
2. Do you know of any boilerplate agreements that exist?
3. Shouldn't more Open Source projects be worried about IP issues that a contributor agreement seeks to prevent?

I'm a JavaNewbie, but I installed Resin in very little time and have it up and running on a beige Mac G3 LinuxPPC box. Now I'm looking into installing and configuring servlets (like those found at CoolServlets). I'm one of the people who hated Java because it was slow, but don't blame the language for the client-side problems. This URL says it all better than I could: http://www.davidreilly.com/java/java_network_progr amming/#6.

If you are a newbie like me and interested in learning more about Java/Servlets/etc. you'll find lots of links at my blog: Brainspatter.

Curious__George

I am the developer who won third place in the "Best Webapps Contest". While a lot of the winning entries didn't seem to be making much headway, my project was under active development.

I was to deliver 4 milestones to complete my project. The first was delivered in early December of last year and I have yet to receive the payment for this milestone yet. I was assured by John Egan of Collab.net as late as February 22, that I would be paid for it. I have a snowballs chance in hell of seeing that money now.

Milestone 2 was scheduled to be released in two weeks after being integrated into the Jive CVS repository.

Milestone 3 is to begin this weekend when I travel to work with Bill and Matt of CoolServlets to consult with them on the best way to include Moderation in the Jive codebase and integrate with existing Moderation code.

I still plan to do Milestone 4.

For those of you wondering what does the passing of SourceXchange mean for the Open Source world? Nothing. SourceXchange was more of a hinderance than a help to my project. They were supposed to supply every project (mine was #39) with a mailing list. The first time that I saw the SourceXchange mailing lists work was when Brian Behlendorf sent out the SourceXchange announcement that they were closing the doors.

Thank you to the hundreds of participants on our various projects, and to the sponsors who were willing to take a risk on a new model (and who, by and large, got good results).

I certainly doubt that MyComponents.com feels that they got good results from SourceXchange. They got very little from the contest winners (myself included) and I am sure absolutely nothing that would benefit them as a business. If MyComponents made any payments to Collab.net, they should be asking for a refund.

The only good thing to come out of the whole "Best Webapps Contest" was that it inspired the First place winner Rickard Oberg to write WebWork.

I am the developer who won third place in the "Best Webapps Contest". While a lot of the winning entries didn't seem to be making much headway, my project was under active development.

I was to deliver 4 milestones to complete my project. The first was delivered in early December of last year and I have yet to receive the payment for this milestone yet. I was assured by John Egan of Collab.net as late as February 22, that I would be paid for it. I have a snowballs chance in hell of seeing that money now.

Milestone 2 was scheduled to be released in two weeks after being integrated into the Jive CVS repository.

Milestone 3 is to begin this weekend when I travel to work with Bill and Matt of CoolServlets to consult with them on the best way to include Moderation in the Jive codebase and integrate with existing Moderation code.

I still plan to do Milestone 4.

For those of you wondering what does the passing of SourceXchange mean for the Open Source world? Nothing. SourceXchange was more of a hinderance than a help to my project. They were supposed to supply every project (mine was #39) with a mailing list. The first time that I saw the SourceXchange mailing lists work was when Brian Behlendorf sent out the SourceXchange announcement that they were closing the doors.

Thank you to the hundreds of participants on our various projects, and to the sponsors who were willing to take a risk on a new model (and who, by and large, got good results).

I certainly doubt that MyComponents.com feels that they got good results from SourceXchange. They got very little from the contest winners (myself included) and I am sure absolutely nothing that would benefit them as a business. If MyComponents made any payments to Collab.net, they should be asking for a refund.

The only good thing to come out of the whole "Best Webapps Contest" was that it inspired the First place winner Rickard Oberg to write WebWork.

Check out Jive for an excellent example of beautiful coding in Java. There are a lot of forum software packages out there but none as complete (in terms of code design).

I've been able to look at this code and immediately understand, admire and learn from Matt Tucker's code from day one. Makes a good read.

Hey-

If you're interested in Servlets, check out this new site.
www.coolservlets.com
It is all about open-source servlets and they have a few packages available already!
CHET OUT

The book is very good! Also, if you're interested in checking out more on servlets, see http://www.coolservlets.com -- they have some pretty good open source servlets there.