Hello,
I personally think that database objects whose administrators/authors
demonstrably doesn't communicate have no right to exist.
It may be considered controversial. But objects should have functional
contact. If it doesn't work, it's fault of object author. But this
effectively declares that the fate of the created object doesn't
interest him.
We may break something for someone, but that's not RIPENCC's fault.
The basic idea behind an exception to existence should be that it is
justified.
If I summarize it, I fully support cleaning up the historical mess. And
I have no problem with exceptions. But the one who needs them has to
communicate with NCC's staff (at least).
- Daniel
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
