diff options
Diffstat (limited to 'gsoc/application.mdwn')
-rw-r--r-- | gsoc/application.mdwn | 151 |
1 files changed, 151 insertions, 0 deletions
diff --git a/gsoc/application.mdwn b/gsoc/application.mdwn new file mode 100644 index 0000000..f66ab8b --- /dev/null +++ b/gsoc/application.mdwn @@ -0,0 +1,151 @@ +[[!meta title="GSoC/Application"]] +[[!meta author="Tlsa"]] +[[!meta date="2014-02-12T18:44:36Z"]] + + +[[!toc]] + +About Our Organization +---------------------- + +### Organisation Name + +NetSurf + +### Organisation Homepage + +<http://www.netsurf-browser.org/> + +### About the NetSurf Organisation + +We are the developers of NetSurf, a fast and small open source browser +written in C with its own layout engine. As well as producing NetSurf we +have created various other libraries which other software can use. These +libraries include libHubbub (an HTML5 parsing library), libCSS (a CSS +parsing and selection engine), and libDOM (a Document Object Model +implementation). All our libraries are written in C, and are written +with a focus on low memory usage, high performance and robust stability. +More about the memebers of the team may be found at +<http://www.netsurf-browser.org/about/team> + +### NetSurf Orgnisation's reason for applying to GSoC 2014 + +We have specific ideas for new development that will be useful for our +project and for other projects that rely on our libraries. We're +applying to GSoC for a couple of reasons: first, because we don't have +time to do all the work we wish to do on the project, and second because +there is useful work that a student with no prior knowlage of NetSurf +could realisitcally do over the summer. We hope to gain a new developer +and new and improved code. + +### Previous GSoC Participation GSoC + +We applied to participate in GSoC in 2008 and 2009, and both +applications were accepted. + +In GSoC 2008 we mentored 4 students, all of whom completed their +projects to a satisfactory standard. + +In GSoC 2009 we mentored 3 students, all of whom completed their +projects to a satisfactory standard. + +This is our first application to GSoC since 2009. + +### Project licenses + +GPL2 for NetSurf itself and MIT for the libraries (libHubbub, libDOM, +libCSS, and others). + +### NetSurf Organisation's Ideas Page + +<http://wiki.netsurf-browser.org/GSoC_2014> + +### Development mailing list + +netsurf-dev@netsurf-browser.org + +<http://vlists.pepperfish.net/cgi-bin/mailman/listinfo/netsurf-dev-netsurf-browser.org> + +### IRC channel + +\#netsurf on FreeNode + +### Organization application template + +None. + +### Our backup organization administrator + +<span style="color:red;">TODO</span> + +About Our Mentors +----------------- + +### Our mentor selection criteria + +We have a relatively small number of core developers, all of whom have a +reasonably good knowledge of the codebase. Lack of knowledge about how +something works is addressed through regular communication. Therefore, +our main criterion for being a mentor was an expressed willingness to +perform the role. + +We have five core developers who are all willing to help a student find +their feet and get the best out of their GSoC experience. + +### Our Mentor listing + +<span style="color: red;">TBC</span> + +- John-Mark Bell +- Michael Drake +- Rob Kendrick +- Vincent Sanders +- Daniel Silverstone + +About Our Participation in the Program +-------------------------------------- + +### Our plan for dealing with disappearing students + +We'll encourage students to check their work into version control +regularly for testing so that at least their work won't be lost. However +we'll try to avoid this problem by constant communication, +encouragement, and help. + +### Our plan for dealing with disappearing mentors + +The offical mentor(s) will be backed up by the other project developers, +who are happy to help and mentor too. + +### Steps we will take to encourage students to interact with our project's community before, during and after the program + +The home of our development community is the \#netsurf IRC channel, +which always has some of the developers and daily discussion of the +browser. We will encourage students to join this channel and the +development mailing list so they are best able to interact with us. + +### What we will do to ensure that your accepted students stick with the project after GSoC concludes + +We will endeavour to ensure that they feel they are making a useful +contribution to the project and that their work is valued. We'll also +try to make the project enjoyable and give regular feedback on their +ideas and work. + +<span style="color:red;">TODO</span> +------------------------------------ + +- Are you a new organization who has a Googler or other organization + to vouch for you? If so, please list their name(s) here. +- Are you an established or larger organization who would like to + vouch for a new organization applying this year? If so, please list + their name(s) here. +- The email addresses associated with the Google Account information + provided during the proposal process will be used as the primary + mode of contact by Google throughout the program, e.g. the email + address which we will use to subscribe you to the Google Summer of + Code mentors/admins-only mailing list. + +Last point means we need google accounts for all mentors/admins. + +--tlsa + |