Workshop Wednesdays

Purpose of project “Workshop Wednesday” is to create a specialized platform/application for recording live streaming video lectures and workshops delivered on a dedicated platform created by Hack for LA and seamlessly integrating the backend with a scheduler and basic video editor to upload the videos on You-Tube Channel post getting automatically edited as per supervised inputs on a specified time. It aims to replace traditional method of manual intervention for editing & scheduling the videos which is generally cumbersome and time-consuming.

Project context

Workshop Wednesdays details : Workshop Wednesdays One Sheet

Technology used

• Each platform or framework should get its own bullet.
• Each platform should include an active link to the official documentation.

How to contribute

Technology Used :

• GitHub
• Product Management Repo:
• Google Drive:
• Slack:

Remember to provide direct links to each channel.

Installation instructions

1. Step-by-step instructions help new contributors get a development environment up and running quickly.
2. You'll want to find the balance between being specific enough for novices to follow, without being so specific that you reinvent the wheel by providing overly-basic instructions that can be found elsewhere.
3. Feel free to adapt this section and its sub-sections to your own processes.
4. Alternatively, you can move everything from Installation instructions through Testing to a separate Contributing.md file to keep your ReadMe.md more succinct.

Working with issues

• Explain how to submit a bug.
• Explain how to submit a feature request.
• Explain how to contribute to an existing issue.

To create a new issue, please use the blank issue template (available when you click New Issue). If you want to create an issue for other projects to use, please create the issue in your own repository and send a slack message to one of your hack night hosts with the link.

Working with forks and branches

• Explain your guidelines here.

Working with pull requests and reviews

• Explain your process.

Testing

• Provide instructions.

Contact info

Include at least one way (or more, if possible) to reach your team with questions or comments.

Licensing

Include details about the project's open source status.

this readme file sourced from Jessica Sand