Nomad 0.1.2-alpha is out, download it here!

Nomad guidelines for Summer of Code projects

First, thanks for stopping by. Nomad needs volunteers to improve the Freedom-respecting Web Browser and to help out the Free Web in many other ways.

What is this?

For general information about the program, check the main page at Google for Summer of Code. This will be the first time Nomad is applying for GSoC.

All Nomad-related organizational Summer of Code discussion happens on the mailing list (subscription info here). Feel free to subscribe if you want to be involved, either as a mentor or student.

We have an idea list for Nomad-related projects for students to implement as part of the Summer of Code. Please read the information on this page too! We've tried to ensure that each project:

The definition of “student” used by Google is reasonably broad. If you know somone who already works on a GNU project and meets the eligibility requirements, please encourage them to submit a proposal.

What to do with the suggestions?

If you are an eligible and interested student, read through the list and note the projects you are interested in. You, as the student programmer, then submit a proposal to Google, as described in the following.

First, submit your application early. By doing so, it will be given a greater share of attention than is possible for applications submitted at the last minute. Many applications are submitted in the last few days; there is no time for us to to give such last-minute student submitters feedback on how to improve their proposal.

You might submit a proposal unchanged (though you will need to include additional information, as described below), or you might adapt it. Changes to the proposal could include:

Your proposal

Proposals are submitted via the Google Summer of Code 2020 web site. When proposing your project, please make sure you include the following information. You must follow this project template in order to have your proposal considered!

Your code and documentation

The Nomad Project has standards relating to how software is developed and how it is documented. These are designed to make the resulting software useful, maintainable, easy to install, and most importantly make sure that it will remain free (as in freedom). You need to do several things:

  1. Comply with the GNU coding standards.
  2. Write good documentation as well as good software.
  3. Work with other members of the project to ensure that your work fits well with the rest of the project you are working on, and Nomad in general.

Summer of Code project suggestions

For the actual project suggestions, please see the separate page with the list of Summer of Code GNU project ideas. We'll be updating this list as new projects are identified (until the proposal deadline).

Even if you are not an eligible student, coming up with good projects meeting the criteria above that benefit Nomad is very welcome (the sooner the better). If you do, please contact the maintainer for Nomad. If you can find a mentor for the project (or can mentor it yourself, with the maintainer's consent), then email the idea to us at

That is not the only list

There are other lists of things that need to be done on the GNU project. This list is not intended to replace them. However, the other task lists are mostly more open-ended, include larger and more complex tasks, and the tasks on the other lists don't come with a mentor; you will need to find one, if you need one.