freedomvote
Freedomvote needs a new host
As per comment on #274, the original authors of the project have moved off and the website and subdomains linked on the README are all inoperable.
An Internet Archive capture from June 2021 shows you the state of the website soon prior to it being taken offline.
The README should be correspondingly updated, and some communications made to the community around this project in case someone else would like to take over.
Would be happy to hear any thoughts from @andreabettich as well as fellow fork'ers @anehx @fabwu @fixdocker @JohnL17 @LiohMoeller @marado @MTEXX @nicorikken @realpasha @tomas1905 @topaxi
@loleg has this codebase been 'secured' to guarantee its availability? I think that is the main thing. Regarding the website that would be mainly to those running a Freedomvote campaign I think. So maybe just update the readme and ensure a core group of custodians has access to this GitHub organization?
From the other issue,
There was an official communication from my/our side - I quote in particular the relevant part:
We are happy to leave the brand, the URL, the code, etc. to someone who would like to continue the project.
Of course the offer still stands :)
And, IMHO, the question here must be: is there anyone interested in maintaining (solo or in group) this project?
While I'd be sad to see the project die, I personally am not interested in being one of its maintainers. If anyone is...
Hi everyone, thanks for starting the discussion. Regarding the website, I would maybe just create a static site on github pages, or as @nicorikken suggested a readme, with the linkes to the active and archived Freedomvote campaigns.
As for maintaining, I'm also not interested in managing the whole thing and maintaining the project. Just not enough interest in it and as usual time is tight and other projects.
We can pitch it at a Hackathon, or look for other patrons & political groups. I totally support the idea of a freebie static page, with at least a screen cast to give a good idea of the functionality.
I don't feel much for continuing development, but happy to be a contact in case people would like to continue the project if the situation arises, just as we adopted it at the time. So I'm in favor of formalizing independent codebase stewardship and cleaning it up and documenting it enough so others can pick it up.
Seeing that it is a separate GitHub organization and that most of us have Owner privileges, I think it is fair to say that the project has been secured.
@andreabettich if we want to keep the webdomain(s) around we could setup a Open Collective fund to transparently fund them. Still there should then be somebody running the account that claims it.
Besides the domain, the main thing seems to be to create a nice README. A public facing website could be a thing, we could also create a .github organization profile repository to add some information on the organization level, or create a section on the main Freedomvote repository.
If we want to do maintenance on the codebase, then probably the most important thing is to keep the backend software as up-to-date as possible for increased security and ease of hosting. I can imagine the frontend being updated when a group actually wants to run it.
I'm fine coordinating the README and other actions from here, but I could also be nice to set up an online meeting in a couple of weeks to meet and discuss further actions.