OpSim, as you know, soon petered out - working for free means that there
are always other pressures, and using Pascal meant that some possible
helpers chose to look elsewhere. The originator of the idea of 'Sim42
reborn' posted on http://opensource.cheme.info/ his thoughts on the
OpSim outcome.
As a note, Sourceforge has several attempts to build a Sim42 follow-on:
http://sourceforge.net/projects/ollints/
http://sourceforge.net/projects/opencheese/
http://sourceforge.net/projects/opsim/
And on an associated note, for wastewater flowsheet modelling, we have a
further two:
http://sourceforge.net/projects/killarney/
http://sourceforge.net/projects/openwwtp/
These have yet to deliver, and I haven't looked at the checked-in code.
Hi,
Best regards,
Christoffer
-------------------------------------------------------------------------------------------
To read our latest newsletter visit http://www.wrcplc.co.uk/default.aspx?item=689 - Keeping our clients up-to-date with WRc's business developments
-------------------------------------------------------------------------------------------
Visit our websites www.wrcplc.co.uk and www.wrcnsf.com, as well as www.waterportfolio.com for collaborative research projects.
-------------------------------------------------------------------------------------------
The Information in this e-mail is confidential and is intended solely for the addressee. Access to this e-mail by any other party is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on the information contained in this e-mail is prohibited and maybe unlawful. When addressed to WRc Clients, any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing WRc Client Agreement.
-------------------------------------------------------------------------------------------
WRc plc is a company registered in England and Wales. Registered office address: Frankland Road, Blagrove, Swindon, Wiltshire SN5 8YF. Company registration number 2262098. VAT number 527 1804 53.
-------------------------------------------------------------------------------------------
We looked at licenses and understood that we could not use code from
Sim42 without addressing the attribution portion of its license if we
were going with the gpl. But then, it was pretty obvious that the
people involved did not want to use python so this was not too big of
an issue.
Eventually, we also wanted to use Open-CAPE as a guideline. I agree
with Hazem that Open-CAPE was too complicated for what we needed as a
starting point.
There was a lot of discussion about the language. Several each
wanting Visual Basic, C#, VC++. We had a poll and FPC/Lazarus won
(think 3 people voted for it).
Thanks for the link to Hazem's thoughts, I had not read that.
My advice for anyone wanting to start on something like OpSim (or any
open source project for that matter):
Don't announce anything. Don't form committees. Don't take votes.
Don't spend time having long email discussions on the name, language,
database backend, requirements, license, etc.
Write code in whatever environment makes you productive.
When you have something that works for your minimum set of
requirements, announce it and let people adapt to your decisions if
they want to contribute.
Fixing and extending is much easier than creation. Having 12 people
argue for days about the name of a program then 9 disappearing when it
comes time to code is incredibly demotivating.
Matt Henley
Just to clarify. GPL code cannot be legally used inside closed source
projects if that project is distributed (such as selling a binary
version) as closed source programs don't by definition don't meet the
GPL's requirements. However, if a company wants to use gpl'd code for
an internal project (as long as they don't distribute), that would be
allowed.
It would legal for others to sell your work under the GPL as long as
they abide by the rules of the GPL. Of course, their customers could
redistribute the code for free.
You as the author, however, could issue the code under multiple
licenses. Trolltech's (now Nokia's) QT is a prime example of this, it
is GPL for GPL projects and they also sell it as commercial product.
However, if you go this route you have to get the people who might add
code to allow for its inclusion into your commercial product. This is
usually done by requiring they assign copyrights to you.
The standard way to make money from open source projects is to have a
customer that wants a feature and is willing to pay you to write it
and include in the GPL'd program or in a non-distributable internal
version, if the bit they want is proprietary.
What I have written is my understanding of the GPL. I recommend you
read at least the FAQ for it before releasing anything, here it is in
Portuguese http://www.gnu.org/licenses/gpl-faq.pt-br.html but I am not
sure it is as complete as the english version:
http://www.gnu.org/licenses/gpl-faq.html
Matt