I hear you. Personally my web dev past is so ancient I'm officially not a coder 
and have to work to get my head around GitHub every time I touch it. Because 
the Code of Conduct and related documents already lived there, that's where 
we're working. Taking the liberty of speaking for the team by saying that 
moving to Google Docs is more administrative labor than we would have the 
availability to take on at this point, but suggestions are certainly welcome 
outside GitHub via this list, Slack, Discord, or direct communication with any 
of us listed at 
https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/css_volunteers.md.
 

If you are someone who was already somewhat familiar with the documents 
themselves but not super comfortable sifting through GitHub, you can see a 
summary of changes and additions, (green for additions, red for deletions) 
here: https://github.com/code4lib/code-of-conduct/pull/80/files 

Anne

Anne Slaughter
Director of Technology Services
Reaching Across Illinois Library System
Burr Ridge Office
Phone: 630.734.5127
Fax: 630.734.5050
[email protected]
https://www.railslibraries.info

-----Original Message-----
From: Code for Libraries <[email protected]> On Behalf Of Natasha Allen
Sent: Thursday, July 11, 2019 3:20 PM
To: [email protected]
Subject: Re: [CODE4LIB] From the Community Support Squad wrt "Note 
[admiistratativia]"

Hi all,

If we are wanting to get community feedback on something like a code of conduct 
page, may I suggest instead of using github,  we have a shared google doc 
allowing folks to make comments/have discussions on that document? I'm sure 
there are probably better ways out there than a google doc, so feel free to 
chime in with other options. I was just thinking that even though a lot of us 
are coders and therefore familiar with github, other folks who may not be as 
familiar with that format might want to have a say.


Natasha

---
Natasha Allen (she/her)
System and Fulfillment Coordinator, University Library San José State University
1 Washington Square
San José , CA 95192
[email protected]
408-808-2655





On Thu, Jul 11, 2019 at 1:09 PM Kate Deibel < 
[email protected]> wrote:

> For people who lack either github or git knowledge and don't want to 
> just try to read the diff outputs, here are the links you need:
>
> This is the particular fork (Bobbi's personal version that she wants 
> to be
> merged):
> https://github.com/bobbi-SMR/code-of-conduct/tree/listserv_edits
>
> In particular, one should look over the following files:
>
> https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/code_
> of_conduct.md
>
> https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/css_v
> olunteers.md
>
> https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/csvch
> arge.md 
> https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/norms
> .md
>
> https://github.com/bobbi-SMR/code-of-conduct/blob/listserv_edits/proce
> dures.md
>
> I hope this helps people who do not know how to merge a pull request 
> on their local copy (or have the resources/time) or how to navigate 
> the Byzantine link structure of github pages.
>
>
> Katherine Deibel | PhD
> Inclusion & Accessibility Librarian
> Syracuse University Libraries
> T 315.443.7178
> [email protected]
> 222 Waverly Ave., Syracuse, NY 13244
> Syracuse University
>
>
> -----Original Message-----
> From: Code for Libraries <[email protected]> On Behalf Of Bobbi 
> Fox
> Sent: Thursday, July 11, 2019 2:42 PM
> To: [email protected]
> Subject: Re: [CODE4LIB] From the Community Support Squad wrt "Note 
> [admiistratativia]"
>
> I have submitted a Pull Request [PR -- a suggestion to change 
> code/text] to the Code of Code4Lib Conduct GitHub repository:
> https://github.com/code4lib/code-of-conduct/pull/80
>
> Suggestions welcome.
>
> Cheers,
>
> Bobbi
>

Reply via email to