[Hyperledger Project TSC] Slack clean up


Mark Parzygnat <markparz@...>
 

Hi everyone,
I hear a lot of people asking questions about what channels to join in slack, where to ask questions and comments around general confusion of all the channels out there. In an effort to reduce confusion and help with consolidation, where it makes sense, I took the liberty of going through every channel that is public on slack. I have noted everyone into 3 of the sections below, all pretty self explanatory. I would like to ask that if you have a channel that you would like to keep that is listed in the 'delete section' to please respond to keep.
 
I have also copied, or added channel purposes to all the channels in the 'keep section'.  Once we have a final list, I will publish on the wiki for reference.
 
All feedback is welcomed.
 
Hyperledger Channels:
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#hackfest
#hyperledger - merge to #help
#interledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK (renamed)
#fabric-sdk-python-dev - Discuss Python SDK (renamed)
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#help - Help for newcomers for any general questions or guidance to the Hyplerledger project
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop to #fabric-cop-dev
#fabric-peer-dev (to fabric-peer-endorser-committer-dev) - new name is probably too long, hence we went with peer - Channel used for technical discussions of both runtimes of a peer endorsing and committing
#fabric-dev - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-java to #fabric-sdk-java-dev
#fabric-sdk-py to #fabric-sdk-python-dev
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  



Baohua Yang
 

Dear Mark
Thanks for your efforts! 

It's really necessary to have efficient channels before the potential of migrating to rocket-chat.

To keep a focused discussion and less confusing,  a minor suggest is to keep a simple channel with the same name for those projects like fabric-cop, fabric-sdk-java/fabric-sdk-py. We can let those members decide when there's need to splits out specific channels like  **-dev or **-general ones.

How do you think?

Thanks!

On Thu, Jan 19, 2017 at 4:26 AM, Mark Parzygnat via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi everyone,
I hear a lot of people asking questions about what channels to join in slack, where to ask questions and comments around general confusion of all the channels out there. In an effort to reduce confusion and help with consolidation, where it makes sense, I took the liberty of going through every channel that is public on slack. I have noted everyone into 3 of the sections below, all pretty self explanatory. I would like to ask that if you have a channel that you would like to keep that is listed in the 'delete section' to please respond to keep.
 
I have also copied, or added channel purposes to all the channels in the 'keep section'.  Once we have a final list, I will publish on the wiki for reference.
 
All feedback is welcomed.
 
Hyperledger Channels:
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#hackfest
#hyperledger - merge to #help
#interledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK (renamed)
#fabric-sdk-python-dev - Discuss Python SDK (renamed)
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#help - Help for newcomers for any general questions or guidance to the Hyplerledger project
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop to #fabric-cop-dev
#fabric-peer-dev (to fabric-peer-endorser-committer-dev) - new name is probably too long, hence we went with peer - Channel used for technical discussions of both runtimes of a peer endorsing and committing
#fabric-dev - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-java to #fabric-sdk-java-dev
#fabric-sdk-py to #fabric-sdk-python-dev
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  



_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Best wishes!

Baohua Yang


Christopher Ferris <chris.ferris@...>
 

Mark,

Thanks for doing this. Baohua is right, a move to RocketChat may offer us a chance to re-organize naturally. That said, a few comments.

- fabric-cop has been renamed fabric-ca, hence the corresponding channels need to be renamed accordingly.
- #help seems overly generic. It isn't clear that having a channel named '#help' will help more than hinder. I could see #<project>-help for each top-level project. Most people use #general to ask for initial help.
- The more I think of it, having separate channels for development and not per component is overkill and actually separates the developers. I would suggest that we might consider (for fabric, since that project is organized this way) having only one channel per component #fabric-<component> and one #fabric-help
- given that seems only fabric is using playbacks, suggest it too be renamed #fabric-playbacks
- I would not delete #interledger
- given we want a cohesive community, I would strongly discourage any organization-specific channels (public or private).
- #hackfest should be kept

Cheers,

Chris

On Wed, Jan 18, 2017 at 3:26 PM, Mark Parzygnat via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi everyone,
I hear a lot of people asking questions about what channels to join in slack, where to ask questions and comments around general confusion of all the channels out there. In an effort to reduce confusion and help with consolidation, where it makes sense, I took the liberty of going through every channel that is public on slack. I have noted everyone into 3 of the sections below, all pretty self explanatory. I would like to ask that if you have a channel that you would like to keep that is listed in the 'delete section' to please respond to keep.
 
