Should social.coop eventually have a wiki?
cloudwater
Public
Seen by 408
We already have plans for a blog, which was talked about in our status update call yesterday. https://oasis.sandstorm.io/grain/Bp6s4CFYhcTrMZF8DKkXAf/
I think it would be great to eventually have a wiki that includes everything from basic tutorials (Mastodon, Loomio, Open-Collective, Linux sysadmin, etc), development tricks, co-operative concepts, community/worker organizing strategies... basically anything relevant to what we are trying to do here. It would also be a great way to document the history and development of social.coop and the achievements of its members, and it would encourage member engagement.
Small wikis don't usually take up a lot of space, so I might be able to host it on the server I rented off of Mayel. That project has taken a backseat to community organizing right now, anyway.
Doug Belshaw Sun 26 Nov 2017 7:16AM
One of the problems with any community project is cohesion. In my experience, I'd suggest having a canonical URL for all projects (not in Loomio!)
Perhaps social.coop/projects?
Michele Kipiel Sun 26 Nov 2017 11:38AM
In the light of what we said in the thread mentioned earlier by @mayel I absolutely agree we:
1. Need a wiki
2. Need to make the number of different tool we are currently using more manageable for users who can't or don't want to waste a ton of time on the (admittedly steep) learning curve.
Mayel de Borniol Sun 26 Nov 2017 4:35PM
So as I proposed the other day, I've now set up a wiki at https://wiki.social.coop (using the same software as wikipedia, I understand people have various ideas about what tools would be appropriate, or how we should start by analysing user needs, I just thought at least this can be a place where we can gather info in the meantime, we can always import all the data from the wiki into something else later...)
Mayel de Borniol Sun 26 Nov 2017 4:38PM
You'll notice the oauth2 login link, which attempts to authenticate you on the wiki using you mastodon account. Unfortunately it's not quite working, and I think it'd be better to use our bespoke members app as the oauth server anyway (that is to say, as the canonical identity). Same with any apps/services we add in the future.
muninn Mon 27 Nov 2017 6:03AM
Should we just make accounts if we want to use it?
cloudwater Sat 2 Dec 2017 10:59AM
Yes. I guess this is my question, too. The wiki is great, but I was hesitating to login until 0auth was configured. I guess it would be wise to just get on and start.
@h Sun 3 Dec 2017 10:34PM
It may be obvious to the more technical members, and I've said this in another thread, but given the nature of Loomio threads it bears repeating here:
- You may start creating and migrating content now on the wiki at https://wiki.social.coop
- Given that OAuth still doesn't work properly, you will need to create a new account exclusively for the wiki.
- It's advisable that you use the same email and user name across different social.coop services (including the wiki) whenever possible. That will make things easier and more precise when we work on an account migration/unification process later.
Luke Opperman Mon 27 Nov 2017 3:41PM
+1 to wiki under the social.coop domain, for informal knowledge capture and organization by anyone. +2 to @mayel suggestion that this and other "official" services use oauth to the masto/members accounts.
I can go either way (-0) on gitbook - it's nice for a more formal set of documentation, and if you otherwise need the advantages of git (development/release of docs to correspond with some other versioned/release, or the distributed aspect - I put up the bylaws/CoC gitbook on gitlabs in part because I knew it would be easy to migrate to a self-hosted social.coop official location if the community felt it was a good direction.) But organizing the same content in a wiki is about as easy and can be done by any volunteer more easily than getting the gitbook stack going.
@h · Sun 26 Nov 2017 12:05AM
Yes, that was just a test because somebody interjected that some sort of bureaucratic process had to be spawned before it could be tested at social.coop. In the meantime, we keep leaking knowledge.