Artifactspublic-v0

curl

master
ply4 git calls28 ms291 KiB3 cachedprotocol v2
216 lines8.2 KiBRaw

Decision making in the curl project

A rough guide to how we make decisions and who does what.

BDFL

This project was started by and has to some extent been pushed forward over the years with Daniel Stenberg as the driving force. It matches a standard BDFL (Benevolent Dictator For Life) style project.

This setup has been used due to convenience and the fact that it has worked fine this far. It is not because someone thinks of it as a superior project leadership model. It also only works as long as Daniel manages to listen in to what the project and the general user population wants and expects from us.

There is no legal entity. The curl project is a bunch of people scattered around the globe with the common goal to produce source code that creates great products. We are not part of any umbrella organization and we are not located in any specific country. We are totally independent.

The copyrights in the project are owned by the individuals and organizations that wrote those parts of the code.

Decisions

The curl project is not a democracy, but everyone is entitled to state their opinion and may argue for their sake within the community.

All and any changes that have been done or are done are eligible to bring up for discussion, to object to or to praise. Ideally, we find consensus for the appropriate way forward in any given situation or challenge.

If there is no obvious consensus, a maintainer who's knowledgeable in the specific area takes an "executive" decision that they think is the right for the project.

Donations

Donating plain money to curl is best done to curl's Open Collective fund. Open Collective is a US based non-profit organization that holds on to funds for us. This fund is used to reimburse and pay for project related expenses etc.

Donations to the project can also come in the form of server hosting, providing services and paying for people to work on curl related code etc. Usually, such donations are services paid for directly by the sponsors.

We grade sponsors in a few different levels and if they meet the criteria, they can be mentioned on the Sponsors page on the curl website.

Commercial Support

The curl project does not do or offer commercial support. It only hosts mailing lists, runs bug trackers etc to facilitate communication and work.

Daniel works for wolfSSL, which offers commercial curl support.

Key roles

User

Someone who uses or has used curl or libcurl.

Contributor

Someone who has helped the curl project, who has contributed to bring it forward. Contributing could be to provide advice, debug a problem, file a bug report, run test infrastructure or writing code etc.

Commit author

Sometimes also called 'committer'. Someone who has authored a commit in the curl source code repository. Committers are recorded as Author in git.

Maintainers

A maintainer in the curl project is an individual who has been given permissions to push commits to one of the git repositories.

Maintainers are free to push commits to the repositories at they see fit. Maintainers are however expected to listen to feedback from users and any change that is non-trivial in size or nature should be brought to the project as a Pull-Request (PR) to allow others to comment/object before merge.

Former maintainers

A maintainer who stops being active in the project gets their push permissions removed at some point. We do this for security reasons but also to make sure that we always have the list of maintainers as "the team that push stuff to curl".

Getting push permissions removed is not a punishment. Everyone who ever worked on maintaining curl is considered a hero, for all time hereafter.

Security team members

We have a security team. That is the team of people who are subscribed to the curl-security mailing list; the receivers of security reports from users and developers. This list of people varies over time but they are all skilled developers familiar with the curl project.

The security team works best when it consists of a small set of active persons. We invite new members when the team seems to need it, and we also expect to retire security team members as they "drift off" from the project or find themselves unable to perform their duties there.

Core team

There is a curl core team. It currently has the same set of members as the security team. It can also be reached on the security email address.

The core team nominates and invites new members to the team when it sees fit. There is no open member voting or formal ways to be a candidate. Active participants in the curl project who want to join the core team can ask to join.

The core team is a board of advisors. It deals with project management subjects that need confidentiality or for other reasons cannot be dealt with and discussed in the open (for example reports of code of conduct violations). Project matters should always as far as possible be discussed on open mailing lists.

Server admins

We run a web server, a mailing list and more on the curl project's primary server. That physical machine is owned and run by Haxx. Daniel is the primary admin of all things curl related server stuff, but Björn Stenberg and Linus Feltzing serve as backup admins for when Daniel is gone or unable.

The primary server is paid for by Haxx. The machine is physically located in a server bunker in Stockholm Sweden, operated by the company Glesys.

The website contents are served to the web via Fastly and Daniel is the primary curl contact with Fastly.

BDFL

That is Daniel.

Maintainers

A curl maintainer is a project volunteer who has the authority and rights to merge changes into a git repository in the curl project.

Anyone can aspire to become a curl maintainer.

Duties

There are no mandatory duties. We hope and wish that maintainers consider reviewing patches and help merging them, especially when the changes are within the area of personal expertise and experience.

