qa:organisers
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
qa:organisers [2008/05/05 15:45] – zoe | qa:organisers [2011/04/06 10:59] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
==== Suggestions and checklist ==== | ==== Suggestions and checklist ==== | ||
- | | + | ===Advance planning=== |
- | * Limit the numbers if you don't have a reasonable ratio of mentors to attendees (suggested max 1:4) | + | |
+ | * Find a suitable location and choose a date within the TestFest range | ||
+ | * Make sure that the location you choose has network connection | ||
+ | | ||
+ | * Publish details of your event somewhere (Usergroup wiki, homepage, blog, etc.) | ||
+ | | ||
+ | * Anounce your event: | ||
+ | * Local usergroup news feed | ||
+ | * Calendar entry on php.net/ | ||
+ | * Announcement to php-qa@lists.php.net | ||
+ | * Any other blogs or relevant places you can think of | ||
+ | * After a short while, check that your event has been approved on http:// | ||
+ | |||
+ | ===In the run-up to the event=== | ||
+ | * Svn access for the group is mailed to the organisers listed on http:// | ||
+ | * Get a list of names of attendees (and email addresses) in advance | ||
+ | * Grant access to SVN in advance (testfest.php.net/ | ||
* Mail attendees the day before to remind them to bring laptops (and possibly power supply and ethernet cable) | * Mail attendees the day before to remind them to bring laptops (and possibly power supply and ethernet cable) | ||
* Ask attendees (with any other OS than Windows) to try and download and compile PHP in advance (to check that they have a build env't) | * Ask attendees (with any other OS than Windows) to try and download and compile PHP in advance (to check that they have a build env't) | ||
- | * Make sure that the location has network connection (wireless/ | ||
* Pick an area (extension) to test in advance and let the attendees know so that they can do some preparation. | * Pick an area (extension) to test in advance and let the attendees know so that they can do some preparation. | ||
* Mail the QA list to say what extension you are looking at so that you can co-ordinate with other groups if they want to work in the same area | * Mail the QA list to say what extension you are looking at so that you can co-ordinate with other groups if they want to work in the same area | ||
* Work out in advance which test cases are missing and have a list of then ready for people to work on | * Work out in advance which test cases are missing and have a list of then ready for people to work on | ||
* If you pick something that has pre-reqs (eg database, libraries) prepare some samples and make sure that people know to install the pre-reqs. | * If you pick something that has pre-reqs (eg database, libraries) prepare some samples and make sure that people know to install the pre-reqs. | ||
+ | |||
+ | ===On the day=== | ||
* Either at the event or in advance have someone give a short talk on the extension and show example of how to use it | * Either at the event or in advance have someone give a short talk on the extension and show example of how to use it | ||
* Be prepared for network failure - have copies of PHP source, Windows builds and docs on a stick. | * Be prepared for network failure - have copies of PHP source, Windows builds and docs on a stick. | ||
* Find a local source of beer for *after* the event | * Find a local source of beer for *after* the event | ||
- | + | | |
- | This is all we thought of for the London one, I expect I'll add to it after the London event with all the things we forgot :-( | + | |
- | + | ||
qa/organisers.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1