Gitea: Seperate the issue management and wiki as 'plugins'

Created on 9 Mar 2017 · 7Comments · Source: go-gitea/gitea

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.

kinproposal revieweconfirmed

Source

ChangePlaces

Most helpful comment

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

tboerger on 10 Mar 2017

👍3

All 7 comments

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

tboerger on 10 Mar 2017

👍3

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

ChangePlaces on 10 Mar 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 on 10 Mar 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 on 10 Mar 2017

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.