Is there any process for adopting stagnating plugins? I see some issues, some pull-requests, but no activity. And I’d like to help maintain it rather than having to run my own fork. Currently there’s a fork that builds and runs with minor modifications but master doesn’t.

Adopting SonarQubeCommunity/sonar-crowd

SonarQube Server / Community Build Plugin Development

ganncamp (G Ann Campbell) August 13, 2018, 2:01pm 2

Hi,

The process for plugins in the SonarCommunity organization is to raise your hand here and volunteer to take over the care and feeding of such plugins. So… what’s your GitHub id?

Ann

1 Like

Support & Status of Perforce Plugin

Topic		Replies	Views
[NEW RELEASE] Crowd plugin 2.1.2 Plugin Development announcement	16	2845	July 10, 2019
Move dependency-check-sonar-plugin to SonarQubeCommunity organisation Plugin Development	3	768	September 9, 2019
Adopting SonarQubeCommunity/sonar-pmd Plugin Development	11	1869	May 11, 2022
[NEW RELEASE] Crowd 2.2.0 (SQ 8.9+ support) Plugin Development	4	1670	August 20, 2021
[NEW RELEASE] Crowd 2.1.3 (SQ 7.9+ support) Plugin Development announcement	4	1139	July 18, 2019

Adopting SonarQubeCommunity/sonar-crowd

Related topics