Difference between revisions of "GSOC 2017 Ideas"

From SatNOGS
m (add markdown tag)
Line 88: Line 88:

Latest revision as of 22:10, 19 January 2020


These ideas were contributed by our developers and users for [Google Summer of Code 2017](https://summerofcode.withgoogle.com). Some of them may be in a rough state, but they can certainly be refined. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are its [forum](http://community.satnogs.org) and its [github repositories](http://github.com/satnogs).



Students wishing to participate in Summer of Code must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer, in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.

Recommended steps


* Read Google's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface 

Check the KDE's [Student Proposal Guidelines](https://community.kde.org/GSoC#Student_proposal_guidelines) for more hints on what your application should look like.

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **LSF**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start. Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

  1. Software Projects
    1. [SatNOGS DB](https://github.com/satnogs/satnogs-db)
      1. Enhance frontend suggestions and moderation capabilities
  • **Description**: Supply the ability for users to suggest new satellites. Supply the ability to moderators to approve or amend satellite and transmitters suggestions.
  • **Skills needed**: Django/Python , HTML, CSS3, Javascript
  • **Expected results**: All satellite and transmitters data should be crowdsourced and moderated through a simple UI.
  • **Mentor**: @comzeradd
    1. [SatNOGS Client](https://github.com/satnogs/satnogs-client)
      1. Build a web based controller able to control the SatNOGS client
  • **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
  • **Skills needed**: Python, Flask
  • **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
  • **Mentor**: @jinxcat
      1. Package SatNOGS client for different distributions
  • **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
  • **Skills needed**: Packaging on major distributions.
  • **Expected results**: Released and submitted upstream packages on major distributions.
  • **Mentor**: @axilleas
    1. SatNOGS Infrastructure
      1. Improve logging and monitoring
  • **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
  • **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
  • **Expected results**: Logs and Monitoring capabilities for the Network administrators
  • **Mentor**: @axilleas
      1. Improve distributed storage of observation data
  • **Description**: SatNOGS observation data must be able to be stored in a distributed manner
  • **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
  • **Expected results**: A distributed storage option for observation data
  • **Mentor**: @jinxcat
      1. Add error rate and karma policies for SatNOGS clients
  • **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
  • **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
  • **Expected results**: Error and karma policies applied to observation job prioritization
  • **Mentor**: @jinxcat
  1. [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)
    1. [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)
      1. Title
  • **Description**:
  • **Skills needed**:
  • **Expected results**:
  • **Mentor**:
      1. Title
  • **Description**:
  • **Skills needed**:
  • **Expected results**:
  • **Mentor**: