Curators - 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




	I just have a quick question





	First contribution





	Issues





	DCO





	Suggesting Enhancements





	Pull Requests





	Code Reviews





	Reporting Bugs





	Copyright and License





	Discord





	Curators







	Developing and Conventions





	Documentation





	Community





	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

/
Curators












More actions







Curators

	Sally MacFarlane





Owned by Sally MacFarlane


Last updated: May 26, 2022










Curators have "triage" access to the Besu GitHub repository which means they can
	curate, manage, label and otherwise categorize bugs and other Github issues for Besu,
	collaborate with the existing maintainers to help coordinate the development and roadmap planning of Besu

This means they have the ability to label and close GitHub issues, helping to keep the project tidy.
This role tends to be held by Product Managers (PMs). All are currently employed by ConsenSys.
The process for becoming a Curator is separate from the process for becoming a Besu maintainer. 
Access is controlled by this GitHub group. 
Granting access
PMs that need access are nominated by a maintainer they work with
	post a message to the besu-contributors Discord channel introducing them and their role

And nomination confirmed by an existing Curator
	reply to the nomination/introduction post in the besu-contributors Discord channel
	tag or direct message to a maintainer of the GitHub group to add the new member, and then access is granted

There is no voting or other approval. The combined reputation of the nominating maintainer and confirming Curator is sufficient "social proof" for membership.
Removing access
A maintainer communicates that the Curator is no longer in the role needing access.
	post a message to the besu-contributors Discord channel

Access is removed after confirming (or after reasonable effort to do so) with the Curator being removed.
	tag or direct message to a maintainer of the GitHub group, and then access is removed

Historical record
The membership of the besu-triage group is the record of current Curators. No other record is kept.







, multiple selections available,





Related content
More info

Collapse
Repositories and other projects
Repositories and other projects

Besu



More like this






Issues
Issues

Besu



More like this






First contribution
First contribution

Besu



More like this






Programs & Grants
Programs & Grants

Besu



More like this






How to Contribute
How to Contribute

Besu



More like this






Besu - Community Support
Besu - Community Support

Besu



More like this

































































        

    


    {"serverDuration": 34, "requestCorrelationId": "11cd14f855aa4b119d9a76d7840687ec"}