Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Details on contact channels #36

Open
wants to merge 4 commits into
base: gh-pages
Choose a base branch
from

Conversation

drolbr
Copy link
Contributor

@drolbr drolbr commented Dec 2, 2018

Hi Mikel,

thank for the work on the Welcome Mat.

I would like to add to this work with a more detailed list of communication channels. I tried my best to add the relevant channels. But of course I'm happy to add further channels.

I have removed to reference to the Wiki because both the referred page wiki.openstreetmap.org does not exist in the welcome mat and I deem the start page of the wiki both unfit to help newbies for orientation and to give people a warm welcome.

Best regards,
Roland

@mikelmaron
Copy link
Contributor

Thanks @drolbr. There's discussion on the approach to integrate the osm-community-index to improve discoverability of communication channels. Let's work on that here

@drolbr
Copy link
Contributor Author

drolbr commented Dec 3, 2018

Dear Mikel,

thank you for the feedback.

I'm happy to have Brian's tool included in the long term. But right now, as I see this, it is still a good deal away from having a end-user friendly interface like (the local meetup map)[http://usergroups.openstreetmap.de/]. A newbie right now would have to navigate through a github repo or would have to set up and account and start and editing session (including a ton of extra activity like confirming the account, clicking away an iD tutorial the user later might want to get back to and so on) to get information on a local contact channel.

In addition, changes like mentioning the license change in the history and a reference to changesets comments is independent of Brian's tool.

I therefore suggest to proceed with a maybe reworked version of this pull request right now and to add Brian's tool once it is end-user ready.

Best regards,
Roland

@mikelmaron
Copy link
Contributor

changes like mentioning the license change in the history and a reference to changesets comments is independent of Brian's tool.

Can we separate out the changes to history page in another PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants