Skip to content

Commit 7549d34

Browse files
Apply suggestions from code review
Co-authored-by: Jonas Schievink <[email protected]>
1 parent 344d0c5 commit 7549d34

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

blog/_posts/2020-08-29-financial-report.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,16 @@ It probably is good that @matklad didn't choose accounting as a career.
99
The next report should be exact though.
1010

1111
We've got about 14000 EUR on open collective after fees.
12-
Of which, we distributed 12000 EUR by splitting it into two buckets:
12+
Of which we distributed 12000 EUR by splitting it into two buckets:
1313

1414
* 50% for Ferrous Systems
1515
* 50% for contributors, not affiliated with Ferrous
1616
1717
We were able to pay more than our usual 20% to contributors because we managed to do some direct contracting work for rust-analyzer.
1818

1919
Ferrous share went to paying for part of https://github.com/matklad[@matklad]'s time and for administrative tasks.
20-
3000 EUR were payed to https://github.com/flodiebold[@flodiebold] for chalk integration and various other type system improvements.
21-
3000 EUR were payed to https://github.com/edwin0cheng[@edwin0cheng] for implementing most of declarative and procedural macro support.
20+
3000 EUR were paid to https://github.com/flodiebold[@flodiebold] for chalk integration and various other type system improvements.
21+
3000 EUR were paid to https://github.com/edwin0cheng[@edwin0cheng] for implementing most of declarative and procedural macro support.
2222

2323
Our biggest Open Collective sponsors in the first half of 2020 are:
2424

@@ -31,6 +31,6 @@ Our biggest Open Collective sponsors in the first half of 2020 are:
3131
<3
3232

3333
If you use rust-analyzer professionally, consider asking your company to https://opencollective.com/rust-analyzer/[sponsor] the development of this project.
34-
We are also planing to announce a couple of new ways to support rust-analyzer development soon, stay tuned!
34+
We are also planning to announce a couple of new ways to support rust-analyzer development soon, stay tuned!
3535

36-
As a reminder, we publish https://rust-analyzer.github.io/thisweek[weekly changelog] to report the progress on rust-analyzer and explain where the money go.
36+
As a reminder, we publish https://rust-analyzer.github.io/thisweek[weekly changelogs] to report the progress on rust-analyzer and explain where the money goes.

0 commit comments

Comments
 (0)