You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,12 @@
1
-
# Contributing to database-stream-processor
1
+
# Contributing to DBSP
2
2
3
-
The database-stream-processor project team welcomes contributions from the community. Before you start working with database-stream-processor, please
4
-
read our [Developer Certificate of Origin](https://cla.vmware.com/dco). All contributions to this repository must be
5
-
signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on
6
-
as an open-source patch.
3
+
The DBSP project team welcomes contributions from the community. Before you start working with DBSP, please
4
+
read our [Developer Certificate of Origin (DCO)](https://developercertificate.org/).
5
+
To acknowledge the DCO, sign your commits by adding `Signed-off-by: Your Name <your@email.com>` to the last
6
+
line of each Git commit message. Your signature certifies that you wrote the patch or have the right to pass
7
+
it on as an open-source patch. The e-mail address used to sign must match the e-mail address of the Git
8
+
author. If you set your `user.name` and `user.email` git config values, you can sign your commit automatically
9
+
with `git commit -s`.
7
10
8
11
## Contribution Flow
9
12
@@ -12,21 +15,21 @@ This is a rough outline of what a contributor's workflow looks like:
12
15
- Create a topic branch from where you want to base your work
13
16
- Make commits of logical units
14
17
- Make sure your commit messages are in the proper format (see below)
15
-
- Push your changes to a topic branch in the vmware repository or a fork if you don't have commit access to vmware (the reason that pushing directly to the vmware repo is preferred is because then CI will be able to add benchmark results to the PR in the comments).
18
+
- Push your changes to a topic branch in the repository or a fork if you don't have commit access to (the reason that pushing directly to the repo is preferred is because then CI will be able to add benchmark results to the PR in the comments).
0 commit comments