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

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

Closed
ChangePlaces opened this issue Mar 9, 2017 · 11 comments
Closed

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

ChangePlaces opened this issue Mar 9, 2017 · 11 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@ChangePlaces
Copy link

ChangePlaces commented 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.

@tboerger
Copy link
Member

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

@ChangePlaces
Copy link
Author

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

@lunny
Copy link
Member

lunny commented 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 lunny added this to the 1.x.x milestone Mar 10, 2017
@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Mar 10, 2017
@ChangePlaces
Copy link
Author

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.

@lunny lunny modified the milestones: 2.x.x, 1.x.x Mar 10, 2017
@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Feb 16, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Feb 19, 2019
@lunny
Copy link
Member

lunny commented Feb 19, 2019

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

@lunny lunny closed this as completed Feb 19, 2019
@lunny lunny removed this from the 2.x.x milestone Feb 19, 2019
@ChangePlaces ChangePlaces mentioned this issue Feb 20, 2019
6 tasks
@lunny
Copy link
Member

lunny commented Feb 20, 2019

depends on #2222

@lunny lunny reopened this Feb 20, 2019
@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. and removed type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Mar 24, 2019
@wxiaoguang
Copy link
Contributor

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

@wxiaoguang wxiaoguang added issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail and removed issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented labels May 13, 2023
@tboerger
Copy link
Member

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.

@wxiaoguang
Copy link
Contributor

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

@delvh
Copy link
Member

delvh commented 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 delvh closed this as completed May 13, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants