We have various communication channels in OpenStreetMap being used for different needs in communication. The mailing lists and forum work reasonably well for free and open discourse of the community, changeset discussions allow communicating on specific edits in the map (and we have for example Pascal's tool to look through these). We have the user diaries for people publishing their thoughts and experiences on the project and discussing them with others. And we have the OSM wiki which is used as a place to document things.
All of these have their issues and room for improvements but they are widely used and accepted as the platforms where communication happens. And they all have relatively low entry barriers as evidenced by the fact that quite a lot of people use them actively.
What we don't have and where we have in OpenStreetmap a fairly obviously increasing need for is a means for project organization and related communication, task and issue tracking etc. There is a very old trac instance but this is hardly used any more and has a fairly awkward usability, in particular for non-programmers. Safe to say this is not an established communication platform any more.
Because of that people have started widely using external commercial platforms, in particular github, for this kind of work.
- corporations doing organized edits have github repositories to track their work - like here, here, here and here
- import planning is frequently performed on github - like here and here
- there are attempts to move tagging discussion to github issue trackers here
- the OSMF and its working groups using github for issue tracking (both publicly and internally), public examples here and here
For OpenStreetMap this is not a good development for various reasons:
- github is designed for software developers and is practically much less accessible for non-developers. Even if non-developers manage to adapt to this they will always feel less at home there and as a result there is an inherent dominance of the software developers over non-developers on github.
- the requirement to register on an external platform and accept the terms of service there poses a highly problematic hurdle. It should always be the goal that an OSM community member should be able to participate in all public community discourse without such hurdles.
- quite a few people have principal ethical concerns regarding platforms like github which are usually financed through either advertisement or sale of personal information about its users.
- since the github software is not open source use of github is in conflict with the general culture of OpenStreetMap to base itself on open source technology.
Because of these problems i am generally inclined to boycott attempts to move non-development discussions to github. But this is somewhat difficult if you can't point to a suitable alternative. I would therefore propose we set up an open source project management system that can be used by everyone with an OSM account for use by the OSM community. There are quite a few software products available for this.
There are various questions and arguments that might come up regarding this suggestion:
- Do we really need this kind of tool in OSM? Yes, the fact that github is used so widely for OSM projects is a clear indicator.
- But github is so convenient, everyone already knows how to use it while something else you would have to newly learn to use. Yes, for you that might apply - but you are putting the convenience of you and a few other people familiar and comfortable with github over the interests of the vast majority of mappers.
- Why should the OSMF invest money and work into self hosting something when there are github alternatives based on open source software available for use that might offer affordable service plans for an organization like OSM? Mostly to ensure a low entry barrier for people to participate by requiring nothing more than an OSM account. If this could be achieved with an externally hosted tool and reliability of the service and access to and ownership of the database are ensured, external hosting would IMO also be an option.
- Won't this fragment the discourse in the OSM community by creating yet another set of communication channels you need to follow to stay informed? Yes, that is a possibility - but as said this is already happening through the use of github at the moment. I think a dedicated OSM platform would improve the situation on this matter.
- Should this be a pure project management/issue tracking platform or also a source code repository and version management system? That's a good question. Many of the free software options available offer both. But most software development projects around OpenStreetMap are independently managed and you can't force any of them to move. The core arguments for not using github i listed do not necessarily apply to all of these projects. The main use case would at least initially be non-development projects. And therefore usability for non-developers should be a primary concern.
- Great, but who does the work necessary to set this up? Ideally such a platform would be integrated into the existing OSM website with notifications via the OSM website messaging system, using the configured language settings and possibly connections to changeset discussions etc. That would be a lot of work to set up. But running it separately similar to the OSM Forum would already be a useful first step. This would require some work from operations to set this up and maintain it. But the more difficult steps are probably to come to a decision with wide support what we need in terms of features, what software should be chosen for this and to configure and adjust it for OpenStreetMap's needs. This post is meant to start the discussion on these questions.