Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
0 + 6 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     

Re: Action List
by Dave_L on 2005/1/28 1:33:14

I posted a topic QA Team Action List Status for keeping track of the items on the action list.

I think I got the volunteers right. If not, please let me know, and I'll correct that.

Also let me know if you think the "target date for completion" for an item you're working on is unreasonable and needs to be changed.

Re: Action Item #5. I don't think this is needed, and that's it's appropriate for the people working on item #1 to choose the module.

Maybe I didn't explain item #1 clearly enough. The result is an example smoketest. I.e., the goal of item #1 is not to test a module. The goal is to write a smoketest that will be used as a basis for developing a "template" for writing other smoketests. So it doesn't matter a lot which module is used for that purpose.
Re: Action List
by daddystu on 2005/1/27 21:16:52

Quote:

Dave_L wrote:
Sorry, I've been meaning to update this topic.

About the "test module", I'm not sure what that means. If you're talking about action item #1, I figured the person (or persons) doing that action item would choose the module.


I didn't assume that, sorry. How about those doing Action #1 submit their preferred choice of module...just in case.
Also then everyone does indeed know
1.that Action #1 has started
2.which module is being worked on.
Re: Action List
by jensclas on 2005/1/24 19:34:33

If these 'Action' items include proof reading text for user freindliness I am willing to help - As an action item I would prefer to be working on the same module that is under smoketest. That way we are working on things together. The text I am thinking of specifically is the 'read me file' and any other text docs that go with how to use a module. I think this is covered in the criteria of a smoketest - so when you are smoketesting if I know which module it is and who is looking at it I can feedback on the 'text' part. criteria would include how the text meets its target audience and purpose, checking the language for correct use of English (for those who have English as a second language it is usually a matter of minor errors that are common that need correcting, readability for newbies)

Doing this would also enable a collection of terms and definitions...but to work up a glossary would be a whole huge task itself. Perhaps xoops.org would consider using a 'dictionary' module so the whole community can contribute to it. I wonder if this could have definitions written in languages other than English at the same time????

This is the best way I can help

Cheers
Jenny
Re: Action List
by irmtfan on 2005/1/24 19:18:48

Quote:

rowdie wrote:
I'd like to help with Action Item #2 - Reviewing the General Module Development Standards.

And for a test module, I vote for SmartFAQ. It is complete with very extensive documentation, and is a relatively new module, so is using the standards as they are understood today. It would be a good test to see how effective those standards really are.

yes i interested to join Item #2 too.
Smartfaq is a well designed module:
useing template for every parts , colorless style and fully compatible with multi-bytes charsets and RTL languages.
therefor my vote is Smartfaq too
Re: Action List
by Dave_L on 2005/1/24 18:57:57

Sorry, I've been meaning to update this topic.

About the "test module", I'm not sure what that means. If you're talking about action item #1, I figured the person (or persons) doing that action item would choose the module.

Who's Online

209 user(s) are online (162 user(s) are browsing Support Forums)


Members: 0


Guests: 209


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits