As we talked about it in the last contribution meeting in May, here I am again after a busy summer.
I’m really eager to contribute regularly to Mobilizon back-end, to help you build new features or tests or anything related, but as felt and told, accepting new contributions to the project seems difficult for the existing dev team and not a priority of the organization.
I understand that good design and technical excellence must be aimed when submitting a pull-request and that we need coordination to be efficient and to not do multiple time the same work.
So, how can we make this work?
As there is no technical documentation on the project I find it really difficult to understand and to test.
A first contribution working on this side would it be welcome? Back in May, someone else was interested to contribute on the QA testing of the project, is it still the case?
I think I could try again on the same I was motivated to start with 5 months ago:
But am still stuck at the same point: there is no technical documentation and even if I’m not a junior developer anymore I find the architecture of the project a bit confusing and cannot find the way to launch only the part of the automatic test that I would be interested in (e.g. my messages on Matrix).
A friend suggest me to just send the source code to an AI to get that, but it’s against my values. I would want to cooperate with you guys to get a bit of kickstart knowledge and even propose you to turn it in documentation to make it more valuable.
Then you understand that regarding the QA I didn’t mean human testing through the interface but automatic testing, through unit tests, integration tests or e2e tests writing. Or at a intermediate level writing acceptance tests if you work or want to work using Behavior-Driven Development.
But honestly I have no clue on how you want to welcome contributions from people not being employed by Kaihuri. Do you have or would want to have any cooperation with volunteers contributors beside reviewing and merging the pull requests? If you don’t know we could also talk about it to see how it’s possible to make it happen.
I think you got the main point, that we mostly collaborate through MR. But we encourage to align on the functionalities before you start a development effort. I looked at the issue you’ve picked, I’m really not sure that one should be able to copy another person’s event. You can share it, but not copy it. It works as intended. Of course it can be discussed further on this forum, in case more people have different opinions. Maybe you can find issues that are easier to deal with.
This being said, we’ve had a meeting with contributors in june Mobilizon contributors meeting and will try to make it happen again in 2026. We can not organize them more frequently, but you can try on your side to gather contributors
Ok so I had already seen this documentation but inside the only semblance of technical documentation is this one:
Which doesn’t really help me to understand the basic of the architecture and tests of the project. Just the lint part.
For this issue, maybe not anyone, but admin of the same group should be allowed I think, as we can use the duplicate function to use previous event as Template. And as a user that exactly what we wanted to do with @Meldane.
Lastly then, if I had to wait an unsure date in 2026 to start contributing, I hope you understand that this doesn’t allow me to contribute regularly. So sorry, but I will certainly look for another project where there is more active cooperation then. And I’ll probably wait for the fixes and new feature to come as a user or look forward a fork of the project as some evocate it on Matrix to make it more cooperative and welcoming to contributions.
Don’t see that last part as threat, I just prefer to be transparent with you guys that the state of the project make some mainteners, users and contributors frustrated. And that could happen for the worse or the better.
On this group, the one in charge of the football or baketball session can change from one week to the other, and the one in charge of it for the week needs to be able to publish the event, make announcements on it, or cancel / delete it, if there are not enough participants.
Having to tell members that they can’t reuse our template, but have to copy it all, with not only the text, but also the pictures, all the tags and correct fields, is a turn-off.
@Lahax : Could there be a way to crowdfund documentation to be able to contribute to Mobilizon coding more easily ?
Not the same, we can see the button but when we try to use the feature an error is displayed during the process.
As I remember, you got the duplicate form and when you change and press the button to publish the new event you got the error.
Sorry for the late reply, I needed to focus on the other projects, lately.
But yes, if a crowdfunding campaign was launched to finance documentation on Mobilizon usage and coding, I would be ready to participate, if it is among others.
: