diff --git a/db/cms_seeds/ruby-together/files/_ruby-api.jpg.yml b/db/cms_seeds/ruby-together/files/_ruby-api.jpg.yml new file mode 100644 index 00000000..0fa3b1a2 --- /dev/null +++ b/db/cms_seeds/ruby-together/files/_ruby-api.jpg.yml @@ -0,0 +1,4 @@ +--- +label: ruby-api.jpg +description: +categories: [] diff --git a/db/cms_seeds/ruby-together/files/ruby-api.jpg b/db/cms_seeds/ruby-together/files/ruby-api.jpg new file mode 100644 index 00000000..e88ceaf0 Binary files /dev/null and b/db/cms_seeds/ruby-together/files/ruby-api.jpg differ diff --git a/db/cms_seeds/ruby-together/layouts/default/content.html b/db/cms_seeds/ruby-together/layouts/default/content.html index 105e90a2..6324af08 100644 --- a/db/cms_seeds/ruby-together/layouts/default/content.html +++ b/db/cms_seeds/ruby-together/layouts/default/content.html @@ -1,8 +1,12 @@ [attributes] +--- label: Page Layout app_layout: application - +position: 0 [content] {{ cms:wysiwyg content }} {{ cms:textarea footer, render: false }} +[js] + +[css] diff --git a/db/cms_seeds/ruby-together/layouts/default/news/content.html b/db/cms_seeds/ruby-together/layouts/default/news/content.html index dfd2e716..1bb96c90 100644 --- a/db/cms_seeds/ruby-together/layouts/default/news/content.html +++ b/db/cms_seeds/ruby-together/layouts/default/news/content.html @@ -1,7 +1,11 @@ [attributes] +--- label: News Layout app_layout: news - +position: 0 [content] {{ cms:text summary, render: false }} {{ cms:markdown content }} +[js] + +[css] diff --git a/db/cms_seeds/ruby-together/pages/index/bylaws/content.html b/db/cms_seeds/ruby-together/pages/index/bylaws/content.html index 53627390..9e4f2c91 100644 --- a/db/cms_seeds/ruby-together/pages/index/bylaws/content.html +++ b/db/cms_seeds/ruby-together/pages/index/bylaws/content.html @@ -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]

A California Nonprofit Mutual Benefit Corporation Effective February 6, 2015

diff --git a/db/cms_seeds/ruby-together/pages/index/companies/content.html b/db/cms_seeds/ruby-together/pages/index/companies/content.html index c58b168f..f6fb2979 100644 --- a/db/cms_seeds/ruby-together/pages/index/companies/content.html +++ b/db/cms_seeds/ruby-together/pages/index/companies/content.html @@ -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]

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.

diff --git a/db/cms_seeds/ruby-together/pages/index/conflict_policy/content.html b/db/cms_seeds/ruby-together/pages/index/conflict_policy/content.html index 14bd40a5..223a47c3 100644 --- a/db/cms_seeds/ruby-together/pages/index/conflict_policy/content.html +++ b/db/cms_seeds/ruby-together/pages/index/conflict_policy/content.html @@ -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]

Effective February 6, 2015

diff --git a/db/cms_seeds/ruby-together/pages/index/content.html b/db/cms_seeds/ruby-together/pages/index/content.html index d7f743af..741e2359 100644 --- a/db/cms_seeds/ruby-together/pages/index/content.html +++ b/db/cms_seeds/ruby-together/pages/index/content.html @@ -1,5 +1,9 @@ [attributes] -label: "Ruby Together" +--- +label: Ruby Together layout: default - +target_page: +categories: [] +is_published: true +position: 0 [wysiwyg content] diff --git a/db/cms_seeds/ruby-together/pages/index/developers/content.html b/db/cms_seeds/ruby-together/pages/index/developers/content.html index eb1d5e00..184d7602 100644 --- a/db/cms_seeds/ruby-together/pages/index/developers/content.html +++ b/db/cms_seeds/ruby-together/pages/index/developers/content.html @@ -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] -
-

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.

- -

We depend on the community to make that dedicated work possible.

- -

When you support Ruby Together, you get:

- -
    - {{ cms:partial "home/member_benefit_items" }} -
- -

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

