> On Oct 7, 2014, at 6:12, Peter Cowburn <[email protected]> wrote: > > > >> On 7 October 2014 09:34, Paul Dragoonis <[email protected]> wrote: >> Hi Lorna/Hannes, >> >> After reviewing your conversation and the questions asked, I have a few >> suggestions that will help alleviate the hurdles we're about to push >> through. >> >> 1) We need to differentiate between confs and meetups by having: >> a) A new form field with 2 radio options to choose from "User Group >> Meetup" or "Conference" >> b) To return this new field in the API responses >> c) An API parameter to filter results by i.e: "?event_type=conference" >> >> 2) For events appearing on php.net by: >> a) Taking the user to the Edit Event after they create their event. >> b) Putting a question on the Edit Event form which is: "Would you like >> your conference to appear on php.net?" which would appear if(they have a >> 'php' tag OR the title of their event has 'php' in it). By choosing yes >> they will get a tag named "phpdotnet" which I can filter by. >> >> OPTIONAL VERIFICATION OF EVENTS: >> d) When the user chooses a "phpdotnet' tag an email will be sent to >> joindin admins to prompt them to "approve" this phpdotnet request and only >> verified events will come back from the API. > > This sounds a lot like the primary sticking point of our current setup: > having someone around at all times to "approve" submissions.
***Joind.in already has a team in place that is doing this. Joind.in's interface also makes event approval a much easier and quicker process than php.net's process. Beth Beth Tucker Long Treeline Design, LLC 807 Arbor Vitae Place Verona, WI 53593 608-770-6677 http://www.TreelineDesign.com
