There is a number of ways you can support the project.
Sing up to the mailing list, follow on twitter and facebook to keep up to date with the latest releases.
Help translate the user manual and app in different languages.
Especially if you are new to the project, and you read through the docs, and things don't make sense, feel free to get in touch via email pietro@autoEdit.io or @pietropassarell or raise an issue on github chances are that if it's not clear to you it's not clear to others, and I'd love to lower the barry of entry as much as possible. Also always looking for people to proofread.
If you have been using autoEdit, or parts of it, or are working on something similar, I am always super interested in hearing about thoughts and considerations in this problem domain.
If you are a developer, check out the roadmap and see if there's anything that it's of interest you'd like to discuss or get involved with or have any insight into any of those areas. Always happy to have a chat.
Also looking for help making some of the reusable components more robust and accessible so that it's easier to get up to speed with projects in similar problem domain.
On that note I am organising an event, textAV.tech as a way to kickstart an ongoing conversation/collaboration a round the use of captions and transcriptions for video production and one of the topics is making an ecosystem of reusable components.
I need to setup a better test strategy for the project and would love some inputs and ideas on this. See testing section.
autoEdit.io it's free and open source. Free as in free speech as well as in free beer. Help support the autoEdit project to keep it that way.
Support will go towards fixing bugs, adding features, provide support for users etc...
Last updated
