Proposal: Discord Server Pub/Priv Channel Split  - Besu - LF Decentralized Trust


    
        
            
                
                                

        


        
            

            






Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
PreferencesOnly necessaryAccept all









LF Decentralized Trust

LF Decentralized Trust

Spaces

Apps
Templates

Create
























Besu




	All content



Shortcuts



	Meetings

Meetings


 This trigger is hidden

	How-to articles

How-to articles


 This trigger is hidden






Content







Results will update as you type.

	Code of Conduct





	Contributing





	Developing and Conventions





	Documentation





	Community




	Besu - Community Support





	Proposal: Discord Server Pub/Priv Channel Split 







	Governance





	Programs & Grants





	Meetings





	Design Documents





	Security





	Audits





	Start Here





	Performance & Stability





	How-to articles





	Incident Reports





	Besu Roadmap & Planning





	How to Contribute



















You‘re viewing this with anonymous access, so some content might be blocked.
Close













Besu

/
Proposal: Discord Server Pub/Priv Channel Split 












More actions







Proposal: Discord Server Pub/Priv Channel Split 

	Matt Nelson (Deactivated)





Owned by Matt Nelson (Deactivated)


Last updated: Aug 31, 2023










Objective: Split the existing chat channels into two distinct sections: one for users on Ethereum Mainnet/public networks, and another for those developing private networks using Besu.
Rationale: This modification aims to ensure both types of users receive appropriate support. By segregating the channels, we can create a focused environment for relevant discussions, debugging, insights sharing, and collaboration. This will also enable new developers and contributors to assist each other more efficiently.
Potential Drawbacks: Users may initially find the new structure confusing, and the channels may appear more segregated. Besu maintainers may need to context switch more frequently to support users in the right place.
Mitigation Plan: To address these issues, we could create a more comprehensive onboarding guide in the discord to navigate the new structure. We could also consider new discord roles to tag certain sets of maintainers (i.e. public-focused maintainer)
Thoughts and feedback on this proposal are welcome!







, multiple selections available,





Related content
More info

Collapse
Transition to Discord Proposal
Transition to Discord Proposal

Task Forces



More like this






Create a Discord Chat Category and Channels
Create a Discord Chat Category and Channels

Community Architects



More like this






Chat Channels
Chat Channels

Community Architects



More like this






2019 Q4 Hyperledger Besu
2019 Q4 Hyperledger Besu

Technical Oversight Committee



More like this






Besu - Community Support
Besu - Community Support

Besu



More like this






Make Besu questions easy to find and answer
Make Besu questions easy to find and answer

Besu



More like this

































































        

    


    {"serverDuration": 16, "requestCorrelationId": "b1a03646c5634836b8c3b968ba08803c"}