[FOLIO-293] Recommendations on when to use Jira vs. Discuss vs. Slack etc. Created: 02/Sep/16 Updated: 12/Nov/18 Resolved: 17/Oct/16 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Nassib Nassar | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 hour, 30 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Some people will be unsure how to decide whether to post a question or problem they have to Jira, Discuss, Slack, etc. Could we develop some recommendations or guidelines to offer them, and post these both in the communication areas and on the developer website? |
| Comments |
| Comment by Nassib Nassar [ 02/Sep/16 ] |
|
I think usually Jira would be used for reporting very specific bugs, problems, or feature requests, while the discussion areas (Discuss/Slack) would be used for open-ended questions or comments. |
| Comment by Peter Murray [ 02/Sep/16 ] |
|
I agree – that makes sense. And, of course, one can link back and forth between the two (if something starts as a Discuss topic and turns into an Issue). |
| Comment by David Crossley [ 06/Sep/16 ] |
|
Commenced at branch https://github.com/folio-org/folio-org.github.io/tree/folio-293-which-forum Ready for an initial look to ensure on the right track. I am not sure how to balance this with: |
| Comment by Marc Johnson [ 07/Sep/16 ] |
|
Hi David, thank you for putting this draft together. I think this is a good start and it is what I had in mind when I asked the question. I'm not an expert in how to do this (I filed my first ever open source issue yesterday), so I don't think I'm well placed to comment on how the process is intended to operate. I think this is a complementary subset of the general guidance, and I think the link which you included is sufficient to reference that. With that in mind though, I think it's ok to omit the Slack section, if we think that it doesn't play much of a role in raising issues. |
| Comment by David Crossley [ 08/Sep/16 ] |
|
Thanks for making time to comment. This issue's Description says to also put these guidelines on the Wiki. I am not sure how that can be done. Perhaps the Wiki could just link to this dev.folio.org page for these developer guidelines. I do think that Slack is relevant, just do not yet know what to recommend. |
| Comment by Nassib Nassar [ 08/Sep/16 ] |
|
David, thanks, I think this is a really good start. My thought was that you might coordinate with Peter who knows all about the wiki. Yesterday we made some changes to the Discuss vs. Slack part of this decision process; Peter can provide you the latest document on it. |
| Comment by Peter Murray [ 08/Sep/16 ] |
|
David Crossley – I integrated a lot of your content into https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces (thank you!). Unless we have something specific to say to developers about the tools (for instance, any developer-specific needs, requirements, or guidance), I think we can drop this page and point to the one on the wiki instead. |
| Comment by Peter Murray [ 08/Sep/16 ] |
|
Added a commit on the branch that has some changes, but I'm of the opinion that we can point to the broader community's FOLIO Communication Spaces page. |
| Comment by David Crossley [ 09/Sep/16 ] |
|
Peter, that is a great evolution of content. The primary/secondary was the key. Reviewing that Wiki page, i do see a few minor typos. However, there is something major. Some of the text had links to other stuff on dev.folio.org and they were relative links. So now busted on the Wiki. These will need absolute links. In one case it is a link to a document in-preparation ("guide-issues") on that branch (
(Ah, reinforced a lesson. Doing two things on the same branch. Erk.) |
| Comment by David Crossley [ 09/Sep/16 ] |
|
Published an update via pull/13 We can later add specific developer notes as needed. |
| Comment by Peter Murray [ 09/Sep/16 ] |
|
Thanks David Crossley. I've updated the wiki to correct the links back to dev.folio.org. (Sorry about missing that in copying-and-pasting from the rendered Markdown.) I think we can close this issue. |
| Comment by David Crossley [ 10/Sep/16 ] |
|
We had a direct discussion in Slack: We need to have all developer-related information gathered at dev.folio.org and the full context is good there. The overlap with the Wiki is fine. This is for a different audience. So will continue with the branch folio-293-which-forum. |
| Comment by David Crossley [ 11/Sep/16 ] |
|
Ready with pull/15 |
| Comment by David Crossley [ 11/Sep/16 ] |
|
That is merged and published now. So finished this first round. |