Introduction message in french → english will follow
Nous avons des contributeurs à l’étranger (Allemagne @potsdamn , Brésil @rennerocha , US @CoreyRSVPStreet …) qui souhaitent que les échanges se fassent en anglais. Framasoft a tout fait depuis le début pour permettre leur inclusion et nous souhaitons continuer (avouons, c’est plutôt excitant!).
Ce que je propose c’est que chacun:
-
utilise le langage qu’il souhaite sur ce forum, en préférant l’anglais quand ça lui est possible
-
utilise la traduction du navigateur quand c’est nécessaire (ça fonctionne plutôt pas mal)
Je continue donc ci-dessous en anglais.
It’s a great pleasure to see that the community is so active and willing, regarding technical contributions, functional contributions and as users or Mobilizon instance admin (or future ones).
Many thanks for your messages, they are heartwarming and very motivating.
I feel like we should tell a bit more about Kaihuri’s on-going project for Mobilizon, and also clarify what we can do and what we won’t, so you know what to expect from us.
Project
We’ll receive a funding from NLNet towards the development of Mobilizon: NLnet; Mobilizon UX
Now we have to make the best use of it, and it’s not a simple task. We’re free to use it as we want, as long as there are deliveries which are validated by NLNet. Unfortunately we already know that we won’t be able to meet all the requirements expressed in this forum. But we need to start somewhere and after quite a lot of brain twisting we’ve decided on some milestones. I’ll create dedicated posts on this forum for of those milestones, where anyone can express their requirements or any other feedback – wait for it 
Milestone 1 – upstream existing developments
We, as instance admin, have had to tweak Mobilizon a bit to suit our needs. I know @potsdamn and @hrenard also have, and maybe there are more out there.
If those instance admin agree to it, we’d like to upstream their developments, so that they can benefit to all. It would make it easier for those admin instances to migrate to the latest version, and we assume that what is already develop is much in line with users’ needs.
Milestone 2 – redesign the front page
That’s most users entry point to Mobilizon. Some of the forum users would like the possibility to personalize it more (ex: Customizing Mobilizon instance home page and other content - #4 par gregorSamsa), so do we.
Milestone 3 – search page and search results
That’s the second area where we’ll revisit the UX, hopefully tackling the grievance found in this post: Réparer l'UX/UI de Mobilizon V3
Milestone 4 – interoperability
Framasoft has done a lot of work and we think it’s so very important that we’ll spend some energy on documenting it, with examples and use cases.
What we’ll do
Welcome and merge contributions.
We’ll do our very best to merge any contribution, but if you’re thinking of doing a big one, we recommend you reach out to us as soon as possible, so we can together make sure that contributions are enriching each other and are not redundant or involuntarily diverging. A post on this forum is the best way to initiate such discussion, moreover anyone can share it’s view point.
Host instances
We offer hosting instances as a service. We see this as a possible income for us, which would help towards maintaining the project on the long run. If you’d like to create a new instance, you can turn to us for implementing and hosting it. I know there are other Mobilizon hosters around so we could deal with many such requests 
What we won’t do
Support
We’re doing volunteer work or almost, on evenings and week-end. We don’t offer any user support, except if we host your instance and are paid for that.
Anyone is free to reach out to the community for help, and we encourage those who can to answer them.
Deal with non listed topics – including bugs
We’ll give full priority to the topics listed as milestones, and we won’t be able to address anything outside of this scope, at least for the first months or even the first year.
As stated before, if there is something you need, you’ll have to get it developed by your own means. What we can do is merge it for you, and maybe help you source a developer.
This limitation includes bug fixing – we don’t commit on fixing all the bugs, especially if they are neither on the home page nor the search page nor the search results. That’s not out of interest, but because we have limited bandwidth. This shouldn’t refrain you for asking for new functionalities nor reporting bugs, it will build some backlog we hope we can attend to at some point.
Thanks for reading and thanks for being part of Mobilizon community!