Re: bug reporting

My question for you is what is the purpose of the site?

It's been my experience that if a small group/organization is trying to
compete with the resources of a long established website, you'll probably be
wasting your time unless you have some trick up your sleeve.  For example, I
use the RedHat distro and so I always start at the RedHat.com website when I
have a problem because their knowledge base is thick enough to solve my
problem most of the time.  I don't want to go looking through the knowledge
base from a dozen different LUG's around the country to find the answer.

The same things goes in the way of a user forum - why are people from around
the world going to suddenly start using your website?  Are you going to be
advertising it other Linux sites?  Will you be doing a weekly give-away of
some piece of computer equipment?  Again, why would I ask a question for a
dozen people to answer when I can ask it of hundreds or thousands?


My recommendation would be to start small and begin documenting everything
the group does.  Document presentations, allow people (like myself) to
document a particular project that I've been working on such as SAMBA or
Evolution.  The other thing that I've noticed the ACLUG site severely
lacking it is information about the group.  It is very difficult to
ascertain when and where the club meetings are to be held, and what is on
the agenda.  Member photos could be helpful, especially to new members.

That's my two cents...
Zack Clobes
Hutchinson

-----Original Message-----
From: Tom Hull [mailto:[email protected]]
Sent: Tuesday, September 23, 2003 12:12 PM
To: [email protected]
Subject: [webdev] bug reporting


Just looking at the aclug.org website: I notice that the links at
the bottom of the page for "Report Bugs", "Tasks", "Developers"
actually link to sourceforge.net. These are probably defaults,
but I don't see any need for them on our website -- indeed, they
would probably just confuse the postnuke developers if we used
them.

On the other hand, we do need some sort of a system to direct
changes/development of the aclug.org website, such as Bugzilla,
which James Violette had set up for the previous openacs-based
website. Could someone look into setting this up? One thing
that I think should be a requirement would be to enforce
compatible user ids for both systems (postnuke and bugzilla),
so that users only have to sign up once and cookie info from
postnuke could be used to log into bugzilla.

BTW, response to my last posting has been underwhelming. Is
anyone out there?

-- 
/*
  *  Tom Hull * thull2(cox.net) * http://www.tomhull.com/
  */