No problems Sean. I will also be there, so if you need on-demand input,
just shout out.
answers within
Sean Corfield wrote:
- copyright / assignment / contributor's agreement etc
- GPL - with a classpath-style exception (GPL3 section 7?) to allow
redistribution of apps with OpenBD bundled
http://wiki.openbluedragon.org/wiki/index.php/Contributing
http://www.openbluedragon.org/zerocost.cfm
As for the GPL, we are basically protecting the core engine from other
parties simply lifting code using it, and not contributing back. We
believe in fairness, and don't want the fat kid at the party to eat all
the cakes. We have no interest in forcing your CFML applications to
be GPL; you are free to use whatever license you wish for that.
- Copyright: TagServlet Ltd
This is the holding UK registered Ltd company
- Do you have a "Contributor's Agreement?
Yes.
- contributors, committers and the patch submission process
- My understanding is that aw2.0 / TagServlet employees are the only
direct committers at present?
No, aw2.0 and New Atlanta people have full commit access. Steering
Committee members have commit access to the test suite.
- Contributions are accepted in the form of patches, which are
reviewed by the committers?
Yes, we have a our Code Tzar (andy) that makes sure nothing "naughty" is
contributed that would cause problems elsewhere.
- Direction for the language comes from:
- aw2.0 core team
- Steering Committee
- openbd mailing list
- Trac submissions
- other?
All of the above, including our users of the engine that will email us
directly. The CFML community does not seem to want to be heard
publicly for some reason. There really is a silent majority.
Although i would caution that the order of the list does not necessarily
imply the most direction.
- Issue tracking is managed on Google Code
Yup.
- Source code is under SVN on svn.openbluedragon.org
- core vs extensions
- core is OpenBD server
- there is an additional GAE-compatible variant of the core server
- work is ongoing to merge GAE-compatible and core server where possible
The Core Engine _includes_ the GAE runtime. We no longer make a
distinction.
- there are a number of official plugins
Correct, these are typically pieces of functionality that should maybe
be in the core engine, but are left as a plugin to let them evolve at
their own pace.
- any third party plugins?
Yes, quite a significant amount of work has been done on true
MS-Exchange plugin. There are smaller plugins that have been submitted
too for integration into the likes of Facebook and Twitter.
- 3rd party libraries - any portable CFML library (so it's
essentially a free-for-all as is true for most open source
communities)
Not quite sure what you mean there? From a Java point of view, no,
because unless you write to the old Allaire library, then no library
will work across all the engines. As for CFML code ... isn't that the
CFML community as a whole?! MachII etc.
Or do you mean the old trick that ACF does which is ship a series of
CFC's and pretend they are part of the core engine? Like http/query
support inside of cfscript.
i wouldn't feel clean/ethical doing that with any OpenBD releases.
- releases and testing
- twice a year (April 27, October 27)
- source access (SVN)
- nightly builds (1.5)
- stable (1.4)
Correct, we celebrate the initial release of our engine to the open
source world every year with a new release. We do this on a 6 monthly
basis as there is just too much goodness to hold back on for a full year.
- community& commercial support
- via the openbd mailing list (~600 members) and the general OpenBD community
- commercial support and professional services available from aw2.0
Yes, and again, many people will email us directly. Yes, you can
purchase support from us, including purchasing feature development ahead
of our roadmap, if you need it now.
- a commercially licensed version of OpenBD is also available from
aw2.0 (my assumption?)
No, aw2.0 does not provide a commercial version. New Atlanta provides
commercial versions for J2EE and .NET. These are completely separate
code branches from the OpenBD branch, and by-in-large, completely
separate products.
aw2.0 is not in the business of CFML. It is not our core business. We
are a Java house focusing on high-performance massive-volume cloud
enterprise solutions. CFML is just but one tool in our arsenal that we
utilise to provide some of these solutions. But aw2.0, as a company,
does not make any direct revenue from OpenBD.
Hope that helps Sean (and anyone else that is reading).
See you in Texas!
--
tag/function ref: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
