Skip to content
This repository was archived by the owner on Jan 16, 2025. It is now read-only.

Commit 21c03d7

Browse files
cloudcannon[bot]graciegregoryabibroomJoelMarcey
authored
CGP Website Changes (#409)
* Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. * Updated 1 file via CloudCannon. --------- Co-authored-by: Gracie Gregory <[email protected]> Co-authored-by: Abi Broom <[email protected]> Co-authored-by: Joel Marcey <[email protected]> Co-authored-by: Gracie Gregory <[email protected]>
1 parent f8324a5 commit 21c03d7

20 files changed

+877
-312
lines changed

_includes/grantslist.njk

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
{% for grant in grantslist %}
22
<section>
3-
<div class="grant">
3+
<div>
44
<h3>{{ grant.data.name }}</h3>
5+
<ul class="grant">
56
<p>{{ grant.data.description }}</p>
6-
<p><a href="{{ grant.url }}">Find out more.</a></p>
7+
<p><a href="{{ grant.url }}">Learn more.</a></p>
8+
</ul>
79
</div>
810
</section>
911
{% endfor %}

_includes/memberslist.njk

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -58,18 +58,3 @@
5858
{% endif %}
5959
{% endfor %}
6060
</ul>
61-
<h2>Donors</h2>
62-
Membership is just one of the ways you can support the Rust Foundation. We are grateful to our non-member
63-
corporate donors, whose generosity ensures we are able to provide even more support to the Rust Project
64-
and Community. If your business would like to become a non-member donor, please <a href="/contact/">get in touch with us</a>.
65-
<ul class="memberslist">
66-
{% for member in memberslist %}
67-
{% if member.data.level == "donor" %}
68-
<li class="donor">
69-
{% if member.data.logo %}
70-
<a href="{{ member.data.url }}" rel="nofollow"><img src="{{ member.data.logo }}" alt="{{ member.data.name }}"/></a>
71-
{% endif %}
72-
</li>
73-
{% endif %}
74-
{% endfor %}
75-
</ul>

css/index.css

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -500,10 +500,6 @@ footer .container {
500500
width: 10em;
501501
}
502502

503-
.donor img {
504-
width: 9em;
505-
}
506-
507503
.platinummember img {
508504
width: 20em;
509505
}
@@ -512,6 +508,22 @@ footer .container {
512508
width: 15em;
513509
}
514510

511+
.donorslist {
512+
text-align: center;
513+
}
514+
515+
.donorslist li {
516+
padding: 1em;
517+
display: inline-block;
518+
position: relative;
519+
background-size: cover;
520+
background-position: center;
521+
}
522+
523+
.donorslist img {
524+
width: 9em;
525+
}
526+
515527
/* Post */
516528

517529
@media only screen and (min-width: 768px) {

grants-eligibility-and-selection.njk

Lines changed: 0 additions & 71 deletions
This file was deleted.

grants-eligibility.njk

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
layout: layouts/base.njk
3+
---
4+
5+
<section class="container" style="margin-bottom: 0;">
6+
<h1>Community Grants Program Eligibility</h1>
7+
</section>
8+
9+
<section class="container" style="margin-top: 0;">
10+
11+
<h2 id="eligibility-criteria">General Eligibility Criteria</h2>
12+
13+
<p>All grant applicants must be over the age of 18 by the date of the grant award.</p>
14+
15+
<p>All grant applicants must ensure that they are able to receive financial transfers from the USA. Details can be found <a href="https://home.treasury.gov/policy-issues/financial-sanctions/sanctions-programs-and-country-information">here</a> of the restrictions to such transactions.</p>
16+
17+
<p>Individuals whose past behavior(s) would have been in breach of the <a href="https://foundation.rust-lang.org/policies/code-of-conduct/">Rust Foundation Code of Conduct</a>, which is an extension of the <a href="https://www.rust-lang.org/policies/code-of-conduct">Rust Project Code of Conduct</a>, will not be eligible for grant funding.</p>
18+
19+
<p>Successful applicants for most of our grants will need to engage with Project Teams and/or Working Groups for whom English is the primary language of technical communication, so a good standard of written English is usually required.</p>
20+
21+
</section>
22+
23+
<section class="container">
24+
25+
<h2 id="exclusion-criteria">General Exclusion Criteria</h2>
26+
27+
<p>Applicants who have no experience of Rust, or who are proposing work that is of trivial (or no) value to the Rust community, will be automatically rejected.</p>
28+
29+
<p>Applicants who attempt to lobby decision-makers involved in the grants selection process will be automatically rejected.</p>
30+
31+
<p>Applicants for Project Grants or Fellowships who are already paid to work on the Rust Project full-time will be automatically rejected (part-time is fine).</p>
32+
33+
<p>Rust Foundation staff, officers, and directors are not eligible to apply for any Rust Foundation grants. In addition, organizations that are Members of the Rust Foundation are not eligible to apply.</p>
34+
35+
<p>Prospective applicants who work for one of the Rust Foundation’s Member organizations should contact us at <a href="mailto:[email protected]">[email protected]</a> prior to completing an application. This will initiate an assessment of whether a grant award to them might represent a conflict of interest for the Foundation.</p>
36+
37+
</section>
38+
39+
<section class="container">
40+
41+
<h2 id="specifics">Specific Eligibility and Exclusion Criteria</h2>
42+
43+
<p>Applicants should also check the information page about the type of grant they are considering applying for. Any specific eligibility or exclusion criteria for that particular grant will be outlined there.</p>
44+
45+
</section>

grants-faqs.njk

Lines changed: 11 additions & 85 deletions
Original file line numberDiff line numberDiff line change
@@ -2,108 +2,34 @@
22
layout: layouts/base.njk
33
---
44

5-
<section class="container">
5+
<section class="container" style="margin-bottom: 0;">
66
<h1>Community Grants Program FAQs</h1>
77
</section>
88

9-
<section class="container">
9+
<section class="container" style="margin-top: 0;">
1010

11-
<h2 id="general">General FAQs</h2>
11+
<h2>Who will be making the grant selection decisions?</h2>
1212

13-
<h3>Why are you running a grants program and not simply supporting people directly through GitHub sponsorship?</h3>
13+
<p>The Rust Foundation’s staff team is responsible for selecting all grant recipients, however we occasionally seek input from leaders within the Rust Project and Rust Foundation Member Directors on specific applications.</p>
1414

15-
<p>We need to be accountable to the organizations that have provided the funding for the grants program. This means that we need to enter into a formal agreement with each of our grantees, and we also need to be able, at the end of the grant year, to clearly demonstrate the impact of the funding program. Additionally, some projects will be best completed by teamwork, and so we need to be able to fund groups or organizations, and not just individuals.</p>
15+
<h2>What is the Rust Project’s involvement in the Community Grants Program?</h2>
1616

17-
<h3>Who will be making the grant selection decisions?</h3>
17+
<p>In developing the program, the Rust Foundation’s staff team consulted with the Rust Foundation Project Directors (representatives for the Rust Project that serve on our board of directors) and grantee mentors from within the Rust Project. While the Foundation makes the ultimate decisions about grants to award, we seek input from leaders within the Rust Project.</p>
1818

19-
<p>The Rust Foundation’s staff team.</p>
19+
<h2>Will the corporate members that fund the Rust Foundation be making the grant selection decisions?</h2>
2020

21-
<h3>Will the corporations that fund Rust be making the grant selection decisions?</h3>
21+
<p>No. While we occasionally consult with specific Rust Foundation Member Directors when they can help us better assess an individual applicant’s candidacy, all final decisions about grants to award are made by the Rust Foundation’s staff team.</p>
2222

23-
<p>No. Decisions will be made by the Rust Foundation’s staff team.</p>
24-
25-
<h3>Can I contact Rust Foundation Board members to talk more about my application?</h3>
23+
<h2>Can I contact Rust Foundation Board members to talk more about my application?</h2>
2624

2725
<p>No. It is essential that the people involved in making the selection decisions can do so without any external interference, and we need to ensure that they are not overwhelmed by a lot of individuals contacting them to lobby for their application. For this reason it is important that your application is as comprehensive and compelling as possible. Any applicant who attempts to lobby one of the Rust Foundation Board members will automatically have their application rejected.</p>
2826

29-
<h3>Can I appeal the decision if my grant application is unsuccessful?</h3>
27+
<h2>Can I appeal the decision if my grant application is unsuccessful?</h2>
3028

3129
<p>No, all grant decisions will be final.</p>
3230

33-
<h3>Will I receive feedback on my application if it is unsuccessful?</h3>
31+
<h2>Will I receive feedback on my application if it is unsuccessful?</h2>
3432

3533
<p>Yes, we hope to be able to give feedback to unsuccessful applicants in order to help them make successful applications in the future. This may take some time, depending on the volume of applications that we receive.</p>
3634

3735
</section>
38-
39-
<section class="container">
40-
41-
<h2 id="event-grants">Rust Event Support Grants FAQs</h2>
42-
43-
<h3>Can teams of people apply for an Event Support Grant?</h3>
44-
45-
<p>Yes, we welcome applications from teams of people and organizations.</p>
46-
47-
<h3>How will you select the Event Support Grants?</h3>
48-
49-
<p>Please see the <a href="/grants-eligibility-and-selection/">Selection process page</a>.</p>
50-
51-
<h3>Does it matter which country I live in or what my citizenship status is?</h3>
52-
53-
<p>No, but you (or your organization) must be able to legally receive funds from the USA to receive an Event Support grant.</p>
54-
55-
<h3>I am 17, can I apply for an Event Support Grant?</h3>
56-
57-
<p>You have to be 18 or older on the date of your event. We need to be mindful of different countries’ child labor laws, and laws that mean people under the age of 18 can’t enter into legal contracts.</p>
58-
59-
<h3>I am not currently a member of a Rust Project Team or Working Group, can I apply for an Event Support Grant?</h3>
60-
61-
<p>Yes.</p>
62-
63-
<h3>I/my organization doesn’t have any experience with Rust, can I apply?</h3>
64-
65-
<p>Experience with running events – particularly events for open source communities – is more important than experience with Rust. But in order to demonstrate that your event will be a success, we'll expect you to show us how well you're connected to your local Rust users.</p>
66-
67-
<h3>Do people have to adhere to a Code of Conduct to be awarded an Event Support Grant?</h3>
68-
69-
<p>Yes, you have to adhere to the <a href="https://foundation.rust-lang.org/policies/code-of-conduct/">Rust Foundation Code of Conduct</a>, which is an extension of the <a href="https://www.rust-lang.org/policies/code-of-conduct">Rust Project Code of Conduct</a>.</p>
70-
71-
<h3>Will I have to write a report about my event?</h3>
72-
73-
<p>Yes, you will have to provide a brief written report about your event, for publication on the Rust Foundation website.</p>
74-
75-
<h3>Will I need to provide receipts?</h3>
76-
77-
<p>Yes, after the event you will need to provide a report showing how the grant was spent, with copies of receipts. If you don’t spend all of the grant money on your event, you will have to return the balance to the Foundation.</p>
78-
79-
<h3>How will I get paid for my event?</h3>
80-
81-
<p>Either by direct bank transfer or through GitHub Sponsorship.</p>
82-
83-
<h3>I have got a question that hasn’t been answered here – how can I get in touch for more information?</h3>
84-
85-
<p>Please email <a href="mailto:[email protected]">[email protected]</a> and we will do our best to help.</p>
86-
87-
</section>
88-
89-
<section class="container">
90-
91-
<h2 id="hardship-grants">Rust Hardship Grants FAQs</h2>
92-
93-
<h3>Who is eligible to apply for a Hardship Grant?</h3>
94-
95-
<p>Rust community members who contribute significantly to the Rust Project and who have urgent financial insecurity.</p>
96-
97-
<h3>I am 17, can I apply for a Hardship Grant?</h3>
98-
99-
<p>You have to be 18 or older. We need to be mindful of different countries’ child labor laws, and laws that mean people under the age of 18 can’t enter into legal contracts.</p>
100-
101-
<h3>Will you make details of the Hardship Grants public?</h3>
102-
103-
<p>No. Out of respect for recipients, we will keep all details of Hardship Grant awards private.</p>
104-
105-
<h3>Can I apply for more than one Hardship Grant?</h3>
106-
107-
<p>You can apply for up to two Hardship Grants in each calendar year.</p>
108-
109-
</section>

0 commit comments

Comments
 (0)