...get it working in Rails 3?

[Dean Satchell]

What I've been able to gather from reading the posts in this forum is that the radiant community want Radiant and its extensions to become engines. There has been brief discussion about major surgery vs a rebuild with no subsequent discussion. Is nobody sure quite what to do next? Noting that the master branch has been broken for 5 months and Radiant refactor hasn't been touched for over a year now, is Radiant stagnating? If so, what can be done to resurrect this project?

My thoughts are that a strategy needs to be in place. William Ross's thoughtful post might be a good place to start. However is this forum the right place for consensus decision making?

Some initial questions I have:

Is there a group of core of developers remaining committed to this project?

Is someone prepared to take the lead and get the ball rolling?

Looking at the posts there are clearly some decisions to be made:

Preparation for rails 4 or just get it working in Rails 3?

What is the best way to open the code up to the community:

A clean branch having no history in radiant/radiant?

Fork it and create radiant/radiant-refactor? 

Follow an upgrade path, or is radiant 2 a new creature?

I'd suggest that before anybody could possibly contribute there needs to be consensus around the development choices. Things like how to deal with extensions, backwards compatability etc. Who should lead robust debate that results in decisions? Is anyone even interested?

Okay, so even if some initial decisions were made around structure, how would the project be broken up into clean chunks that individual contributors can get their teeth into and feel they are part of a team? Is co-ordination the key role of the project leader rather than simply chief developer? 

As in all things in life, nobody wants to participate unless the direction is clear and positive...