I have also copied, or added channel purposes to all the channels in the 'keep section'.  Once we have a final list, I will publish on the wiki for reference.
 
All feedback is welcomed.
 
Hyperledger Channels:
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#hackfest
#hyperledger - merge to #help
#interledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK (renamed)
#fabric-sdk-python-dev - Discuss Python SDK (renamed)
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#help - Help for newcomers for any general questions or guidance to the Hyplerledger project
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop to #fabric-cop-dev
#fabric-peer-dev (to fabric-peer-endorser-committer-dev) - new name is probably too long, hence we went with peer - Channel used for technical discussions of both runtimes of a peer endorsing and committing
#fabric-dev - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-java to #fabric-sdk-java-dev
#fabric-sdk-py to #fabric-sdk-python-dev
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  



_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Mark Parzygnat <markparz@...>
 

Great suggestions.... Here is the cleaned up list...
 
I agree if we are moving to Rocket Chat soon, then no reason to delete anything from slack right now, however, if we could do the few renames, that'd be great.  I will also posted the channels I listed as 'KEEP' on the wiki (https://wiki.hyperledger.org/community/slack_channels) so we have those listed out as keepers for Rocket chat, and what they are used for. I also linked the above off the main page under tools.
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#help
#hyperledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK
#fabric-sdk-python-dev - Discuss Python SDK
#general - generic postings and or questions when unsure of where else to post.
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#hackfest - Discuss HL hackfests.
#interledger - Discuss interledger protocol.
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop-dev to #fabric-ca
#fabric-peer-dev to #fabric-peer-endorser-committer
#fabric-dev to #fabric-help - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-py to #fabric-sdk-python
#fabric-ledger-dev to #fabric-ledger
#fabric-sdk-dev to #fabric-sdk
#fabric-sdk-node-dev to #fabric-sdk-node
#playbacks to #fabric-playbacks
#java-chaincode to #fabric-java-chaincode
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  

 
 

----- Original message -----
From: Christopher Ferris <chris.ferris@...>
To: Mark Parzygnat/Raleigh/IBM@IBMUS
Cc: hyperledger-tsc <hyperledger-tsc@...>, hyperledger-discuss@...
Subject: Re: [Hyperledger Project TSC] Slack clean up
Date: Thu, Jan 19, 2017 8:23 AM
 
Mark,
 
Thanks for doing this. Baohua is right, a move to RocketChat may offer us a chance to re-organize naturally. That said, a few comments.
 
- fabric-cop has been renamed fabric-ca, hence the corresponding channels need to be renamed accordingly.
- #help seems overly generic. It isn't clear that having a channel named '#help' will help more than hinder. I could see #<project>-help for each top-level project. Most people use #general to ask for initial help.
- The more I think of it, having separate channels for development and not per component is overkill and actually separates the developers. I would suggest that we might consider (for fabric, since that project is organized this way) having only one channel per component #fabric-<component> and one #fabric-help
- given that seems only fabric is using playbacks, suggest it too be renamed #fabric-playbacks
- I would not delete #interledger
- given we want a cohesive community, I would strongly discourage any organization-specific channels (public or private).
- #hackfest should be kept
 
Cheers,
 
Chris
 
On Wed, Jan 18, 2017 at 3:26 PM, Mark Parzygnat via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi everyone,
I hear a lot of people asking questions about what channels to join in slack, where to ask questions and comments around general confusion of all the channels out there. In an effort to reduce confusion and help with consolidation, where it makes sense, I took the liberty of going through every channel that is public on slack. I have noted everyone into 3 of the sections below, all pretty self explanatory. I would like to ask that if you have a channel that you would like to keep that is listed in the 'delete section' to please respond to keep.
 
I have also copied, or added channel purposes to all the channels in the 'keep section'.  Once we have a final list, I will publish on the wiki for reference.
 
All feedback is welcomed.
 
Hyperledger Channels:
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#hackfest
#hyperledger - merge to #help
#interledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK (renamed)
#fabric-sdk-python-dev - Discuss Python SDK (renamed)
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#help - Help for newcomers for any general questions or guidance to the Hyplerledger project
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop to #fabric-cop-dev
#fabric-peer-dev (to fabric-peer-endorser-committer-dev) - new name is probably too long, hence we went with peer - Channel used for technical discussions of both runtimes of a peer endorsing and committing
#fabric-dev - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-java to #fabric-sdk-java-dev
#fabric-sdk-py to #fabric-sdk-python-dev
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  



_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
 


Brian Behlendorf
 

