Metadecidim Reloaded ⚡️
Hi there! 👋
Since its launch, Metadecidim has been evolving, and has gone from being an experimental instance and mainly intended for dogfooding, to having its own entity, consolidating itself as the reference space for the Decidim community and its Association.
Although it is important that we continue "eating our own dogfood", we saw that it was necessary to reorganize the structure of Metadecidim and integrate it with other channels we use. This will make the way we organize ourselves more understandable to people who are approaching the community for the first time, and will allow us to reactivate discussions, working groups and more horizontal dynamics to people who have been part of it for a long time.
We've been working with great excitement to present this proposal at our annual meeting point, the Decidim Fest! Like everything in Decidim, it is a first iteration, and we count on your feedback to keep improving it 😊.
Whether you're new around here or not, we recommend you start by taking the tour through the new Metadecidim 🚂! Leave us a comment below telling us your overall impression, and if there's anything you'd change. For sure, we've left out a lot of things, especially when translating in 3 languages, so typo warnings are welcome too!
Comment details
hi! looks amazing meta.decidim!
just one question, regarding bugs process: https://meta.decidim.org/processes/bug-report/f/210/
will be open on meta.decidim? or just in github? if it's only in github, I'll suggest to put the information. if not, seems that is not possible to report a bug (if you are not a developer and know about github)
Hey Pau, yes, it's an open space in Metadecidim. And it's certainly not the first time that action in this process disappears without touching the configuration...🤔 I just checked the logs. Stranger Things of Decidim. We'll keep an eye out if it happens again. Thanks for the heads up!