-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Comments
We want to introduce a plugin system, but it's always difficult to drop functionality that is already part of the core. |
@geek1011 I actually meant "tired of gogs development slowing down" |
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. |
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. |
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. |
Duplicated with #661 and I will close this one. Please discuss further there. |
depends on #2222 |
Is it still feasible? Especially for the issue part, the PR system directly depends on it. |
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. |
But, how to ? If not feasible, is it worth to keep it open? |
I agree with @wxiaoguang. |
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.
The text was updated successfully, but these errors were encountered: