Discourse 주제/카테고리와 GitHub/Gitlab 이슈 트래커 간 양방향 동기화

기여 기능
1

I’m replying here rather than starting a new Topic. Other related Topics are here, here, here and here. (This Topic thread in particular is just both relatively recent and relatively long.)

I asked on the Topic for Discourse Code Review about whether it had any support for GitHub Issues:

tl;dr some degree of bidirectional sync of GitHub Issues and Discourse Topics as a feature of Discourse Code Review could be helpful for projects that currently have some ambiguity and redundancy between the two.

Cross-posting here because the other thread auto-deletes replies after a month.

5개의 좋아요
GitHub Plugin: Support for Issues
Discourse Code Review Questions
2

엘시, 안녕하세요! GitHub 플러그인에 대해 말씀하셨는데, 그건 코드 리뷰 플러그인이 아니므로 여기에서 새로운 Contribute > Feature 주제를 개설하시는 것이 좋을 것 같습니다.

매우 열정적인 것 같네요. Discourse Code Review 에 이슈 지원 추가는 PR이 환영되는 사항일 것 같지만, 확신은 없습니다. 혹시 여기에서 계획하신 내용을 좀 더 자세히 설명해 주시면, 커뮤니티에서 누군가가 이를 이어갈 수 있을지도 모릅니다. 예산이 있으시다면 Marketplace 에도 게시하실 수 있습니다.

2개의 좋아요
3

Hi @tobiaseigen—thanks for your response. I’m not an administrator on any Discourse forums, and my suggestion is mainly based on a recurring experience I’ve had as a user and sometimes contributor on a variety of projects.

The reason I picked out Discourse Code Review is that it seems to be de facto the sole Discourse GitHub integration, unless there are other currently maintained projects I’m not aware of. Regardless, I’m going to rename this Topic to make it a little more generalized.

Basically the problem is triage: usually projects that have both a Discourse instance and a public GitHub issue tracker tend to have their users concentrated more on the Discourse instance, and when a user Topic is more properly a GitHub Issue, sometimes there will be friction in the process of the Topic finding its way to the people responsible for handling it.

Another way of looking at this is as inboxes or buckets: if end users are more active on the Discourse instance, and the developers are more active on the GitHub repository, essentially the developers or someone tasked with triage has to keep track of multiple redundant places for people to post their problems and figure out a consistent way of migrating Issues and Topics when necessary.

What I’m imagining with GitHub Issue sync is something like the Discourse WordPress plugin, where the Issue tracker and a corresponding Discourse Category are, to the end user, different views for the same underlying set of conversations.

Again, I’m not in a position to spend money on this feature. I’m posting here based on my experience and frustration with it being unclear where to post different types of feedback on certain projects and the tendency of misplaced feedback to fall through the cracks.

(Oh, and preferably there would be exactly the same functionality for Gitlab as for GitHub…)

2개의 좋아요
4

Yet another way of framing this is that Issue trackers are just forums (or, to use older parlance, “bulletin board services”) with a thick layer of Agile project management slathered on top. Weirdly, they’re also kind of mailing lists, because people can interact with them entirely via email. Discourse is in the unique, central position of tying these superficially different (but in many ways functionally similar) services together in order to reduce fragmentation.

1개의 좋아요
5

Thanks for explaining all this. Really it sounds like you need to ask the projects you are contributing to that are using Discourse to work on this. Right now it’s not even clear to me how many projects are making use of Discourse Code Review and how it’s working out for them. Feel free to PM me with some details so we can get specific.

That plugin is different.. the discussions live only in Discourse and are embedded at the bottom of WordPress posts. They are not synced.

Assign a Github Issue to a topic?
6

Right, yes, the fact that WordPress is so much more modular would facilitate that in a way that GitHub wouldn’t.

7

@elsiehupp Did you ever make progress with this? I’d like to implement something similar - bidirectional syncing of Github issues to a discourse topic.

8

I’ve been working on this for a few different projects. There’s a POC here

I’m hoping to have a test version live in a few projects in the next few weeks.

8개의 좋아요
9

Happy to help test once you are ready!

2개의 좋아요
10

@elsiehupp @angus @sunjam Did you guys have been able to create bidirectional sync between GitHub issues and discourse topics. I am also looking for this feature. Any help or guidance in this regard would be very appreciating.

1개의 좋아요
11

I haven’t done any further work on the branch I posted, but perhaps it still works

You can try it out and report back if you like.

3개의 좋아요
12

I wonder if this can be updated with relatively low effort, it’s a must for non-very-technical communities.

13

안녕하세요! 저는 디스코러스 메타에 처음 온 사람입니다. 제가 특정 통합 기능이 필요한데, 제가 조사한 바로는 GitHub와 디스코러스 간 토론 동기화에 문제가 생겼기 때문에 해당 기능이 중단되었다고 합니다. 하지만 제가 필요한 것은 동기화가 아닙니다. 특정 게시글이나 답변을 GitHub의 이슈로 변환하는 기능입니다. 완전히 정적인 방식으로, 정보를 가져와서 이슈를 생성하고, 그 이슈는 GitHub에서 독립적으로 관리되며 디스코러스로 다시 동기화되지 않는 형태여야 합니다.

컨텍스트를 설명드리자면, 저는 몇몇 정부 솔루션의 비즈니스 팀에 속해 있습니다. 최근 책임 범위가 주(州)와 시(市) 단위로 확대되면서, 우리의 솔루션을 사용하는 공공기관이 매우 많아졌습니다. 따라서 커뮤니티 규모가 매우 크고, 이전에 GitHub로 관리해 보았지만 GitHub는 디스코러스만큼 사용자 친화적이지 않습니다. 디스코러스는 커뮤니티 관리에 정말 훌륭한 도구입니다. 제안, 오류 보고 등을 오가며 관리하는 것은 6명으로 구성된 팀의 몫인데, 커뮤니티 규모에 비해 인력이 부족합니다. 제가 필요한 것은 특정 게시글을 지정된 저장소(하나만 가능하거나 선택 가능해도 무방합니다)의 이슈로 변환할 수 있는 기능뿐입니다. 우리의 병목 현상은 GitHub로 이슈를 전달하는 과정이며, 이후로는 GitHub에서 관리하고 있습니다.

저는 기술 팀 소속이 아니므로,Ruby에 대한 지식이 전혀 없어 기술적으로 기여할 수 없습니다. 기술에 관심이 많고 호기심도 많지만, Ruby에 대해서는 아는 것이 전혀 없습니다. 누군가 도움을 주실 수 있다면 감사하겠습니다!

수정: 어디에 게시해야 할지 몰랐습니다. 이슈와 게시글 간의 관계에 대한 논의가 이미 존재하므로, 새로운 토픽을 열지 않았습니다.

1개의 좋아요