Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Commit

Permalink
update cms seeds as of 2021-11-02
Browse files Browse the repository at this point in the history
  • Loading branch information
@indirect
indirect committed Nov 2, 2021
1 parent b52ba49 commit 7585660
Show file tree
Hide file tree
Showing 14 changed files with 277 additions and 250 deletions.
4 changes: 4 additions & 0 deletions db/cms_seeds/ruby-together/files/_ruby-api.jpg.yml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
---
label: ruby-api.jpg
description:
categories: []
Binary file added db/cms_seeds/ruby-together/files/ruby-api.jpg
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 5 additions & 1 deletion db/cms_seeds/ruby-together/layouts/default/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
[attributes]
---
label: Page Layout
app_layout: application

position: 0
[content]
{{ cms:wysiwyg content }}

{{ cms:textarea footer, render: false }}
[js]

[css]
6 changes: 5 additions & 1 deletion db/cms_seeds/ruby-together/layouts/default/news/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,11 @@
[attributes]
---
label: News Layout
app_layout: news

position: 0
[content]
{{ cms:text summary, render: false }}
{{ cms:markdown content }}
[js]

[css]
9 changes: 7 additions & 2 deletions db/cms_seeds/ruby-together/pages/index/bylaws/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,11 @@
[attributes]
label: "Ruby Together Corporate Bylaws"

---
label: Ruby Together Corporate Bylaws
layout: default
target_page:
categories: []
is_published: true
position: 1
[wysiwyg content]
<section class="group">
<p>A California Nonprofit Mutual Benefit Corporation Effective February 6, 2015</p>
Expand Down
9 changes: 7 additions & 2 deletions db/cms_seeds/ruby-together/pages/index/companies/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,11 @@
[attributes]
label: "Put Better Tools In Your Toolbox"

---
label: Put Better Tools In Your Toolbox
layout: default
target_page:
categories: []
is_published: true
position: 7
[wysiwyg content]
<section class="group">
<p>Companies rely on robust tools to build the best apps possible, but the volunteers who maintain those critical Ruby tools and infrastructure can't keep up in their free time. All too often, individual companies end up paying full-time engineers to privately work around issues shared by the entire Ruby community.</p>
Expand Down
9 changes: 7 additions & 2 deletions db/cms_seeds/ruby-together/pages/index/conflict_policy/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,11 @@
[attributes]
label: "Ruby Together Conflict of Interest Policy"

---
label: Ruby Together Conflict of Interest Policy
layout: default
target_page:
categories: []
is_published: true
position: 6
[wysiwyg content]
<section class="group">
<p>Effective February 6, 2015</p>
Expand Down
8 changes: 6 additions & 2 deletions db/cms_seeds/ruby-together/pages/index/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
[attributes]
label: "Ruby Together"
---
label: Ruby Together
layout: default

target_page:
categories: []
is_published: true
position: 0
[wysiwyg content]
50 changes: 26 additions & 24 deletions db/cms_seeds/ruby-together/pages/index/developers/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,27 +1,29 @@
[attributes]
label: "Work without workarounds"
---
label: Work Without Workarounds
layout: default
target_page:
categories: []
is_published: true
position: 8
[text_area footer]

[wysiwyg content]
<section>
<p>Stop relying on workarounds or waiting for someone to fix shared Ruby tools in their spare time! Ruby Together pays developers to dedicate time to maintaining and improving shared Ruby tools so they work better for everyone.</p>

<p>We depend on the community to make that dedicated work possible.</p>

<h4>When you support Ruby Together, you get:</h4>

<ul>
{{ cms:partial "home/member_benefit_items" }}
</ul>

<p><a href="/team">Our team</a> has a proven track record of delivering year-over-year improvements to Ruby's <a href="/roadmap">public infrastructure</a>. With funding, we'll transform the tools you use so that they work for you. Like tools should.</p>
</section>

