Something like that. An OpenStreetMap based map. Only a city name as location.
That’s a really cool idea!
Something like that. An OpenStreetMap based map. Only a city name as location.
That’s a really cool idea!
Something like this?
Greate, exactly that!
For pictures and videos this open source solution:
http://www.resourcespace.com/developers
can be useful.
But pictures can also just live on the forum… no?
Hey all,
I am reviving this topic as we can start with this as soon as we want. But before we start we need to make some decisions. We have some ideas on what we could do with such a server, but not yet on how we are going to do it…
Hi Douwe,
If I’m not alone I can help administrating the server.
I would recommend:
I guess the server should be a virtual machine? This would make things easier e.g. upgrading, backup and independency from hardware.
Who will be responsible for regular backups? Is this done by the hoster? This would be much easier for us.
Did you already decide where the server will be hosted? If not I can send you some “green” providers from Austria.
Greetings
Werner
Can we implement a scheduling vote application on the new server? I’m thinking of something like dudle.
Hi,
I think that should be possible. As far as I can see it requires only Ruby and enabled CGI:
Thank you for your feedback so far! It looks like the map made by @Stefan and the idea of the corresponding email lists is the most tangible as a use case at the moment… correct?
Maybe we can start with that and then on a per-case basis look if we expand into deploying other tools?
I came up with four questions we need to ask ourselves before deploying a new tool:
How does the Fairphone community improve when we use this tool? Do we get more independent? Are we more likely to reach our goals?
Setting up a new app/tool is done quickly, but patches need to be applied and updates to be done. If you request a new tool, can you also take care of it?
With great power comes great responsibility. Some tools, like Nextcloud, allow people to upload a lot of stuff. Are we prepared to be responsible for their stuff? Can the tool allow usage everyone? By invite only? Just a few?
Nothing so sad as a wiki where the latest modification date is over a year ago… How do you determine if the tool serves a purpose and is worth keeping online?
What do you think? Are these some good questions? Do you have more?
2 posts were merged into an existing topic: Local technical support by community members: project description
Framadate can also be a good candidate, and relies on PHP/SQL instead of ruby (maybe easier to setup/maintain)
I have another use case for a file cloud: Fairphone could upload databases for http://map.fairphone.com for everyone to be used freely (for example the physical touch points).
Cc @Esmee
During our last München Gettogether, we discussed the possibility to document our discussions, be it some hints for using the device, on recycling, agendas or whatever. So I thought about this idea to generate a community page. My questions are:
We’re starting slowly with mailinglists now.
But wouldn’t what you want also work on this forum? Or are you missing functionality here?
While playing with various solutions, I came to a similar solution. So I will next start defining exactly what features are needed and then I will probably start a thread that others could bookmark.
By the way, how would I make a thread a wiki?
We would probably need a mixture of wiki and forum.
The @moderators can do this for you. You can simply flag a post (click the flag symbol below a post), choose “something else” and write us a quick message. The post will be wikied as soon as a mod sees the message.
Edit:
When you know what features you need, we can tell you ways how the forum could (or could not) provide you with these features.
PS.: I just found out, that you can subscribe to RSS feeds of a topic, by adding “.rss” to the URL: https://forum.fairphone.com/t/wearefairphone-community-server-fairphone-community-domain/25029.rss
I know there will be a need for a buildserver for the LineageOS FP2 port at some point.
When LineageOS was still called CyanogenMod I rented a VPS to automate the building of images.
Whenever a change was pushed to the WeAreFairphone github a trigger was done to Jenkins (on this VPS) which initiated a new full build of the ROM. The resulting files could be downloaded from this host directly and the buildlog would also be publicly available. Right now the cm12.1 is deprecated and I stopped the VPS.
But now, with a working LineageOS 14.1 ROM, there is a need again.
I don’t think it would be smart to host this on a shared server as performance of this server will be greatly impacted during a build.
I’d say the better solution is to redirect forum.fairphone.com to fairphone.community instead.
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.