This is is a similar story to the memory and basement packages but, I think, not mission critical.
There is a need to fork the hourglass package. It arises because Vincent Hanquez, its originator and sole Hackage maintainer, does not wish to develop it further or introduce other maintainers.
hourglass is a simple package and, given my forking experience elsewhere, I am willing to maintain a fork. However, I want to pick a name that is apt or, at least, the community does not dislike. I’ve consulted a thesaurus.
I was thinking sandtimer. (timepiece would have been my first choice, but TimePiece is taken).
3 Likes
Sounds good, but why not prefix it with “crypton” also?
My thinking was that there is an imaginary boundary that separates the " tls universe " (networks, protocols, cryptography) from the more fundamental ‘platform’ on which it is built (which includes memory and basement) - and that hourglass fell below that boundary.
2 Likes
I think this is fine. I was considering “crypton” as the signature for a fork of Vincent’s packages, LOL.
Question: why not fork and name Vincent’s libs as memory-2, hourglass-2, basement-2 (and so on, maybe a different suffix instead of 2, could be f for fork or n for new/next, mn for maintained, x for w3 4r3 l33t) so that if someone searches for memory they will get the maintained library on top of the deprecated one if they search via name or via tags in Hackage?
2 Likes