[#66126] Creation/Conversion methods/functions table for Ruby types — SASADA Koichi <ko1@...>
Hi,
5 messages
2014/11/07
[#66289] Re: Creation/Conversion methods/functions table for Ruby types
— Eric Wong <normalperson@...>
2014/11/14
SASADA Koichi <[email protected]> wrote:
[#66293] Re: Creation/Conversion methods/functions table for Ruby types
— SASADA Koichi <ko1@...>
2014/11/14
On 2014/11/15 7:44, Eric Wong wrote:
[#66248] [ruby-trunk - Feature #10423] [PATCH] opt_str_lit*: avoid literal string allocations — normalperson@...
Issue #10423 has been updated by Eric Wong.
3 messages
2014/11/13
[#66595] [ruby-trunk - Bug #10557] [Open] Block not given when the argument is a string — bartosz@...
Issue #10557 has been reported by Bartosz Kopinski.
3 messages
2014/11/30
[ruby-core:66485] [ruby-trunk - misc #10547] How to move the ruby project to git
From:
duerst@...
Date:
2014-11-26 11:28:26 UTC
List:
ruby-core #66485
Issue #10547 has been updated by Martin D=C3=BCrst. Shyouhei Urabe wrote: > The situation is that no one in ruby-core is actively willing to do any d= irty work to get things move to git. I think we are all OK when someone el= se did so. Hello Shyouhei, I think Sytse is offering to help with the dirty work, which is great. But = in my view, the main issue is that when people discussed moving to git, the= y implied moving to github, which is different from gitlab. But I may be wr= ong. ---------------------------------------- misc #10547: How to move the ruby project to git https://bugs.ruby-lang.org/issues/10547#change-50103 * Author: Sytse Sijbrandij * Status: Open * Priority: Normal * Assignee:=20 * Category:=20 * Target version:=20 ---------------------------------------- I'm posting this on the bugtracker as suggested by Koichi, feel free to mov= e or close this if I've posted in the wrong project. During rubyconf 2013 I briefly discussed the migration of ruby from svn to = git with the core team. During the Q&A of Rubyconf 2014 Matz again mentione= d that the community wants this and there are two problems that need to be = solved: 1. Incremental numbering 2. Running scripts I love ruby a lot and it is the reason I learned programming and became a d= eveloper. I now am CEO of GitLab B.V., we make open source software to coll= aborate on code. The two problems are things that we can solve in GitLab: 1. Make a project service that tags each commit on master incrementally. 2. Scripts are easy to run on your own GitLab server, see http://doc.gitlab= .com/ce/hooks/custom_hooks.html If the ruby core team is interested we can make 1. and set up a GitLab serv= er, convert the existing scripts and help maintain it for free. If the core team wants to move to GitHub or Bitbucket we are also willing t= o help with scripting and conversion. Best regards, Sytse Sijbrandij CEO GitLab B.V. --=20 https://bugs.ruby-lang.org/