I definitely like where this is going.  The keep list still feels a bit long, and I worry that much of the conversation, even chatty, still belongs on email, regardless of the advent of RocketChat.  But let's give it a try and we can revisit this again in six-ish months. 

Brian

Great suggestions.... Here is the cleaned up list...
 
I agree if we are moving to Rocket Chat soon, then no reason to delete anything from slack right now, however, if we could do the few renames, that'd be great.  I will also posted the channels I listed as 'KEEP' on the wiki (https://wiki.hyperledger.org/community/slack_channels) so we have those listed out as keepers for Rocket chat, and what they are used for. I also linked the above off the main page under tools.
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#help
#hyperledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK
#fabric-sdk-python-dev - Discuss Python SDK
#general - generic postings and or questions when unsure of where else to post.
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#hackfest - Discuss HL hackfests.
#interledger - Discuss interledger protocol.
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop-dev to #fabric-ca
#fabric-peer-dev to #fabric-peer-endorser-committer
#fabric-dev to #fabric-help - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-py to #fabric-sdk-python
#fabric-ledger-dev to #fabric-ledger
#fabric-sdk-dev to #fabric-sdk
#fabric-sdk-node-dev to #fabric-sdk-node
#playbacks to #fabric-playbacks
#java-chaincode to #fabric-java-chaincode
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  

 
 
----- Original message -----
From: Christopher Ferris <chris.ferris@...>
To: Mark Parzygnat/Raleigh/IBM@IBMUS
Cc: hyperledger-tsc <hyperledger-tsc@...>, hyperledger-discuss@...
Subject: Re: [Hyperledger Project TSC] Slack clean up
Date: Thu, Jan 19, 2017 8:23 AM
 
Mark,
 
Thanks for doing this. Baohua is right, a move to RocketChat may offer us a chance to re-organize naturally. That said, a few comments.
 
- fabric-cop has been renamed fabric-ca, hence the corresponding channels need to be renamed accordingly.
- #help seems overly generic. It isn't clear that having a channel named '#help' will help more than hinder. I could see #<project>-help for each top-level project. Most people use #general to ask for initial help.
- The more I think of it, having separate channels for development and not per component is overkill and actually separates the developers. I would suggest that we might consider (for fabric, since that project is organized this way) having only one channel per component #fabric-<component> and one #fabric-help
- given that seems only fabric is using playbacks, suggest it too be renamed #fabric-playbacks
- I would not delete #interledger
- given we want a cohesive community, I would strongly discourage any organization-specific channels (public or private).
- #hackfest should be kept
 
Cheers,
 
Chris
 
On Wed, Jan 18, 2017 at 3:26 PM, Mark Parzygnat via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hi everyone,
I hear a lot of people asking questions about what channels to join in slack, where to ask questions and comments around general confusion of all the channels out there. In an effort to reduce confusion and help with consolidation, where it makes sense, I took the liberty of going through every channel that is public on slack. I have noted everyone into 3 of the sections below, all pretty self explanatory. I would like to ask that if you have a channel that you would like to keep that is listed in the 'delete section' to please respond to keep.
 
I have also copied, or added channel purposes to all the channels in the 'keep section'.  Once we have a final list, I will publish on the wiki for reference.
 
All feedback is welcomed.
 
Hyperledger Channels:
 
DELETE:
#admin-tools
#applications -> Application development discussion should be handled in the more active #app-dev channel
#bitcoin
#business-scenarios - Merge into #requirements
#ca - 6 Participants, no recent activity
#cic_directie - no participants
#cls - no participants
#compliance - no activity…. merge to #fabric-crypto
#dev
#dockerimages
#dtcc
#docsdisplay
#fabric-ledger - merge with #fabric-ledger-dev
#fabric-reconcile
#fabric-preview
#fabric-ledger-couchdb -> merge to #fabric-ledger-dev
#fabric-preview
#fabric-next-protos
#fabric-reconcile
#fabric-sdk - point to appropriate #fabric-sdk-XXX-dev
#fabric-sdk-node - merge into #fabric-sdk-node-dev
#fabric-sdk-noe
#fabric-test-hackathon
#fabric-next-proto
#security-lending
#gostr_and_cop
#hackfest
#hyperledger - merge to #help
#interledger
#it-people-fabric
#mainframe
#maintainers
#mcgui
#membership
#membership-services “states it has been deprecated and to use fabric-cop”
#next_security_arch - merge to #fabric-crypto
#openmainframe2016
#paypal
#performance-benchmark -merge to CI-pipeline
#playback - merge to #playbacks
#privacy
#rel-criteria-build
#sawtooth-hackathon
#scope
#sdk-dev
#security-lending
#share2016
#technical-discuss -> those discussions should go in the appropriate channels
#testing
#winroom-antool
#zbuild

