After 3+ months experience with Fair.Coop, I've got a sample of the current scenario mostly around tech and would like to invite everyone to think together about the following concerns.
1) The work required to have UseFairCoin as a great tool seems to not make sense since there's just me working on the code, and I'm not a fan of wordpress nor its the best area of my expertise. For that reason, I've started to look through mapo.komun.org and it looks quite ok. There seem to be several missing features and there are some things which don't work. Of course everything could be fixed and it's always much easier collaborating.
Since we are just a few in core tech, the best we can do for ourselves and for the community is to work as close and coordinated as possible. So I'm looking forward to getting hands on the code and contribute to it.
2) Interaction with autonomous organisations
Which mechanisms shall we adopt in order to welcome and interact in a mutually healthy way with independent efforts like Komun.org, Fairkom or others, so there is a clean relationship of mutual support?
Shall we start rethinking the technical roadmap with the acquired experience?
We probably need to split that task in two groups:
- One or more researching, proposing and developing new technologies and solutions for the ecosystem.
- Another or more for maintaining and improving the current tools and infrastructure for the immediate needs.
4) Tech on other areas
It seems a good idea that areas manage their own projects to avoid bureaucracy of passing always through tech, which is a typical bottlenech as tech is always a busy area. However, for that to work, we might need to think of a protocol for assisting tech projects ocurring on other areas, like suggest best practices, recommend tools for the different tasks and needs and be ready for providing advise and support.
Basically we need to think, propose and shape this together.
5) Improving the toolset
Hopefully with the improvement of many tools we really need, our work will be simpler, more comfortable and more efficient, thus relieving pressure from ourselves and eachother. Shall we try to solve a couple of them in parallel to the replanning?
6) Use of trackers
As an excercise, I propose that we take a few of the major topics and create the corresponding issues on the trackers of choice, so that we could start discussing them and updating the issues accordingly for a proper tracking, following the best practices from the free software development communities.
7) Some spare ideas (we can expand on them later):
federated login service to unify access to the different tools.
bots to file issues directly from the groups.
- users could easily see how to do it themselves right from there.
- should post back the link to the tracker for future reference.
- should automatically announce to the group when an issue is closed.
implement some kind of captcha before revealing the join link to Telegram groups
pads indexing and search
have all groups pin a message with their link resources pad, to ease life to current group members as well as newcomers.
there were a lot more from other people too I think.
- shall we setup some "ideas repository"? It would be easier to find stuff in there using a tracker's search, and better organized than pads probably.
Are we doing this together?