Seperate the issue management and wiki as 'plugins' #452

New Issue

GiteaMirror · 2025-11-02T03:24:00-06:00

GiteaMirror commented

2025-11-02 03:24:00 -06:00

Originally created by @ChangePlaces on GitHub (Mar 9, 2017).

I'd like to suggest that issue managment and the wiki be pulled out of the core code and added as optional plugins. This will help keep gogs even more trim.

In my use case, I want just a git repository manager with a basic web UI that allows me to create repos, push and view contents of the files.

I've grown tired of gogs development slowing down to a snail pace, but I think this plugin separation would allow gogs to be developed separately and allow it to be more useful to many more developers.

Originally created by @ChangePlaces on GitHub (Mar 9, 2017). I'd like to suggest that issue managment and the wiki be pulled out of the core code and added as optional plugins. This will help keep gogs even more trim. In my use case, I want just a git repository manager with a basic web UI that allows me to create repos, push and view contents of the files. I've grown tired of gogs development slowing down to a snail pace, but I think this plugin separation would allow gogs to be developed separately and allow it to be more useful to many more developers.

GiteaMirror added the type/proposal issue/needs-feedback labels 2025-11-02 03:24:00 -06:00

GiteaMirror closed this issue

2025-11-02 03:24:00 -06:00

GiteaMirror commented

2025-11-02 03:24:01 -06:00

@tboerger commented on GitHub (Mar 10, 2017):

We want to introduce a plugin system, but it's always difficult to drop functionality that is already part of the core.

@tboerger commented on GitHub (Mar 10, 2017): We want to introduce a plugin system, but it's always difficult to drop functionality that is already part of the core.

GiteaMirror commented

2025-11-02 03:24:01 -06:00

@ChangePlaces commented on GitHub (Mar 10, 2017):

@geek1011 I actually meant "tired of gogs development slowing down"

@ChangePlaces commented on GitHub (Mar 10, 2017): @geek1011 I actually meant "tired of gogs development slowing down"

GiteaMirror commented

2025-11-02 03:24:01 -06:00

@lunny commented on GitHub (Mar 10, 2017):

You can disable them on the repo settings. @ChangePlaces And we have introduced a unit concept to make a basic of plugin. #947 will let you define a team who only see codes or issues or wiki. Of course, this could be a global options then you could disable all repo issues or wiki.

@lunny commented on GitHub (Mar 10, 2017): You can disable them on the repo settings. @ChangePlaces And we have introduced a unit concept to make a basic of plugin. #947 will let you define a team who only see codes or issues or wiki. Of course, this could be a global options then you could disable all repo issues or wiki.

GiteaMirror commented

2025-11-02 03:24:02 -06:00

@ChangePlaces commented on GitHub (Mar 10, 2017):

I know you can disable them per repo, but that's still checking for issues that may be assigned to you. I was envisioning a global removal, rather than a disabling. e.g. the core system is installed, and plugins such as different types of issue trackers could be used depending on your needs, different wiki's etc.

@ChangePlaces commented on GitHub (Mar 10, 2017): I know you can disable them per repo, but that's still checking for issues that may be assigned to you. I was envisioning a global removal, rather than a disabling. e.g. the core system is installed, and plugins such as different types of issue trackers could be used depending on your needs, different wiki's etc.

GiteaMirror commented

2025-11-02 03:24:02 -06:00

@stale[bot] commented on GitHub (Feb 16, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 16, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:24:02 -06:00

@lunny commented on GitHub (Feb 19, 2019):

Duplicated with #661 and I will close this one. Please discuss further there.

@lunny commented on GitHub (Feb 19, 2019): Duplicated with #661 and I will close this one. Please discuss further there.

GiteaMirror commented

2025-11-02 03:24:02 -06:00

@lunny commented on GitHub (Feb 20, 2019):

depends on #2222

@lunny commented on GitHub (Feb 20, 2019): depends on #2222

GiteaMirror commented

2025-11-02 03:24:02 -06:00

@wxiaoguang commented on GitHub (May 13, 2023):

Is it still feasible? Especially for the issue part, the PR system directly depends on it.

@wxiaoguang commented on GitHub (May 13, 2023): Is it still feasible? Especially for the issue part, the PR system directly depends on it.

GiteaMirror commented

2025-11-02 03:24:03 -06:00

@tboerger commented on GitHub (May 13, 2023):

IMHO it's still valid. Somebody would potentially replace the builtin issues with another system similar to jira. And in general gitea should still provide a big plugin system.

@tboerger commented on GitHub (May 13, 2023): IMHO it's still valid. Somebody would potentially replace the builtin issues with another system similar to jira. And in general gitea should still provide a big plugin system.

GiteaMirror commented

2025-11-02 03:24:03 -06:00

@wxiaoguang commented on GitHub (May 13, 2023):

But, how to ? If not feasible, is it worth to keep it open?

@wxiaoguang commented on GitHub (May 13, 2023): But, how to ? If not feasible, is it worth to keep it open?

GiteaMirror commented

2025-11-02 03:24:03 -06:00

@delvh commented on GitHub (May 13, 2023):

I agree with @wxiaoguang.
Especially since there are already dedicated issues for plugins like #20126.
The only portion that isn't covered by this issue is the "remove issues and wiki from core" part.
And like @wxiaoguang, I doubt that that is really possible.

@delvh commented on GitHub (May 13, 2023): I agree with @wxiaoguang. Especially since there are already dedicated issues for plugins like #20126. The only portion that isn't covered by this issue is the "remove issues and wiki from core" part. And like @wxiaoguang, I doubt that that is really possible.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#452