As another BDFL, I was disappointed to see that these were a set of principles about what curl/the curl project should be, rather than principles for how to be a BDFL. Obviously, they are related - how you conceive of the project is quite intertwined with how you intend to be-a-BDFL.<p>But the BDFL cannot by themselves satisfy most of the goals listed in TFA.<p>If I had to sum up my own right now, without much thought:<p>1. keep the project actually alive by ensuring there is clear evidence to all of continuous, significant development.<p>2. be respectful to all those currently involved, and to all who wish to become involved.<p>3. always remain open to the possibility that I'm doing something wrong, and eagerly seek out criticism that may reveal that to be the case.<p>4. notwithstanding #3, accept that I am the expert of experts in most senses, and have accumulated a lot of domain and application specific knowledge along the way; do not get hustled by newcomers.<p>5. notwithstanding #4, acknowledgement that newcomers may have ideas that hold the key to improving usability, discoverability, functionality and more. In general, strive to give their ideas serious attention.<p>6. Be nice. Be kind. Be respectful. Answer (most) questions asked of me personally.<p>7. When it is possible to financially compensate people for significant participation, do so.<p>8. Always acknowledge the contributions of others.<p>9. Promote the idea of my own humanity and that of all those involved, in order to encourage kind behavior and an understanding of what is possible (or not).<p>10. Always remember that it is other people who make my work possible, not me.