OK, we promised. Here on this blog, and to customers and partners too. Sure, we will release it. Just a few more weeks. Days! Well, this year, for sure. Of course, when you start promising stuff, life makes sure you'll be too busy to keep them. But this year, by all means, was not a bold promise.
So here I am, on New Year's Eve, copying the last few license files to our repository:
https://svn.re-motion.org/svn/Remotion/trunk/
Q: What took you so long?
A: Other stuff got in the way. Plus, this is a large code base, with different licenses for different components. First, we had some funny ideas how we could get away with a single source file license header for multiple licenses, just to make our own lives easier. After dropping this idea, it turned out that we still had to restructure our repository, or nobody would understand which license applies to which part.
Q: What do you mean, multiple licenses? You told us it would be LGPL, didn't you?
A: The re-motion core framework is licensed under the GNU Lesser General Public License (LGPL) v3. This includes mixins and a lot of stuff that we have not blogged about yet, like our O/R mapper (re-store) and our ASP.NET libraries for data binding (re-bind) and control flow (re-call).
This includes everything in https://svn.re-motion.org/svn/Remotion/trunk/Remotion/
There are two components that we're releasing under the GNU Affero General Public License (AGPL) v3: An access control facility (re-strict) and a document management system (re-vision).
This includes everything in https://svn.re-motion.org/svn/Remotion/trunk/SecurityManager/ and https://svn.re-motion.org/svn/Remotion/trunk/Dms/
Q: When are you going to provide some documentation about all of those components?
A: Next year.
Q: Wait: does that mean New Year's Eve again?
A: Oh very funny, but fair enough. No. We have a large amount of documentation for re-strict re-store, re-call and re-bind already. Fabian is going to blog a lot about mixins (he promised!). Documentation for re-strict is next on our list. re-vision will take some time, we only have the client-side components checked in yet, the server-side stuff is still in the realm of an individual project's repository, as is the upcoming human workflow library (guess what: re-flow).
Q: What are your next steps?
A: I believe the most obvious feature missing from re-motion right now is a nice little community site. We will have to overhaul our development process to, so that outside contributors have a chance to catch up with what we're thinking and planning.
Q: I cannot access your repository.
A: Make sure you don't forget the 's' in https.
Enough for today, see you next year! I'm going to see friends who have a little house with a very nice view over Vienna. Let's see how the city celebrates our release! ;-)
Happy New Year!
- Stefan
Edit: It's re-store that we already have documentation for, not (yet) re-strict