Feedback on the decision for no SotM 2023

When we started to work on the decision for SotM 2023 it was obvious that we prefer Cameroon to Kosovo for two reasons.

We prefered a venue out of Europe as past three SotMs took place in Europe. And we didn’t want to have the double conference with FOSS4G for several reasons, even if there are good reasons to have the conferences in neighbourhood.

For several meetings we worked on the bid of the local team of Cameroon. We asked a lot of questions to the team of Cameroon also about security issues. The aim was to go there and to improve circumstances. We investigated the conditions to make a hybrid conference. So that everyone could participate even if it attendees decide against a travel due to security issues.

All members of the SotM WG were aware of security issues of a travel to Cameroon. But we wanted to provide a strong hybrid part as alternative. So we asked about technical background in the venue in detail and it was “no question of budget” to do everything possible in this direction.

It was known from the beginning that LGTBQ+ community won’t be able to travel to Cameroon. But at this stage I thought the hybrid is a good solution to have everybody involved …

Then something happend. We received mails of a board member (not private, but with board email and board cc) that “reminded” us to the security policy of OSMF. It was not possible any longer to organize a SotM in Cameroon. Other board members asured me that we have all support of the board. You can see in the minutes mentioned above how strong the board put pressure on SotM working group. I cannot find any comment in it that the board should let do SotM working group their work …

In our last meeting we had three options. Going on with Cameroon. Choosing Kosovo or no (international) SotM. We decided to stay with Africa but to work on a venue that is possible for everyone. This is not possible for 2023. So we announce that for 2024.

For me personnaly this was the most sad desicion in my “SotM career”. I felt deeply disappointed about this decision. At the other hand of course we want to have LGTBQ+ people part of SotM. Of course!

Please support SotM Africa in Cameroon as local conference!

3 Likes

At the risk of just repeating what others have written: There is still no good reason put forward why the 2023 SotM couldn’t be in Kosovo. The original announcement spoke of a very strong application, without mentioning any negative points. In the ongoing discussion, ad-hoc references are being made to visa issues and now the parallel FOSS4G. The former potential issue I can’t judge, the latter just seems weird. Would you care to elaborate on this? Anyway, judging on what has been published and written so far in the “official” channels and here, the selection process seems highly problematic and certainly discouraging for future applicants.

9 Likes

Kosovo bid is strong enough that we will ask them to repeat their bid in future. We never rejected a “strong bid” forever. Mailand and also Heidelberg participated at the call several times and we support local teams with their bid and also asked them to repeat their bid and we also ask teams to make a “early” bid - even things are not thought out to the end.

here is really no need to feel discouraged by a rejected bid. And also now with the rejected Cameroon bid we try to work with the Africa-wide team to find the perfect venue.

It is difficult for me as chair of the SotM working group to argue against SotM side by side with FOSS4G without blaming the magnifique work of the local team in Florence. But Wikimedia Italia is one of the strongest communities in OSM worldwide … this is really an exception. Hosting SotM is hard work and absorbs a lot of force of a local team. And also preparing it … looking for great spaces for socialising etc. needs being with heart at SotM and it is always worse to work at the same time for an other conference.

And to tell the truth … the formal Kosovo bid was neither strong nor very strong as the text was just a copy and paste of FOSS4G bid. Of course we know they can do well … so we call it strong. But the formal was not good enough for 2023.

1 Like

I am also member of the SotM organizing committee and took part in the decision to not host a global SotM in 2023. I don’t have all too much to add to what has already brought forward in this discussion, but one thing that bothers me a bit is the following: Why is skipping one global SotM such a big deal? Did I (and my colleages) overlook some negative aspect associated to skipping the conference? I mean, it has happened before (in 2015) and people still came back to the SotMs in the years after. I even argued that having no global SotM next year would even “strengthen” regional and local SotMs in 2023 such as SotM Africa, as there would be automatically greater “demand” for other SotMs if there’s no global one.

Sure, it’s one less opportunity to meet, present, exchange and network in 2023… hey, if you’re so enthusiastic about SotM: why not go ahead and organize your own regional or local SotM in 2023? PS: And please consider joining the SotM organizing committee. :slight_smile:

2 Likes

What worried me is that (from what was published) there was a secret requirement of not making SOTM in Europe which was not communicated to applicants. And they were doomed to failure no matter what they did.

Maybe Kosovo bid was poor and “strong bid” was euphemism/untrue/misleading. And SOTM 2023 was cancelled due to lack of viable bids. Though in such case maybe use euphemism that is not misleading? Rather than claim that SOTM was cancelled to increase diversity?

What worried me is that it seemed to be applying “1 good thing from Europe and 1 good thing from Africa is preferable to 20 good things from Europe and 1 good thing from Africa” as a rule. Which makes no sense to me. Cancelled SOTM is not a big problem, but this kind of “solution” can be applied also elsewhere.

5 Likes

