What are our goals for 2.0 and how can I help?

17 views
Skip to first unread message

Johannes Fahrenkrug

unread,
Mar 15, 2012, 6:11:29 AM3/15/12
to Radiant CMS: Dev
Hi,

I've seen that Jim has created a 2.0 branch a few days ago.
What are our goals for the 2.0 release?

These are the things I would have in mind:
- Moving to Rails 3
- Easy but solid role-based permission system
- Better ability to invalidate the page cache for select pages
(instead of purging the whole cache)
- Making the sites extension a first-class citizen (possibly shipping
it as a default extension)
- Performance improvements

How can I help?

Cheers,

Johannes

Jim Gay

unread,
Mar 15, 2012, 7:06:33 AM3/15/12
to radiant...@googlegroups.com
On Thu, Mar 15, 2012 at 6:11 AM, Johannes Fahrenkrug
<jfahr...@gmail.com> wrote:
> Hi,
>
> I've seen that Jim has created a 2.0 branch a few days ago.
> What are our goals for the 2.0 release?
>
> These are the things I would have in mind:
> - Moving to Rails 3

Yes! By turning Radiant into an Engine.

> - Easy but solid role-based permission system

Not really. I'd like to allow you to provide your own user system.
I think we should be able to pull radiant into an existing project
with an existing user system and only need to provide some glue.
For example if you already have a "users" table and are using
something like devise, why not just hook into that for radiant?
However, I do want to pull out our user system as an extension to
provide an easy upgrade path.

> - Better ability to invalidate the page cache for select pages
> (instead of purging the whole cache)

Yes.

> - Making the sites extension a first-class citizen (possibly shipping
> it as a default extension)

I haven't looked at sites lately, but yes. We should support multiple
sites by default.

> - Performance improvements

Yes!

>
> How can I help?

I spent some time doing a rebase of the old rails3 onto version 1.
There's a branch called "rails3rebase" that should have some valuable
things in it, but be forewarned that I wasn't too careful about what
was moved around. My goal was to just pull up the changes in the
rails3 branch to a later baseline.

I pulled snippets out into an extension and I'd like to do the same
with layouts. Pages don't *need* layouts, and we could even assume
that if you add radiant to an existing project, you'd want to use your
existing rails layouts. Layouts should be more flexible.

A path to follow would either be, pull out users and layouts for a 1.2
release and so that there is less code to worry about for rails 3, or
work on getting rails 3 going now.

As far as 2.0 goes, if it's not tested, delete it. I want to get this
codebase smaller and easier to understand.

Thank you for your help!

>
> Cheers,
>
> Johannes
>

--
Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC
571-403-0338

Reply all
Reply to author
Forward
0 new messages