Requirements

  • only merge code that meets our quality and style guide requirements.
  • never merge code without doing a PR first, unless the change is "trivial"
  • if in doubt, ask for input/feedback from others

Recommendations

  • we require two-factor authentication enabled on your GitHub account to reduce risk of malicious source code tampering
  • consider enabling signed git commits for additional verification of changes

Merge advice

When you are merging patches/pull requests...

  • make sure the commit messages follow our template
  • squash patch sets into a few logical commits even if the PR did not, if necessary
  • avoid the "merge" button on GitHub, do it "manually" instead to get full control and full audit trail (GitHub leaves out you as "Committer:")
  • remember to credit the reporter and the helpers.

Who are maintainers?

The list of maintainers. Be aware that the level of presence and activity in the project vary greatly between different individuals and over time.

Become a maintainer?

If you think you can help making the project better by shouldering some maintaining responsibilities, then please get in touch.

You are expected to be familiar with the curl project and its ways of working. You need to have gotten a few quality patches merged as a proof of this.

Stop being a maintainer

If you (appear to) not be active in the project anymore, you may be removed as a maintainer. Thank you for your service.

Post-Daniel BDFL

At the point in a future when Daniel steps away from the project and stops being the project lead, there is reason to reconsider how to keep driving the project forward. Countries, companies and organizations have a single president or CEO for a reason; having a single leader that responsibly can take quick daily decisions is efficient. Without Daniel as BDFL, either someone else needs to step up and become president, or the project needs to adopt a council-driven process. Maybe both? Maybe vote a new project leader for one year or a few years at a time?