Hi Christine and thank you for the detailed posts. I share your feelings about it being a sad decision in your SotM career as I recall feeling the same way when I was in the Working Group and saw the cancellation of SotM 2015. It sounds like similar circumstances; in that you picked a bid to work with and when that fell through there was not enough time to go and work with the other bid.

You also had the extra complexity of an OSMF that acted to take power away from the Working Group. Unfortunately this is a regular occurrence (e.g. the same happened with the LCCWG Moderation Subcommittee) and can demotivate the working group volunteers. I hope you are all well and not feeling down/sad for long. I call on OSFM again for you to get all the support you need in event organisation, planning and safety for SotM 2024 and beyond.

Credit where credit is due, I do know that the OSMF do support SotM WG via the paid work of Dorothea. So in that sense I know that OSMF can be supportive, it just needs to widen this out.

The other lesson, as with the cancellation of SotM 2015, is that it takes a huge amount of time and therefore planning needs to start as early as possible. I personally feel that the burden on volunteers is too large and hence my calls for more paid support from the OSMF. Volunteering in working group roles is not the same as doing voluntary mapping. With mapping you can simply stop when life gets busy and have as long a pause as necessary. This is not the case with the working groups as they are either working to deadlines (e.g. to stick to the SotM conference date) or have 24/7 pressures (e.g. keeping the servers online and functional). The more we recognise this, the better supported the OSM community will be through the efforts of the Working Groups.

3 Likes

And to tell the truth … the formal Kosovo bid was neither strong nor very strong

If the Kosovo bid was not strong, then I’d much rather have the announcement of no SoTM to state it clearly, and identify weaknesses they had, instead of saying that is was strong, when in fact it was not.

Such avoiding of saying what is truly going on in order to not hurt someones feeling (or whatever the reason was) is unnecessary and does not help anyone; in fact it make situation worse for everyone involved:

Community that wants to attend SotM is left utterly confused why strong bid is completely ignored, Kosovo team does not get feedback about what they need to improve on to make a better bid, and OSMF/SoTM WG gets a black dot for deliberately not being transparent.

Not that “no SotM” is the end of the world, but I’d like to think that everybody learnt something from this and will do better next time. Anyway, big :heart: to everybody volunteering their time to try to make things happen! Even if it is not always evident, we all do appreciate all the hard work you put in! Don’t let such mistakes pull you down, but let them instead inspire you to avoid those pitfalls next time! :+1:

11 Likes

I want to clarify that the OSMF did no such thing. The minutes show that we had a chat, and that the action item was “The Secretary to suggest a meeting of the board with the State of the Map working group. (Post meeting addition: The meeting was declined, as the SotM working group is already under pressure).

I regret that SotM WG didn’t want to talk to the board, and that we now won’t have a SotM 2023 at all.

4 Likes

Prizren is a wonderful location for a SOTM. I went there for another conference a few years ago. Super accomodation.

Polyglot

1 Like

Was a virtual SotM considered?

Hi @Stereo. It did sound like it based on what Christine wrote but I’d rather not get in to a “did they, didn’t they” argument here. Some collective responsibility needs to be taken though as it is the OSM community that suffers if the OSMF Board and Working Groups do not work in unison.

Perhaps you could reach out to the WG again now they have a bit more free time until the next SotM…?

1 Like

Please note that the Board meeting at which SotM 2023 was discussed did not include 3 of us, including myself. Indeed if I had been there I would have spoken strongly for allowing the SotM WG to do its work without undue interference. I’m sorry you and the WG were put in that position.

Thank you for sharing your feedback and suggestions on the decision not to hold a State of the Map conference in 2023. Your experience and insights as a former volunteer and member of the international team are valuable and appreciated.

Regarding the bid from Cameroon, you make a valid point that risk can be managed with proper planning and support. It would be worth exploring ways for the OpenStreetMap Foundation to provide professional support to identify suitable locations and reduce risks for future events.

Regarding the bid from Kosovo, rejecting a strong bid based solely on the location being in Europe and the assumption that it’s not different enough from other European cities seems unfair to the local community. As you suggest, rejecting a willing community should be an absolute last resort, and a transparent set of criteria should be established in advance to avoid wasting the community’s time and effort.

Your proposal to ask the OSMF to fund professional event companies to help identify suitable locations and manage day-to-day admin is worth considering. This could potentially help alleviate some of the burden on local communities and ensure that events are safe and successful.

Thank you again for sharing your thoughts and suggestions. It’s important to have open and constructive conversations to improve the State of the Map conference and support the global OpenStreetMap community.

1 Like

I agree wholeheartedly with the sentiment below. The rejection and stated rationale for the Kosovo bid were extremely disappointing. To the point of diversity, 2023 would have been the first year the SOTM occurred in a nation with a Muslim majority if the Kosovo bid had been accepted. Isn’t this an objective win for diversity? Also, If other reasons not related to its geographic location ultimately figured into the rejection of the Kosovo bid, this was not communicated adequately.

