Re: Planet Debian revisions [and 1 more messages]
Hello, On Fri 04 Jan 2019 at 05:29pm GMT, Ulrike Uhlig wrote: >> Exactly. I understand Ulrike's practical concerns but do not consider >> them to outweigh the need to avoid permanency. Even writing "possible >> CoC violation" could hurt someone twenty years down the line. > > Ack. I have no strong opinion on this detail and trust your judgement to > find a possibility that would satisfy concerns of transparency while > being respectful to privacy. I've added a note to the wiki page about this. -- Sean Whitton signature.asc Description: PGP signature
Re: Planet Debian revisions [and 1 more messages]
Hello, On Fri 04 Jan 2019 at 03:03pm GMT, Ian Jackson wrote: > Years later someone who did some bad things when they were much > younger might reasonably come to us and say "can you please redact > that unfortunate incident from your public web page - it's ancient > history now". We should be able to honour such a request without > using git-filter-branch. Exactly. I understand Ulrike's practical concerns but do not consider them to outweigh the need to avoid permanency. Even writing "possible CoC violation" could hurt someone twenty years down the line. > Surely we can find a way to make this information transparent in a way > that makes it easier to expire it ? Even a dedicated mailing list > would be better since it would let us expire the archives. Yes. The commit message could contain a link to the mailing list archives, which could be made to 404. -- Sean Whitton signature.asc Description: PGP signature
Re: Planet Debian revisions [and 1 more messages]
Ulrike Uhlig writes ("Re: Planet Debian revisions"):
> Please, no. A commit message ensures that everybody is aware of the
> removal reason, including planet admins. Resorting to email? I don't
> think emails are encoded in the feeds and we cannot reasonably expect
> people to search for them...
I agree that some kind of publication of the reason is a good thing.
However:
Sean Whitton writes ("Re: Planet Debian revisions"):
> I'm afraid I don't follow. I wanted to keep details out of commit
> messages because of the fact that commit messages are a permanent
> record. How does contacting the planet admin team solve this?
I very strongly agree with Sean that we should not immemorialise such
things in commit messages.
Years later someone who did some bad things when they were much
younger might reasonably come to us and say "can you please redact
that unfortunate incident from your public web page - it's ancient
history now". We should be able to honour such a request without
using git-filter-branch.
Surely we can find a way to make this information transparent in a way
that makes it easier to expire it ? Even a dedicated mailing list
would be better since it would let us expire the archives.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
