A proposal for code removal prior to FreeBSD 13
Stefan Esser
se at freebsd.org
Tue Dec 18 18:33:22 UTC 2018
Am 18.12.18 um 17:00 schrieb Warner Losh:
> Being too old isn't the only reason. That's one of the many reasons
> articulated. The age of the code, the lack of innovation, the severe
> technical deficiencies, the sparse use, the lack of maintainer, the opinion
> of the domain experts in this field (Ian, myself, George and Poul-Hennig)
> which say this is poo, the nature of the commits in the last decade
> suggesting it's more of a drag on the tree than a help, etc. All strongly
> suggest it's time to go. Don't get hung up on any one of these being
> insufficient on its own: taken all together it's clear timed costs more
> than the benefit it brings to the project.
>
>> 1) It is only used by a small group of people (we should
>> define what the size of that group is that makes things
>> deprecatable.) The non existant data we have that leads
>> us to think it is ok to remove timed may be wrong, and
>> the 17.4 commiters procedure is designed to help catch
>> that.
>>
> 2) It has a reasonable replacement in ntpd
>> 3) It has a small, but perhaps measurable maintance cost.
>> (Though this well now be born by who ever if anyone
>> bothers to maintain your git version)
>>
>
> It will be. My github branch is complete now. All that it needs is someone
> to create a port and I'll move it over to the project repo space. I'm
> doubtful anybody will step up, but I've done the hard work of extraction.
I do not use timed, but I'd be willing to create a port and perform the
same steps as done for the removal of CTM from head.
Just give me some time (I'm quite busy before the holidays), but I should
have sufficient spare time within the next 2 weeks ...
Regards, STefan
More information about the freebsd-arch
mailing list