Distributions

Is anyone working with OC in an Aegir workflow? I have questions related to that which may just be due to my lack of familiarity with the distro process. I attempted to create a platform using git clone because I wanted to test the latest version. I directed the platform to the openchurch.make but it failed. Is there a particular make file I should set the front end on or should I build the core and distro. Any help in directing me to a more efficient workflow would be greatly appreciated.

Several people have expressed interest in contributing back to the OpenChurch project.
The great news is that now with Apps, there is a functional way for 3rd parties to add their own modules/apps to OpenChurch as a way to extend functionality without baking everything into the core project.

See App Store screenshot: https://twitter.com/#!/drupalninja/status/184011723102101504/photo/1/large

At the Drupal for Churches BoF (at DrupalCon Denver), we discussed the idea of discussing things like OpenChurch and Open Parish (and things that would revolve around Church-specific distributions and features) on Groups.Drupal.org. Here's a quick post just to kick off the discussion!

As some of you have already gathered, I'm developing a Drupal distribution for church websites.

One of the early decisions I would like to make is whether to require users of church websites to use their real name. I feel usernames give a false sense of being anonymous and have a tendency to encourages internet flame wars or otherwise cause people to act less composed then when they use their real names. In addition, church websites should be extensions of their physical communities and real names help easily associate virtual users with their physical counterpart.

It seems the variety of options to create some sort of distro or feature set or pattern or template or whatever are broad, but one thing that is united under all of them is the need to collect a list of what sort of features should be included in this. So what features do you think every or most church websites should have. Let's stay away from modules, how it would be accomplished.

This is a question about defining the problem. We can figure out how to solve it later.

Our church is going to re-do their web site and I sold them on doing it with Drupal, so I am now charged with the task of making it happen :)

I thought I'd create a discussion on g.d.o. that would document my process in a way that might help others as I go along.

Okay, I say lets do it. There seems to be need and interest, and a reasonably well defined list of basic requirements to get started. I'm gonna start with this post as a basic list of requirements, and go from there. My basic list of modules is there as well. I've started a basic profile and gotten the following modules to use:

audio*
bloginfo
calendar*
cck
coder
contact_list
dblclick
event*
focus
forward
front
image*
logintoboggan
og
paging
panels
pathauto*
simplenews*
upload_preview
views*
views_bonus