Misc #11783: Do you have any idea if you have a budgets?

• Status: Open
• Assignee: -

[ko1 (Koichi Sasada)]

Do you have any idea about Ruby interpreter implementation to do with budgets?

Background

Now, we are summarizing many contributions from many people, organizations and companies.

https://docs.google.com/document/d/1y1sQc40qeuWjF84rVrTmH-ogZ_iNGqU-RUSE8GDlRuk/edit?usp=sharing

(please let me know if you know any other contributes)
(sorry we wrote contributions especially for MRI, because we don't know)

The great recent news is we get new mac mini machine to run CI on El Capitan. We already have a mac mini machine running CI, but on Yosemite. So we can run CI on both Yosemite and El Capitan.

This new mac mini machine was sponsored by YassLab, Japanese small company.

At first, we ask Nihon-Ruby-no-Kai to prepare this machine, and Takahashi-san (chair man of this organization) tweet about it ("anyone can support it?"). Yasukawa-san, the president of YassLab answers "ok, we'll support it".

We learned that if we show requirements explicitly, anyone may help us.
Listing is important.

Any idea?

Today's developers meeting, we had discussed about that and itemize some dreams.

nurse: VPS severs for CI are welcome. Especially for Azure.
ko1: travel fee (1,000,000 JPY?) for hackathon to gather MRI developers in one place
ko1: physical machines for development and benchmarks (300,000 JPY)
nobu: development machine (400,000 JPY) because he has several trouble on current machine.
nurse: icc (and other softwares) to try.
martin: grant project for MRI development topics
ko1: education to grow other MRI developer (no estimation)

Do you have any other idea?
I'll show these list at RubyKaigi, and someone may consider to support us.

(IMO, maybe sponsoring nobu's machine is great contribution for Ruby worlds.
Nobu will put companies logo stickers on his laptop)

Thanks,
Koichi

[usa (Usaku NAKAMURA)]

Koichi Sasada wrote:

nurse: VPS severs for CI are welcome. Especially for Azure.

I should note that mswin CI will be given up just after Ruby 2.3 release because I can never keep its cost.

[duerst (Martin Dürst)]

Usaku NAKAMURA wrote:

I should note that mswin CI will be given up just after Ruby 2.3 release because I can never keep its cost.

Does this mean cost of infrastructure (which can be paid for) or cost of your work (which may be very difficult to pay)?

[usa (Usaku NAKAMURA)]

Martin Dürst wrote:

I should note that mswin CI will be given up just after Ruby 2.3 release because I can never keep its cost.

Does this mean cost of infrastructure (which can be paid for) or cost of your work (which may be very difficult to pay)?

The former. It costs about $130 per month.

[takahashim (Masayoshi Takahashi)]

Hi all,

I'm Takahashi, as mentioned in "Background" section of this ticket.

Koichi Sasada wrote:

nurse: VPS severs for CI are welcome. Especially for Azure.

I've talked with Yoshida-san at Microsoft Japan to use Azure for Ruby CI, using OSS developer supporting program of Microsoft.
I don't know the program in detail yet, so I'll ask and write it later. Please wait for a while.

[ko1 (Koichi Sasada)]

I made a page: https://bugs.ruby-lang.org/projects/ruby/wiki/Donation

[shevegen (Robert A. Heiler)]

Guido (the creator of python) linked in this at twitter recently, for python:

https://www.python.org/psf/donations/2019-q2-drive/

Perhaps something similar could be done for ruby, in particular right at
the starting homepage at:

https://www.ruby-lang.org/en/

Or like Haiku OS:

https://www.haiku-os.org/

I am not suggesting a 1:1 copy of the idea, but the primary reason for
the suggestion is to make it simpler/more convenient for people to
donate resources to ruby & ruby's development; and possibly indicators
(e. g. fundraising "goals", even though the word is strange, I think it
actually works, or appears to work for other projects to some extent).

I would not mind donating at all to ruby as a whole myself (and I don't
care how the donation is used, either), but I would ideally like it to
be very simple as a process, and possibly others would like it to be
simple(r) too.