-
- -
-{{ cms:partial "home/memberships/developer_small" }} -{{ cms:partial "home/memberships/developer_medium" }} -{{ cms:partial "home/memberships/developer_large" }} -{{ cms:partial "home/memberships/one_time" }} -
- -{{ cms:partial "home/ruby_together_is" }} -{{ cms:partial "home/faq" }} +
+

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.

+ +

We depend on the community to make that dedicated work possible.

+ +

When you support Ruby Together, you get:

+ +
    + {{ cms:partial "home/member_benefit_items" }} +
+ +

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

+
+{{ cms:partial "home/memberships/developer_small" }} +{{ cms:partial "home/memberships/developer_medium" }} +{{ cms:partial "home/memberships/developer_large" }} +{{ cms:partial "home/memberships/one_time" }} +

{{ cms:partial "home/ruby_together_is" }}

{{ cms:partial "home/faq" }}

\ No newline at end of file diff --git a/db/cms_seeds/ruby-together/pages/index/example_proposal/content.html b/db/cms_seeds/ruby-together/pages/index/example_proposal/content.html index e18baea3..bcde241d 100644 --- a/db/cms_seeds/ruby-together/pages/index/example_proposal/content.html +++ b/db/cms_seeds/ruby-together/pages/index/example_proposal/content.html @@ -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] +
[wysiwyg content]

What project are you applying for?

@@ -57,5 +64,3 @@

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

-[html footer] -
diff --git a/db/cms_seeds/ruby-together/pages/index/projects/content.html b/db/cms_seeds/ruby-together/pages/index/projects/content.html index 80aa1dd8..9078546c 100644 --- a/db/cms_seeds/ruby-together/pages/index/projects/content.html +++ b/db/cms_seeds/ruby-together/pages/index/projects/content.html @@ -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] -

Nominate your project for funding.

- -
-

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.

-
- -
-

Requirements

- -

To be eligible for funding, your project needs to meet a few requirements:

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

How To Apply

- -

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!)

-
- -
-

Work Expectations

- -

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.

- -

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.

-
- -
-

Selection process

- -

The Ruby Together project selection committee will evaluate proposals based on several criteria:

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

Today, the project committee includes the board of directors. Funded projects will be announced in the Ruby Together monthly update each cycle.

-
- -
-

Project reports

- -

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 Ruby Together’s monthly updates.

-
- -
-

Funding

- -

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.

- -

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.

-
- -
-

Schedule

- -

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.

- -

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

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

Apply now!

- -

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

- -

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

-
- -
-

Support us

- -

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

- - {{ cms:partial "home/join" }} -
+

Nominate your project for funding.

+

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.

+
+

Requirements

+ +

To be eligible for funding, your project needs to meet a few requirements:

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

How To Apply

+ +

Open the project proposal form 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!)

+
+

Work Expectations

+ +

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.

+ +

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.

+
+

Selection process

+ +

The Ruby Together project selection committee will evaluate proposals based on several criteria:

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

Today, the project committee includes the board of directors. Funded projects will be announced in the Ruby Together monthly update each cycle.

+
+

Project reports

+ +

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 Ruby Together’s monthly updates.

+
+

Funding

+ +

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.

+ +

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.

+
+

Schedule

+ +

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.

+ +

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

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

Apply now!

+ +

Submit your application for project funding today.

+ +

Feel free to refer to the example application as your fill out your application.

+
+

Support us

+ +

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

+ + {{ cms:partial "home/join" }} +
\ No newline at end of file diff --git a/db/cms_seeds/ruby-together/pages/index/roadmap/content.html b/db/cms_seeds/ruby-together/pages/index/roadmap/content.html index bcd5f8fe..b3dd6bb5 100644 --- a/db/cms_seeds/ruby-together/pages/index/roadmap/content.html +++ b/db/cms_seeds/ruby-together/pages/index/roadmap/content.html @@ -1,37 +1,35 @@ [attributes] -label: "The RubyGems Partnership" +--- +label: Our Roadmap +layout: default +target_page: +categories: [] +is_published: true +position: 2 +[text_area footer] [wysiwyg content] -

Take a look at where we're headed.

- -
-

Focus Areas

- -

Today, Ruby Together is committed to improving the three most widely-used core Ruby tools:

- -
    -
  • Bundler, the Ruby dependency manager, used by every Ruby project to manage and install gems
    • -
  • RubyGems, the code that makes it possible to create gems in the first place
    • -
  • RubyGems.org, the website that provides free hosting for public gems
    • -
-
- - -
-

Upcoming Projects

- -

As time and funding permits, the Ruby Together team will:

- -
    -
  • Roll out a new gem index that will make installing gems two to ten times faster than today
    • -
  • Migrate all of RubyGems.org to the Fastly CDN, providing dramatic speed improvements when downloading gems and gem data
    • -
  • Build a gem caching server to easily allow data centers and offices to cache local copies of the gems they need, whether public or private
    • -
  • Improve RubyGems.org, adding search, statistics, and more gem information to every page
    • -
- -

And there will be more! We start new projects based on community need and Ruby Together's available funding.

-
- -{{ cms:partial "home/funding_levels" }} - -{{ cms:partial "home/join" }} +

Take a look at where we're headed.

+

Focus Areas

+ +

Today, Ruby Together is committed to improving the three most widely-used core Ruby tools:

+ +
    +
  • Bundler, the Ruby dependency manager, used by every Ruby project to manage and install gems
    • +
  • RubyGems, the code that makes it possible to create gems in the first place
    • +
  • RubyGems.org, the website that provides free hosting for public gems
    • +
+
+

Upcoming Projects

+ +

As time and funding permits, the Ruby Together team will:

+ +
    +
  • Roll out a new gem index that will make installing gems two to ten times faster than today
    • +
  • Migrate all of RubyGems.org to the Fastly CDN, providing dramatic speed improvements when downloading gems and gem data
    • +
  • Build a gem caching server to easily allow data centers and offices to cache local copies of the gems they need, whether public or private
    • +
  • Improve RubyGems.org, adding search, statistics, and more gem information to every page
    • +
+ +

And there will be more! We start new projects based on community need and Ruby Together's available funding.

+

{{ cms:partial "home/funding_levels" }}

{{ cms:partial "home/join" }}

\ No newline at end of file diff --git a/db/cms_seeds/ruby-together/pages/index/rubygems/content.html b/db/cms_seeds/ruby-together/pages/index/rubygems/content.html index c0b1b305..1257259b 100644 --- a/db/cms_seeds/ruby-together/pages/index/rubygems/content.html +++ b/db/cms_seeds/ruby-together/pages/index/rubygems/content.html @@ -1,6 +1,11 @@ [attributes] -label: "The RubyGems Partnership" - +--- +label: The RubyGems Partnership +layout: default +target_page: +categories: [] +is_published: true +position: 4 [wysiwyg content]

The Rubygems Partnership is a cooperative effort between Ruby Central and Ruby Together to ensure that RubyGems.org is funded, stable, maintained, and supported.

diff --git a/db/cms_seeds/ruby-together/pages/index/team/content.html b/db/cms_seeds/ruby-together/pages/index/team/content.html index a485841d..e85bceda 100644 --- a/db/cms_seeds/ruby-together/pages/index/team/content.html +++ b/db/cms_seeds/ruby-together/pages/index/team/content.html @@ -1,78 +1,77 @@ [attributes] -label: "The RubyGems Partnership" +--- +label: Our Team +layout: default +target_page: +categories: [] +is_published: true +position: 5 +[text_area footer] [wysiwyg content] -
-

Ruby Together funds up to 8 hours per month of ongoing work by a development team consisting of:

- - - -

Developer team alumni include:

- - -
- -
-

The Ruby Together board of directors is made up entirely of volunteers. The board currently includes:

- - - -

Board alumni include:

- -
- -
-

Ruby Together relies on its own team to enable and evangelize our non-profit work. That team includes:

- - - -

Team alumni include:

- - -
+
+

Ruby Together funds up to 8 hours per month of ongoing work by a development team consisting of:

+ + + +

Developer team alumni include:

+ + +
+

The Ruby Together board of directors is made up entirely of volunteers. The board currently includes:

+ + + +

Board alumni include:

+ +
+

Ruby Together relies on its own team to enable and evangelize our non-profit work. That team includes:

+ + + +

Team alumni include:

+ + +
\ No newline at end of file