3 Likes

I just want to respond to those who claims that “OSMF failed to run a conference this year.”

OSMF didnt fail to run a conference this year, SotM WG operates it.

OSMF honored SotM WG’s decision to not run a conference this year… and in my opinion, SotM WG (and OSMF) succeeded in breaking the status quo and honored diversity and inclusion in this decision. And I think that is a win.

2 Likes

This I agree with, and will indemnify OSMF from the SotM WG decision. There was no easy or correct way for OSMF to handle that (if OSMF overruled SotM WG, there would likely have been even worse consequences).

I’ll agree that something was broken, but it was not (only) status quo :cry:.
What worries me, is that if OSMF/SotM WG refuse to even acknowledge that there was a problem and that it could’ve been handled better, then there is no chance of improvement and handling it better next time.

What? I might be misunderstanding that, but you seem to be saying it is good that there is no SotM? Because it is better that there is no SotM at all, then if there is one that is only somewhat [1] more diverse then previous ones?

Please tell me I am not reading that correctly. Shouldn’t it be, by the same logic, “a win” if syadmin team were to shutdown all servers, as it would “honor diversity and inclusion” by making sure that everybody has the same access rights - i.e. that nobody is able to access to servers (instead of only disadvantaged people behind great Chinese firewall and North Korea being affected)?


Don’t get me wrong. I’m all for improving diversity where possible. If Cameroon was able to be chosen, that would’ve been great. But rejecting Kosovo because “Sure it is quite diverse from all previous SotM conferences, but that is not good enough if there exist some other even more diverse place, even if we are unable to organize SotM there” is just, ah, completely unlogical to me.

You know what would be even more diverse and inclusive than Cameroon? Antarctica. Should we cancel all future SotM until one can be organized in Antarctica? (this is just a rhetorical parable. Please do not consider it for real. The fact that I feed I need to emphasize that is telling something too.)

The solution, upon realizing that Cameroon was unattainable for this year, should’ve been to choose next attainable best diverse place, which was Kosovo. Or something else, but definitely not “no SotM”.

[1] even there I would argue that Kosovo would’ve been quite more diverse than western EU / USA. I might be able to understand if only other contender was UK or Italy or some other country which has hosted multiple SotMs already (but not really. Even “meh same country again” would’ve been better then “nothing”)… But Europe itself is so diverse in itself, even if it is technically one continent. Rejecting even the consideration of all that diversity, and even celebrating it as “a win for diversity and inclusion” is appalling to me.

10 Likes

I’ve been in a few working groups and always saw it as working for the OSMF. As such a WG failure is an OSMF failure. Trying to argue differently shows the flaw in the OSMF and WG structure/relationship.

If you’re not working for OSMF then why does any profit from SotM go to OSMF?

P.s. I am very much of the mindset that in any organisational structure, for successes you celebrate it at the lower levels (those who did the work) and when there is a failure it is the higher level that takes ownership for it. In this case the OSMF.

8 Likes

I should clarify perhaps that above I actually mostly meant “OSMF Board” when I said I indemnify “OSMF” for SotM WG decisions. (I do indemnify large parts of whole OSMF of course too, as vast majority of them were likely no more or less involved in that decision process than any random OSM mapper. But I obviously do not indemnify SotM WG itself, even if it is part of OSMF, as AFAICT they were the ones who made that decision).

Well, it is, according to the homepage. The OSMF (OpenStreetMap Foundation) arguably includes not only the board and working groups, but all (paying or free) normal and corporate and associate members too. So perhaps saying “OSMF” is (sometimes) including more that one meant.

While I agree that such mindset is good for employee morale and general public opinion (and thus very important for OSM which hugely depends on community) I wouldn’t want that to be interpreted as a permission to say “OK let’s get a few scapegoats to take the blame, name them the Board, and then just ignore any mistakes, sweep them under the rug and pretend they are fixed by assigning the blame”, as that would mean the problem would remain unfixed in the future.

To me, only those that actually made decisions that resulted in some outcome are actually responsible for it. So even if it would look nice that the Board that should publicly “take full responsibility” for any problem, it is only going to work if the Board acts on that responsibility (i.e. they identify the problem and take measures so it won’t repeat). Otherwise it would be just paying a lip service.

I’d much rather that the SotM WG (who as I understand made the “no SotM” decision) but also the Board actually:

  • admit that there was a problem, i.e. that this situation could’ve been handled better (and that we actually could’ve had some acceptable SotM this year) and issue a clear statement saying that.
  • try to identify what sequence of actions led to a problem (it would be best if each participant suggested what they themselves could’ve done differently to affect the outcome)
  • try to suggest changes for the procedures so the next time the outcome would be better then the “no SotM” (hey, even fully online would’ve been quite diverse enough)

It saddens me that (even at this late point of time) even that first milestone seems yet unattainable.

1 Like