TL;DR: There’s a lot here, but I need your help and input, so please take time to read and respond.
I’m forwarding Khayrattee’s message below from the sponsors mailing list, since I’d like everyone else on this list to be able to participate in this discussion.
First, a few updates:
- I am behind on things I wanted to have ready by September 1.
- I’m working on a way to share and contribute slides for PHP TestFest presentations so that group leaders are able to present without much preparation. That is a work-in-progress in this branch here: <https://github.com/phpcommunity/phptestfest.org/tree/slides-setup/slides>.
- In our last Google Hangouts session, Sara proposed the idea of a points system for awarding prizes. What follows is a rough outline of how I think that should work. **I would like feedback.**
- We need a tutorial/presentation clearly outlining the steps to create and submit tests for consideration in PHP TestFest. The following notes also talk a little bit about this process.
SUBMISSION PROCESS AND POINTS SYSTEM (needs feedback)
- We will need reviewers who have the expertise needed to review phpt tests and judge whether they are good and useful tests.
- Sara Golemon and Joe Watkins have volunteered as reviewers. We need a few more.
- General test submissions for PHP TestFest must be made as PRs to the phptestfest-2017-master branch at this repo: <https://github.com/phpcommunity/phptestfest-php-src>
- Bug test submissions (for bugs logged at <https://bugs.php.net/>) must be made against the appropriate PHP version branch at the same repo (phptestfest-2017-PHP-7.2, phptestfest-2017-PHP-7.1, or phptestfest-2017-PHP-7.0).
- Each pull request should include only one test file. This makes reviewing and awarding points simpler.
- Reviewers will have access to review these PRs and will award points to submissions.
- Points could be awarded, as follows:
- 1 point for each valid submission
- Extra points for a test that verifies a bug from <https://bugs.php.net/>
- Extra points for a particularly meaningful test
- 5 points for a submitter who has never contributed to core
- 10 points for finding a bug and opening a new bug report
- Extra points for improving an existing test to make it run faster or not fail intermittently
- Each point counts as an entry in the raffle, so the more points you have, the higher your chances of winning a prize
- In addition to the raffle, the reviewers will pick three submitters whose work stands out from the rest. These three will receive “big” prizes (what do we want to consider “big?”).
- The group whose members receive the most total points will win a prize. What kind of prize would be good for a group?
- Could we give away something like a sticker pack to all who participated?
As for tracking the points, submissions, and groups, I am working on a site that integrates with GitHub and can help us keep track of these things.
Okay, that’s enough brain dump for now. I want to hear from you. Khayrattee’s message follows. He needs feedback, as well.
Cheers,
Ben
Begin forwarded message:From: Khayrattee Wasseem
Subject: [ThinkTank Session] - Structure of Award System & Prize Sponsorship Expectation..etc
Date: August 30, 2017 at 10:15:13 AM CDT
To: PHP TestFest Sponsorships
Hi Ben,
following my first batch of email request to potential sponsors (I reached out to 23 companies & other individuals), it came to mind about the below:
1) What are we expecting from Sponsors?
i) Are we expecting them to "propose what they can offer"
ii) or do we actually want them to "buy in & provide" what we actually want them to provide.
To a couple of them, I have said that we currently do not have any kind of package, we are still working on an approach. And they could just propose what they can offer, for e.g any kind of subscriptions, vouchers, tools, tool licenses or ebooks - that could actually be useful to any (dev) participant and hence serve nicely as "prize raffles".
2) How will the sponsor get their name out there to the crowd? The places of exposure where sponsors will be listed..etc
3) A rough number of participants - so sponsors can better propose how much to actually provide..etc
4) Featuring Sponsors on our TestFest website - details we need from them:
i) Logo or banner (what acceptable sizes?)
ii) A bio or just the title of their company?
iii) Will we allow them to put a small marketing message as well?
iv) And I guess we should also let them display contact points - Main contact person, email or social pointers..etc ?
Would be great if we can all agree on finalising 'way-forward' to the above and I can better address/communicate with potential sponsors to convince them.
Anything I missed or you have (had) in mind?
PS: Let me know anything else in terms of expectation from me, so I can help further.
Let's Rock This PHP TestFest!
cheers
7PHP