@clayton @mattcropp @vmatekole @ntnsndr @Matt_Noyes

https://wiki.social.coop/

@mayel @ntnsndr @vmatekole @mattcropp @clayton

This needs some updating! ;-)

https://wiki.social.coop/Social.coop_Roles

@Matt_Noyes @clayton @mattcropp @vmatekole @ntnsndr @mayel all wikis/documentation are always out of date. Thankfully, it's a wiki! :)

@Greg @mayel @ntnsndr @vmatekole @mattcropp @Matt_Noyes

oh great. my favorite kind of error. 😑🤣 https://social.coop/media/vIBrGS4AzFDDaurkQ8I

@Matt_Noyes Loomio has been working nicely so far for the conversation and decision making. But I agree that putting more into the wiki about current teams, processes, etc would be super useful --
especially for new comers trying to understand the lay of the land. @clayton @mattcropp @vmatekole @ntnsndr @mayel

@edsu @ntnsndr @vmatekole @mattcropp @clayton @Matt_Noyes

Yeah, it was discussed before that we should document (and link to) every Loomio proposal and its outcome on the wiki.

@mayel that seems a bit heavy to me. Having the results of loomio decisions inform work that gets done on the wiki seems doable though. For example, IMHO the social.coop system architecture info belongs in the wiki where it can be shaped by members and not buried in a loomio discussion comment. @Matt_Noyes @clayton @mattcropp @vmatekole @ntnsndr

@mayel @Matt_Noyes @ntnsndr @vmatekole @mattcropp Amazing!!! Thanks!!!

One point about that wiki: I believe it's running on the #SocialCoop production server(s).

I think it'd be sensible to keep our admin and operations documents somewhere which is
a) still accessible if our servers aren't &
b) backed up and replicated

Likewise any issue tracker, which I think we need to adopt fairly urgently.

Hence my suggestion to use https://git.coop

And my proposal
https://www.loomio.org/d/1wlJU8DG/tech-wg-budgeting

@clayton @mattcropp @vmatekole @ntnsndr @Matt_Noyes @mayel