[Osmf-talk] Some questions about candidates' statements

Dietmar Seifert privat at dietmar-seifert.de
Sat Dec 7 07:38:45 UTC 2019


Hello Peda, hello List,


Am 06.12.19 um 00:10 schrieb Peter Barth:
> Hello candidates,
> 
> I read through most of the questions and statements and I have a
> few follow-up questions, especially in the topic of CoIs which
> has a high significance for me.
> 
...

> 
> Do you agree with my statement or description of CoI/potential
> CoI? How would you cope with a CoI? How with a potential CoI?
> Especially will you take part in discussions? Share
> arguments,...? Public only? Private? Will you participate in
> votes? Will you make your CoI public? Will you make a potential
> CoI public?
> 
> I am specifically interested to hear an opinion of anyone
> directly or indirectly working for or with OSM or GIS data.

...


I fully agree with your statement.

If i would come in a potential CoI, i would say or write this to the
board members and in a board meeting, i would provide the same
information for public audience. I would give the information to the
board, they need to know and to vote. In the discussion, how to handle
the potential CoI, i would listen, but not discuss active, if not wanted
by the other board members. I would abstaining from voting.

Neither in my Answers to the nor in the Manifesto, i published the
company, i work for, so i do it now: Its Nahverkehrsgesellschaft
Baden-Württemberg (NVBW), based in Stuttgart in Germany. It is a private
based company, but under 100% control of the ministry of Transport in
Baden-Württemberg. The Ministry of Transport was the main sponsor for
the last SOTM in Heidelberg, and i tried to influence them, that they
would sponsor the SOTM.

At our company, we don't use OSM for business purposes (make profit or
so), we use OSM data for routing and we want to enhance the OSM data,
either by giving data to the community and / or by edits from ourselves.
In the latter case, we would discuss this process first with the community.

Greetings

Dietmar



More information about the osmf-talk mailing list