OSGeo - User contributions [en]

User talk:Alex-mathew

2020-05-19T12:35:31Z

Madi: Welcome!

'''Welcome to ''OSGeo''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Madi|Madi]] ([[User talk:Madi|talk]]) 05:35, 19 May 2020 (PDT)

User:Alex-mathew

2020-05-19T12:35:31Z

Madi: Creating user page for new user.

GSoC`20 student developer working on simple transaction implementation in pygeoapi.

User talk:FarheenBano

2020-05-19T12:35:11Z

Madi: Welcome!

User:FarheenBano

2020-05-19T12:35:10Z

Madi: Creating user page for new user.

I am Farheen Bano. I have done my B.Tech in Computer Science Engineering from West Bengal University of Technology. I am currently pursuing my Master's in Geo-informatics Engineering under Centre of Studies in Resources Engineering from Indian Institute of Technology Bombay, Mumbai, India.

User talk:Rajhim2

2020-05-18T15:37:01Z

Madi: Welcome!

User:Rajhim2

2020-05-18T15:37:01Z

Madi: Creating user page for new user.

Final year undergraduate pursuing B.Tech in Information Technology from NIT Srinagar.

User talk:Prakashupes

2020-05-18T15:28:06Z

Madi: Welcome!

User:Prakashupes

2020-05-18T15:28:05Z

Madi: Creating user page for new user.

Pursuing B.Tech in Computer Science Engineering. Positive attitude towards work and great ability towards the result-oriented output. Passionate about contributing to Open Source projects and having good problem-solving skills using algorithms and data structures. I am adaptive to any new technology with good communication skills and effective leadership quality.

User talk:Jolicar

2020-05-16T06:10:36Z

Madi: Welcome!

User:Jolicar

2020-05-16T06:10:36Z

Madi: Creating user page for new user.

Master degree student on Geomatic Engineering and Geoinformation at the Universidad Politécnica de Valencia (UPV). Nowadays I have been selected to Google Summer of Code 2020 with OSGeo and gvSIG.

User talk:Belgacem nedjima

2020-05-16T06:10:18Z

Madi: Welcome!

User:Belgacem nedjima

2020-05-16T06:10:17Z

Madi: Creating user page for new user.

Computer Science and Engineering student, Google Summer of Code participant working on the QGIS 3D project

User talk:Krashish8

2020-05-15T10:16:13Z

Madi: Welcome!

User:Krashish8

2020-05-15T10:16:13Z

Madi: Creating user page for new user.

I am a GSoC ‘20 student and an Open Source Enthusiast. I will be working as an Open Source Contributor with the pgRouting community, under the OSGeo organization, an umbrella organization, for the upcoming summers.

The link to my GSoC 2020 project: https://summerofcode.withgoogle.com/projects/#5537889326202880.

User talk:Aditi Sawant

2020-05-15T09:50:55Z

Madi: Welcome!

User:Aditi Sawant

2020-05-15T09:50:47Z

Madi: Creating user page for new user.

My name is Aditi Mohan Sawant. I am Computer Science graduate from Mumbai University, pursuing Master's degree in Geoinformatics Engineering under Centre of studies in Resource Engineering, Indian Institute of Technology Bombay,Mumbai, India.

Google Summer of Code 2018

2019-09-03T09:25:40Z

Madi: /* Welcome to the OSGeo Google Summer of Code 2018 page */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

== Welcome to the OSGeo [https://developers.google.com/open-source/gsoc/ Google Summer of Code] 2018 page ==

* OSGeo's [[Google_Summer_of_Code_Application_2018|application]] to GSoC 2018, as a mentoring organization.
* If you are a '''student''', please visit our [[Google Summer of Code 2018 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages
* If you are a '''mentor''' you should go to our [[Google Summer of Code 2018 Administrative]] page.
* See [[Google Summer of Code 2018 Accepted]] students
* GSoC 2018 is over. See the '''outcomes at [[Google Summer of Code 2018 Results]]'''
* [[Google Summer of Code 2018 Mentor Summit]]

See also older Google Summer of Code
[[Google Summer of Code 2017|2017]],
[[Google Summer of Code 2016|2016]],
[[Google Summer of Code 2015|2015]],
[[Google Summer of Code 2014|2014]],
[[Google Summer of Code 2013|2013]],
[[Google Summer of Code 2012|2012]],
[[Google Summer of Code 2011|2011]],
[[Google Summer of Code 2010|2010]],
[[Google Summer of Code 2009|2009]],
[[Google Summer of Code 2008|2008]] and
[[Google_Summer_of_Code_2007|2007]] wiki pages for previous ideas and blogs from the 180+ students we've graduated through the program already.

You can subscribe to the OSGeo Google Summer of Code Mailing List here:

: http://lists.osgeo.org/mailman/listinfo/soc

[[Category:Google Summer of Code]]

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:36:24Z

Madi: /* Google Summer of Code 2019 Mentor Summit */

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:35:01Z

Madi:

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:34:09Z

Madi: /* OSGeo Delegates 2018 */

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:33:36Z

Madi: /* GSoC Mentor Candidates */

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:33:09Z

Madi: /* Google Summer of Code 2019 Mentor Summit */

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:32:29Z

Madi: /* Google Summer of Code 2019 Mentor Summit */

Google Summer of Code 2019 Mentor Summit

2019-08-05T10:31:55Z

Madi:

Google Summer of Code 2019 Mentor Summit

2019-08-05T08:35:28Z

Madi: /* Proposed tool for Random Selection */

Google Summer of Code 2019 Mentor Summit

2019-08-05T08:35:09Z

Madi:

Google Summer of Code 2019 Mentor Summit

2019-08-05T08:33:37Z

Madi: /* Google Summer of Code 2019 Mentor Summit */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2019]] @ OSGeo wiki page.

= Google Summer of Code 2019 Mentor Summit =

Each year Google hosts the "Mentor Summit" event at their headquarters, where up to 3 OSGeo delegates can attend. The date for this year's summit is: [https://developers.google.com/open-source/gsoc/2019/mentor-oa-announcements#may_17_2019_the_2019_google_summer_of_code_mentor_summit Thursday, October 17 - Sunday, October 20 2019].

== Selection Process ==

For 2019 we'll use the same rules as decided last year:

* Of the 3 OSGeo delegates, an admin, a GSoC mentor and a GCI mentor, unless no admins or no mentors apply to go, in which case, it'll be 2 admins or 2 mentors for GSoC. The GCI mentor's invitation has been sent separately, so if no GCI mentor candidates to go, nobody can replace him / her.
* Eligibility:
** must comply with Google requirements (must be 2019 Mentors with assigned student projects or a 2019 Organization Administrator);
** for mentors : must be mentor of an OSGeo project (at least as an OSGeo [[OSGeo_Community_Projects|community project]] or as a project entered into OSGeo [https://wiki.osgeo.org/wiki/Incubation_Committee#Projects_Currently_In_Incubation incubation], if not an official OSGeo project), as you would be a delegate of the OSGeo foundation.
* The call is open to hear who is interested to go. Whoever responds must COMMIT to go, otherwise you will take away the opportunity from someone else. Deadline for expression of interest is 8th August. Please enter your names in this page.
* Selection: we agreed that we must make a (fully transparent, open) lottery (Thanks Victoria). We will use a randomizer tool (below) to decide if need be. Time is short and people need to make paperwork for VISA. Please sign your name below if you are interested to attend.
* Other requirements: '''the selected delegates are requested to make a report after returning home from the summit'''.

== GSoC Mentor Candidates ==

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery

=== GSoC Admins ===

* Add your name here

=== Mentors ===

* Add your name here

=== Draw Time ===

...

=== Lottery Results ===

*

== GCI Mentor Candidates ==

Google has recently notified the OSGeo admins that Google would like to invite 1 of the OSGeo mentors from GCI 2017 to come to the [https://sites.google.com/view/gsoc-mentorsummit-2018/home GSoC 2018 Mentor Summit] (to possibly have a total of 3 OSGeo attendees at the summit). Google will add $1100 to the stipend that is sent in early September, if OSGeo decides to send a GCI mentor to the GSoC 2018 summit.

OSGeo admins have agreed to open the opportunity to attend to the recent OSGeo GCI mentors, using a lottery to decide if need be. Here are the requirements:

* Eligibility:
** must comply with Google requirements (must have been a 2017 GCI Mentor for OSGeo);
** must have been a mentor who participated in at least one OSGeo project task instance, working with a student (meaning that you interacted with a student on at least one instance, through the GCI Dashboard)

=== Sign Below ===

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery

* [[Victoria Rautenbach]]
* [[user:vidhan13j07|Vidhan Jain]]
* add your name here

=== Draw Time ===

2018-08-20 @ [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=8&day=20&hour=14&min=0&sec=0 14.00 UTC]

=== Proposed tool for Random Selection ===

* [https://www.randompicker.com/ RandomPicker.com]
** free for non-profit organizations
** jmckenna has created an account for "OSGeo"
** we can create 5 draws per day (they refer to the draws as "projects")
** a record is kept of the draw
*** example of a test draw result, for mentors (scroll the page down, you will see that "Tanya" won): https://app.randompicker.com/Project/Public/Protocol.aspx?Key=543299x22118

=== Report ===

The selected OSGeo delegates are required to make a report after returning home from the summit. GCI delegate is requested to send it to the "gci-discuss" OSGeo mailing list. All, please write your report here.

=== Lottery Results ===

*

== OSGeo Delegates 2018 ==

*

== Reports ==

[[Category: Google Summer of Code]]

Google Summer of Code 2019 Mentor Summit

2019-08-05T08:33:22Z

Madi: Created page with "<center> link=https://developers.google.com/open-source/gsoc/ @ Image:Osgeo-logo.png|300px|link=http://www.osgeo.o..."

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2019]] @ OSGeo wiki page.

= Google Summer of Code 2019 Mentor Summit =

Each year Google hosts the "Mentor Summit" event at their headquarters, where up to 3 OSGeo delegates can attend. The date for this year's summit is: [https://developers.google.com/open-source/gsoc/2019/mentor-oa-announcements#may_17_2019_the_2019_google_summer_of_code_mentor_summit Thursday, October 17 - Sunday, October 20 2019].

== Selection Process ==

For 2019 we'll use the same rules as decided last year:

* Of the 3 OSGeo delegates, an admin, a GSoC mentor and a GCI mentor, unless no admins or no mentors apply to go, in which case, it'll be 2 admins or 2 mentors for GSoC. The GCI mentor's invitation has been sent separately, so if no GCI mentor candidates to go, nobody can replace him / her.
* Eligibility:
** must comply with Google requirements (must be 2019 Mentors with assigned student projects or a 2019 Organization Administrator);
** for mentors : must be mentor of an OSGeo project (at least as an OSGeo [[OSGeo_Community_Projects|community project]] or as a project entered into OSGeo [https://wiki.osgeo.org/wiki/Incubation_Committee#Projects_Currently_In_Incubation incubation], if not an official OSGeo project), as you would be a delegate of the OSGeo foundation.
* The call is open to hear who is interested to go. Whoever responds must COMMIT to go, otherwise you will take away the opportunity from someone else. Deadline for expression of interest is 8th August. Please enter your names in this page.
* Selection: we agreed that we must make a (fully transparent, open) lottery (Thanks Victoria). We will use a randomizer tool (below) to decide if need be. Time is short and people need to make paperwork for VISA. Please sign your name below if you are interested to attend.
* Other requirements: '''the selected delegates are requested to make a report after returning home from the summit'''.

== GSoC Mentor Candidates ==

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery

=== GSoC Admins ===

* Add your name here

=== Mentors ===

* Add your name here

=== Draw Time ===

...

=== Lottery Results ===

*

== GCI Mentor Candidates ==

Google has recently notified the OSGeo admins that Google would like to invite 1 of the OSGeo mentors from GCI 2017 to come to the [https://sites.google.com/view/gsoc-mentorsummit-2018/home GSoC 2018 Mentor Summit] (to possibly have a total of 3 OSGeo attendees at the summit). Google will add $1100 to the stipend that is sent in early September, if OSGeo decides to send a GCI mentor to the GSoC 2018 summit.

OSGeo admins have agreed to open the opportunity to attend to the recent OSGeo GCI mentors, using a lottery to decide if need be. Here are the requirements:

* Eligibility:
** must comply with Google requirements (must have been a 2017 GCI Mentor for OSGeo);
** must have been a mentor who participated in at least one OSGeo project task instance, working with a student (meaning that you interacted with a student on at least one instance, through the GCI Dashboard)

=== Sign Below ===

Signing below, you commit to go to the summit in the event of a positive outcome in the lottery

* [[Victoria Rautenbach]]
* [[user:vidhan13j07|Vidhan Jain]]
* add your name here

=== Draw Time ===

2018-08-20 @ [https://www.timeanddate.com/worldclock/fixedtime.html?year=2018&month=8&day=20&hour=14&min=0&sec=0 14.00 UTC]

=== Proposed tool for Random Selection ===

* [https://www.randompicker.com/ RandomPicker.com]
** free for non-profit organizations
** jmckenna has created an account for "OSGeo"
** we can create 5 draws per day (they refer to the draws as "projects")
** a record is kept of the draw
*** example of a test draw result, for mentors (scroll the page down, you will see that "Tanya" won): https://app.randompicker.com/Project/Public/Protocol.aspx?Key=543299x22118

=== Report ===

The selected OSGeo delegates are required to make a report after returning home from the summit. GCI delegate is requested to send it to the "gci-discuss" OSGeo mailing list. All, please write your report here.

=== Lottery Results ===

*

== OSGeo Delegates 2018 ==

*

== Reports ==

[[Category: Google Summer of Code]]

Board Meeting 2019-07-29

2019-07-23T13:25:27Z

Madi: /* Current items */

This board meeting is '''scheduled 29 July 2019''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=7&day=29&hour=16&min=0&sec=0&p1=256&p2=286&p3=161&p4=269 16:00 - 17:00 UTC], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.

