-
Website
http://fredbrunel.com/journal/ -
Original page
http://fredbrunel.com/journal/2007/06/what-are-the-best-tools-for-project-management/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
jaampool
1 comment · 1 points
-
Brandon
1 comment · 1 points
-
Daniel Ha
1 comment · 396 points
-
Busby SEO Test
1 comment · 1 points
-
Mark Douglass
2 comments · 2 points
-
-
Popular Threads
Also, I always use CruiseControl so everyone know that breaking the build is BAD! and fixing it is always priority #1.
And at http://www.standoutjobs.com we're starting to use Campfire for sharing code and ideas. with great success I think.
We also use nightly builds and continuous integration as part of our development process.
I like Campire very much. What makes Basecamp great is the integration of these services in the context of your project.
But we still haven't made our mind.
it was obvious for everyone here at mobiluck.com that efficient data manegement tool was part of the success of our dev effort. As soon as i joined the companyy i've made basecamp hq as the central db of the company. No more plethoric-hard-to-track to do lists. No more mail torrents, no more i-told-you-thisk-2-weeks-ago thing. Now everything is stored once, up-2-date. Specs included.
That's not perfect though. But productivity dramatically improved.
about the activeCollab project, you're comment is a bit misleading. The licence will remain free, but like many projects of its kind, you will have the possibility of paying for commercial support. It's using a derivative of the GPL. Hopefully, we can convince the author to switch to GPLv3 now that it covers a loophole the HPL wanted to seal, thus making its licence compatible with more software.
@robin I don't think the activeCollab 1.0 will be under GPL, it will be a commercial licence only -- or do I misunderstand something?
"Making money. I find it normal to expect something in return for your work. activeCollab will always be free but there will be commercial support as soon as we hit 1.0 for people who need a little more that community support, you can hire me to customize activeCollab to fit your needs or help you integrate it with system you are already running on your server. Or you can just see what I can do and hire me for some project not related with activeCollab."
It's pretty rare to go from a free licence to a proprietary one and to announce it in advance. It doesn't help get collaborators on board :)
Also, it's not GPL but HPL, which is a derivative of the GPL, much like the Affero Licence, which addresses distribution as a service. The GPLv3 too addresses that loophole, that's why I'm hoping it will be changed from HPL to GPL with an upcoming release.
The page you quoted was posted on 18 June 2006. Since then Ilija Studen has had quite a change of mind and is moving the software to a commerical license starting with the largely rewritten verion 1.0. A free to use version will be available but it will be of the Lite variety, while all "business features" will be available on the commercial license. The source will be available but from the sounds of it, under a pretty restrictive license.
0.71 is still available under the GPL and Project Pier are trying to fork from that code. But from the looks of the website, I've personally no hope of that project taking off anytime soon.
See these posts for clarification:
Status update
Status update followup
I don't care about freeware as you probably figured. It's free software (open source, call it what you want) for me or nothing. Of course, the licence is always in the hand of the developper and I respect that.
I'm surprised I didn't see the followups you linked to. I'm not perfect :)
Thanks also for the link to Project Pier, I will keep an eye on that.
Just found out that ToughtWorks (Martin Fowler company that just hired Ola Bini from the JRuby project) offer an Agile PM tool : Mingle.
Maybe it's worth having a look http://studios.thoughtworks.com/mingle-project-...
Cheers - c.
No project can go without a build and release management system. Our Parabuild may be a good option to address this need: http://www.viewtier.com/parabuild.htm
Regards,
Slava Imeshev
You are welcome.
As I see it, automated build and release management (this includes Continuous Integration) is the last untapped source of significant increase of productivity in the software development life cycle.
Tools-wise, we've gotten it covered from the requirements gathering to CM and issue tracking. Build and release management adoption is still (yet?) dragging behind. Only the finest software organizations are already using it.
Regards,
Slava Imeshev