| 22 Feb 2021 |
|  al3xth3k1d joined the room. | 10:08:44 |
| 23 Feb 2021 |
 dcht00 | depri-kichers: Fed Wikis are interesting, but of course, I always — and also since the first HACC meetings :) — maintained that it's not less important which collaboration solution you deploy, and much more important who will take the administrator & editorial role, and that this person has a track record of working with that platform and producing cohesive results | 17:04:24 |
| dcht00 | * depri-kichers: Fed Wikis are interesting, but of course, I always — and also since the first HACC meetings :) — maintained that it is less important which collaboration solution you deploy, and much more important who will take the administrator & editorial role, and that this person has a track record of working with that platform and producing cohesive results | 17:05:04 |
| dcht00 | If you leave this up to "everyone", and think the work stops once you install the package, this will never result in a functional & long-term knowledge base . Sadly , https://hacc.wiki became an example of this. | 17:06:40 |
| dcht00 | You will always need somebody to clean up, merge, ping people for meeting notes, establish editorial protocols — in other words, you need an initial, responsible and dedicated editor. Of course only later, if you have tens of regular contributors because the system is working, you take that the editor will be able to scale and shift efforts towards a team — but still without diluting and losing responsibility and consistency. | 17:09:03 |
| dcht00 | I see HACC is curently moving towards using pads as a knowledge base, on https://pad.hacc.space/ . I personally believe it's best if we try to find a consensus, commit to & support that effort | 17:10:42 |
 zauberberg | In reply to @dcht00:matrix.org
I see HACC is curently moving towards using pads as a knowledge base, on https://pad.hacc.space/ . I personally believe it's best if we try to find a consensus, commit to & support that effort At the beginning the Pads were still also imported into the wiki, but this was stopped because the pads started to have details of persons and people were uncomfortable with putting details like those in an open wiki. | 19:46:08 |
| zauberberg set a profile picture. | 19:48:19 |
 depri-kichers | In reply to @dcht00:matrix.org
depri-kichers: Fed Wikis are interesting, but of course, I always — and also since the first HACC meetings :) — maintained that it is less important which collaboration solution you deploy, and much more important who will take the administrator & editorial role, and that this person has a track record of working with that platform and producing cohesive results Oh ofc.... Any Wiki used by many activist orgs would probably need some central maintaining Team. which doesn't cope well with the philosophy of a "movement" which is most often a finite operation. | 20:41:32 |
| 25 Feb 2021 |
| dcht00 | zauberberg: that's an important info! i was not aware, and I can understand what you mean. all info in the pads was written by the people at CCC themselves, so there was implicit consent, I suppose, to have it published, but you have a good point that it would be stretching it a little bit, and that is not acceptable, to copy that information onward | 21:39:51 |
| dcht00 | so I think what we could definitely talk about, is how to form a 1-minute quick debrief on what happens with this information, to have an opt-in, for next HACC gatherings | 21:40:33 |
| dcht00 | I definitely understand privacy concerns, especially in DE there is a lot of care about this.
but we must make sure that we are functional, and give the many people who would love to publish their details and expose themselves, a chance to do that. i would like to make this a priority, and I'm happy we're having this conversation | 21:41:32 |
| dcht00 | depri-kichers: that's another really interesting topic. the editorial work I do at totalism.org, which holds documents that were authored by dozens of people, is not really very glorious. it's mostly about keeping a consistent style, and folding together the mess people make when doing these 1-hour, 100 people gatherings. in that sense, I don't see it as true "editorial" work really, but maybe it would be interesting to write some sort of a "guide" about how this part of the work is done, and even set limits of to where the "maintenance team" as you said has free operation, and which decisions about content it should try to pass onward to a common governance | 21:45:22 |
| dcht00 | ... i saw many collectives doing it with having "note taking delegates", which organize notes, and those are then "confirmed" by voting, but i saw those often as quite symbolic. tools to make this more insightful could definitely be found / spec'd / developed ... seems quite important IMO | 21:46:42 |
| dcht00 | In reply to @l:lukas.studio
At the beginning the Pads were still also imported into the wiki, but this was stopped because the pads started to have details of persons and people were uncomfortable with putting details like those in an open wiki. sorry to mix threads, but also I want to add, a good flow would not have any importing, transporting etc. pads can keep being edited after the public moment. I've used this pattern extensively to really nice effect. including with HACC — the original pads are still there, and look good. better than the wiki "imports". ;-) | 21:51:41 |
| 6 Mar 2021 |
| dcht00 | I refreshed the https://pad.hacc.space/hacc.int index page a bit. It now includes the interesting "HACCer seeks" page, please add some ideas you'd like help with | 20:23:12 |
| 19 Mar 2021 |
|  schmidt_fu joined the room. | 16:06:55 |
| 21 Mar 2021 |
| dcht00 | not bad
https://newrepublic.com/article/161575/climate-change-effects-hurtling-toward-global-suicide | 15:58:39 |
| dcht00 | I really dislike the "We" thing though, when somebody is writing about the problems & possible trajectories but "politely" including themselves in there. | 15:59:48 |
| dcht00 removed the room topic "hackers against climate change - collaboration, science, visualization, data -
Every 10th of a month starting at 18:00 UTC. International hacc-call on https://meet.ffmuc.net/hacc.int". | 16:02:46 |
| dcht00 set the room topic to "hackers against climate change🌍 collaboration, science, visualization, data 🌍 bi-monthly call: Every 10th & 25th starting 18:00 UTC on https://meet.ffmuc.net/hacc.int
🌍 index: https://pad.hacc.space/hacc.int". | 16:04:32 |
| dcht00 | Added the second monthly call slot (25th) to the topic. :) | 16:05:23 |
| 11 Apr 2021 |
|  francois.dedo.berlin joined the room. | 10:27:04 |
| 27 Apr 2021 |
| dcht00 changed the room topic to "hackers against climate change🌍 collaboration, science, visualization, data 🌍 bi-monthly call: Every 10th & 25th at 18:00 UTC 🌍 https://pad.hacc.space/index" from "hackers against climate change🌍 collaboration, science, visualization, data 🌍 bi-monthly call: Every 10th & 25th starting 18:00 UTC on https://meet.ffmuc.net/hacc.int
🌍 index: https://pad.hacc.space/hacc.int". | 02:45:18 |
| dcht00 | yesterday's regular meeting with some important points. https://pad.hacc.space/20210425 | 02:45:57 |
| zauberberg | In reply to @dcht00:matrix.org
yesterday's regular meeting with some important points. https://pad.hacc.space/20210425 Why is this in hacc.csv? | 06:34:14 |
| dcht00 | zauberberg: It relates to how the workgroup will operate in the future. | 17:25:34 |
| zauberberg left the room. | 21:04:49 |
| 2 May 2021 |
|  avanautikum joined the room. | 01:23:20 |
| 12 May 2021 |
|  @christian_zerfass:matrix.org joined the room. | 16:55:43 |
