[OSM-dev] Google Summer of Code

[Graham Jones]

Hi All,

I am pleased to announce that OSM has been accepted to participate in this year's Google Summer of Code programme (http://www.google-melange.com/gsoc/org/google/gsoc2012/osm).

Thanks to all of you who have contributed to our ideas page (http://wiki.openstreetmap.org/wiki/GSoC_Project_Ideas_2012), which supported the application.

Over the next few weeks we can expect potential students to review the ideas page and contact us to seek clarification on ideas or guidance on how to develop them.

Ian Dees has set a good example in responding to such requests positively, and with a steer that a good start is to learn a bit about mapping.

I would be grateful if you would again review the ideas list and provide any clarifications that may help students in producing a project proposal from them.   

I would also like to hear from anyone that would be prepared to act as a mentor on this year's programme.    

I will do a bit more work on a wiki page that I have started on the process I propose to follow for this year's GSoC (http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/Processes), and send another update email so you know what we will be doing.

Thanks again for your support.

Regards

Graham.

--
Graham Jones

Hartlepool, UK.

[Philipp Borgers]

Congratulations!

Would it be possible that the students write some kind of regular
report, telling us about problems they solved, problems to solve etc.
Last time the traffic on the dev list was very low. Or is there a
mailing list I do not know?

Thank you for your great work!

Regards
Philipp

> _______________________________________________
> dev mailing list
> d...@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev

[H.S.Rai]

On Sat, Mar 17, 2012 at 5:06 AM, Philipp Borgers
<bor...@mi.fu-berlin.de> wrote:
>
> Congratulations!

:-)

> Would it be possible that the students write some kind of regular
> report,

IMO, can be. In what ever way we can communicate better, is acceptable
even without any hard rules.

> telling us about problems they solved, problems to solve etc.
> Last time the traffic on the dev list was very low.

There is a list of Mentors and students working for OSM, but
discussion on Dev List is important and a lot needed to be discussed
here.

Review of previous OSM projects, enhancing them and integrating them
may be considered an important task.

--
H.S.Rai

[Mikel Maron]

Well done!!!

 

* Mikel Maron * +14152835207 @mikel s:mikelmaron

---

From: Graham Jones <grahamj...@gmail.com>
To: OSM-talk Openstreetmap <ta...@openstreetmap.org>; OSM-Dev Openstreetmap <d...@openstreetmap.org>
Sent: Saturday, March 17, 2012 1:03 AM
Subject: [OSM-dev] Google Summer of Code

[Janani Nayanathara]

My congratulations to OpenStreetMap !

I am interested in and hoping to apply for the "Improve / Create Simple Android OSM editor" project as a student. I think this summer will be more interesting with OSM.

--
--Best Regards,

Janani Nayanathara,

Uva Wellassa University,

Sri Lanka.

[Graham Jones]

Hi Philipp,
You are quite right - one of our shortcomings over the last couple of years has been in communication with the wider osm community and we should improve that this year.

What we have had over the last couple of years is a private mailing list for mentors to discuss the proposals to make the choice of which to select, and one for the mentors and students to discuss their projects.   It was always my intention to report back to the wider community on how things are going, but that never really happened.

I will try to make sure that happens this year, but please ask again if you do not see this happening - 'pressure' from the wider community to know how things are going will help to encourage everyone involved.

Regards

Graham.

from my phone

On 16 Mar 2012 23:37, "Philipp Borgers" <bor...@mi.fu-berlin.de> wrote:

Congratulations!

Would it be possible that the students write some kind of regular

report, telling us about problems they solved, problems to solve etc.
Last time the traffic on the dev list was very low. Or is there a
mailing list I do not know?

Thank you for your great work!

Regards
Philipp

On Fri, 2012-03-16 at 19:33 +0000, Graham Jones wrote:

> Hi All,
> I am pleased to announce that OS...

[kabum]

Hi,

I am interested in "Nominatim (or alternative)", but there isn't any mentor mentioned. Where could I discuss about the idea?

Best regards,

Morris Jobke

[Graham Jones]

Hi,
Thank you for your interest in applying for GSoC with Openstreetmap.   This list will be fine to ask questions.

Here are a few suggestions to get you started:

- It is important to understand the fundamentals of what OSM is, so if you have not done so before, please start by creating an account and making some improvements to the map in your local area.

- It would also be good to look at the OSM data structure.  Details of the xml file format can be found on our wiki.

- If you search for Nominatim on the OSM wiki you should find some information on the current service and links to the source code to see how it currently does searching to see how it could be improved.

The project idea was suggested by 'sabas88' - could he/she provide some more information on the issues behind this project suggestion please?

Hope that helps.   Please feel free to ask more questions as you develop your proposal.

Regards

Graham

_______________________________________________
dev mailing list
d...@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev

[kabum]

Hi,

Am 19. März 2012 22:45 schrieb Graham Jones <grahamj...@gmail.com>:

Hi,
Thank you for your interest in applying for GSoC with Openstreetmap.   This list will be fine to ask questions.

Here are a few suggestions to get you started:

- It is important to understand the fundamentals of what OSM is, so if you have not done so before, please start by creating an account and making some improvements to the map in your local area.

I heard of OSM a long time ago, but was just to lazy to contribute to. So I tried these days and I was really surprised how fast changes are visible in the rendered map. I've taken several notes of my surrounding waiting for filled into the OSM database. :)

- It would also be good to look at the OSM data structure.  Details of the xml file format can be found on our wiki. 

Done :) 

- If you search for Nominatim on the OSM wiki you should find some information on the current service and links to the source code to see how it currently does searching to see how it could be improved. 

The project idea was suggested by 'sabas88' - could he/she provide some more information on the issues behind this project suggestion please?

I've asked him and the only answer was a link to the GSoC project site in the OSM wiki. :(

I read a lot about OSM, it's mechanism, assistant tools, etc and also about Nominatim and I realized, that this isn't what I want to do. I've looking for some other contribution to OSM and GSoC and found the suggestion for an quality assurance tool specialized for edits/changesets (by Derick Rethans). There are many quality assurance tools but no one like this - or have I missed it?

The idea is to have a engine that gets a (set of) changesets or edits and analyse them. It should detect things like logical mistakes, mass deletions without corresponding insertions, etc and take also user metadata like duration of membership or count of his edits into account. It would be great if it compare the changes with current state of the data in this area and detect senseless checks, because the data is out of date and already corrected. 

Some other things to keep in mind while planning:

- extensibility through "plugins": engine (calls)-> several detection plugins

- there could be searches for suspicious changesets/edits in specific area

This was just a quick outline of the proposal. Are there some suggestions, wishes, questions or doubts?

In the next days I plan to specify this proposal.

Best regards,

Morris Jobke

[kabum]

Hi,

me again. Derick answered my PM and I recognized, that I've missed some features.

The interface should be a simple website listing the suspicious changesets. As well a possibility to mark false positives and false negatives were great.

Derick suggested also a integration with JOSM and mentioned its changeset reverting capabilities.

Best regards,

Morris Jobke