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

Organisation of discussion threading #3

Closed
pat-s opened this issue Jan 19, 2017 · 6 comments
Closed

Organisation of discussion threading #3

pat-s opened this issue Jan 19, 2017 · 6 comments

Comments

@pat-s
Copy link
Member

pat-s commented Jan 19, 2017

Referring to r-spatial/rspatial_spark#9 (comment).

  • How to deal with long conversations under "issues"? Githubs capabilities for discussions is rather limited- However grouping is needed -> Labels provide some limited way of grouping.
  • Without moderation or a sticky summary of (at least) the most important issues in the Wiki, most comments will just stay comments in a discussion
  • New members joining here after lots of comments need hours to catch up and may loose motivation
  • Moderation needed? Distinguish between chatty / content input

I see the advantages of discussing on Github (everyone has an account, many will easily join in and follow up). While this is not a problem right now, it will be come one when more issues are raised and more comments are written.

This is an important (and yeah annoying) topic to deal with...

@ateucher
Copy link
Contributor

Would an r-spatial Slack channel help? Or would it just throw another medium into the mix and further fragment the discussion?

@pat-s
Copy link
Member Author

pat-s commented Jan 19, 2017

I also thought about this and deleted it again in my first post. I guess it would help for the chatty talks but also make the discussion non-visible for most of the public. However, Slack is also limited in organising large discussions?

My idea with Slack was to open several channels like issues here and summarise the discussion content on Github as a Wiki page. But yeah, not sure if mixing/splitting up makes sense here.

@ateucher
Copy link
Contributor

Agreed - Slack (at least as far as I've used it) is good for the chatty stuff, but not sure much else. Linking services like Travis builds so you can keep track of multiple packages/projects is a handy feature, but not what we're talking about here.

@pat-s
Copy link
Member Author

pat-s commented Jan 24, 2017

Slack just introduced "threaded messaging" - maybe that could help us? https://slackhq.com/threaded-messaging-comes-to-slack-417ffba054bd#.lfu3u9n7f

@pat-s
Copy link
Member Author

pat-s commented Mar 1, 2018

@tim-salabim
Copy link
Member

Given the lack of activity, both here and the slack channel, I am closing this. Feel free to re-open if necessary

edzer pushed a commit that referenced this issue Apr 9, 2021
osgeo-email.md: language fixes (and a suggestion)
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

No branches or pull requests

3 participants