Making WordPress.org

Opened 6 years ago

Closed 5 years ago

#4177 closed defect (bug) (maybelater)

Changes to the Meetup organizer application form

Reported by: sippis's profile sippis Owned by:
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords: needs-patch
Cc:

Description

Improving the Meetup organizer application form was proposed and discussed in the community P2. As a result of the discussion, the following changes to the form are agreed on and needs to be done at some point. I'm opening this trac ticket, because I guess the new meetup status tracker should be taken into account when making changes to the form.

Questions to add to the form:

  • Could you introduce yourself and tell us more about your connection with WordPress?
  • Would you mind sharing your blog with us, and links to your Twitter, Facebook and Instagram accounts?
  • Why do you want to start a WordPress Meetup in your city? And what are your immediate plans?
  • Have you talked with people in your community to check the level of interest?
  • Anything else you want us to know while we're looking over your application?

Fields to remove from the form:

  • How would you describe yourself? (connection with WP responds to this)
  • Anything you’d like to tell us about yourself, or what you hope to do with a meetup group?

For social media accounts, we have one textarea-field instead of locked fields for each platform. Label for the field contains information about what links we would like to see and it is easily changed, unlike fields which need coding the logic every time platforms change.

Change History (12)

#1 @iandunn
6 years ago

  • Keywords needs-patch added
  • Status changed from new to assigned

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


6 years ago

This ticket was mentioned in Slack in #community-team by sippis. View the logs.


6 years ago

#4 @sippis
6 years ago

At the same time while doing these changes to the form, would it be possible to also require wordpress.org login or do some kind of check that entered username is correct? That would also help much while vetting applications.

This ticket was mentioned in Slack in #meta-wordcamp by iandunn. View the logs.


6 years ago

#6 @iandunn
6 years ago

consensus from latest Slack discussion:

  • require login
  • show the form, but disable it, and show a log-in modal on top of it
  • reuse the speaker application code for the above, after refactoring it to be generic
Last edited 6 years ago by iandunn (previous) (diff)

This ticket was mentioned in Slack in #community-team by sippis. View the logs.


6 years ago

#8 @francina
6 years ago

I am available for testing and CSS work. I think this would be a great change to our form and make deputies lives easier during vetting!
Thanks

This ticket was mentioned in Slack in #community-team by sippis. View the logs.


5 years ago

This ticket was mentioned in Slack in #community-team by sippis. View the logs.


5 years ago

This ticket was mentioned in Slack in #meta-wordcamp by sippis. View the logs.


5 years ago

#12 @coreymckrill
5 years ago

  • Resolution set to maybelater
  • Status changed from assigned to closed

This issue has been moved to GitHub.

Note: See TracTickets for help on using tickets.