Deciding the replacement person and governance is a subject for the curl core team to vote on. When that happens, this section of this document should also get updated.

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Decision making in the curl project
9A rough guide to how we make decisions and who does what.
11## BDFL
13This project was started by and has to some extent been pushed forward over
14the years with Daniel Stenberg as the driving force. It matches a standard
15BDFL (Benevolent Dictator For Life) style project.
17This setup has been used due to convenience and the fact that it has worked
18fine this far. It is not because someone thinks of it as a superior project
19leadership model. It also only works as long as Daniel manages to listen in to
20what the project and the general user population wants and expects from us.
22## Legal entity
24There is no legal entity. The curl project is a bunch of people scattered
25around the globe with the common goal to produce source code that creates
26great products. We are not part of any umbrella organization and we are not
27located in any specific country. We are totally independent.
29The copyrights in the project are owned by the individuals and organizations
30that wrote those parts of the code.
32## Decisions
34The curl project is not a democracy, but everyone is entitled to state their
35opinion and may argue for their sake within the community.
37All and any changes that have been done or are done are eligible to bring up
38for discussion, to object to or to praise. Ideally, we find consensus for the
39appropriate way forward in any given situation or challenge.
41If there is no obvious consensus, a maintainer who's knowledgeable in the
42specific area takes an "executive" decision that they think is the right for
43the project.
45## Donations
47Donating plain money to curl is best done to curl's [Open Collective
48fund](https://opencollective.com/curl). Open Collective is a US based
49non-profit organization that holds on to funds for us. This fund is used to
50reimburse and pay for project related expenses etc.
52Donations to the project can also come in the form of server hosting, providing
53services and paying for people to work on curl related code etc. Usually, such
54donations are services paid for directly by the sponsors.
56We grade sponsors in a few different levels and if they meet the criteria,
57they can be mentioned on the Sponsors page on the curl website.
59## Commercial Support
61The curl project does not do or offer commercial support. It only hosts
62mailing lists, runs bug trackers etc to facilitate communication and work.
64Daniel works for wolfSSL, which offers commercial curl support.
66# Key roles
68## User
70Someone who uses or has used curl or libcurl.
72## Contributor
74Someone who has helped the curl project, who has contributed to bring it
75forward. Contributing could be to provide advice, debug a problem, file a bug
76report, run test infrastructure or writing code etc.
78## Commit author
80Sometimes also called 'committer'. Someone who has authored a commit in the
81curl source code repository. Committers are recorded as `Author` in git.
83## Maintainers
85A maintainer in the curl project is an individual who has been given
86permissions to push commits to one of the git repositories.
88Maintainers are free to push commits to the repositories at they see fit.
89Maintainers are however expected to listen to feedback from users and any
90change that is non-trivial in size or nature *should* be brought to the
91project as a Pull-Request (PR) to allow others to comment/object before merge.
93## Former maintainers
95A maintainer who stops being active in the project gets their push permissions
96removed at some point. We do this for security reasons but also to make sure
97that we always have the list of maintainers as "the team that push stuff to
98curl".
100Getting push permissions removed is not a punishment. Everyone who ever worked
101on maintaining curl is considered a hero, for all time hereafter.
103## Security team members
105We have a security team. That is the team of people who are subscribed to the
106curl-security mailing list; the receivers of security reports from users and
107developers. This list of people varies over time but they are all skilled
108developers familiar with the curl project.
110The security team works best when it consists of a small set of active
111persons. We invite new members when the team seems to need it, and we also
112expect to retire security team members as they "drift off" from the project or
113find themselves unable to perform their duties there.
115## Core team
117There is a curl core team. It currently has the same set of members as the
118security team. It can also be reached on the security email address.
120The core team nominates and invites new members to the team when it sees fit.
121There is no open member voting or formal ways to be a candidate. Active
122participants in the curl project who want to join the core team can ask to
123join.
125The core team is a board of advisors. It deals with project management
126subjects that need confidentiality or for other reasons cannot be dealt with
127and discussed in the open (for example reports of code of conduct violations).
128Project matters should always as far as possible be discussed on open mailing
129lists.
131## Server admins
133We run a web server, a mailing list and more on the curl project's primary
134server. That physical machine is owned and run by Haxx. Daniel is the primary
135admin of all things curl related server stuff, but Björn Stenberg and Linus
136Feltzing serve as backup admins for when Daniel is gone or unable.
138The primary server is paid for by Haxx. The machine is physically located in a
139server bunker in Stockholm Sweden, operated by the company Glesys.
141The website contents are served to the web via Fastly and Daniel is the
142primary curl contact with Fastly.
144## BDFL
146That is Daniel.
148# Maintainers
150A curl maintainer is a project volunteer who has the authority and rights to
151merge changes into a git repository in the curl project.
153Anyone can aspire to become a curl maintainer.
155### Duties
157There are no mandatory duties. We hope and wish that maintainers consider
158reviewing patches and help merging them, especially when the changes are
159within the area of personal expertise and experience.
161### Requirements
163- only merge code that meets our quality and style guide requirements.
164- *never* merge code without doing a PR first, unless the change is "trivial"
165- if in doubt, ask for input/feedback from others
167### Recommendations
169- we require two-factor authentication enabled on your GitHub account to
170 reduce risk of malicious source code tampering
171- consider enabling signed git commits for additional verification of changes
173### Merge advice
175When you are merging patches/pull requests...
177- make sure the commit messages follow our template
178- squash patch sets into a few logical commits even if the PR did not, if
179 necessary
180- avoid the "merge" button on GitHub, do it "manually" instead to get full
181 control and full audit trail (GitHub leaves out you as "Committer:")
182- remember to credit the reporter and the helpers.
184## Who are maintainers?
186The [list of maintainers](https://github.com/orgs/curl/people). Be aware that
187the level of presence and activity in the project vary greatly between
188different individuals and over time.
190### Become a maintainer?
192If you think you can help making the project better by shouldering some
193maintaining responsibilities, then please get in touch.
195You are expected to be familiar with the curl project and its ways of working.
196You need to have gotten a few quality patches merged as a proof of this.
198### Stop being a maintainer
200If you (appear to) not be active in the project anymore, you may be removed as
201a maintainer. Thank you for your service.
203# Post-Daniel BDFL
205At the point in a future when Daniel steps away from the project and stops
206being the project lead, there is reason to reconsider how to keep driving the
207project forward. Countries, companies and organizations have a single
208president or CEO for a reason; having a single leader that responsibly can
209take quick daily decisions is efficient. Without Daniel as BDFL, either
210someone else needs to step up and become president, or the project needs to
211adopt a council-driven process. Maybe both? Maybe vote a new project leader
212for one year or a few years at a time?
214Deciding the replacement person and governance is a subject for the curl core
215team to vote on. When that happens, this section of this document should also
216get updated.
Diagnostics4 git calls · 28 ms
CallStatusSizeTime028 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=22
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2003.8 KiB · hit23 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=3869
git.response.cache=HIT
git.response.duration_ms=23
git.fetch.wants=bae06009b9b3f9ec2df2f56de937a939a854c42b
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=3869
git.pkt.payload.max=3848
git.sideband.band1.bytes=3847
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e2f0404cdffda9
Request
a8b5feda…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format