KEEP with these as the channel descriptions
#architecture - Discuss architectural aspects and differences of any Hyperledger project
#blockchain-explorer - Collaborate about a blockchain UI for Hyperledger projects
#chaincode - Collaboration regarding CC development system or application chaincode.
#ci-pipeline - Discuss continuous integration and anything regarding testing including performance, workload generator tools, benchmark results.
#cello - Discussion on the Cello project
#corda - Collaborate on Corda architecture and technical discussion
#deployment-tools - Deployment tool chains for deploying Hyperledger across multiple IaaS/PaaS environments (AWS, Azure, OpenStack, Vmware, Cloud Foundry, Bluemix, Predix, OpenShift, Mesosphere etc).
#ethereum - Discuss Ethereum contribution plus requirements and strategy
#exit-criteria - Discuss exit criteria requirements and progress of projects from incubation to mature.
#fabric-arch - Discuss general architecture of Fabric
#fabric-ci-status - Autogenerated messages of Fabric builds
#fabric-cop-dev - Discussions about using and developing the fabric-cop component.  fabric-cop is a runtime component which issues cryptographic material which can be used to participate in a Fabric network.
#fabric-crypto - Security aspect of Fabric
#fabric-events - The purpose of this channel is to discuss the architecture and requirements for an event infrastructure for fabric nodes
#fabric-ledger-dev - Technical aspects of the Fabric ledger.
#fabric-maintainers - Discussion amongst the maintainers of the various fabric-related projects
#fabric-pr-review - Weekly review of outstanding PRs
#fabric-sdk-dev - Discussion on SDK topic agnostic to programming language
#fabric-sdk-node-dev - Discuss node.js SDK
#fabric-sdk-java-dev - Discuss Java SDK (renamed)
#fabric-sdk-python-dev - Discuss Python SDK (renamed)
#github-invite - request to join the hyperledger github org: Please mention your github handle (@ryjones, for instance)
#graphql - Discuss using GraphQL as query/mutation interface
#grpc - Discuss grpc framework
#help - Help for newcomers for any general questions or guidance to the Hyplerledger project
#identity - Discuss identity solutions, use cases, questions, requirements also see information on the identity working group at https://wiki.hyperledger.org/community/calendar-public-meetings#hyperledger_identity_wg_biweekly_meeting
#internetofthings - Discussions related to Internet of Things (IoT).
#iroha - Discuss Iroha contribution plus requirements and strategy
#java-chaincode - Implement java chaincode support in the fabric
#logging-monitoring - requirements and tools that are needed for any Hyperledger project
#marketing - Help blockchain-based solutions bring their innovative solutions to market cost-effectively
#playbacks - The purpose of this is to show developers’ most recent work. Keep checking back, the plan is to at absolute MINIMUM new playbacks every 2 weeks.
#protocol - Discuss a common blockchain protocol. There are many messages from handshake to transaction to block synchronization. The objective is to define the structures of these messages, their extendability and rules.
#random - A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
#requirements - Collaborate to collect and document use cases and develop all requirements for blockchain technology. Please see https://wiki.hyperledger.org/groups/requirements/requirements-wg for information about the Requirements Working Group.
#sawtooth - Discuss Sawtooth Lake contribution plus requirements and strategy
#slack-invite - request to add email domain to whitelist, or request individual email invite to this slack account
#sovrin - Sovrin Foundation specific discussion
#thailand - Hyperledger discussions among Thai implementors
#tsc - Technical steering committee discussion
#twg-china - Technical working group in China
 
RENAME:
#fabric-cop to #fabric-cop-dev
#fabric-peer-dev (to fabric-peer-endorser-committer-dev) - new name is probably too long, hence we went with peer - Channel used for technical discussions of both runtimes of a peer endorsing and committing
#fabric-dev - If you are unsure of where to ask your question, place it here, and we can redirect to proper channel. Triage channel
#fabric-sdk-java to #fabric-sdk-java-dev
#fabric-sdk-py to #fabric-sdk-python-dev
 
 

Regards
 

Mark Parzygnat  4205 S Miami Blvd
Blockchain  Durham, 27703-9141
6Q1A  USA
   
Phone: +1-919-254-6056  
e-mail: markparz@...  



_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
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