<html><head></head><body>To answer some of your questions: <br><br>I definitely "own" the documents. So I'm making the final editorial calls based on the goals of each resource. <br><br>We don't get spam, but it would be easy enough to lock comments if we did. And I do post the documents to email lists, but they're not publicly archived so the URLs haven't really gotten out to where vandals would find them. <br><br>Depending on the document I handle edits in different ways.<br><br>On the regional groups page, it's really just that we get around to updates once every few months. We try to check the document and incorporate any edits at least that often. If we get suggestions (we do sometimes) that don't fit the goals of the guide, I just delete them. In some cases I explain why. ("Thank you for this, looks great. I'm trying to keep this particular guide to x/y/z.") But if they're really off base I just ignore them. Before we adopted this approach, people would randomly email us with corrections that we'd have to incorporate immediately or hang into until we were ready to make updates. Neither approach was a good use of staff time. <br><br>In our guide to fair practice, there's a window when it's open to feedback and we let our members know that. I make a point of clearly responding to all the feedback in a letter to our members, along with the release of the updated guide. With that document it's important for our members to know that we didn't just ignore their feedback. <br><br>And, for fun, another one: <a href="https://docs.google.com/document/d/1uDHB7e9ObF03mw502_RJJ3w6U734mmx4-3yuWV9i0dU/edit?usp=drivesdk">https://docs.google.com/document/d/1uDHB7e9ObF03mw502_RJJ3w6U734mmx4-3yuWV9i0dU/edit?usp=drivesdk</a><br><br><div class="gmail_quote">On November 16, 2021 6:28:16 AM PST, Kristin Antin <kristin@huridocs.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Amanda - thank you so much for sharing your process!! This is incredibly helpful, and good to know that others are also reluctantly in the Google boat for now (we are also looking for alternatives). I really like that on the published resource itself, you include a link to the google doc where people can make suggestions. I really admire the openness and inclusivity. Do you get any problems with spam? I would be curious to know more about your quarterly process for updating the resources -- how do you decide which changes to accept and which ones don't fit?<div><br></div><div>I think we will try out this type of approach -- using Google docs for collaboration and feedback, and sharing the content on our wordpress site for easy findability and searchability. And I'll plan to include links to the google docs!</div><div><br></div><div>And Brendon - thank you for sharing your thoughts on the importance of community and engagement, over platforms. It's so true, and I appreciate this reminder. </div><div><br></div><div>We will be proactively seeking feedback through online group discussions (conference calls). If anyone has any advice on the best way to facilitate a feedback discussion like this, I would be very happy to receive it! For example, I'm trying to figure out the right amount of content to ask people to review. Brendon I would love to learn more from you about how to best facilitate community learning groups!</div><div><br></div><div>Please keep the ideas coming! I will send another update when we're ready to seek feedback on our resources so you can see how things are shaping up for us. </div><div><br></div><div>All the best, </div><div>Kristin</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 15, 2021 at 11:58 PM Amanda <<a href="mailto:amanda@velociraptor.info">amanda@velociraptor.info</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I kind of hate to admit it because I loathe feeding the Google ecosystem, but what has consistently worked for us is Google Docs. I haven't found anything else that works consistently with our users: I use Google Docs for this all the time. I would love a better alternative but I haven't found one that doesn't flummox people.</div><br><div>A few examples:</div><br><div>There are a few resource roundups that I have assembled and frequently share and then ask for additions to. I incorporate the feedback and then re-release them. I think the open drafts get as much traffic as the pages on our site:</div><div>* Legal Resources; <a href="https://docs.google.com/document/d/1QC02RG3m8zhtX0xVzTmwbMOqhu64Uov9UwiPU2NKiJs/edit#" target="_blank">https://docs.google.com/document/d/1QC02RG3m8zhtX0xVzTmwbMOqhu64Uov9UwiPU2NKiJs/edit#</a></div><div>* Budgets and Case Studies: <a href="https://docs.google.com/document/d/1TVv5D2cKL7eTYEgFgEK8NyyovWcFshxcgxnzezhJkXk/edit#" target="_blank">https://docs.google.com/document/d/1TVv5D2cKL7eTYEgFgEK8NyyovWcFshxcgxnzezhJkXk/edit#</a></div><div>* Remote Recording: <a href="https://docs.google.com/document/d/1la0xZBapSVrL-33fqDZ4aNSh2U2alDy5wO6A1LndVMw/edit#" target="_blank">https://docs.google.com/document/d/1la0xZBapSVrL-33fqDZ4aNSh2U2alDy5wO6A1LndVMw/edit#</a> -- this one has a few lingering threads that I haven't had a chance to address. </div><br><div>Our regional groups page is a round up of local groups in our field<span>:</span> <a href="https://airmedia.org/regional-groups" title="https://airmedia.org/regional-groups" target="_blank">https://airmedia.org/regional-groups</a> -- the way we handle taking edits/updates/suggestions to that page is to invite folks to comment on a Google Doc. We incorporate those comments ~quarterly when we update the page. </div><br><div>When we update resources like our <a href="https://airmedia.org/tools/code-of-fair-practice" title="https://airmedia.org/tools/code-of-fair-practice" target="_blank">Guide to Fair Practice</a>, a piece of the process is always to post the draft for our membership to weigh in on, and we get a lot of comments. I always leave it open to comments from anywhere, so you don't have to log in if you don't want to. </div><br><div>I try to lead each document with some kind of preamble that explains the status, owner and purpose of feedback, so that if someone stumbles on the document they can tell what they're looking at. </div><br><div>I'd love to know if you've found systems that work for you!</div><br><div>-Amanda</div><br><br><div><u></u><table cellpadding="0" cellspacing="0"><tbody><tr><td style="vertical-align:top"></td><td>✧ ✧ ✧<div><b>Amanda Hickman</b> (she/her)</div><div>Berkeley, CA</div><div><span style="margin-right:8px">(510) 545-6631</span></div></td></tr></tbody></table><u></u></div><div>On Nov 12 2021, at 9:28 am, Kristin Antin <<a href="mailto:kristin@huridocs.org" target="_blank">kristin@huridocs.org</a>> wrote:</div><blockquote><div><div>Hello resource creators! </div><div><br></div><div><div>I have some questions for you about platforms for collaborative resources. (sorry for the long email!)</div><br><div>Short version:</div><br><div>If we go through the trouble of configuring a beautiful, collaborative wiki platform for our resources, how likely is it that people would actually use those collaboration features (e.g. commenting on specific words, sentences or paragraphs, suggested changes, making edits to the content, creating new content, have a discussion)? What has already been learned about collaboration platforms (or systems) in this space?</div><br><div>Does anyone have experience (successful or unsuccessful) using different approaches to getting feedback/input on content? I would be so grateful for any lessons you have learned.</div><br><div>Long version:</div><br><div>I’ve been thinking a lot about the right **platform(s)** to create and share our community-driven resources.</div><br><div>For resources that are created with and for a community of practitioners, ideally that resource would be: super easy to collaborate on (e.g. suggestions, questions, comments, edits, ideas, debate), very transparent in terms of who worked on what and when, and really accessible in terms of it being easy to find, search, navigate, download, translate and learn.</div><br><div>...but we are just one staff person, two interns, and no dedicated budget. So how do we approach this in a more iterative and realistic way, so that we can build and improve as we gain more support?</div><br><div>When I think about our platform requirements related to accessibility and transparency, these seem pretty straightforward. I know there are many platforms that address our needs regarding these. The place where I get stuck is knowing what our collaboration feature requirements are for a platform (or platforms).</div><br><div>I’ve narrowed down the options to some stand-alone open source wiki platforms (e.g. mediawiki, xwiki, dokuwiki), and using Wordpress plugins which would allow us to host all the content on our existing <a href="http://huridocs.org" title="http://huridocs.org" target="_blank">huridocs.org</a> website. So I drafted some pros/cons:</div><br><div>* Pros to stand alone wiki: these platforms come with some great collaboration features. It would be awesome to build a community around the creation of these resources!</div><br><div>* Cons to stand alone wiki: it’s yet another platform for HURIDOCS to install, configure, maintain, and it’s yet another platform for our users to have to create an account and figure out how to do the tasks. Our audience would need to go to another place (away from our website), which might be confusing.</div><br><div>* Pros to the Wordpress plugin approach: people would know where to find it, there are some beautiful knowledge base plugins out there, and it’s easier to maintain for HURIDOCS.</div><br><div>* Cons to the Wordpress plugin approach: the collaboration would be limited to more superficial feedback forms.</div><br><br><div>So I wonder -- if we go through the trouble of configuring a beautiful, collaborative wiki platform for our resources, how likely is it that people would actually use those collaboration features (e.g. commenting on specific words, sentences or paragraphs, suggested changes, making edits to the content, creating new content, have a discussion)? I know there are many factors that go into this, including how much effort is made to engage people in contributing, and the usability of the platform. But I wonder what has already been learned about collaboration platforms (or systems) in this space? Is it really more about the process and discussion with people about the resource, than it is about the platform? </div><br><div>Does anyone have experience (successful or unsuccessful) using different approaches to getting feedback/input on content? I would be so grateful for any lessons you have learned.</div><br><div>Thank you!</div><div>Kristin</div><div><br></div><div>--</div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><span style="color:rgb(136,136,136)"><font style="font-size:12.8px"><strong>Kristin Antin</strong></font></span></div></div><div><div><span style="color:rgb(136,136,136)"><font style="font-size:12.8px"><span style="color:rgb(68,68,68)"><font size="1"><font style="font-family:arial,helvetica,sans-serif">Knowledge Collaboration Lead</font></font></span></font></span></div></div><div><span style="color:rgb(68,68,68)"><font size="1"><font style="font-family:arial,helvetica,sans-serif">she/her</font></font></span></div><div><br></div><div><div><img src="https://www.huridocs.org/wp-content/uploads/2016/01/huridocs-signature-logo.jpg" alt="" width="96" height="17"></div><br><div><font style="font-size:12.8px"><span style="color:rgb(102,102,102)"><font size="1"><font style="font-family:arial,helvetica,sans-serif">New York</font></font></span></font></div><div><div><font size="1"><span style="color:rgb(102,102,102)"><font style="font-family:arial,helvetica,sans-serif">Skype: kjantin | Twitter: </font></span></font><font size="1"><span style="color:rgb(102,102,102)"><font style="font-family:arial,helvetica,sans-serif"><a href="https://twitter.com/kjantin" title="https://twitter.com/kjantin" target="_blank">@kjantin</a></font></span></font><font size="1"><span style="color:rgb(102,102,102)"><font style="font-family:arial,helvetica,sans-serif"> | </font></span></font><font size="1"><span style="color:rgb(102,102,102)"><a href="https://pgp.mit.edu/pks/lookup?op=get&search=0x4AB61F4BBED26639" title="https://pgp.mit.edu/pks/lookup?op=get&search=0x4AB61F4BBED26639" target="_blank"><font style="font-family:arial,helvetica,sans-serif">PGP</font></a></span></font><font size="1"><span style="color:rgb(102,102,102)"><a href="https://pgp.mit.edu/pks/lookup?op=get&search=0x4AB61F4BBED26639" title="https://pgp.mit.edu/pks/lookup?op=get&search=0x4AB61F4BBED26639" target="_blank"> public key</a></span></font></div></div><div><div><font size="1"><span style="color:rgb(102,102,102)"><a href="https://www.huridocs.org/donate" title="https://www.huridocs.org/donate" target="_blank">Donate to us!</a></span></font></div></div></div><div><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><a href="http://huridocs.org/" title="http://huridocs.org/" target="_blank"><span style="color:rgb(11,83,148)">website</span></a></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(102,102,102)"> |</span></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(61,133,198)"> </span></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><a href="http://facebook.com/huridocs" title="http://facebook.com/huridocs" target="_blank"><span style="color:rgb(11,83,148)">facebook</span></a></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(102,102,102)"> |</span></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(61,133,198)"> </span></font></font></font><font style="font-size:12.8px"><font size="1"><font style="font-family:arial,helvetica,sans-serif"><a href="http://twitter.com/huridocs" title="http://twitter.com/huridocs" target="_blank"><span style="color:rgb(11,83,148)">twitter</span></a></font></font></font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div>_______________________________________________</div><div>Discuss mailing list</div><div><a href="mailto:Discuss@fabriders.net" target="_blank">Discuss@fabriders.net</a></div><div><a href="https://lists.ghserv.net/mailman/listinfo/discuss" target="_blank">https://lists.ghserv.net/mailman/listinfo/discuss</a></div><div>For more details see: <a href="https://www.fabriders.net/network-centric/" target="_blank">https://www.fabriders.net/network-centric/</a></div></blockquote>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@fabriders.net" target="_blank">Discuss@fabriders.net</a><br>
<a href="https://lists.ghserv.net/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.ghserv.net/mailman/listinfo/discuss</a><br>
For more details see: <a href="https://www.fabriders.net/network-centric/" rel="noreferrer" target="_blank">https://www.fabriders.net/network-centric/</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="color:rgb(136,136,136);font-size:12.8px"><b style="color:rgb(68,68,68);font-family:arial,helvetica,sans-serif;font-size:small">Kristin Antin</b><br></div><div style="color:rgb(136,136,136);font-size:12.8px"><font size="1" face="arial, helvetica, sans-serif" color="#444444">Knowledge Collaboration Lead<br></font></div><div><font color="#444444" face="arial, helvetica, sans-serif" size="1">she/her</font></div><div style="color:rgb(136,136,136);font-size:12.8px"><font size="1" face="arial, helvetica, sans-serif" color="#444444"><br></font></div><div><font style="color:rgb(136,136,136);font-size:12.8px" face="arial, helvetica, sans-serif"><a href="https://www.huridocs.org/" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.huridocs.org/wp-content/uploads/2016/01/huridocs-signature-logo.jpg" alt="" width="96" height="17"></a><br></font><div style="font-size:12.8px"><font size="1" face="arial, helvetica, sans-serif" color="#666666">New York</font></div><div><font size="1"><font color="#666666"><font face="arial, helvetica, sans-serif">Skype: kjantin | Twitter: <a href="https://twitter.com/kjantin" target="_blank">@kjantin</a> | </font><a href="https://pgp.mit.edu/pks/lookup?op=get&search=0x4AB61F4BBED26639" target="_blank"><span style="font-family:arial,helvetica,sans-serif">PGP</span> public key</a><br></font></font></div><div><font size="1"><font color="#666666"><a href="https://www.huridocs.org/donate" target="_blank">Donate to us!</a><br></font></font></div></div><div style="font-size:12.8px"><font size="1" face="arial, helvetica, sans-serif"><a href="http://huridocs.org/" target="_blank"><font color="#0b5394">website</font></a><font color="#666666"> |</font></font><font size="1" face="arial, helvetica, sans-serif"><font color="#3d85c6"> </font><a href="http://facebook.com/huridocs" target="_blank"><font color="#0b5394">facebook</font></a><font color="#666666"> |</font></font><font size="1" face="arial, helvetica, sans-serif"><font color="#3d85c6"> </font><a href="http://twitter.com/huridocs" target="_blank"><font color="#0b5394">twitter</font></a></font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>