Title: How to do discussions? · Issue #9 · utPLSQL/utPLSQL · GitHub
Open Graph Title: How to do discussions? · Issue #9 · utPLSQL/utPLSQL
X Title: How to do discussions? · Issue #9 · utPLSQL/utPLSQL
Description: On Sourceforge, we had two discussion forums: utPLSQL Development General Discussion GitHub doesn't do forums. What do we do instead? GitHub Issues I think Issues might work OK, but they could be mixed up with other types of issues. Labe...
Open Graph Description: On Sourceforge, we had two discussion forums: utPLSQL Development General Discussion GitHub doesn't do forums. What do we do instead? GitHub Issues I think Issues might work OK, but they could be m...
X Description: On Sourceforge, we had two discussion forums: utPLSQL Development General Discussion GitHub doesn't do forums. What do we do instead? GitHub Issues I think Issues might work OK, but they could ...
Opengraph URL: https://github.com/utPLSQL/utPLSQL/issues/9
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"How to do discussions?","articleBody":"On Sourceforge, we had two discussion forums:\n- [utPLSQL Development](https://sourceforge.net/p/utplsql/discussion/utplsql-dev/)\n- [General Discussion](https://sourceforge.net/p/utplsql/discussion/general/)\n\nGitHub doesn't do forums. What do we do instead?\n### GitHub Issues\n\nI think Issues might work OK, but they could be mixed up with other types of issues. Labels should help with this (i.e. [Filter on the discussion label](https://github.com/utPLSQL/utPLSQL/issues?q=is%3Aissue+is%3Aopen+label%3Adiscussion)) . I'm also experimenting with [waffle.io](https://waffle.io/utPLSQL/utPLSQL) to help visualise Issues - discussions would probably work best in their own column. I like the idea that it's part of GitHub - no separate site, no separate logins, everything links and cross-references really well, etc. It's actually pretty close to being a forum, once you've done the initial filtering on a label. I want to carry on with this at least in the interim unless/until we find something better\n### Slack\n\nI've just had a quick look at Slack. I've never used it and know next to nothing about it, but it seems to be a popular tool. The main issue I've seen so far is that while the conversations can be public, people have to be invited before they can contribute. This doesn't necessarily rule it out (new people can always ask to be added), but it's not great.\n### Gitter\n\n[Gitter](https://gitter.im/) looks to integrate very nicely with GitHub. The conversation seems more like a chat room rather than threaded converations, but I think we could setup different rooms to talk about the main different subjects.\n### Google+ Communities\n\nIn commit e798cf8 @rlove suggested that other projects have used Google+ Communities.\n\nWhat does anyone think?\n","author":{"url":"https://github.com/PaulWalkerUK","@type":"Person","name":"PaulWalkerUK"},"datePublished":"2016-02-23T20:23:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/9/utPLSQL/issues/9"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:cc56c1aa-befa-3062-45db-21da9f82c03e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | AF7E:171CBE:450CAF5:60B03E7:6A5FB5AA |
| html-safe-nonce | d846af4b8a35e4321c1749ccdec82d3dc9016629f65c5a6ca92510b0f2bfd146 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBRjdFOjE3MUNCRTo0NTBDQUY1OjYwQjAzRTc6NkE1RkI1QUEiLCJ2aXNpdG9yX2lkIjoiMTE2MTIyMzcxNjgyOTM3Nzk2MiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 5db798ed3b8f218fc6eacc53162796a4303cab774567be15bca444bc091051dc |
| hovercard-subject-tag | issue:135853798 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/utPLSQL/utPLSQL/9/issue_layout |
| twitter:image | https://opengraph.githubassets.com/0e47e2ba578bb620daf19640f97ce759be3a370598428bfc1de265d437313ac7/utPLSQL/utPLSQL/issues/9 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/0e47e2ba578bb620daf19640f97ce759be3a370598428bfc1de265d437313ac7/utPLSQL/utPLSQL/issues/9 |
| og:image:alt | On Sourceforge, we had two discussion forums: utPLSQL Development General Discussion GitHub doesn't do forums. What do we do instead? GitHub Issues I think Issues might work OK, but they could be m... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | PaulWalkerUK |
| hostname | github.com |
| expected-hostname | github.com |
| None | e0cfc367faf9c4c774d2a903897aa214c786247c4f45ffcee48cda2b819fb0c8 |
| turbo-cache-control | no-preview |
| go-import | github.com/utPLSQL/utPLSQL git https://github.com/utPLSQL/utPLSQL.git |
| octolytics-dimension-user_id | 15661281 |
| octolytics-dimension-user_login | utPLSQL |
| octolytics-dimension-repository_id | 50728220 |
| octolytics-dimension-repository_nwo | utPLSQL/utPLSQL |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 50728220 |
| octolytics-dimension-repository_network_root_nwo | utPLSQL/utPLSQL |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 94569c859bc88d6bf7de7e0ce3f2a11cd529a131 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width