Good to see this. You'll not be surprised I'm in favor of an as-early-as-possible upgrade to Rails 3, and I'd like to help for that. Maybe we could have a 1.1 announced as a RC so that people have the time to upgrade plugins ? Is somebody working on the idea of a plugin directory (it could help if we had something like http://railsplugins.org) ?

About the main features, everything you say sounds great. There's a couple of things I'd like to work on :

add a permission-like system for notifications : today there's no single point of passage to decide whether notification should be sent or not, it's a bit scattered in the code, and building simple plugins to tweak that is not easy at all. As a first step I'd like to rewrite it with no more user visible functionalities. I'll propose something about that to have feedbacks before integrating this. I hope I have the time before 1.1.

I think it might sense to wait on that to give plugin developers time to migrate as well.

My schedule gives them (me) 3 months to upgrade and migrate. That should be plenty of time.

Jean-Baptiste Barth wrote:

Good to see this. You'll not be surprised I'm in favor of an as-early-as-possible upgrade to Rails 3, and I'd like to help for that. Maybe we could have a 1.1 announced as a RC so that people have the time to upgrade plugins ?

When 1.1.0 RC releases, I'd like to have most of the active plugins ready. Either new releases or a branch to support Rails 3.

Is somebody working on the idea of a plugin directory (it could help if we had something like http://railsplugins.org) ?

It's been discussed a bunch. I'm trying to slow down my business a bit so I can take some time to get something up.

About the main features, everything you say sounds great. There's a couple of things I'd like to work on :

Sounds good. I've talked with a client about moving the Admin Projects interface to become the main interface at /projects. That should help make feature development for the Projects views a lot easier.

add a permission-like system for notifications : today there's no single point of passage to decide whether notification should be sent or not, it's a bit scattered in the code, and building simple plugins to tweak that is not easy at all. As a first step I'd like to rewrite it with no more user visible functionalities. I'll propose something about that to have feedbacks before integrating this. I hope I have the time before 1.1.

I have something similar in production already. It adds a single method on User that takes an object and returns true or false. It's only used with Issues right now but it can easily be extended to support any object in Redmine. A plugin API for adding new notifications sources would be pretty nice too.

Implementing API for time entries will be really great! One of the main reasons to use external API is to track time (redmine client app, for example) and adding API for that will be very useful. Maybe someone will create something like JiraClient for Redmine.