== Agenda ==

=== Current items ===

Items in italic are recurring at each meeting.

Agenda:

* ''roll call''
* ''appoint meeting chair, meeting scribe/secretary''
* ''Review and approve past minutes''
** [[Board_Meeting_2019-06-24]]
* Review outstanding action items
* Planning F2F Meeting
* Discuss whether to support the [https://publiccode.eu/ PublicCode campaign] by [https://fsfe.org/index.it.html FSFE]
** [https://lists.osgeo.org/pipermail/discuss/2019-July/038443.html Request]
* Additional topics are welcome, meeting is open and you are encouraged to attend

== Minutes ==

* Presiding:
* Scribing:

Attending:

* tbd

=== Review and approve past minutes ===

Minutes recorded here [[https://wiki.osgeo.org/wiki/Board_Meeting_2019-06-24]]

=== Review of outstanding action items ===

[[Category:Board]]
[[Category:Board Meetings 2019]]

Google Summer of Code Recommendations for Students

2019-06-03T07:01:01Z

Madi: /* Weekly reports */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see your weekly progress report posted to the soc@osgeo and the developer mailing list of your project. You are requested to send the report even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to expand your report, however this is the minimum required.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-06-03T07:00:03Z

Madi: /* Weekly reports */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see your weekly progress report posted to the soc@osgeo and the developer mailing list of your project. You are requested to send the report even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to expand your report, however this is the minimum required.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-06-03T06:58:22Z

Madi:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, your weekly progress report. You are requested to send the report mail even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to expand your report, however this is the minimum required.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

User talk:Vicennial

2019-05-10T07:10:38Z

Madi: Welcome!

User:Vicennial

2019-05-10T07:10:38Z

Madi: Creating user page for new user.

I am a GSoC 2019 student. The link to my project: https://summerofcode.withgoogle.com/projects/#5188028799123456
I will be working with the pgRouting community, under the OSGeo umbrella over the upcoming summer.

User talk:Fenilgmehta

2019-05-09T06:31:57Z

Madi: Welcome!

User:Fenilgmehta

2019-05-09T06:31:57Z

Madi: Creating user page for new user.

GitHub: https://github.com/fenilgmehta
Linkedin: www.linkedin.com/in/fenil-mehta

I practice data structure and algorithm questions at CodeChef.
Codechef: https://www.codechef.com/users/fenilgmehta

I have created a few Android applications which are live on the Google Play Store
Google Play Store: https://play.google.com/store/apps/developer?id=Fenil+Mehta&hl=en_IN

GSoC 2019 student

Google Summer of Code 2019 Accepted

2019-05-08T12:02:22Z

Madi:

User talk:Ismailsunni

2019-05-08T09:59:56Z

Madi: Welcome!

User:Ismailsunni

2019-05-08T09:59:56Z

Madi: Creating user page for new user.

I am a [geospatial] software engineer who likes open source. I work mostly with Python, QGIS, and Django.
I got my bachelor degree in informatics engineering (Institut Teknologi Bandung, Indonesia)
Currently, I am studying in Germany for pursuing my master degree in geospatial technologies.

Google Summer of Code Recommendations for Students

2019-04-05T15:10:31Z

Madi: /* 3. Timeline */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

INSPIRE tools inventory

2019-04-05T15:04:08Z

Madi: /* Other */

According to the INSPIRE Directive, View and Download services should be set up for the data which is within scope and metadata should be provided. Furthermore, data needs to comply with the INSPIRE data schemes and monitoring, testing and validation of the data, metadata and services should be executed.

This page aims at building an inventory of the tools aiding the INSPIRE implementation. The OsGeo-Live environment includes Open Source software that is needed to implement these different INSPIRE components. Furthermore, several software tools have been developed within EU-funded projects and are suitable for reuse, but are often unknown to the broader community.

If you are aware of free software implementing INSPIRE specifications, please contribute to this inventory.

== Software ==

Please add a short description of the software implementation and a link to the online resource.

=== Metadata management ===

==== OSGeoLive tools ====
* [https://live.osgeo.org/en/quickstart/geonetwork_quickstart.html GeoNetwork] is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer. It is currently used in numerous Spatial Data Infrastructure initiatives across the world.

==== Other ====
* [https://joinup.ec.europa.eu/software/euosme/description/ INSPIRE EUOSME]: (European Open Source Metadata Editor) developed by EC-JRC in the EuroGEOSS project, and deployed in the [http://inspire-geoportal.ec.europa.eu/editor/ INSPIRE Geoportal] to allow user to test editing capabilities and testing ISO19139 XML files. Unfortunately, the development of the editor has been discontinued.
* [https://github.com/GeoSmartCity-CIP/Excel-Metadata INSPIRE Excel file]: developed within [http://www.geosmartcity.eu/ GeoSmartCity project] to collect INSPIRE XML19139 compliant metadata in easy and quick way
* [http://52north.org/communities/metadata-management/smarteditor smartEditor]: smartEditor is a web based editor to easily create and update metadata documents on geospatial data sets, services, series and applications and many more resources supporting ISO19115/19119 and the INSPIRE metadata specification (INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119)
* [http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support GRASS GIS ISO/INSPIRE Metadata support] developed within [http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS Google Summer of Code 2014]

=== Data storage/management ===
* [http://postgis.net/ PosgGIS] adds spatial capabilities to the PostgreSQL relational database. It extends PostgreSQL so it can store, query, and manipulate spatial data. In this Quickstart we will use ‘PostgreSQL’ when describing general database functions, and ‘PostGIS’ when describing the additional spatial functionality provided by PostGIS.
* [http://www.rasdaman.org Rasdaman]: flexible, scalable spatio-temporal raster server, supporting OGC WMS, WCS, WCPS, WPS; OGC WCS Core Reference Implementation.
* [http://www.gaia-gis.it/gaia-sins/ SpatiaLite]: ...

=== Data modeling ===
* [http://idm.spatialdbgroup.polimi.it/it/inspire-data-model-tools/ INSPIRE Data Model Tools]: developed by Politecnico di Milano to facilitate the browsing of INSPIRE Data Specifications and provide procedure to structure PostGIS pseudo-INSPIRE SQL structure

=== Data mapping/transformation ===
==== OSGeoLive tools ====
* [http://www.deegree.org/ deegree]: deegree supports a internal DSL (a XML configuration file) to specify mappings from a database model into a GML application schema which allow on-the-fly transformation of data.
* [https://live.osgeo.org/en/quickstart/geokettle_quickstart.html Geokettle] is an ETL tool and can be useful to transform an existing dataset to comply with the schemes defined by the INSPIRE Directive. ''note: currently set to be retired in Live 11''
* In GDAL, the GMLAS driver is available which can read and write XML files of arbitrary structure, included those containing so-called Complex Features, provided that they are accompanied by one or several XML schemas that describe the structure of their content. While this driver is generic to any XML schema, the main target is to be able to read and write documents referencing directly or indirectly to the GML namespace.

==== Other ====
* [http://www.esdi-community.eu/projects/hale HALE] is a tool for defining and evaluating conceptual schema mappings. HALE allows domain experts to create logically and semantically consistent mappings and to transform geodata based on these mappings. Furthermore, a major focus is put on the documentation of the schema transformation process and its impacts, e.g. in the form of lineage information attached to the resultant transformed data . Within the context of INSPIRE, data transformations will be needed both to publish data in compliance with the INSPIRE schemes and to use the published (and downloaded) data in combination with other sources.
* [http://inspire-foss.org inspire-foss.org INSPIRE FOSS]: ETL-tooling for INSPIRE Data harmonization and harmonized web services (largely unmaintained)
* [https://joinup.ec.europa.eu/software/java4inspire/description Java4INSPIRE]: is a java library to handle INSPIRE data as java objects; it may be used to transform existing spatial datasets into INSPIRE compliant datasets
* [http://www.stetl.org Stetl]: Python-framework for ETL. With [https://github.com/justb4/stetl/tree/master/examples/basics/10_jinja2_templating Examples] for INSPIRE data harmonization.

=== Network services ===

==== Discovery ====
* [http://pycsw.org pycsw]: OGC CSW server. Standalone or embeddable. Powers CSW in CKAN, GeoNode. OGC Reference Implementation
* Geonetwork
* [http://www.deegree.org/ deegree]: Provides an implementation of a OGC CSW 2.0.2 APISO server. Supporting harvest operation and storage of MD records for centralized approach. The [https://live.osgeo.org/fr/quickstart/deegree_quickstart.html Quickstart of Degree for the OsGeo-Live] uses an INSPIRE example.

==== View ====
* [http://geoserver.org/ GeoServer] is a tool for serving maps for other clients to draw. It allows to setup view and download services as required by the INSPIRE Directive.
* [http://www.deegree.org/ deegree]: Provides an OGC compliant WMS 1.1.1 and 1.3.0 server (OGC reference implementation). Additional it has an implementation of the OGC WMTS 1.0 standard.
* [http://mapserver.org/ MapServer] is an Open Source server-based application that allows you to publish geographic map images and vector data through the internet using OGC standards such as WMS, WFS, and WCS.

==== Download ====
* GeoServer
* [http://www.deegree.org/ deegree]: Provides an OGC compliant WFS 2.0 support the Simple conformance class and GML 3.2.1 (Both are OGC reference implementations!)
* MapServer
* [https://wiki.52north.org/bin/view/SensorWeb/SensorObservationServiceIVDocumentation 52°North Sensor Observation Service 4.x]: Enhanced SOS implementation for serving observation data compliant with the INSPIRE requirements for Download Services

=== Validation services ===
* [http://inspire-geoportal.ec.europa.eu/validator2/ INSPIRE Geoportal Validator]: developed by EC-JRC, it is used in the context of the INSPIRE Geoportal to perform validation of the metadata of resources discovered through the Member State Discovery Services.
* [https://github.com/inspire-eu-validation/ INSPIRE Validation & conformity testing]: Workspace for EU INSPIRE MIG Validation & conformity testing sub-group on GitHub
* [http://cloud.epsilon-italia.it/eenvplus_new/ eENVplus Validation Service]: developed by [http://www.epsilon-italia.it/ Epsilon Italia], in the frame of the [http://www.eenvplus.eu/ eENVplus project], is an online tool for the validation of INSPIRE datasets. It is freely accessible and open source, built upon TEAM Engine and the OGC CITE GML 3.2 Conformance Test Suite. It provides Executable Test Suites (ETS) implementing the Abstract Test Suites (ATS) which are included in the Annex A of the INSPIRE Data Specifications.

=== Clients ===
* [http://www.qgis.org/ QGIS] can be used to consume INSPIRE compliant view and download services. The [https://github.com/INSPIRE-MIF/gml_application_schema_toolbox QGIS plugin ‘GML Application Schema Toolbox’] makes use of the GMLAS driver for GDAL and aims to develop tools to manipulate complex features in a GIS desktop application. On the related [https://github.com/INSPIRE-MIF/qgis-ogr-gmlas GitHub page] ‘Consumption and use of GML complex features like INSPIRE harmonised data (vector), GeoSciML within QGIS’, specific INSPIRE use cases are described and illustrated.
* [http://www.geomajas.org/ geomajas] can be used to support eGov workflows and create a controlled environment where processes can be executed based on available INSPIRE data.

=== Registry ===
* [https://joinup.ec.europa.eu/software/re3gistry/description INSPIRE Re3gistry] implemented by EC-JRC and deployed on the [http://inspire.ec.europa.eu/registry/ INSPIRE web site]

=== GeoPortals ===
* [http://www.getmap.gr/v2/eng/index.php?option=com_content&task=view&id=255&Itemid=554 GET SDI Portal] developed by [http://www.getmap.eu/ Geospatial Enabling Technologies Ltd]. A ready to deploy, fully featured SDI Services client already used at regional government level INSPIRE Geoportals.

=== Other ===
* [https://joinup.ec.europa.eu/community/are3na/home Are3na] is A Reusable INSPIRE Reference Platform. This open community aims to support access to common reusable software and other components for spatial data in European e-government.
* [https://inspire-reference.jrc.ec.europa.eu/tools INSPIRE in Practice] is a collaborative platform with the aim of bringing together INSPIRE implementers, solution providers, and application developers. Among other content, it provides an inventory of useful tools supporting the INSPIRE implementation tasks. Those tools can range from desktop/server software, libraries, plug-ins, online services and many more technical products and solutions that help people to share INSPIRE data, metadata and services.

== Actions to improve the existing tools ==
* It could be useful that OSGeoLive projects listed on this page include some INSPIRE example in their quickstart documentation to illustrate their usefulness in the specific perspective of INSPIRE.
* It would be beneficial having these tools in the [https://inspire-reference.jrc.ec.europa.eu/tools INSPIRE in Practice platform tool section] highlighting how those ones actually support INSPIRE, for example by adding the [https://inspire-reference.jrc.ec.europa.eu/vocabulary/tasks INSPIRE tasks] they support (See example: https://inspire-reference.jrc.ec.europa.eu/tools/geoserver)

[[Category: Standards]]
[[Category: INSPIRE]]

INSPIRE tools inventory

2019-04-05T13:35:37Z

Madi: /* Other */

According to the INSPIRE Directive, View and Download services should be set up for the data which is within scope and metadata should be provided. Furthermore, data needs to comply with the INSPIRE data schemes and monitoring, testing and validation of the data, metadata and services should be executed.

This page aims at building an inventory of the tools aiding the INSPIRE implementation. The OsGeo-Live environment includes Open Source software that is needed to implement these different INSPIRE components. Furthermore, several software tools have been developed within EU-funded projects and are suitable for reuse, but are often unknown to the broader community.

If you are aware of free software implementing INSPIRE specifications, please contribute to this inventory.

== Software ==

Please add a short description of the software implementation and a link to the online resource.

=== Metadata management ===

==== OSGeoLive tools ====
* [https://live.osgeo.org/en/quickstart/geonetwork_quickstart.html GeoNetwork] is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer. It is currently used in numerous Spatial Data Infrastructure initiatives across the world.

==== Other ====
* [https://joinup.ec.europa.eu/software/euosme/description/ INSPIRE EUOSME]: (European Open Source Metadata Editor) developed by EC-JRC in the EuroGEOSS project, and deployed in the [http://inspire-geoportal.ec.europa.eu/editor/ INSPIRE Geoportal] to allow user to test editing capabilities and testing ISO19139 XML files. Unfortunately, the development of the editor has been discontinued. The source code (a very old version of it) has been published here: https://joinup.ec.europa.eu/release/euosme-103/103
* [https://github.com/GeoSmartCity-CIP/Excel-Metadata INSPIRE Excel file]: developed within [http://www.geosmartcity.eu/ GeoSmartCity project] to collect INSPIRE XML19139 compliant metadata in easy and quick way
* [http://52north.org/communities/metadata-management/smarteditor smartEditor]: smartEditor is a web based editor to easily create and update metadata documents on geospatial data sets, services, series and applications and many more resources supporting ISO19115/19119 and the INSPIRE metadata specification (INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119)
* [http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support GRASS GIS ISO/INSPIRE Metadata support] developed within [http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS Google Summer of Code 2014]

=== Data storage/management ===
* [http://postgis.net/ PosgGIS] adds spatial capabilities to the PostgreSQL relational database. It extends PostgreSQL so it can store, query, and manipulate spatial data. In this Quickstart we will use ‘PostgreSQL’ when describing general database functions, and ‘PostGIS’ when describing the additional spatial functionality provided by PostGIS.
* [http://www.rasdaman.org Rasdaman]: flexible, scalable spatio-temporal raster server, supporting OGC WMS, WCS, WCPS, WPS; OGC WCS Core Reference Implementation.
* [http://www.gaia-gis.it/gaia-sins/ SpatiaLite]: ...

=== Data modeling ===
* [http://idm.spatialdbgroup.polimi.it/it/inspire-data-model-tools/ INSPIRE Data Model Tools]: developed by Politecnico di Milano to facilitate the browsing of INSPIRE Data Specifications and provide procedure to structure PostGIS pseudo-INSPIRE SQL structure

=== Data mapping/transformation ===
==== OSGeoLive tools ====
* [http://www.deegree.org/ deegree]: deegree supports a internal DSL (a XML configuration file) to specify mappings from a database model into a GML application schema which allow on-the-fly transformation of data.
* [https://live.osgeo.org/en/quickstart/geokettle_quickstart.html Geokettle] is an ETL tool and can be useful to transform an existing dataset to comply with the schemes defined by the INSPIRE Directive. ''note: currently set to be retired in Live 11''
* In GDAL, the GMLAS driver is available which can read and write XML files of arbitrary structure, included those containing so-called Complex Features, provided that they are accompanied by one or several XML schemas that describe the structure of their content. While this driver is generic to any XML schema, the main target is to be able to read and write documents referencing directly or indirectly to the GML namespace.

==== Other ====
* [http://www.esdi-community.eu/projects/hale HALE] is a tool for defining and evaluating conceptual schema mappings. HALE allows domain experts to create logically and semantically consistent mappings and to transform geodata based on these mappings. Furthermore, a major focus is put on the documentation of the schema transformation process and its impacts, e.g. in the form of lineage information attached to the resultant transformed data . Within the context of INSPIRE, data transformations will be needed both to publish data in compliance with the INSPIRE schemes and to use the published (and downloaded) data in combination with other sources.
* [http://inspire-foss.org inspire-foss.org INSPIRE FOSS]: ETL-tooling for INSPIRE Data harmonization and harmonized web services (largely unmaintained)
* [https://joinup.ec.europa.eu/software/java4inspire/description Java4INSPIRE]: is a java library to handle INSPIRE data as java objects; it may be used to transform existing spatial datasets into INSPIRE compliant datasets
* [http://www.stetl.org Stetl]: Python-framework for ETL. With [https://github.com/justb4/stetl/tree/master/examples/basics/10_jinja2_templating Examples] for INSPIRE data harmonization.

=== Network services ===

==== Discovery ====
* [http://pycsw.org pycsw]: OGC CSW server. Standalone or embeddable. Powers CSW in CKAN, GeoNode. OGC Reference Implementation
* Geonetwork
* [http://www.deegree.org/ deegree]: Provides an implementation of a OGC CSW 2.0.2 APISO server. Supporting harvest operation and storage of MD records for centralized approach. The [https://live.osgeo.org/fr/quickstart/deegree_quickstart.html Quickstart of Degree for the OsGeo-Live] uses an INSPIRE example.

==== View ====
* [http://geoserver.org/ GeoServer] is a tool for serving maps for other clients to draw. It allows to setup view and download services as required by the INSPIRE Directive.
* [http://www.deegree.org/ deegree]: Provides an OGC compliant WMS 1.1.1 and 1.3.0 server (OGC reference implementation). Additional it has an implementation of the OGC WMTS 1.0 standard.
* [http://mapserver.org/ MapServer] is an Open Source server-based application that allows you to publish geographic map images and vector data through the internet using OGC standards such as WMS, WFS, and WCS.

==== Download ====
* GeoServer
* [http://www.deegree.org/ deegree]: Provides an OGC compliant WFS 2.0 support the Simple conformance class and GML 3.2.1 (Both are OGC reference implementations!)
* MapServer
* [https://wiki.52north.org/bin/view/SensorWeb/SensorObservationServiceIVDocumentation 52°North Sensor Observation Service 4.x]: Enhanced SOS implementation for serving observation data compliant with the INSPIRE requirements for Download Services

=== Validation services ===
* [http://inspire-geoportal.ec.europa.eu/validator2/ INSPIRE Geoportal Validator]: developed by EC-JRC, it is used in the context of the INSPIRE Geoportal to perform validation of the metadata of resources discovered through the Member State Discovery Services.
* [https://github.com/inspire-eu-validation/ INSPIRE Validation & conformity testing]: Workspace for EU INSPIRE MIG Validation & conformity testing sub-group on GitHub
* [http://cloud.epsilon-italia.it/eenvplus_new/ eENVplus Validation Service]: developed by [http://www.epsilon-italia.it/ Epsilon Italia], in the frame of the [http://www.eenvplus.eu/ eENVplus project], is an online tool for the validation of INSPIRE datasets. It is freely accessible and open source, built upon TEAM Engine and the OGC CITE GML 3.2 Conformance Test Suite. It provides Executable Test Suites (ETS) implementing the Abstract Test Suites (ATS) which are included in the Annex A of the INSPIRE Data Specifications.

=== Clients ===
* [http://www.qgis.org/ QGIS] can be used to consume INSPIRE compliant view and download services. The [https://github.com/INSPIRE-MIF/gml_application_schema_toolbox QGIS plugin ‘GML Application Schema Toolbox’] makes use of the GMLAS driver for GDAL and aims to develop tools to manipulate complex features in a GIS desktop application. On the related [https://github.com/INSPIRE-MIF/qgis-ogr-gmlas GitHub page] ‘Consumption and use of GML complex features like INSPIRE harmonised data (vector), GeoSciML within QGIS’, specific INSPIRE use cases are described and illustrated.
* [http://www.geomajas.org/ geomajas] can be used to support eGov workflows and create a controlled environment where processes can be executed based on available INSPIRE data.

=== Registry ===
* [https://joinup.ec.europa.eu/software/re3gistry/description INSPIRE Re3gistry] implemented by EC-JRC and deployed on the [http://inspire.ec.europa.eu/registry/ INSPIRE web site]

=== GeoPortals ===
* [http://www.getmap.gr/v2/eng/index.php?option=com_content&task=view&id=255&Itemid=554 GET SDI Portal] developed by [http://www.getmap.eu/ Geospatial Enabling Technologies Ltd]. A ready to deploy, fully featured SDI Services client already used at regional government level INSPIRE Geoportals.

=== Other ===
* [https://joinup.ec.europa.eu/community/are3na/home Are3na] is A Reusable INSPIRE Reference Platform. This open community aims to support access to common reusable software and other components for spatial data in European e-government.
* [https://inspire-reference.jrc.ec.europa.eu/tools INSPIRE in Practice] is a collaborative platform with the aim of bringing together INSPIRE implementers, solution providers, and application developers. Among other content, it provides an inventory of useful tools supporting the INSPIRE implementation tasks. Those tools can range from desktop/server software, libraries, plug-ins, online services and many more technical products and solutions that help people to share INSPIRE data, metadata and services.

== Actions to improve the existing tools ==
* It could be useful that OSGeoLive projects listed on this page include some INSPIRE example in their quickstart documentation to illustrate their usefulness in the specific perspective of INSPIRE.
* It would be beneficial having these tools in the [https://inspire-reference.jrc.ec.europa.eu/tools INSPIRE in Practice platform tool section] highlighting how those ones actually support INSPIRE, for example by adding the [https://inspire-reference.jrc.ec.europa.eu/vocabulary/tasks INSPIRE tasks] they support (See example: https://inspire-reference.jrc.ec.europa.eu/tools/geoserver)

[[Category: Standards]]
[[Category: INSPIRE]]

Google Summer of Code Recommendations for Students

2019-04-04T07:14:37Z

Madi: /* 6. GSoC participation */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-04-04T07:10:10Z

Madi: /* 3. Timeline */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-04-04T07:05:34Z

Madi: /* 3. Timeline */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code 2019 Ideas

2019-03-28T07:55:25Z

Madi: /* The ideas pages */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.

* See also ideas from [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].
-----

== OSGeo Google Summer of Code 2019 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!

* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2019 Administrative]] wiki page.

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

To add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation graduated projects ===

[[Image:logo-qgis.png|60px|right]]
* [https://github.com/qgis/QGIS/wiki/Google-Summer-of-Code-2019-Ideas '''QGIS''' Ideas ]: [https://qgis.org QGIS] is a user friendly Open Source GIS that runs on Linux, macOS and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2019 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-postgis.png|60px|right]]
* [https://trac.osgeo.org/postgis/wiki/GoogleSummerCode2019 '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2019_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.



=== OSGeo Foundation community projects ===

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas%3A-2019 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

=== OSGeo Guest Projects ===

[[Image:Mapmint-logo-small.png|60px|right]]
* [https://github.com/mapmint/mapmint/wiki/MapMint-In-Google-Summer-of-Code#google-summer-of-code-2019 '''MapMint''' Ideas]: [http://mapmint.com/ MapMint] is an internet-based Geographic Information System (GIS), which is designed to facilitate deployment of Spatial Data Infrastructure (SDI). MapMint combines various different software in a complete and coherent web mapping platform, thus helping users in building their own maps and web-applications."

=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|500px|center]]

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']

[Back to [[Google Summer of Code 2019]] @ OSGeo]
[[Category: Google Summer of Code]]

File:Mapmint-logo-small.png

2019-03-28T07:54:00Z

Madi:

Google Summer of Code 2019 Ideas

2019-03-28T07:52:31Z

Madi: Adding MapMint ideas page

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.

* See also ideas from [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].
-----

== OSGeo Google Summer of Code 2019 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!

* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2019 Administrative]] wiki page.

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

To add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation graduated projects ===

[[Image:logo-qgis.png|60px|right]]
* [https://github.com/qgis/QGIS/wiki/Google-Summer-of-Code-2019-Ideas '''QGIS''' Ideas ]: [https://qgis.org QGIS] is a user friendly Open Source GIS that runs on Linux, macOS and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2019 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-postgis.png|60px|right]]
* [https://trac.osgeo.org/postgis/wiki/GoogleSummerCode2019 '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2019_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software.



=== OSGeo Foundation community projects ===

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas%3A-2019 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

=== OSGeo Guest Projects ===

* [https://github.com/mapmint/mapmint/wiki/MapMint-In-Google-Summer-of-Code#google-summer-of-code-2019 '''MapMint''' Ideas]: [http://mapmint.com/ MapMint] is an internet-based Geographic Information System (GIS), which is designed to facilitate deployment of Spatial Data Infrastructure (SDI). MapMint combines various different software in a complete and coherent web mapping platform, thus helping users in building their own maps and web-applications."

=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|500px|center]]

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']

[Back to [[Google Summer of Code 2019]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-03-02T15:10:58Z

Madi:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2019_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Google Summer of Code Recommendations for Students

2019-02-26T09:15:20Z

Madi: /* Application instructions */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://summerofcode.withgoogle.com/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

-----
* Back to the main OSGeo [[Google Summer of Code 2019]] wiki page.
* Check out the [[Google_Summer_of_Code_2018_Ideas | Ideas web page]] or propose your own!

-----

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

'''OSGeo mailing lists of interest for GSoC students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated to GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].

If you want, feel free to write *more*. But three sentences is the bare minimum.

Please explicitly mention your project in the subject and in the introduction to the e-mail.

'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

During past years this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeo-of-code posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]