On Fri, Dec 25, 2015 at 11:52 AM, Love Mehta <lovemehta...@gmail.com> wrote: > Hello eveyone, > > I am a second year student of Indian Institute of Technology, Ropar. I am > quite comfortable with c, c++, HTML, CSS, javaScript and java programming. > > I am new in the open source software community and wish to contribute in > free software. I have found out about the FFmpeg community from the Google > Summer of Code website. I am interested in the initiative and work done by > the FFmpeg community and wish to contribute in the community. > > Please someone guide me as to which project will be good for me to work on > and where can i use my skills and enthusiasm the best.
There are numerous ways to get involved here: 1. You find a component that you use regularly, or care about for other reasons. For the sake of an illustration, say you like a particular codec in libavcodec. You then see that there is some feature missing, or it does not handle something correctly, and then start submitting patches following the guidelines laid out at: https://ffmpeg.org/developer.html. 2. You filed a bug report for something at https://trac.ffmpeg.org/. As the project does not have a lot of manpower, it may take some time for things to get fixed. By getting involved yourself, you can speed up the process. You may perhaps then get interested in bug fixing more generally, or use it as a launching pad for other work in the project. 3. You have some favorite cpu architecture and/or platform, and are dissatisfied with some performance aspect. You can ask people here (or maybe better on IRC https://ffmpeg.org/contact.html#IRCChannels) where something can use speedups, be it in the form of more efficient algorithms/C code, or assembly code in many instances. 4. More generally, you said you had a look at the GSOC page. It has some project suggestions, along with interested developers who may help you out. You can apply for GSOC, alternatively it should also give some ideas as to what developers here consider reasonable projects. 5. Just watch for a few days ffmpeg-devel and/or ffmpeg-cvslog (the commit history) or more generally the overall codebase to get an idea of what different people do here. Studying these things will not only make you more familiar with the project, but also gives a sense for what can be done, what is easy to do, and what is hard to do. Ultimately, there are a lot of opportunities for worthy contributions to the project, and the above just scratched the surface. Concrete ideas/interests/suggestions can help us understand what you want to do better. Welcome to FFmpeg, and I hope you continue to explore the project and start contributing. > > > Thanks > > > > Sent with MailTrack > <https://mailtrack.io/install?source=signature&lang=en&referral=lovemehta...@gmail.com&idSignature=22> > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
