--ftEhullJWpWg/VHq
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 12, 2011 at 08:37:00PM +0900, Luis Lavena wrote:
> On Wed, Jan 12, 2011 at 5:17 AM, Hiroshi Nakamura <nakahiro / gmail.com> wr=
ote:
> > Hi, committers,
> >
> > Please don't think it's a fork. =A0I'm going to keep ext/openssl at
> > Ruby's repository up-to-date and stable like rubygems and rdoc. =A0We'll
> > keep master branch of the new repository in sync with ext/openssl at
> > Ruby's repo. =A0Any CRuby committer should have an commit bit of the new
> > repo.
> >
> > And eventually I want Martin to be a maintainer of ext/openssl.
> >
> > Where's the best repository location for this purpose do you think?
> > github.com/ruby/ruby-openssl if we can use?
>=20
> I think the repository under ruby organization will be the best option.
>=20
> > github.com/emboss/ruby-openssl? (Martin's one, already exist)
>=20
> Once ruby/ruby-openssl is created (as fork from emboss), you can ask
> GitHub to mark ruby one as root of the tree.
>=20
> A shameless plug, but since you guys are going to build it as a gem to
> keep improving the project and sync back to Ruby, can you guys use
> rake-compiler?
>=20
> http://github.com/luislavena/rake-compiler
>=20
> Using rake-compiler, specially it's cross compiling abilities will
> highly reduce the amount of work I would have to do to ensure the
> project installs and works on Windows.

I don't think Martin has pushed the Rakefile yet, but it is using
rake-compiler.

--=20
Aaron Patterson
http://tenderlovemaking.com/

--ftEhullJWpWg/VHq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iQEcBAEBAgAGBQJNLeN8AAoJEJUxcLy0/6/G8gsIAJeG7AK/mPHfcsh0Evt7mvzO
ElBJ+e/kyD3za2rNDYYwEp9KvsnjfVLV/jK53TrZIYVCAYyW1qJz3eEdk2PN3H1z
CVa7kIvlJLiFsgZW0bSjqejTPXZIEz6jiv3HxPfATw0guTO5pDrVw7PqU0YeYK/H
Od9S6fVpNSFCeZgDOePEWAq6nmWpXQL0r+aTu/d7jHCIRDPoAw5TtXbsY2LuBt6u
AavLpvmXnDl6tYbdp5x2pvM1Sxv9xpe8NY73GyCNUj5JAv/ecxvaM1vmGVAcHZpe
8CQU2S80jeMevM94ptVbP+8NZrQJXDF1cFSu6jzfQES+0+7/zMTE4roQWisZ+Sk=
=p2YW
-----END PGP SIGNATURE-----

--ftEhullJWpWg/VHq--

On Wed, Jan 12, 2011 at 08:37:00PM +0900, Luis Lavena wrote:
> On Wed, Jan 12, 2011 at 5:17 AM, Hiroshi Nakamura <nakahiro / gmail.com> wr=
ote:
> > Hi, committers,
> >
> > Please don't think it's a fork. =A0I'm going to keep ext/openssl at
> > Ruby's repository up-to-date and stable like rubygems and rdoc. =A0We'll
> > keep master branch of the new repository in sync with ext/openssl at
> > Ruby's repo. =A0Any CRuby committer should have an commit bit of the new
> > repo.
> >
> > And eventually I want Martin to be a maintainer of ext/openssl.
> >
> > Where's the best repository location for this purpose do you think?
> > github.com/ruby/ruby-openssl if we can use?
>=20
> I think the repository under ruby organization will be the best option.
>=20
> > github.com/emboss/ruby-openssl? (Martin's one, already exist)
>=20
> Once ruby/ruby-openssl is created (as fork from emboss), you can ask
> GitHub to mark ruby one as root of the tree.
>=20
> A shameless plug, but since you guys are going to build it as a gem to
> keep improving the project and sync back to Ruby, can you guys use
> rake-compiler?
>=20
> http://github.com/luislavena/rake-compiler
>=20
> Using rake-compiler, specially it's cross compiling abilities will
> highly reduce the amount of work I would have to do to ensure the
> project installs and works on Windows.

I don't think Martin has pushed the Rakefile yet, but it is using
rake-compiler.

--=20
Aaron Patterson
http://tenderlovemaking.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iQEcBAEBAgAGBQJNLeN8AAoJEJUxcLy0/6/G8gsIAJeG7AK/mPHfcsh0Evt7mvzO
ElBJ+e/kyD3za2rNDYYwEp9KvsnjfVLV/jK53TrZIYVCAYyW1qJz3eEdk2PN3H1z
CVa7kIvlJLiFsgZW0bSjqejTPXZIEz6jiv3HxPfATw0guTO5pDrVw7PqU0YeYK/H
Od9S6fVpNSFCeZgDOePEWAq6nmWpXQL0r+aTu/d7jHCIRDPoAw5TtXbsY2LuBt6u
AavLpvmXnDl6tYbdp5x2pvM1Sxv9xpe8NY73GyCNUj5JAv/ecxvaM1vmGVAcHZpe
8CQU2S80jeMevM94ptVbP+8NZrQJXDF1cFSu6jzfQES+0+7/zMTE4roQWisZ+Sk=
=p2YW
-----END PGP SIGNATURE-----