Create a gitter.im lobby.

[grabear]

Create a gitter.im lobby for chatting, and add a gitter badge to the README file. This is the hypothetical link you would use:

I would create the PR myself, but I think I would need primary access. I think this would help create a community for discussion, and remove some of the redundant Issues that occur.

[spholmes]

Hi Rob, I'd like to wait on this as we'd like to coordinate more, we don't want to have multiple channels to monitor and this is only for a certain number of cutting edge people, some have chosen other channels. I don't see how it removes redundancy, could you explain that? Thanks Susan

On Wed, Apr 4, 2018 at 7:35 PM, Rob Gilmore notifications@github.com wrote:

Create a gitter.im lobby for chatting, and add a gitter badge to the README file. This is the hypothetical link you would use:

[image: Join the chat at https://gitter.im/phyloseq/Lobby] https://gitter.im/phyloseq/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge

I would create the PR myself, but I think I would need primary access. I think this would help create a community for discussion, and remove some of the redundant Issues that occur.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joey711/phyloseq/issues/912, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJcveFo5vxS3EO_0-N76Ur7lkfyKH87ks5tlYL3gaJpZM4THxdb .

-- Susan Holmes John Henry Samter Fellow in Undergraduate Education Professor, Statistics 2017-2018 CASBS Fellow, Sequoia Hall, 390 Serra Mall Stanford, CA 94305 http://www-stat.stanford.edu/~susan/

[grabear]

You could take 5 vetted individuals who are well versed in phyloseq and R programming (but not working on the phylsoeq package directly), get them to join the lobby, and point people to the lobby for answers by default with GitHubs Issue Templates. You could also explicitly tell people to go there, when their issues aren't really issues. The vetted members can answer outstanding questions, and eventually there will be plenty of people in the lobby to answer questions as time moves forward.

I realize that this is an open source project and there might not be enough resources, man power, or motivation for that.

[spholmes]

I am afraid that it's worse than "opensource", we are not funded either, so most of us (~3) work on weekends and off hours, I don't see that we have the resources right now, but we are thinking of ways to support our project, so this is going to be one of the strategies we could consider going forward, Susan

On Wed, Apr 4, 2018 at 8:03 PM, Rob Gilmore notifications@github.com wrote:

You could take 5 vetted individuals who are well versed in phyloseq and R programming (but not working on the phylsoeq package directly), get them to join the lobby, and point people to the lobby for answers by default with GitHubs Issue Templates. You could also explicitly tell people to go there, when their issues aren't really issues. The vetted members can answer outstanding questions, and eventually there will be plenty of people in the lobby to answer questions as time moves forward.

I realize that this is an open source project and there might not be enough resources, man power, or motivation for that.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/joey711/phyloseq/issues/912#issuecomment-378807054, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJcvZMyqcl0xmRJzXIaM5vaUNYVNl6pks5tlYmNgaJpZM4THxdb .

-- Susan Holmes John Henry Samter Fellow in Undergraduate Education Professor, Statistics 2017-2018 CASBS Fellow, Sequoia Hall, 390 Serra Mall Stanford, CA 94305 http://www-stat.stanford.edu/~susan/