On Tue, Sep 13, 2022 at 6:36 PM Dima Pasechnik <dimp...@gmail.com> wrote:

>
>
>
>
>
>
> On Tue, 13 Sep 2022, 23:03 Matthias Koeppe, <matthiaskoe...@gmail.com>
> wrote:
>
>> On Tuesday, September 13, 2022 at 3:01:14 PM UTC-7 Thierry
>> (sage-googlesucks@xxx) wrote:
>>
>>> Also, several people have already explicitely requested for a break (if
>>> not a truce, given the level of agressivity).
>>
>>
>> Excuse me, Thierry, your accusations about others being aggressive &
>> likening anything here to war is highly inappropriate.
>>
>
> I repeat: we need no formal voting on this issue whatsoever - because trac
> is a long-standing liability, i.e. a bug that must be fixed, and we don't
> do voting on whether a bug is to be fixed, we go and fix it.
> No, no truce, no quarter to bugs, sorry.
>

I disagree on whether we need a vote, obviously.  I think it's very
important for the whole community to be involved in discussing and agreeing
to a change as major as switching from trac to git**b.  My hope (and
expectation) is that the benefits of the switch will be sufficiently
apparent that we'll get buy-in from a solid majority of developers.  And
the giving time for that discussion and making an effort to convince people
is likely to improve our eventual setup, to the benefit of Sage.

That being said, I don't think we should wait a month, as Thierry has
suggested.  I'm sympathetic to not having time to contribute to the switch
right now, which is why I've proposed a summary of pros and cons to be
included in the voting email.  Thierry, if you have more time in a couple
months, I'm sure that there will still be infrastructure improvements to be
made.

As far as *my* mental health is concerned, I swear I will not touch the
> Sage project infrastructure any more -- unless we proceed with retiring
> trac.
>

That sounds very fair to me.  We all appreciate everything you've done on
the project's infrastructure, on top of the very visible way you help
people with build and support questions.  And for my part, I'm going to
work with you to try to make sure we do retire trac soon.
David


>
>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/aaf7b1d7-747d-4318-974b-c8ea9e150d42n%40googlegroups.com
>> <https://groups.google.com/d/msgid/sage-devel/aaf7b1d7-747d-4318-974b-c8ea9e150d42n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq1-xuF1JYtWV09hceaeSG%3Djvqs%2B_f%3Dti%2BQ%3D-z09T-6qkQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/sage-devel/CAAWYfq1-xuF1JYtWV09hceaeSG%3Djvqs%2B_f%3Dti%2BQ%3D-z09T-6qkQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_kDgLwPyg1p034SbNrUseNzcJj3MHVNPKUO_5jrrVEGsQ%40mail.gmail.com.

Reply via email to