Is a release still in the works? At the summit meeting it was stated that
biggest thing holding up a release was the WM licensing issues. Is this
still the case? I would like to be able to contribute to the release,
unfortunately I am tied up with deadlines. As a Turbine user and not a
core developer, I will admit that it is difficult to coordinate a project
with Turbine as it stands. I would really like to say I am using release X
which is known to have certain properties and not a random build that I
pulled from CVS. If I posted something like, "I'm using a build from 620
and I'm having a problem, is this known?" I would probably be told to get
the most recent build. But this isn't practical since it often means
changing my code to meet a new interface. I can't do this if I am going to
production.
I personally think it would help the adoption of the product if an official
release was made. Is this going to happen if WM is released with an
acceptable ASF license? I would interesting in knowing what is happening
"behind the scenes." Not knowing much about copyright law, can the GPL be
revoked once code is released with the license? I thought the GPL was
structured in such a way as to prevent this. Collab.net isn't going to
make a monetary deal with Jason to change the license are you? Now that
could be weird.
~christopher
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
