Needed change in governance

Faré fahree at
Fri Sep 16 22:53:06 UTC 2016

That's all entirely my fault. I should have remembered this work
conflicted with a branch you had.

I got carried away. I lazily continued to act the way I always did
(i.e. push any supposed improvement to master), even though I'm not
maintainer anymore.

I'm backing out, and will not commit anything myself directly to
master anymore. I will only put merge requests on gitlab for code
review and merge by Robert (or whoever steps forward to replace him).

Robert: I can revert the offending commit, or merge in yours, etc., at
your leisure.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
I have not yet begun to procrastinate

On Fri, Sep 16, 2016 at 6:38 PM, Stelian Ionescu <sionescu at> wrote:
> On Fri, 2016-09-16 at 12:23 -0500, Robert Goldman wrote:
>> I can no longer be the maintainer of ASDF unless I gain some control
>> over the contents of the repository.
>> Right now, I am just reacting to changes other people are making.
>> This
>> is ok if I am in the loop, but if other developers are simply wading
>> into the repository and committing changes that I have no idea are
>> coming, then I cannot do my job.
>> The last straw for me was last night's commits, which
>> completely blind-sided me and also invalidated work-in-progress I had
>> outstanding.
>> So, we need to either
>> 1. develop some informal means of clearing coming commits through me,
>> perhaps using this mailing list;
>> 2. lock out other developers and change the main repository only
>> through
>> merge requests (this is not my favored alternative, as it requires
>> more
>> busy work on my part); or
> I think this would be the best choice. ASDF is no longer in need of
> quick changes so delaying commits and pondering longer by way of a code
> review would be better.
> --
> Stelian Ionescu a.k.a. fe[nl]ix
> Quidquid latine dictum sit, altum videtur.

More information about the asdf-devel mailing list