public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Gentoo Core <gentoo-core@lists.gentoo.org>
Subject: Re: [gentoo-dev] OpenRC & baselayout-2 meets Gentoo
Date: Mon, 24 Mar 2008 16:47:36 -0400	[thread overview]
Message-ID: <47E81368.1020001@gentoo.org> (raw)
In-Reply-To: <47E810A4.8070805@gentoo.org>

Josh Saddler wrote:
> Doug Goldstein wrote:
>> It appears my migration plan was not good enough for Mike Frysinger 
>> <vapier@gentoo.org> and he went ahead and wrote his own version of 
>> the OpenRC ebuild, differing from the one in the OpenRC layman repo, 
>> and committed it to the tree this weekend.
>>
>> Since my offer to work on the migration was not good enough for him, 
>> I'm backing out and allowing him to handle the whole migration 
>> himself since I haven't heard from him at all despite Roy (author of 
>> OpenRC) and my attempts to contact him for 2 weeks regarding a 
>> migration plan for OpenRC. All issues and comments can be directed to 
>> him.
>>
>> I guess working together and documenting everything before having it 
>> hit the tree was a bad plan and it had to be one-upped.
>
> Well, *somebody* had better get their act together and talk with me 
> about the migration document. I don't care about the ebuild so much as 
> I do about making sure there's a howto for the migration process.
>
> If baselayout-2 & OpenRC are the future of Gentoo, then gosh darnit, 
> we need to work together. That means people "in the know" need to 
> communicate with me on the draft (that I've already sent to cardoe), 
> regardless of any who's-ebuild-are-we-using-epenis-fights. :)
>
I was trying to work together with the docs guys, the GMN peoples, the 
release engineering people, and our arch teams. However, Mike "The 
Decider" Frysinger does not want to work with everyone and has chosen to 
do his own thing. It just sucked the fun right out of the project for me 
and made it disinteresting in a heart beat.

I had the fun of trying his ebuild out on one of my machines this 
morning and it happily broke my stable amd64 install.

I would give you information if I was in possession of any.... Mike has 
still yet to reply to anyone's attempts to contact him.


-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-24 20:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  5:19 [gentoo-dev] OpenRC & baselayout-2 meets Gentoo Doug Goldstein
2008-03-20  6:59 ` Josh Saddler
2008-03-20 12:12   ` Roy Marples
2008-03-20 14:16     ` Doug Goldstein
2008-03-20 14:34       ` Daniel Pielmeier
2008-03-20 20:13 ` [gentoo-dev] Re: [gentoo-core] " Mike Frysinger
2008-03-24 20:26 ` [gentoo-dev] " Doug Goldstein
2008-03-24 20:35   ` Josh Saddler
2008-03-24 20:47     ` Doug Goldstein [this message]
2008-03-24 21:08   ` [gentoo-core] " Mike Frysinger
2008-03-24 21:16     ` Doug Goldstein
2008-03-24 21:32       ` Mike Frysinger
2008-03-24 21:36         ` Doug Goldstein
2008-03-24 21:42           ` Mike Frysinger
2008-03-24 21:53             ` Doug Goldstein
2008-03-24 22:03               ` Mike Frysinger
2008-03-24 23:49                 ` Doug Goldstein
2008-03-25 12:30                   ` Mike Frysinger
2008-03-25  8:33                 ` Roy Marples
2008-03-25 12:29                   ` Mike Frysinger
2008-03-27 14:57 ` Doug Goldstein

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-all from there: mbox

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

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

  git send-email \
    --in-reply-to=47E81368.1020001@gentoo.org \
    --to=cardoe@gentoo.org \
    --cc=gentoo-core@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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