Changes

2,881 views
Skip to first unread message

Paul Chiusano

unread,
Jan 7, 2015, 9:20:50 AM1/7/15
to sca...@googlegroups.com
Hi everyone,

Quick summary: I've just reinstated Tony as a GitHub owner, with no objections from Lars, and Lars will be handing back the "keys" to #scalaz ASAP. It looks exceedingly likely that Lars will be leaving the project sometime soon on his own accord to work on a fork of some sort. I'll let him speak for himself on that.

Background: Tony reached out to me a couple days ago to ask to be added back as a GitHub owner. I've had the GitHub permissions to do this for a while, but didn't want to just make unilateral changes. (Like was done at the start of this mess!) But since I also didn't think it was fair to forcibly keep Tony on the sidelines any longer (especially now that the discussion has imploded), I emailed Lars to give him a heads up that I'd like to make the change. He indicated he's okay with it happening.

I'm saddened by how this whole mess has all played out, and even after taking a long break from dealing with this stuff, I already feel burned out on it again just from the past few days. :\ I think I just don't have the stomach for it and would rather focus my energies on other things. I'm going to take a step back from any sort of leadership role here and let others step up.

Cheers,
Paul :)

TexasMynsted

unread,
Jan 7, 2015, 10:15:21 AM1/7/15
to sca...@googlegroups.com
Thank you.

Pascal Voitot Dev

unread,
Jan 7, 2015, 10:49:39 AM1/7/15
to scalaz
Thanks Paul for bearing this burden...
Sad end...

Pascal

On Wed, Jan 7, 2015 at 4:15 PM, TexasMynsted <growing...@gmail.com> wrote:
Thank you.

--
You received this message because you are subscribed to the Google Groups "scalaz" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalaz+un...@googlegroups.com.
To post to this group, send email to sca...@googlegroups.com.
Visit this group at http://groups.google.com/group/scalaz.
For more options, visit https://groups.google.com/d/optout.

Alois Cochard

unread,
Jan 7, 2015, 11:16:51 AM1/7/15
to sca...@googlegroups.com
Thanks for all your effort Paul, you did your best.

Byron Shelden

unread,
Jan 7, 2015, 1:56:02 PM1/7/15
to sca...@googlegroups.com
Thank you.

Lars Hupel

unread,
Jan 7, 2015, 3:56:26 PM1/7/15
to sca...@googlegroups.com
> Quick summary: I've just reinstated Tony as a GitHub owner, with no
> objections from Lars, and Lars will be handing back the "keys" to #scalaz
> ASAP. It looks exceedingly likely that Lars will be leaving the project
> sometime soon on his own accord to work on a fork of some sort. I'll let
> him speak for himself on that.

To clarify: I do have objections, but I was planning to resign from scalaz
anyway, so it doesn't matter to me anymore.

I have just left the organization on GitHub and have no intentions of
contributing anything to scalaz in the future. The IRC channel is probably
back in control by Tony already. I still have access rights on org.scalaz
on Sonatype and to the CI build on CloudBees, which I will not exercise.
If there's any process to delete these privileges, I'm happy to oblige.
The domain scalaz.org is owned by Jason. I will also leave this mailing
list for good.

As Paul indicated, typelevel will pursue a different route, and there will
be an official announcement shortly. To that extent, scalaz and
scalaz-stream have already left the typelevel project.

Lars Hupel

unread,
Jan 7, 2015, 4:07:02 PM1/7/15
to sca...@googlegroups.com
> I have just left the organization on GitHub and have no intentions of
> contributing anything to scalaz in the future. The IRC channel is probably
> back in control by Tony already. I still have access rights on org.scalaz
> on Sonatype and to the CI build on CloudBees, which I will not exercise.
> If there's any process to delete these privileges, I'm happy to oblige.
> The domain scalaz.org is owned by Jason. I will also leave this mailing
> list for good.

Forgot one thing: I'll have to disable the CI builds on CloudBees, because
they contain my Sonatype credentials in plain text. CloudBees is not
critical for scalaz, though; they only serve for publication of snapshot
artifacts.

If anybody wants to re-enable them, they need to add SONATYPE_USER and
SONATYPE_PASSWORD as job parameters.
Reply all
Reply to author
Forward
0 new messages