Support Forum
#supportforum Any doubts or questions on how to use Decidim? Check them with the Community!
Dear Decidim,
While I appreciate your efforts to eat your own dogfood, I I find in horribly devastating for the community that you have decided to disable posting new GitHub issues.
As an example, I'd like to ask you to try to format a Decidim proposal similar to this issue at GitHub:
https://github.com/decidim/decidim/issues/4660
This types of issues that provide technical information and possibly ways to solve the issue will be lost in the wind because of the decision to disable GitHub issues. For developers, I believe my GitHub issue provides much more information for finding a solution and reaching a conclusion than those few lines I am limited with a Decidim proposal.
Thank you for your attention.
(While posting this proposal, my initial title was too short and my body exceeded 1000 characters.)
...CONTINUED IN THE COMMENTS...
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
You can check the rest of the comments here.
Conversation with Xabier
@ahu thanks for you comment. I must say that I agree with what @andres said previously. This decision has been taken after a long period of internal discussion. And it is good to open up the debate.
I think it is first very important to note that bug reporting CAN still be moved and discussed on GitHub, it is simply that it needs to be originally reported here. This is a practice that has been implemented on some other projects as well. It has its pros and cons. But there is a trade off we have considered carefully: a) developers are forced to use Decidim (often for the first time), b) there can be an integrated tracking of all bugs, c) we all meet here to improve Decidim and not on GitHub where only developers meet (in a non-free, non-sovereign digital platform). We understand it might be frustrating at first, but we hope the benefits to become higher than the inconveniences.
This being said, we can change this policy in the future or anybody can also push an initiative to change it.
I see what you mean ... for first time comers. Can we discuss giving the ability to report issues directly in Github for developpers already afiliated to the project (us, Antti etc.)?
I guess I'd welcome the feedback of people who already are part of the Github organization and can report issues.
Do @mrcasals @oliver_valls always report bugs using metadecidim or do they file them directly on the repo ?
> I guess I'd welcome the feedback of people who already are part of the Github organization and can report issues. Do @mrcasals @oliver_valls always report bugs using metadecidim or do they file them directly on the repo ?
The idea is exactly that, that all project developers use metadecidim.
I like this idea of reporting to meta.decidim. @virgile_deville, until now we used to report first to meta.decidim except for very technical issues. Now we'll report everything to meta which is not bad. Maybe we should totally disable github issues and link PR directly to meta.dedicim?
Regarding these points:
a) In case the platform would be as competitive for reporting technical bugs, I wouldn't see any problem with this and I believe the change could happen naturally. Forcing people to use a specific tool sounds more like dictatorship (or corporate management) rather than democracy.
b) While I see the benefits from project management side, I just feel very confused currently browsing Metadecidim or report any issues here (compared doing that in GitHub).
I understand that Metadecidim is more than a developer community and I feel it should be kept like that. In my opinion development related bug reporting is not relevant regarding the discussion that happens here.
In my opinion the integrated tool should be GitHub and non-technical users could still leave the unformatted bug reports at Metadecidim.
c) We are talking about bug reporting here. I am not convinced that the average person would participate in a bug report that points to a line of code and suggests...
...a fix.
While GitHub is non-free and non-sovereign platform, you have decided to use that platform for code contributions for this project rather than using a free and sovereign alternative (which also exists).
GitHub also does not prevent you from detaching the issues from their platform and storing them somewhere else using their API:
https://developer.github.com/v3/issues/
Loading comments ...