For those who have not read Status update post and discussion that followed here is a short list of most important decisions that we announced:
This announcements raised a lot of concern in the community. Main problem with Status update post is that it is brief and without details on what we are doing now and how we plan to structure the project in the future so most of the people got only a blurry image of what is happening and that caused a lot of confusion. I've posted a followup comment with more details on questions that people asked but decided to republish it as a separate blog entry so everyone can read it (thanks to Dan for a suggestion). So, here is the list of most important questions raised by the community and explanations:
We never said that. Version that you can download and install on your own server will be available (free and commercial versions).
What we said is that beta testing will be done in hosted environment and we have a really strong reason for that decision:
Usually process for installable software: Pack a release, release it, support upgrade and installation, wait for new features and bug fixes to accumulate, pack another release, release it, wait for people who upgrade their installation just two weeks ago to finally find time to download new version and install it, provide support to people who are upgrading, see how it works… Repeat!
We don't want that kind of overhead in development process so we decided to go with hosted environment where we can provide bug fixes instantly and roll out new features as soon as they are ready for testing. As soon as we get ready for testing public announcement will be made and people will be able to sign for an account. We will have limited number of accounts (server resources are limited) so please subscribe to RSS feed or to our newsletter to get notified on time.
1.0 has been under development for some time now (about a month or so) and it already has plugin support and thanks to RESTful approach the whole application is one big API. Plugins are mini applications that hook into the system (like time tracking, invoicing…) and system provides a great number of hooks that let them handle events thrown by system or other plugins. I would dare to say that with 1.0 version activeCollab is finally extensible.
Development of core features will be handled by new company, but it does not mean that source code will not be available. With plugin support in place it is really important to give people something they can learn from. Having code available would help them better understand how system works. That will eventually result in some cool plugins and implementations and we want to support that.
We will make sure that developers get access to the source code, but that does not mean that it will be available under the terms of classic open source licenses such is GPL, LGPL, MPL... There are a lot of communities that work this way - vBulletin, IPB, Expression Engine etc. Developers have all the resources they need to develop their own functionality on top of the system, but the system itself is still the property of company who develops it. Some may think that open source is superior than this approach but just looking at projects that are structured this way shows that it works pretty nicely, even better than some open source project that they compete with.
Line will be drawn between common features and business features. Unless you need business features free version will do just fine (most home users and non profit organizations will not notice the difference). If you need activeCollab for your business you will be able to develop all the features you need as plugins or to go with Business edition where you get commercial support and additional, business related plugins. Commercial versions will be reasonably priced.
If you really think this way you will be really surprised when you see first screenshots ;)
We plan to blog about how development is progressing. We definitely want you to know what cool stuff we are building so sound recording hardware and screen capturing software is in place. Consider it as one new media / software development experiment.
Hope this helps. If you have any further questions or need more info than it is provided in this post please post a question in comments, but note that even we don't have all the answers at this moment.
Will they be able to import current projects into V. 1.0?
slajax said:
...the only way I would contribute to the 1.0 project is if community developed business plugins were GPL’d. Seeing as you’ve already said that this won’t be the case…
Doug Farnes said:
I probably missed something, but is that the case? Expression Engine developers can GPL their own modules. I’m pretty sure that you can even create add-ons and sell them as well (just not bundled with EE). Will that not be allowed with activeCollab?
Will they be able to import current projects into V. 1.0?
Of course.
Of course it will be allowed. You can sell your plugins or give them for free if you wish. It is completely up to developers to decide whatever they will sell their plugins and services or give them away for free. bq.
Doug Farnes
The entries from the blog show up as new in Bloglines for me as well.
Now that you mentioned Bloglines, I played with it a bit and there is a setting when you are adding a new feed witch says to Bloglines what to do with updated entries – mark them as new (default) or ignore them. You should select ignore…
acuserguy:
Will the free version of 1.0 have at least the same functionality as the current version 0.7?
acuserguy:
Will the free version of 1.0 be installable on any server or have a fixed hosting requirement?
acuserguy:
What will the price be of the business version, and what additional items will we get for that price?
Perhaps I am naive, and this was the business model all along. i.e. Build a community for the free software during early development and testing, then close it up just as the project matures.
If you have something important to say about the issues discussed in this post please write at hi@a51dev.com.
Although most people think that a private core is bad for the project, I think that it’s actually beneficial since it’s a huge motive for the development team. Go for it mate :)