Re: TestFest organisers notes suggestions

On Thu, May 7, 2009 at 1:45 PM, Russell Flynn <russ@redpill-linpro.com> wrote: > Hi, > > This is the first time I've tried to organise a test fest, and I found that > there were a few things missing in the "how to" department for me, so have > some suggestions to add to http://wiki.php.net/qa/organisers to > save the > pestering in IRC :) > > Most of the suggestions on the above list assume that the event is already > planned and a few days away, so taking a step back there could be something > like: > > * Contact your nearest user group to see if they are, or know of anybody > already planning on running a TestFest in your area > * Find a suitable location and choose a date within the TestFest range > * Check that a mentor will be able to assist with your event > * Publish details of your event somewhere (Usergroup wiki, homepage, blog, > etc.) > * Anounce your event: > ** Local usergroup news feed > ** Calendar entry on php.net/cal > ** 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 > php.net/cal and is listed on http://wiki.php.net/qa/testfest > * Some time before the event (somebody help me here) you will be contacted > with details of Subversion access for your group > > This relates only to my personal experience, I'm sure others can shed some > light on other steps, and make corrections if necessary :) > > Russ. > > (Freenode: rooster) > Maybe you could push it on the wiki. Not a bad list of things to take care off. E.g., I just added "us" to the calendar. ;-) (Cheers for that!) The only thing I'd add would be 'selecting an extension' to test. That's where we're stuck currently. Or maybe not stuck, but we're discussing it. Also, I don't think this should be a requirement for every event -- but for Berlin, we created a Github repo to check in tests so we can all sync up and work in a VCS. Most of us are familiar with git so there shouldn't be an issue. We just wanted a repo everyone had access to. And then we'll sync up to SVN when they are done. Till