A/V Release Forms for WordPress.tv

Welcome to the official blog of the TV review team for WordPress.tv

We approve and publish all videos on WordPress.tv as well as help WordCamps with video post-production and captioning and subtitling of published videos.

We use this P2P2 “P2” is the name of the theme the blogs of make.wordpress.org use. When asked to post or view something “on the p2” by a member of the WPTV team, that usually means you’re asked to check https://make.wordpress.org/tv. to post our progress, status reports, and occasional geeky video debates. Use the “Subscribe to Blog via Email” widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to follow along!

Want to help us?

Video Editing — You can see what videos we have that need editing in this spreadsheet. No special credentials are needed, just download the raw video file, and use your favorite app to edit.

Get started here!

Subtitles/captions — You can help us extend the reach of of WordPress.tv by adding captions or subtitles to any published video. Just find your favorite video, and follow the steps here to create a caption/translation file and submit for review.

Weekly meetings

We use Slack for real-time communication. As contributors live all over the world, there are discussions happening at all hours of the day. We have weekly team meetings every Thursday at 17:00 UTC, and they are open to the public!

Our meeting is every Thursday at 15:00 UTC in the #wptv channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. (Find out more about Slack.)

You’re welcome to listen in, or say “hi!” We would love to have your help.

Konstantin Obenland raised the point today that WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. A/V forms are a pain compared to the agreement forms we’ve digitized/automated. Since the way we handle A/V forms is a leftover from more than 5 years ago, that’s not surprising, and we should update that bit.

Not all speakers fill out an application form, so tying it to that wouldn’t cover everyone.
Opting in to global permission should be an option, but not the default. Anyone who does not choose global option will need to agree on an event-by-event basis.
We’ll be getting more meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. videos moving forward, so the wording should be for general WordPress events, with a listing of the events approved for use.
While someone can’t undo permission they’ve already granted, if they have chosen global option they should be able to log in and undo that option for future.
It might make sense to tie this to the .org profiles, as more event activity is going to live there.

#meetups-2, #video, #wordcamps

Aaron Jorbin 7:11 pm on February 3, 2014

These all sound wonderful. I especially love the idea of global opt-in.
David Bisset 7:34 pm on February 3, 2014

No complaints here. Global permission seems like a good place to start.
Ian Dunn 11:36 pm on February 3, 2014

@jenmylo and @obenland, how are you picturing this will look to the user?

My first thought was a page on central.wordcamp.org that has a dropdown-list of all upcoming WordCamps, and a field for the speaker to enter their name, and a checkbox to allow it to apply globally to all future WordCamps.

That ways organizers just have to send speakers to a single link, and speakers only have to type their name, select the camp, and hit submit. If they also check the box, then they won’t have to fill it out ever again. If they don’t, then’d need to fill it out for each camp they speak at.

That’s just my first thought, though, maybe there’s a better option.

Do we need it to include a way for organizers to verify that all of their speakers have signed?

Tying it into WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles would probably need to wait until after we get some of the activity stream APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. built, so it’d probably be better to get a v1 up on WordCamp.org for now.
- Andy 3:52 pm on February 6, 2014
  
  I really like this idea. Would upvote it if I could. 😛
Mike Schroder 1:24 am on February 4, 2014

It would be awesome to be able to handle this on a global level!
Konstantin Obenland 6:26 pm on February 11, 2014
What do you think of this?
- Global release checkbox in .org profile.
- On WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. site (Admin): Add column in speaker table with release date.
- On WordCamp site (Front end): Page with agreement and optional global release checkbox.
This way, Organizers have an easy way to see who has released and who hasn’t (let’s make the date green and the default red!). Speakers can opt-in on a per-WordCamp basis if desired.

If a speaker removes global opt-in, we’d go through all future WordCamps and see if they are registered somewhere and set that flag back to the red default.

Thoughts?

/cc @andreamiddleton
Jen Mylo 4:07 pm on May 7, 2014

That all sounds good. only thing that you’d want to potentially work around is that we had been talking about changing the wordcamp.org CPTs we use for speakers/organizers and switch over to having users login/register to sign up for wordcampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more./apply to speak, etc, and use built in user-roles and user metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. to identify people as speakers, etc. We lost @iandunn to language packs for a while and I don’t think anyone picked that up, but something to consider.
Andy McIlwain 4:10 pm on May 7, 2014

Abstracting a bit from the speaker level… “Has this [WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ user] signed a release for WordCamps? Y/N” Could even have a little badge for it on the profiles if they’ve signed a catch-all release for every WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more..
- Jen Mylo 4:25 pm on May 7, 2014
  
  Profiles are meant more for public consumption than for legal bookkeeping, so I probably wouldn’t attach it to the public profile, but it could be a hidden field.
  - Andy McIlwain 6:15 pm on May 7, 2014
    
    Fair enough. I’m just a sucker for achievement hunting. 😉
- Ian Dunn 4:40 pm on May 7, 2014
  
  Since it’s for WordCamps, I think it’d make more sense to put it on wordcamp.org rather than profiles.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
  
  Either a front-end form on central.wordcamp.org, or something on their back-end user profile — e.g., 2014.example.wordcamp.org/wp-admin/profile.php (similar to how we’ve talked about adding volunteer/sponsor/speaker/organizer usermeta fields).
  
  That would keep all the WordCamp.org code on WordCamp.org itself, rather than splitting it between WordCamp.org and profiles.wordpress.org, and would also keep all the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. data on WordCamp.org, rather than splitting in between two sites.
  - Jen Mylo 9:46 pm on May 7, 2014
    
    Yes, please. 🙂