We use cookies on our website to improve the performance and content of the site. The cookies enable us to provide a more individual user experience and social media channels.
Cookie settings
We use cookies to ensure the basic functionalities of the website and to enhance your online experience. You can choose for each category to opt-in/out whenever you want.
These cookies are essential for the proper functioning of my website. Without these cookies, the website would not work properly.
Type
Name
Service
Description
Cookie
_session_id
This website
Allows websites to remember user within a website when they move between web pages.
Cookie
decidim-consent
This website
Stores information about the cookies allowed by the user on this website.
These cookies allow the website to remember the choices you have made in the past
Analytics cookies are cookies that track how users navigate and interact with a website. The information collected is used to help the website owner improve the website.
These cookies collect information about how you use the website, which pages you visited and which links you clicked on.
Oooops! Your network is offline. This is a previously cached version of the page you're visiting, perhaps the content is not up to date.
Comment details
You are seeing a single comment
View all comments
Conversation with Carol Romero
Beyond this, there is an important underlying issue unsolved, and I think we should start looking for ways to solve it, and that is the fact that we do not have a stable development team that can handle all the requests that are coming in. Someone (ideally a developer from the Decidim Association) would participate in the Product team and be in charge of the review, acceptance and integration of the PRs that are arriving. This is offtopic in this proposal so I am not going to elaborate it further here, so I propose that it be a topic to talk about in the next meeting of the Association.
Indeed, this kind of discussion is very much needed, and we should include as much developers in it as possible.
I think many comments refer to the internal regulations (https://meta.decidim.org/processes/decidim-gov/f/996/), the code of ethics, and the certification process for companies, and I don't think we should discuss it in a proposal within this process.
According to the roadmap, before October we should have been able to trace it. https://metadecidim.s3.amazonaws.com/uploads/decidim/attachment/file/2095/FULLDERUTACOMIT%C3%88DE_COORDINACI%C3%93.pdf
Now that it seems that Saturday will clear up the panorama in Barceona, it may be a good time to reactivate the governance process (https://meta.decidim.org/processes/decidim-gov/)
I think that the current explanation (the one updated today) is not enough. There's still the uncertainty when a proposal will be accepted. For example, this spring we've proposed to implement a "Department admin" role feature, I think this feature is in accordance with the social contract, but was refused without further discussion.
As it is explained in the process page all proposals that accomplish with the social contract should be accepted, independently on the number of adhesions. I think it is not good to accept every proposal that accomplish the social contract, we have the risk to convert Decidim into a Frankenstein. But also think that the protocol on how proposals are accepted should be more predictable.
Some kind of debate around this will be great :D
Thanks @oliver_valls, I completely agree with you. For the ones working on the code every day we have the need to eliminate uncertainty. And I'm not sure if we should delay much this discussion and set up, at least some provisional rules to follow. This will contribute to the developers happiness, which is quite important on a opensource project.
Loading comments ...