ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: ko1@atdot.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72478] [Ruby trunk - Misc #11783] Do you have any idea if you have a budgets?
Date: Fri, 25 Dec 2015 08:28:45 +0000	[thread overview]
Message-ID: <redmine.journal-55764.20151225082844.51485bc24a7ad26e@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11783.20151207102955@ruby-lang.org

Issue #11783 has been updated by Koichi Sasada.


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


----------------------------------------
Misc #11783: Do you have any idea if you have a budgets?
https://bugs.ruby-lang.org/issues/11783#change-55764

* Author: Koichi Sasada
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
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




-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2015-12-25  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11783.20151207102955@ruby-lang.org>
2015-12-07 10:29 ` [ruby-core:71899] [Ruby trunk - Misc #11783] [Open] Do you have any idea if you have a budgets? ko1
2015-12-07 11:47 ` [ruby-core:71903] [Ruby trunk - Misc #11783] " usa
2015-12-08  6:15 ` [ruby-core:71939] " duerst
2015-12-08 11:25 ` [ruby-core:71944] " usa
2015-12-15 13:40 ` [ruby-core:72146] " takahashimm
2015-12-25  8:28 ` ko1 [this message]
2019-05-16 21:06 ` [ruby-core:92688] [Ruby trunk Misc#11783] " shevegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-55764.20151225082844.51485bc24a7ad26e@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).