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” widgetWidgetA 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.
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.
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!
Hi everyone, I finished the video tutorial I started some month ago, and now it’s completed with both video and audio.
This will be a nice start for new contributors that will attend today’s online Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. of WordCampWordCampWordCamps 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. Europe and of course for everyone who wants to contribute to the WordPress.tv team.
This project was born during a weekly chat about the need for a new tutorial to unify the process and to make the tutorial more consistent because now we have a written tutorial for Windows users (here: Shotcut tutorial) and a video tutorial for Mac users (here: iMovie tutorial) using two different applications, Shotcut for the former, iMovie for the latter.
We chose to use Shotcut because of its easiness of use (at least in doing what editing for WordPress TV requires), and because it matches some important requirements such as open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. code (link to GitHub repo), constant updates and cross platform binaries (it officially supports Windows, MacOS and Linux).
In this video I recorded the basic steps for cutting unwanted footage at the beginning and at the end, adding the intro/outro slides, adding the speaker’s slides when needed and exporting the final video.
You can find the video attached to this post and on WordPress.tv, and the English, Italian, and Spanish (thanks @yordansoares for that one) scripts, that are currently hosted on GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ to let everyone improve them.
The scripts will be very useful to make subtitles/captions for the video to make it more accessible for everyone.
The video can be improved (I hope you can all understand my not so perfect English pronunciation!), so feel free to give some feedback. I’ll collect them and in the future I can make a new improved version.
As someone with fairly good typing skills, I thought it would be easy to subtitle a 12 minute video, thinking that I could do maybe two or three videos in the day. I was surprised that it took the entire day to do this. Other people had problems too:
Current challenges with the subtitling process
Now while Amara is a fantastic free resource, the following considerations need to be met:
The reading rate shouldn’t exceed 21 characters
You need to lengthen duration, reduce text or split the subtitle.
The “beginner” mode in plays 4 seconds, then pauses.
You have to do this while being aware of subtitle limits
After editing you have to line up the subtitle with the video in the timeline editor.
This process is generally straightforward but sometimes you need to go back and split the subtitle so it reads more naturally.
You have to be aware of typos and adding off camera indications such as laughter or a second person talking.
One of the good things about Amara is that it easily allows alternative language subtitles to be done too, multiple people to be working on subtitles of the same video, and the possibility to pick up an existing transcription if a contributor gets stuck.
Investigation into AI tools.
Subtitling is important for accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), but also for search, user experience, and learning. WordPress TV have a campaign running on subtitling- some subtitling work can be done by automation, but this still needs human involvement.
Videos hosted on YouTube already have access to an excellent auto-captioning library available in English, Dutch, French, German, Italian, Japanese, Korean, Portuguese, Russian, and Spanish. While YouTube are constantly improving their speech recognition technology, automatic captions might misrepresent the spoken content due to mispronunciations, accents, dialects, or background noise.
Therefore, allowing YouTube to automate 80-90% of the captioning process could form a good starting point for the transcription as time stamps would have been created allowing the final ~10% to be reviewed and properly transcribed. The downside is that the automated versions would likely not be as intended creating all sorts of implications, and publishing responsibilities.
WordCampWordCampWordCamps 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. videos on YouTube are being uploaded from January 2018 and up.
Doing a quick search on GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ also reveals hundreds of open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. libraries for “Speech-to-text” implementations. Mozilla is actively developing a speech to text implementation called DeepSpeech
DeepSpeech is an open source Speech-To-Text engine, using a model trained by machine learning techniques based on Baidu’s Deep Speech research paper. Project DeepSpeech uses Google’s TensorFlow to make the implementation easier.
I managed to install DeepSpeech locally with Docker and to my excitement was able to output some text via the terminal from a small English/American audio clip. The process is quite prone to error as you need to have all the required libraries installed but I will be investigating this further.
Ideally, DeepSpeech would be installed on some globally available server with an interface to upload audio files and download text. However, the bottleneck would still come from create and reviewing the ttml file.
While the video file can be downloaded from WordPress TV, isolating the audio file needs to be done manually.
The transcripts from WordCamps, speakers providing their notes, some of the text versions produced by STTR and tools also contribute to making subtitling easier. In addition, subtitles broaden the usage of videos and make them easier to translate / be used by people who can not access the recorded language.
Dublin did a lot of testing on this to produce materials which could help the community and this is being put together. The more that people subtitle and correct automated transcripts, the better the tools will become at learning different accents, words and dialects.
Do you love contributing to WordPress? Do you love telling other
people about how much you love contributing to WordPress? Would you like
those people to start contributing to WordPress themselves? Then do I
have the opportunity for you!
If you’ve been to WordCampWordCampWordCamps 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. Europe or US before you’ll be familiar
with the Get Involved table – it’s a central location (an actual
physical table) where attendees can find out more information about
contributing to WordPress. The table is staffed by community volunteers,
and we aim to have it staffed by at least one person (but preferably
more) from the start of registration to the end of the final session on
each day of the WordCamp, not including Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..
People working at the Get Involved table simply need to be able to
explain how WordPress contributions work and help people find a good fit
in the project for their particular set of skills.
What we’re looking for here is for community members to sign up for
volunteer shifts at the Get Involved tables for WordCamp Europe 2019 in
Berlin. We have split up the two conference days up into 1-hour shifts
to make things easier and it would be great to have a selection of
people from across the project (not just the Community team) involved
Apologies for pulling down yesterdays poll, we discovered it was not locking out multiple votes so the results could not be trusted. Instead I have created the following Google Survey, so please vote at the below link.
As a reminder, the team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. role does not indicate a position of leadership. Team reps report to the broader WordPress community on the work that the team does. For this reason, while all votes will be counted from the community, votes from active members of the WordPress.tv team will be weighted more heavily when selecting representatives for the team.
Thank you @casiepa@prathameshp@roseapplemedia for your interest in being team lead for 2019. Everyone seemed to like the idea of having co-reps to share responsibilities and support one another so with this in mind I’d like to open voting. Please make two (2) choices in the below poll. The two nominees with the most votes will co-rep the team going forward. Best of luck to you all!
Update: The poll did not lock out multiple votes, so I’ve taken it down for now and will post a new poll. sorry!
It is that time. We are saying “Goodbye” to Benny, Elvin, and Dexter. They are WordPress TV’s LiveStream kits that have helped many WordCamps to LiveStream their sessions to WordPressers all around the world.
They were in use for several years. The technology has advanced so fast, and the equipment that we used in these kits has become obsolete. With the streaming capabilities of venues where we hold WordCamps and possibility of even using cellphones for streaming caused the use of LS Kits to sharply decline.
Last year only two WordCamps used our LS Kits.Also, we have to pay large amounts to LS for the subscription for live streaming. So this was a mutual decision of the WordPress community.
Please join me saying “Goodbye” to these legends and make sure that you continue listening to their great music.
Thanks for everyone who replied to the proposal for the WordPress Community Conduct Project. We have recieved lots of great feedback and positivity towards the project both in person at WordCampWordCampWordCamps 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. Europe and online.
In 2012 a Code of Conduct was introduced for official WordPress events to make WordCamps safer and more inclusive. It is now applied to all WordCamps worldwide and anyone who attends a WordCampWordCampWordCamps 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. automatically agrees to it.
Since the Code of Conduct was first introduced, the community has grown and diversified.
At the 2015 Community Summit, a group discussed expanding the scope of the WordCamp Code of Conduct to apply to the WordPress community as a whole. Work on such a Community Code of Conduct has been ongoing since early 2013, and a ticket was created in 2015, but no finalized version has ever been presented to the community and ratified.
The WordCamp Code of Conduct has been active for 5 years as a tool to promote the safety and inclusion of all community members at WordCamps world wide. The Community Conduct Project aims to expand the scope of the Code of Conduct to promote the same values of safety and inclusion in all official community spaces including WordCamps, WordPress Meetups, official fora and websites including comment sections, and official chat channels (specifically SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. and IRC).
Everything needs a starting point, so this began as a proposal by Jenny Wong and Morten Rand-Hendriksen, and reviewed by various community members.
We would like to now take this opportunity to share this project proposal with you all, the amazing WordPress community.
We propose a new Community Conduct Project to update the WordCamp Code of Conduct and expand its scope to become a WordPress Community Code of Conduct (CCoC).
The Project has two main goals:
a) Create a CCoC, to be posted on WordPress.orgWordPress.orgThe 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/, promoting safety and inclusion for all community members in community spaces,
b) create a system for reporting, handling, and resolution of CCoC-related issues as they arise.
To meet these goals, several questions need to be answered including:
Who can be called a “WordPress Community Member”?
In what spaces does the CCoC apply?
Under what circumstances can a person be considered to be acting as a community member?
What values and ideals would a CCOC protect?
Based on these values and ideals, what is the baseline assumption a person can expect whilst being in a WP space.
What spaces, physical or virtual, are considered “community spaces” in which all members can be expected to promote and/or adhere to these values and ideals and any agreed upon community guidelines derived from them?
The answers to these questions will help inform the process of drafting a new CCoC, a system for reporting, handling, and resolving issues, which will become the enforcement procedures based on WordPress community values.
The work will be done in three phases:
Phase 1: Community review and input on the existing Code of Conduct including a survey for the community to participate in.
Phase 2: Review and categorize feedback.
Phase 3: Draft a revised Code of Conduct based on feedback from Phases 1 and 2.
The first task of the project will be to gather data about the current Code of Conduct. As a starting point, we have prepared a draft for a survey to be discussed by the group at the first meeting. This survey will be published publicly to learn more about how the current CoC is used in the real world.
Any and all community members are encouraged to provide input and/or join the project, no previous skills or experience required. In particular, we are seeking diverse voices so if you identify as a member of a diverse, underrepresented, or marginalized group you are encouraged to join.
All meetings will be conducted in the #community-team Slack channel, and minutes published on the Make Community blog to ensure full transparency using the tag CCOC. Working documents will be available for review by the community throughout the project and these will be linked at the end of each post.
If you or someone you know are interested in contributing to this project, please leave a comment below providing a rough ideal time in UTC format, which timezone you are based in and join the #community-team channel. Before scheduling a regular meeting time, we will review the ideal times and timezones of interested community members, to ensure everyone can take part.
We met today to discuss the state of WPTV for another week. Here is what we talked about:
1. Incoming WordCampWordCampWordCamps 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. videos – WordCamp Hamilton had some uploader issues but is sorted out. Videos starting to trickle into our AWS account. Waiting on several recent camps to submit as well
2. Post Production/Publishing – We are also all caught up on videos pending publication.
3. Outreach – @roseapplemedia has been trying this, but there has not been a ton of response so far. We discussed the difficulty in finding out who the AV coordinator is, and how we can easily find out that contact so we can pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” them
4. WPTV Blog – second “featured on wptv” post is live, and traffic to the WPTV blog is much improved. We also took a look at @jwparky‘s recent interviews with community members, and looks like we are a go to start publishing those bi-monthly
We also took a bit of time to discuss @oleg‘s proposal to bring more vodcast and interview content onto our site, from existing YT channels. Full post is here if you’d like to comment.
Full transcript of the meeting here: https://wordpress.slack.com/archives/wptv/p1466096511000123
Want to join our meeting next week? See the blue box at the top of the page to see when our next meeting is!