A better Support Community . . .

Worker Joined: Nov 10, 2004 Posts: 110

[support options]
I was thinking how we can find new ways to develop CNBYA more efficiently. Some options came into my mind.
I would love to hear your opinion on these. Please vote in the poll and comment your choice in this topic.

Let's make things better...

Cheers,
Richard

registered · Posted: Tue Dec 07, 2004 12:17 pm

I would be more than happy to be a part of your beta test team. I think you need to develope a good test team and come out with new releases once things are tested well.

Maybe also come up with better version identification. Wink

Posted: Tue Dec 07, 2004 12:24 pm

I get to vote too? LOL!

So long as Andre is project manager we have the facilities to provide the above services at colaborar.softwarelivre.gov.br its just a matter of making use of them. Between www.phpnuke.org.br (PHPNuke Brazil) and www.ravenphpscripts.com and all of our collective personal sites I really think we have the support issue covered. Its just a matter of us getting ourselves better organized. Where credibility and team work can really begin to pay off.

So (not to sound as if there is discontent among the troops here) I voted with option :
Lesser public releases, many beta releases for enrolled beta-testers
With the note that we we must make use of the powerful system we have.

My .02 on the topic.

Posted: Tue Dec 07, 2004 12:30 pm

You are right six,
We have a bugtrackersystem we don't really make use of at the moment.
We'll have to investigate it and start using it !
(I voted: all of the above)

Cheers,
Richard

Useless Joined: Aug 23, 2002 Posts: 213 Location: Chicago

I have realized that no matter how many beta testers you have, it's truely the public who actually finds most of the bugs.
We do need a bug tracking system but everything else seems to be working fine as of right now.

Posted: Tue Dec 07, 2004 8:29 pm

Yeah we should put a link directly to the bug tracker into the app I think because its really simple and it allows anyone to post they don't have to join or anything like some of those other CVS sites to make a bug report.

Posted: Tue Dec 07, 2004 8:31 pm

http://colaborar.softwarelivre.gov.br/tracker/?atid=105&group_id=21&func=browse

Posted: Tue Dec 07, 2004 8:34 pm

Sure let's use that but users still post here or at CNB's main site and then one of the team member confirms it before it gets added to the bug tracker. This way it will be free with false and/or old bugs that has already been fixed.

Posted: Wed Feb 02, 2005 4:36 pm

I voted the opposite of how I voted in November, "all of the above".

I only did this as my, "none of the above" vote during the election didn't pan out. HitsFan

I really like the bug track system that they use over at cpgnuke as it seems to do its thing really well. I'm not sure what you guys have as I haven't seen anything yet, but a central place is always the best practice for that kind of thing. It's probably a good idea to make whatever solution you use for pre-release software, private (to testers) so the kids don't get too anxious about upcoming releases. Smile

As for production versions, I love a good bug track system as it seems better suited than forums. I think forums are good for reporting bugs for joe schmoe where you might not get all of the information that you want, and also because they make a great way to answer FSQ's, but from a development perspective I prefer a system where every bug reported includes all version information of the server (including PHP, MySQL, settings, etc...) as well as the Nuke Environment (Version, build, add-ons like groups, etc...) that might have an impact of the module itself (sometimes inadvertantly). I find it easier to look at them and address them this way as they don't have all kinds of little chit-chats mixed in which make it harder to look for and address specific bugs.

Whatever you go with, I'm sure it will be great. Roadmaps seem fairly easy to me and support has seemed outstanding from my perspective, so I'm pretty confident in all regards.

Steph