distribution profile

Hi,

Just wanted to pop my head in and let everyone know of the new release of ProsePoint (www.prosepoint.org), a CMS for publishing online newspapers and magazines.

If you look closely at ProsePoint, you'll discover it's derived from Drupal. In fact, it's a Drupal distribution bundled into a single tarball for easy download. Of course, that means there's third party code in there, but it's all in the name of making life easier for end users.

Hi,

Just wanted to announce the availability of the first (alpha) release of ProsePoint, a newspaper content management system.

Some things to note:

ProsePoint is a distribution built on top of Drupal 6.

It is currently alpha software and this is the first release. Hence, there are most likely all sorts of bugs and design inefficiencies. Please be welcome to try it, but use at your own risk.

It has the most customisation and add-on functionality of any distribution that I know of. The eventual aim is to have everything ready to go out of the box. No more searching for extra modules or testing of combinations of modules. Just install and go!

Hace un tiempo que estoy desarrollando un foro en Drupal con funcionalidades similares a los que todos conocemos.

Durante este proceso documente todos los pasos para crear un foro con Drupal 5.2.

Check it out here: http://drupaled.alphabetademo.org

The site can function as a blogging platform, a podcasting platform, a wiki, an informal learning space, a course management space, and/or as a replacement for an organizational intranet. Within the site, users can create working groups or communities of practice. The site also supports social bookmarking. The homepage of the site gives a more complete overview of the functionality.

It's looking like there's already a ton of interest and excitement pertaining to install profiles and distributions. As Drupal groups seem to be an ideal platform for collaboration, I'm thinking we should continue to figure out/define some best practices or rules of the road pertaining to keeping the communication open while keeping the signal to noise ratio high.

I'm assuming there are no clear answers or set guidelines, but here are some questions...

This (somewhat old) post from Zacker does a great job summing up a catch-22 that comes along with an open source community like Drupal (allow me to excerpt):

<

blockquote style="font-style: italic">

• most of the value created by the Drupal community that vendors and consultants rely on to sell as services to customers come from unpaid core contributions
• many of the seasoned Drupal core hackers are getting job offers left and right to come and do Drupal consulting full time.
• This is creating a scenario in which while many more people are paying their bills through Drupal hacking and more and more business are built around business value created by the Drupal community, it is not getting any easier to make sure the heavy lifting on core work is getting done.

What can we do now to make sure that some of the money coming into the community over the next year is put back in to supporting the core work that we as a community are relying on?

Well, probably one of the biggest sources of information for this group is the page in the handbook:

HOWTO: Write an installation profile for the Drupal installer.

I'm not sure how recent that document really is, though. The most recent version is from June. I may have to try it out to find out the status.

Hey, everybody!

Maybe someone will recognize me; I post here and there, but I would like to begin by pointing out that I did not create this group because I want to moderate it or set it's agenda; I created it so that one was available and I see my role as keeping track of what kind of Drupal distribution profiles are being developed or discussed and then reporting that information back to this group.