From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Status update of Sunrise project?
Date: Sun, 12 Apr 2015 18:13:22 +0800 [thread overview]
Message-ID: <1806927.R9hZiOYz1D@localhost> (raw)
In-Reply-To: <552A4318.9080407@gentoo.org>
On Sunday 12 April 2015 12:04:08 hasufell wrote:
> On 04/12/2015 12:02 PM, Patrick Lauer wrote:
> > On Sunday 12 April 2015 11:59:09 hasufell wrote:
> >> On 04/11/2015 01:54 PM, Rich Freeman wrote:
> >>> 1. What does proxy-maintainers lack in comparison to sunrise
> >>> exclusively. The immediate question is whether sunrise should be
> >>> migrated to proxy-maintainers, so this specific comparison is
> >>> important.
> >>
> >> proxy-maintainers lack:
> >> 1. a repository with a usable VCS
> >> 2. an actual review workflow... @proxy-maintainers are just some sort of
> >> backup committers. it's not a hub for contributors to gather, discuss,
> >> get reviews and improve skills
> >> 3. means to ensure the tree doesn't break
> >> 4. actively look for and educate potential developers, even before the
> >> recruitment process
> >
> > Oh my.
> >
> > Can you please stop being such a drama queen and accept reality every now
> > and then?
>
> I am unable to see how that contributes anything to the discussion.
> Could you please stay on the factual level?
So.
(1) is a completely subjective opinion
(2) is kinda ... like ... your opinion, if you were actually involved with
proxy-maint you'd know better
(3) uhm what? That is just absurd speculation without a factual base in our
common shared reality
(4) That's, like, your opinion, maaan.
If you actually spent time near proxy-maint, or in #gentoo-dev-help, or
basically anywhere where you'd interact with people, you'd not have these
absurd fantasies about stuff.
So I suggest you can try to do some proper fact finding first :)
... and then we could even try having a constructive discussion. That'd be,
like, AAAWESOOME.
>
> >> So it should, if at all, be the other way around: dissolve
> >> proxy-maintainers, fix the sunrise workflow and make it the contribution
> >> hub again it once was. But I'm not actually advocating for that. I think
> >> the sunrise concept doesn't work anymore.
> >
> > proxy-maint is the least broken process we have. Unless you have
> > constructive criticism I don't see why you waste time whining about
> > everything.
> You have obviously not read the whole email. I did offer an alternative
> solution. Please read the whole text.
Mhhh yes. No. Thanks for playing.
(Are you trying to get me drunk? Because that's how you get me drunk ...)
next prev parent reply other threads:[~2015-04-12 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 6:15 [gentoo-project] Status update of Sunrise project? Ben de Groot
2015-04-09 18:57 ` Thomas Sachau
2015-04-09 22:55 ` Ben de Groot
2015-04-10 16:14 ` Thomas Sachau
2015-04-11 5:38 ` Ben de Groot
2015-04-11 10:12 ` hasufell
2015-04-11 11:54 ` Rich Freeman
2015-04-12 9:59 ` hasufell
2015-04-12 10:02 ` Patrick Lauer
2015-04-12 10:04 ` hasufell
2015-04-12 10:13 ` Patrick Lauer [this message]
2015-04-12 10:21 ` hasufell
2015-04-12 10:34 ` Patrick Lauer
2015-04-12 11:22 ` Rich Freeman
2015-04-12 12:03 ` Michał Górny
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=1806927.R9hZiOYz1D@localhost \
--to=patrick@gentoo.org \
--cc=gentoo-project@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