-
Notifications
You must be signed in to change notification settings - Fork 0
NewProject
This page describes the steps to propose and create a new Freeseer project. If you are interested in Google Summer of Code, UCOSP, or just want to get good at video/gstreamer/python/qt programming, please follow these steps to get started with Freeseer.
Looking for more information about Freeseer? Read this.
These videos will help give you a sense of what Freeseer is and does:
Setting up Freeseer for VGA capture
and view the [[introduction presentation | http://www.fosslc.org/drupal/content/freeseer-video-recording-and-streaming-tool]
If you know and trust us, and vice versa, you'll have a lot more fun using the software and hacking the code (if you choose to do so).
The best way to do this is to use the software, join our mailing list, and hang out in IRC.
Typically your success getting code accepted and/or project funded depends on support from the community. The best way to secure support is to get to know the team and community. You do that by interacting in on the mailing list and IRC channel.
For those that haven't used Internet Relay Chat (IRC) before, it is a group instant messaging system. It allows the project team to type messages to the rest of the team and communicate. The following link is a web IRC client. You just make up a nickname and can enter the IRC channel for freeseer. freeseer on freenode.net
If you have an IRC client already or want to download a free one (such as Pidgin) - the channel is #freeseer on irc.freenode.net.
Take a look at any tickets in our issue tracker tagged with summercode. These tend to be good items for new people to start with. You are absolutely encouraged to suggest new ideas. To rally support for your idea and get input on how to best approach it please bring it up on the mailing list.
Use our designer guide template to start documenting your idea. Once you've got something captured, share it with the mailing list to solicit feedback.
The template is a guide so feel free to add new sections or explain in your document why certain sections aren't relevant. Our design process is intended to be light weight and iterative and still preserve stability and maximize quality in the code base.
a) When you set up your account, don't forget to set up ssh keys b) When you fork the project in github, you're creating your own private clone of the code. This also gives you your own wiki, bug tracker, etc. This will come in handy for working on the code. c) You can keep your fork in sync with the code from fosslc's freeseer project by rebasing. fosslc's copy is considered the defacto version and the one we publish for download.
Those involved with Google Summer of Code (GSoC), Under Graduate Capstone Open Source Project (UCOSP), Fedora Summer Coding (FSC), and similar programs are required to send us their resume so we know enough about you to vouch for you in the program. Please send your resume to our project lead, Andrew Ross. His email is fosslc at gmail dot com.
We welcome all contributions. If you're not involved in the programs listed above, you are not required to send your resume but are welcome to do so if you wish. Many of the team are gainfully employed and often are looking for good people.
Also, be sure to include a brief summary of your Previous python/qt/gstreamer experience and why you want to work on the project. A letter of recommendation from 2 people will help your chances to be accepted.
Use your favourite editor. Most of the community use vim at the moment, but you could use which ever editor you prefer.
If we can see your code as you work, we can give you tips and suggestions as you go rather than all at once at the point you try and submit your change. To make it easier for us to follow along, please:
Before we accept your change, you'll need to make sure your design document is up to date. It's fairly light weight so just take a few moments to do so. We'll be very happy you did.
The community will scrutinize the code. You must get approval from at least 2 committers AND your code must integrate without conflicts or test issues on fosslc/development (fosslc's copy of the code, development branch).