On Mar 31, 2008, at 1:15 PM, Sean Cribbs wrote:
To this end, I want to attempt an experiment. The first step is
that I
would like to open up the codebase for more experimentation. I have
created a clone of the Radiant Subversion repository on GitHub
(http://github.com/seancribbs/radiant/tree/master). I encourage
everyone who is interested in hacking the Radiant codebase to fork it,
make your changes, and send me pull requests. During this experiment,
we will also be maintaining the traditional SVN repo and I will push
changes to it when necessary. For those who are familiar with 'git',
this should be an opportunity to try out that cool feature you've
always
been wanting to build.
This sounds like a fun experiment. Perhaps something should be said
about this on the development home page.
A couple things to note. While I agree that I would love to see
development on Radiant moving forward at a faster pace, I think it's
important to keep the ideals of the project in focus. To that end,
here are a couple of things I think we should keep in mind when
applying patches to the Radiant code base:
1. Code is a liability. It is important to realize that every
feature we add increases the complexity of the code base. The added
complexity costs us exponentially over time to maintain. To this end
we should do everything in our power to keep the code base lean.
Removing extraneous code should be a sport.
2. Features should only be added that are generally useful to the
community.
3. We need to be absolutely brutal about rejecting feature
proposals that do not live up points 1 and 2. Extensions are the
perfect place to work out pet peeves.
4. Radiant is primarily designed for static Web sites (that is,
sites that are not dynamically generated). It is not, and should not
become, portal software.
5. Clarity and beauty should be valued over brevity. I would like
to especially encourage people to submit patches that "clean up" the
code base.
That said, I'd like our basic ground-rule to
apply, namely, that any patch you submit should have adequate specs.
Amen to that.
The second step is that I am going to start restructuring my time to
give Radiant the TLC that it needs. I want to be a more nurturant
parent. Earlier this year, John Long asked me to take
responsibility of
the programming aspects of the project so that he could focus on the
design. In recent weeks I have found that I am not logging a full
40-hour week on my projects, and yet Radiant is not moving forward.
Therefore, I will block out one day a week (Friday) to spend tending
to
Radiant. During this day each week, I will be developing the
codebase,
addressing tickets and patches, and possibly working on a podcast. I
also intend to have "office hours" on the #radiantcms IRC channel on
FreeNode all day (8AM US Central to about 6PM).
Three cheers for Sean! He is by far the most frequent committer of any
of the core team members (including myself). I can't believe he is
planning to devote even more time to the project. He deserves a medal.
--
John Long
http://wiseheartdesign.com
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
