Thanks for describing how Medsphere is carefully examining its investment in
each area of the platform for rich client development. I have these two
suggestions about licensing variety.
1. The line in the sand between personal/investigative use and "commercial use"
(which is presumably any deployment in production with monetary exchange).
This is often a traditional distinction, but that positioning of the
*line* may limit use by a known competitor at the price of stifling possible
collaboration between various providers who are not serious competitors, all
facing a large and varied pool of demand. It seems to me that commercial
deployment *within limits* is exactly the kind of community of users that
Medsphere would want to support and favorably license, so that feedback is
coming from a variety of installations with their particular goals of vertical
application development.
To address #1 a license might be limited to a single or (limited number of
commercial deployments) as a way to amplify your software investment and network
of contact.
2.Community record keeping
One would hope that any license where there is a high demand for use would
be widely deployed, but perhaps the problem for a pioneer developer is not how
much the cat is out of the bag, but how much the pioneer knows about deployment
and the potential partners that exist anywhere. This means that some terms of
the license should provide means to *know* about deployment. This is in the
realm of registration etc. but all of that success depends on the leading
pioneer putting into place the database and communication tools for the user
community to be known and to know itself...or to assure that the community is
doing that in a way that meets the needs of the original creator.
I am sure you all deliberate these and many other points of open source more
than I .Since you welcomed suggestions in your post, I figured to just voice
these two and look forward to your future discussions.
Rusty Maynard
Todd Berman wrote:
On Wed, 2005-07-27 at 15:00 -0700, Jim Self wrote:
Todd Berman wrote:
As I said before, we are in the process of open-sourcing pieces of our
work. I have been involved in a decent amount of meetings over the last
couple of weeks that show real progress towards something that will be
beneficial to everyone.
Can you say yet what parts will certainly be released and what parts will not
be or are in
question? If there are questions regarding the server or middleware, would they
be eased
by development of the RPC function on M2Web?
The current thinking is to release both the middle-ware and the client.
However, the licensing on the two would be very different. We would like
everyone to be able to take advantage of the middleware, as it does
provide a *lot* of needed functionality (and more going forward). So I
believe the current thinking is GPL on that. However, the client itself
is much more of a investment for us, and I believe currently we are
thinking about going with something like a non-commercial license with
very easy licensing terms. There are several reasons for this, which I
wont go into deeply here, but mostly it comes down to preventing a
company like SAIC to go ahead and snag what we have done. However, this
is all speculative at this point, and could change pre-initial release
and post initial release. If you have any licensing suggestions, feel
free to bring them up. We are still attempting to work through various
issues while continuing to actually get *real* work done.
--Todd
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