<section class="group">
{{ cms:partial "home/memberships/developer_small" }}
{{ cms:partial "home/memberships/developer_medium" }}
{{ cms:partial "home/memberships/developer_large" }}
{{ cms:partial "home/memberships/one_time" }}
</section>

{{ cms:partial "home/ruby_together_is" }}
{{ cms:partial "home/faq" }}
<section>
<p>Stop relying on workarounds or waiting for someone to fix shared Ruby tools in their spare time! Ruby Together pays developers to dedicate time to maintaining and improving shared Ruby tools so they work better for everyone.</p>

<p>We depend on the community to make that dedicated work possible.</p>

<h4>When you support Ruby Together, you get:</h4>

<ul>
{{ cms:partial "home/member_benefit_items" }}
</ul>

<p><a href="/team">Our team</a> has a proven track record of delivering year-over-year improvements to Ruby's <a href="/roadmap">public infrastructure</a>. With funding, we'll transform the tools you use so that they work for you. Like tools should.</p>
</section><section class="group">
{{ cms:partial "home/memberships/developer_small" }}
{{ cms:partial "home/memberships/developer_medium" }}
{{ cms:partial "home/memberships/developer_large" }}
{{ cms:partial "home/memberships/one_time" }}
</section><p>{{ cms:partial "home/ruby_together_is" }}</p><p>{{ cms:partial "home/faq" }}</p>
13 changes: 9 additions & 4 deletions db/cms_seeds/ruby-together/pages/index/example_proposal/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,13 @@
[attributes]
label: "Example Project Proposal"

---
label: Example Project Proposal
layout: default
target_page:
categories: []
is_published: true
position: 0
[html footer]
<br>
[wysiwyg content]
<p><b>What project are you applying for?</b></p>

Expand Down Expand Up @@ -57,5 +64,3 @@

<p>I previously worked as a detective, solving difficult crimes with my human partner. For the details of one case, see The Caves of Steel. </p>

[html footer]
<br>
189 changes: 88 additions & 101 deletions db/cms_seeds/ruby-together/pages/index/projects/content.html
View file
Original file line number Diff line number Diff line change
@@ -1,104 +1,91 @@
[attributes]
label: "Ruby OSS Project Funding"
---
label: Ruby OSS Project Funding
layout: default
target_page:
categories: []
is_published: true
position: 3
[text_area footer]

[wysiwyg content]
<p class="callout">Nominate your project for funding.</p>

<section class="group">
<p>Ruby Together funds open source projects on a quarterly basis. We accept project proposals at any time, and once every three months the Ruby Together project committee decides which projects we will fund for the next three months.</p>
</section>

<section class="group">
<h3 id="requirements">Requirements</h3>

<p>To be eligible for funding, your project needs to meet a few requirements:</p>

<ul>
<li>Your project must be open source</li>
<li>Your project must benefit the Ruby community</li>
<li>Your project must have an enforced code of conduct</li>
<li>If you are not a project maintainer, your proposal needs to already be approved by existing maintainers</li>
</ul>

</section>

<section class="group">
<h3 id="how-to-apply">How To Apply</h3>

<p>Open {{ cms:helper link_to "the project proposal form", proposal_path }} and fill it out. We ask questions to be able to understand and evaluate the project and your work proposal. It shouldn’t take you more than a few minutes to fill out a proposal (and if it does, please tell us about it so we can fix it!)</p>
</section>

<section class="group">
<h3 id="work-expectations">Work Expectations</h3>

<p>Project proposals will be evaluated on outcomes, not on hours worked. We do not expect you to work an exact number of hours, but we are looking for projects that resemble what you might do in three months at a full-time job. When applying, the most important thing is to know how much time you will actually be able to spend, and what meaningful results you can achieve in that time.</p>

<p>Ruby Together project funding is intended to support work that needs large blocks of concentrated time, or needs a large amount of time, to get done. We are happy to fund both boring work like triage and bugfixes as well as exciting work like creating new tools that have never existed before.</p>
</section>

