diff options
Diffstat (limited to 'gsoc')
| -rw-r--r-- | gsoc/application.mdwn | 151 | ||||
| -rw-r--r-- | gsoc/information.mdwn | 9 | ||||
| -rw-r--r-- | gsoc/requirements.mdwn | 85 | ||||
| -rw-r--r-- | gsoc/student_guidelines.mdwn | 66 |
4 files changed, 311 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 + diff --git a/gsoc/information.mdwn b/gsoc/information.mdwn new file mode 100644 index 0000000..58a2398 --- /dev/null +++ b/gsoc/information.mdwn @@ -0,0 +1,9 @@ +[[!meta title="GSoC/Information"]] +[[!meta author="Tlsa"]] +[[!meta date="2009-07-08T17:00:22Z"]] + + +[[!toc]] + +1. REDIRECT [[GSoC/|gsoc/]] + diff --git a/gsoc/requirements.mdwn b/gsoc/requirements.mdwn new file mode 100644 index 0000000..4d4dfc7 --- /dev/null +++ b/gsoc/requirements.mdwn @@ -0,0 +1,85 @@ +[[!meta title="GSoC/Requirements"]] +[[!meta author="James Bursa"]] +[[!meta date="2009-05-27T01:14:50Z"]] + + +[[!toc]] + +Basic requirements for GSoC students +------------------------------------ + +Students are expected to work a "standard" work week. Anything above +that is fine too, but we expect a commitment similar to normal +employment. After all, Google are paying for your time. + +Expectations for communications +------------------------------- + +The NetSurf team use IRC, so you will be expected to be on \#netsurf on +Freenode and communicate there. + +Each week, (or more often if suitable) you are expected to send a report +to your mentor indicating what you have achieved, what you intend to +achieve over the coming week, and anything which is blocking you from +proceeding. Your mentor will then post to the netsurf-dev mailing list +providing a redux of this information suitable for others. + +If you have any issues with anyone else, you are expected to take it up +with your mentor, or if the issue is with your mentor, with one of the +other mentors in the project. The mentors are: John-Mark Bell (jmb), +Michael Drake (tlsa), Rob Kendrick (rjek) and Daniel Silverstone +(kinnison). + +Who to talk to +-------------- + +Your mentor is your first point of call for anything directly related to +the running of GSoC. They are the person responsible for your midterm +and final assessment and you should be using them for this. + +For queries about your actual project work, you are encouraged to ask +for advice or help on the IRC channel or mailing list. Generally the IRC +channel is most suitable for but for involved questions or issues that +require a lot of planning, use the netsurf-dev mailing list. This allows +the entire NetSurf team to help and advise you. + +Sometimes we may ask you to work something out for yourself, not out of +spite or laziness, but to encourage you to learn more for yourself. GSoC +is not just a chance to make money, but a chance for you to learn new +skills and to interact with other ways of developing software. + +How to work +----------- + +In terms of your work environment, we recommend that you have a well-lit +comfortable place to work, and that you isolate it from your normal home +computing environment in the sense that if you normally have hundreds of +IRC channels open, browse tens of websites etc, you try not to during +your "work day" -- we're not saying you can't enjoy yourself, just that +the fewer distractions, the easier you will find it to begin with. + +We recommend that you don't have the television or a talk-radio station +on while working. Music however is fine and often encouraged. + +Repository layout +----------------- + +You will be given a branch space on our Subversion repository. It will +be in /branches/<yourname> and you will have total control over that +part of the repository. You are encouraged to make feature branches and +to request that your mentor review and merge them regularly. Ideally you +will make a branch, implement one feature (or one packet of work towards +a feature) and get it reviewed and merged. Then make a new branch and +work on the next bit. + +This sounds a little long-winded, but it means that we don't get huge +merge jobs at the end of GSoC, but still fulfils the requirements that +we have to provide to Google your work so that they can see that you +didn't cheat them out of their money. + +You are encouraged to commit early and often to your branch. Changes you +make will be sent to the public commits list, so be sensible in your +commit logs. Regular smaller commits will allow the team to review your +code in-flight and suggest improvements or ideas which might mean you +waste less time writing something which ultimately isn't suitable. + diff --git a/gsoc/student_guidelines.mdwn b/gsoc/student_guidelines.mdwn new file mode 100644 index 0000000..30912da --- /dev/null +++ b/gsoc/student_guidelines.mdwn @@ -0,0 +1,66 @@ +[[!meta title="GSoC/Student Guidelines"]] +[[!meta author="James Bursa"]] +[[!meta date="2009-05-27T01:13:40Z"]] + + +[[!toc]] This page details some of +the things students thinking of applying to the NetSurf Project during +the Google Summer of Code 2009 should know, do, and keep in mind. + +Read the section at the top of our ideas page +--------------------------------------------- + +It has all sorts of details and advice for students interested in +working with NetSurf for Google Summer of Code. + +Build NetSurf and play with it for a while +------------------------------------------ + +Building NetSurf should be quite easy. You should get the source with +Subversion, as described [on the developer +pages](http://www.netsurf-browser.org/documentation/develop#Subversion). +Don't download a tarball from the websvn interface: it's broken. If you +have any trouble building it, ask on \#netsurf. The only common gotcha +is obtaining the lemon parser generator, it only appears to be Debian +and Ubuntu who package it separately. Fedora, specifically, builds it +during the creation of the SQLite packages, but then throws it away! +Fortunately, it's very trivial to build yourself: just ask Google for +"lemon parser generator". + +Explore the NetSurf website +--------------------------- + +There's loads of background information, documentation, and other juicy +tidbits on our main website. Explore it thoroughly. Find it at +[www.netsurf-browser.org](http://www.netsurf-browser.org/). + +We have a commitment to support RISC OS +--------------------------------------- + +You've most likely not heard of RISC OS. It's possible by the end of +your work with us you'll wish you never had. We have a history of +supporting RISC OS (it was our first platform) and we have a commitment +to continue doing so. Anything you write that's platform agnostic should +work well on RISC OS. See Caveat RISC OS for a list of gotchas. + +Read what documentation exists +------------------------------ + +There isn't currently much documentation for NetSurf's source code, but +it's all well worth reading. Start with the documents in Subversion. + +Remember, we're British +----------------------- + +Well, in the most part, anyway. We consider tea, beer and curry all more +important than NetSurf. We have a seemingly unnatural fascination with +the weather. Don't be surprised by this. Also, our source code has an +(unwritten, mostly) rule that things should be spelt in British English. +So colour rather than color, etc. + +Please don't cut corners in your communications +----------------------------------------------- + +Contractions like **u** for **you** in emails and IRC conversation make +us cringe. Please avoid! + |