Collaborative Hosting Of High Values Addons/gems for Decidim #2
Replies: 6 comments 15 replies
-
hello Ivan, I agree. I also wanna sign up to the bugfix party. the examples of stalled PRs you propose are also fine by me. I can start checking the alabs calendar module. |
Beta Was this translation helpful? Give feedback.
-
Super cool if we can have shared ownership of some modules and more collaboration on maintaining them! I think moving them to a common organisation on Github is an interesting idea. But can't we just fork the old outdated modules instead? And update the forks? |
Beta Was this translation helpful? Give feedback.
-
Hello, I agree this is a good suggestion ! I explain, community modules are not always simple for contribution since there is no coding style pre-defined. Also, I think it could be interesting to have a documentation for :
|
Beta Was this translation helpful? Give feedback.
-
An important aspect is to make the financiers of this module visible, even though ourselves if we contribute without external financing. I believe we must be concerned with the effort made by these organizations in favor of the global decidim and recognised. I think that it is a transparent mechanism and it gives relevance to the co-financing of open source |
Beta Was this translation helpful? Give feedback.
-
@microstudi Thanks for the well documented proposal! I have some questions before reacting ;)
Just to check: I understand you talk about governance for gem management: who bring repos help the gems and takes part to decision. And not about an actual DICE board who takes decisions over the whole group. Is it right?
I understand here that the manifesto will be the reference for decision. Does it mean that the "board vote" you talk earlier is a veto kind of vote? Thanks, |
Beta Was this translation helpful? Give feedback.
-
I like the idea @microstudi For me it's like have a community maintained Addons/gems for Decidim Also will be easier to choose when you are looking for Addons/gems, it''s kind of guaranty that this code will be supported long term |
Beta Was this translation helpful? Give feedback.
-
I'm starting this discussion in order to se if we can figure out a (simple) set of rules that we all agree for dealing non official modules for Decidim. Non-official modules are usually created by the companies providing service to final clients that want some tweaks or custom behavior out of their Decidim instance. This is great as it generates value around Decidim and promotes diversity.
However, we've identified a set of problems with the current approach were each company creates their own product (or module), usually thanks to the funding of a sole client. The need to have a community-based approach is due the fact that many other organizations can and want to benefit from those plugins.
Current problems will be (please amend this in the comments):
As a quick list of examples of stalled PRs in popular plugins we see for instance:
One solution proposed to improve this situation, is to have a central organization where to host all of these high value plugins. The main point of this approach would be to have a shared authority on the hosted plugins. This way, if a developer abandons some plugin it can be assigned to another maintainer. Of course that, for this to happen, the original developer/company must agree with a set of rules that permits this organization to do that. And, for that, we should discuss which are the rules for a healthy community of plugins around Decidim.
Beta Was this translation helpful? Give feedback.
All reactions