<section class="group">
<h3 id="selection-process">Selection process</h3>

<p>The Ruby Together project selection committee will evaluate proposals based on several criteria:</p>

<ul>
<li>Community impact (how much will this proposal benefit the Ruby community as a whole?)</li>
<li>Project usage (larger, more popular projects are more likely to help more of the community)</li>
<li>Project plan (a more detailed and specific plan of changes or features is more likely to help the community than “bugfixes and improvements”)</li>
<li>Member feedback (which proposals are most helpful to Ruby Together’s existing members?)</li>
<li>Track record (what is the history of the project? what about the history of the person applying?)</li>
</ul>

<p>Today, the project committee includes the <a href="/team">board of directors</a>. Funded projects will be announced in the Ruby Together monthly update each cycle.</p>
</section>

<section class="group">
<h3 id="project-reports">Project reports</h3>

<p>Each accepted project will be expected to submit a project report twice per month. Project reports should demonstrate that the work proposed is being accomplished, and will be used to provide updates to Ruby Together’s members. For example project reports, see the Ruby Toolbox section in <a href="/news">Ruby Together’s monthly updates</a>.</p>
</section>

<section class="group">
<h3 id="funding">Funding</h3>

<p>Accepted proposals will include a total funding amount between $3,000 and $30,000 USD, set by the project committee. The total amount will be paid in three payments, once per month. Each monthly payment will be made after both progress reports for that month have been submitted, and the work has been verified by the Ruby Together team.</p>

<p>We are able to send payments via international wire and PayPal. We may be able to accommodate other payment methods, although we can’t guarantee it will be possible.</p>
</section>

<section class="group">
<h3 id="schedule">Schedule</h3>

<p>Ruby Together reviews proposals and funds projects once every three months. Our yearly funding cycles run from December to February, March to May, June to August, and September to November.</p>

<p>For example, here is the expected schedule for a February to April funding cycle:</p>

<ul>
<li>Nov 1 through Jan 1: proposals for Feb-Apr are open</li>
<li>Jan 1: Feb-Apr proposals close, May-Jul proposals open</li>
<li>Jan 15: proposals decisions are sent via email</li>
<li>Feb 1: project work begins</li>
<li>Feb 15: first project reports are submitted</li>
<li>Mar 1: second project reports are submitted, first payment is sent</li>
<li>Mar 15: third project reports submitted</li>
<li>Apr 1: fourth project reports, second payment</li>
<li>Apr 15: fifth project reports</li>
<li>May 1: projects submit final report, final payment sent</li>
</ul>
</section>

<section class="group">
<h3 id="apply-now">Apply now!</h3>

<p>{{ cms:helper link_to "Submit your application for project funding today", proposal_url }}.</p>

<p>Feel free to refer to the {{ cms:helper link_to "example application", example_proposal_path }} as your fill out your application.</p>
</section>

<section class="group">
<h3 id="support-us">Support us</h3>

<p>Help us fund Ruby open source projects by signing up for a developer membership or encouraging your company to join as a member.</p>

{{ cms:partial "home/join" }}
</section>
<p class="callout">Nominate your project for funding.</p><section class="group">
<p>Ruby Together funds open source projects on a quarterly basis. We accept project proposals at any time, and once every three months the Ruby Together project committee decides which projects we will fund for the next three months.</p>
</section><section class="group">
<h3 id="requirements">Requirements</h3>

<p>To be eligible for funding, your project needs to meet a few requirements:</p>

<ul>
<li>Your project must be open source</li>
<li>Your project must benefit the Ruby community</li>
<li>Your project must have an enforced code of conduct</li>
<li>If you are not a project maintainer, your proposal needs to already be approved by existing maintainers</li>
</ul>

</section><section class="group">
<h3 id="how-to-apply">How To Apply</h3>

