Re: [CODE4LIB] Listserv communication, was RE: Proposed Duty Officer

2016-02-26 Thread Kyle Banerjee
> You're also always going to have trouble with getting people to ask > questions, unless the concept of asking for help/guidance has been drilled > into them as not stupid, but constructive, for a very long time. I'm > talking life span. > Responses people expect are also a barrier to

Re: [CODE4LIB] Listserv communication, was RE: Proposed Duty Officer

2016-02-26 Thread BWS Johnson
My fellow nerds, I'm snipping *a lot* but in brief I definitely agree with Julie. > Kyle’s main issue was really a question about what to do with > private and anonymous feedback – not that we should avoid it, but rather we > should discuss how that should be handled. For example,

Re: [CODE4LIB] Listserv communication, was RE: Proposed Duty Officer

2016-02-26 Thread Timothy Tavarez
Some notes on participation/inclusion: 1) It can be difficult integrating yourself into a group where you may feel like more or less of an outsider. An on-boarding experience of some sort - even so simple as a web page for new users might help. The code4lib website has little pieces of advice

[CODE4LIB] Listserv communication, was RE: Proposed Duty Officer

2016-02-26 Thread Julie Swierczek
I just want to respond to let people know that Kyle and I have been discussing this further through private channels, and we agree on many points. My earlier response was not meant to be a criticism of what Kyle said specifically; rather, I was responding to what I see are the larger