Date
1 - 6 of 6
[Hyperledger Project TSC] Standard naming for Slack channels, followed by some pruning
|
Brian Behlendorf <bbehlendorf@...>
While I'd still love to see Slack used less, or us move to an alternative like Rocket Chat (anyone up to evaluate that?) so we get archiving, while we do continue to use Slack I'd like to see if we could come up with a documented taxonomy for the lists - really to answer the questions:
"Where do I go to ask for help with ____" "What's the minimum channels I should follow if I want to say I'm following project _____" "What's in scope for channel ______" For example, the #general channel is very active with basic questions about Fabric, that seem like maybe they should be on #fabric, but then maybe that's too deep for new users just getting started, or...? Or, is the #grpc specific to Fabric, or for any project using grpc as its protocol? If anyone feels so motivated, the Wiki may be the best place to draft a prototype on this, starting from the existing set of channels but then recommending certain channel name changes if they make sense. I might suggest there are two types of channels, one generic across Hyperledger (e.g. "#general" really should be for HL-wide general issues or "#ci-tools" for continuous integration tooling available to all projects) that we'd have others defined as related to projects. So e.g.: #general #ci-tools #tsc and then for any project $project, #$project (for new users, basic questions, the occasional #$project-dev (for deeper dev discussions) #$project-whatever so that projects can have their own namespace for unique channels, but not too many Then the final step would be to prune away some of the older channels, so that the full list of channels isn't so overwhelming to new devs. Thoughts? Brian -- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf |
|
|
|
Ray Chen <ray@...>
Brian Behlendorf wrote:
I might suggest there are two types of channels, one generic acrossIt makes sense to me since namespacing can keep the channels clear and more friendly to new users. Beside, we may need to put a good purpose description in each channel's 'Channel Details' field so when new users come to join Slack, they can quickly find their interested channels. Then the final step would be to prune away some of the older channels,Agreed! Ray -- Ray Chen Senior Engineer, Hyperchain Technologies Co., Ltd. |
|
|
|
Jeremy Sevareid <jeremysevareid@...>
What about making a renewed push to encourage folks to transition from
toggle quoted message
Show quoted text
slack? -----Original Message-----
From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of Ray Chen via hyperledger-tsc Sent: Thursday, October 27, 2016 1:06 AM To: Brian Behlendorf <bbehlendorf@...> Cc: hyperledger-tsc <hyperledger-tsc@...> Subject: Re: [Hyperledger Project TSC] Standard naming for Slack channels, followed by some pruning Brian Behlendorf wrote: I might suggest there are two types of channels, one generic acrossIt makes sense to me since namespacing can keep the channels clear and more friendly to new users. Beside, we may need to put a good purpose description in each channel's 'Channel Details' field so when new users come to join Slack, they can quickly find their interested channels. Then the final step would be to prune away some of the older channels,Agreed! Ray -- Ray Chen Senior Engineer, Hyperchain Technologies Co., Ltd. _______________________________________________ hyperledger-tsc mailing list hyperledger-tsc@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc |
|
|
|
Brian Behlendorf <bbehlendorf@...>
Two things would be helpful here:
toggle quoted message
Show quoted text
a) Lots of mentions of Rocket Chat as an open source alternative to Slack. http://rocket.chat/ We need someone to give it a serious evaluation, including what its operational burden would be. Simply for bandwidth reasons at the moment I/LF IT can't take this on, but someone in the community could really help us here during the research phase, and we could potentially host it later. Would be very interesting to see if we can get integrated single sign-on with the other LF properties. b) Help test out Discourse. http://discuss.hyperledger.org/ Really hammer on it, we can prune away later. It's not official yet, but with enough testing we can bring it up again on a future TSC. More of a potential replacement for some of what we use Mailing Lists for as well. Brian On 10/27/2016 08:27 AM, Jeremy Sevareid via hyperledger-tsc wrote:
What about making a renewed push to encourage folks to transition from --
Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf |
|
|
|
Ray Chen <ray@...>
Brian Behlendorf <bbehlendorf@...>:
b) Help test out Discourse. http://discuss.hyperledger.org/ Really hammer onTesting Discourse. BTW I see Discourse was introduced as a candidate to replace Mailman, but actually it is more likely to be a platform like 'hyperledger.stackexchange.com' IMHO. Ray |
|
|
|
Arnaud Le Hors
While I'm all for experimenting with an
alternative to Slack which I like using but is pretty terrible without
history, I think we need to try and time-box these experiments a bit better.
Failing to do so means we end up with the old systems and the new ones
running in parallel for long periods of time which makes things very confusing.
toggle quoted message
Show quoted text
For instance, the current situation with github wiki and wiki hyperledger means there is a lot of duplicated info and it's not clear to the reader which is the most up-to-date. I think we need to put an end to this and retire github wiki. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Cloud From: Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> To: hyperledger-tsc@... Date: 10/27/2016 10:30 PM Subject: Re: [Hyperledger Project TSC] Standard naming for Slack channels, followed by some pruning Sent by: hyperledger-tsc-bounces@... Two things would be helpful here: a) Lots of mentions of Rocket Chat as an open source alternative to Slack. http://rocket.chat/ We need someone to give it a serious evaluation, including what its operational burden would be. Simply for bandwidth reasons at the moment I/LF IT can't take this on, but someone in the community could really help us here during the research phase, and we could potentially host it later. Would be very interesting to see if we can get integrated single sign-on with the other LF properties. b) Help test out Discourse. http://discuss.hyperledger.org/Really hammer on it, we can prune away later. It's not official yet, but with enough testing we can bring it up again on a future TSC. More of a potential replacement for some of what we use Mailing Lists for as well. Brian On 10/27/2016 08:27 AM, Jeremy Sevareid via hyperledger-tsc wrote: > What about making a renewed push to encourage folks to transition from > slack? > > -----Original Message----- > From: hyperledger-tsc-bounces@... > [mailto:hyperledger-tsc-bounces@...] On Behalf Of Ray Chen > via hyperledger-tsc > Sent: Thursday, October 27, 2016 1:06 AM > To: Brian Behlendorf <bbehlendorf@...> > Cc: hyperledger-tsc <hyperledger-tsc@...> > Subject: Re: [Hyperledger Project TSC] Standard naming for Slack channels, > followed by some pruning > > Brian Behlendorf wrote: > >> I might suggest there are two types of channels, one generic across >> Hyperledger (e.g."#general" really should be for HL-wide general >> issues or "#ci-tools" for continuous integration tooling available to >> all projects) that we'd have others defined as related to projects. >> >> So e.g.: >> >> #general >> #ci-tools >> #tsc >> >> and then for any project $project, >> >> #$project (for new users, basic questions, the occasional >> #$project-dev (for deeper dev discussions) #$project-whatever so that >> projects can have their own namespace for unique channels, but not too >> many > It makes sense to me since namespacing can keep the channels clear and more > friendly to new users. Beside, we may need to put a good purpose > description in each channel's 'Channel Details' field so when new users come > to join Slack, they can quickly find their interested channels. > >> Then the final step would be to prune away some of the older channels, >> so that the full list of channels isn't so overwhelming to new devs. > Agreed! > > Ray > > -- > Ray Chen > Senior Engineer, Hyperchain Technologies Co., Ltd. > > > _______________________________________________ > hyperledger-tsc mailing list > hyperledger-tsc@... > https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc > > _______________________________________________ > hyperledger-tsc mailing list > hyperledger-tsc@... > https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc -- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf _______________________________________________ hyperledger-tsc mailing list hyperledger-tsc@... https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc |
|
|