So - does anyone volunteer for the following
not-so-fun-but-very-important tasks?
- Writing Install / Admin doc's for newbie admins to go along with the
kit's.
- Working on an install script / package for newbie admins.
-Zack
-Original Message-
From: Shannon Little [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 26, 2003 10:39 AM
To: Zack Rosen
Subject: Re: [hackers] A Proposition
I'd strongly...VERY strongly suggest that new and better installation
instructions are included. Don't depend on the drupal instructions
because they stink and are confusing for the average person. Like I
said when I first joined...I had installed a lot of php scripts before
and installing drupal was a total pain in the kiester. If any
announcements are made before the ease of installation issue is dealt
with the group is going to be totally bogged down with answering
install questions and it will interfere in the ability to get the tools
done. There also needs to be VERY clear instructions on how to set up
the forum and various modules that use taxonomy. I just finally got
the forum working last night because the explanations in the taxonomy
admin section don't tell you what vocabulary to use. Suggestions
should be added that tells people what vocabulary should be used for
which module that requires taxonomy. Drupal is a great CMS, but it's
not nearly as user friendly as others. I think there will be MANY
people who will want to utilize the tools...so it's important to make
things easy to understand for those of us who are a little technically
challenged. Just my two cents.
On Saturday, July 26, 2003, at 02:27 AM, Zack Rosen wrote:
So here it is. Say what you think. If nobody objects, let's do it.
If
there are concerns, let's figure it out. If it is unworkable we
forget
it.
Basically I am proposing we dissolve the H4D working group and
reform
the organization as the Dean Space development community. This
entails:
1) Setting up a new Drupal site on deanspace.net / org
2) Get new mailing lists / forums / communication means to use for
development discussions set up on the site and shutting down H4D's.
3) Figure out how we are going to host the site ourselves
4) Start working on setting up a tech / admin help desk with the
Drupal
project module to assist the test nodes in setting up the code
5) Announce the project formally on DFA, and tell people who will want
to run our code to start experimenting with Drupal RC 4.2.
6) Make another call for dev help, and direct people right to the new
DeanSpace community.
7) Get some test nodes up running our early code and working with us
to
test the tools as soon as they go on the CVS.
Thoughts?
-Zack