<p>Open <a href="https://rubytogether.org/proposal">the project proposal form</a> and fill it out. We ask questions to be able to understand and evaluate the project and your work proposal. It shouldn’t take you more than a few minutes to fill out a proposal (and if it does, please tell us about it so we can fix it!)</p>
</section><section class="group">
<h3 id="work-expectations">Work Expectations</h3>

<p>Project proposals will be evaluated on outcomes, not on hours worked. We do not expect you to work an exact number of hours, but we are looking for projects that resemble what you might do in three months at a full-time job. When applying, the most important thing is to know how much time you will actually be able to spend, and what meaningful results you can achieve in that time.</p>

<p>Ruby Together project funding is intended to support work that needs large blocks of concentrated time, or needs a large amount of time, to get done. We are happy to fund both boring work like triage and bugfixes as well as exciting work like creating new tools that have never existed before.</p>
</section><section class="group">
<h3 id="selection-process">Selection process</h3>

<p>The Ruby Together project selection committee will evaluate proposals based on several criteria:</p>

<ul>
<li>Community impact (how much will this proposal benefit the Ruby community as a whole?)</li>
<li>Project usage (larger, more popular projects are more likely to help more of the community)</li>
<li>Project plan (a more detailed and specific plan of changes or features is more likely to help the community than “bugfixes and improvements”)</li>
<li>Member feedback (which proposals are most helpful to Ruby Together’s existing members?)</li>
<li>Track record (what is the history of the project? what about the history of the person applying?)</li>
</ul>

<p>Today, the project committee includes the <a href="/team">board of directors</a>. Funded projects will be announced in the Ruby Together monthly update each cycle.</p>
</section><section class="group">
<h3 id="project-reports">Project reports</h3>

<p>Each accepted project will be expected to submit a project report twice per month. Project reports should demonstrate that the work proposed is being accomplished, and will be used to provide updates to Ruby Together’s members. For example project reports, see the Ruby Toolbox section in <a href="/news">Ruby Together’s monthly updates</a>.</p>
</section><section class="group">
<h3 id="funding">Funding</h3>

<p>Accepted proposals will include a total funding amount between $3,000 and $30,000 USD, set by the project committee. The total amount will be paid in three payments, once per month. Each monthly payment will be made after both progress reports for that month have been submitted, and the work has been verified by the Ruby Together team.</p>

<p>We are able to send payments via international wire and PayPal. We may be able to accommodate other payment methods, although we can’t guarantee it will be possible.</p>
</section><section class="group">
<h3 id="schedule">Schedule</h3>

<p>Ruby Together reviews proposals and funds projects once every three months. Our yearly funding cycles run from December to February, March to May, June to August, and September to November.</p>

<p>For example, here is the expected schedule for a February to April funding cycle:</p>

<ul>
<li>Nov 1 through Jan 1: proposals for Feb-Apr are open</li>
<li>Jan 1: Feb-Apr proposals close, May-Jul proposals open</li>
<li>Jan 15: proposals decisions are sent via email</li>
<li>Feb 1: project work begins</li>
<li>Feb 15: first project reports are submitted</li>
<li>Mar 1: second project reports are submitted, first payment is sent</li>
<li>Mar 15: third project reports submitted</li>
<li>Apr 1: fourth project reports, second payment</li>
<li>Apr 15: fifth project reports</li>
<li>May 1: projects submit final report, final payment sent</li>
</ul>
</section><section class="group">
<h3 id="apply-now">Apply now!</h3>

<p><a href="https://rubytogether.org/proposal">Submit your application for project funding today</a>.</p>

<p>Feel free to refer to the <a href="/example_proposal">example application</a> as your fill out your application.</p>
</section><section class="group">
<h3 id="support-us">Support us</h3>

<p>Help us fund Ruby open source projects by signing up for a developer membership or encouraging your company to join as a member.</p>

{{ cms:partial "home/join" }}
</section>
Loading

0 comments on commit 7585660

Please sign in to comment.