why I'm not on #debian-tech

So, I guess this is an example of the sort of self-recusement from #debian-tech that aj is referring to:

@1130344829 <joeyh!joey@kitenet.net> aj: sigh, did you realy have to break d-i yet again right as we're trying ot release it?
@1130344847 <aj!aj-irc@azure.humbug.org.au> ?
@1130344881 <aj!aj-irc@azure.humbug.org.au> joeyh: (also, please try to avoid making things overly personal on this channel, cf the charter)
@1130344919 <joeyh!joey@kitenet.net> fine, did one have to ignore the d-i release and make a package upload with lots of changes that broke d-i internalls. Yes one did
@1130344928 <joeyh!joey@kitenet.net> for at least two values of one
@1130344967 <aj!aj-irc@azure.humbug.org.au> joeyh: please explain what you're talking about, in technical terms
@1130344989 <aj!aj-irc@azure.humbug.org.au> joeyh: if you do so, it might get fixed
@1130345337 <aj!aj-irc@azure.humbug.org.au> joeyh: hello?
@1130345448 <h01ger!~holger@bone.digitalis.org> joeyh, i guess you're referring to the debootstrap-upload of aj ?! /me wonders why an upload to unstable breaks the d-i beta, isnt that build+based on etch ?
@1130345451 <joeyh!joey@kitenet.net> sorry, busy fixing the beakage
@1130345474 <Sledge!steve@217.147.81.17> looks like a debootstrap change is causing problems in CD builds
@1130345481 <joeyh!joey@kitenet.net> well, there has not been a usable combination of apt, debootstrap, and d-i in testing for well over a week
@1130345634 <aj!aj-irc@azure.humbug.org.au> so you're saying i didn't break it just as you're trying to release?
@1130345720 <joeyh!joey@kitenet.net> no you broke it just as the fixed NMU was ready to go into testing
@1130345758 <h01ger!~holger@bone.digitalis.org> .oO( ah )
@1130345783 <aj!aj-irc@azure.humbug.org.au> sigh
@1130345792 <neuro!~rmurray@h24-80-164-222.sbm.shawcable.net> ...and we're still waiting for the technical details
@1130345813 <aj!aj-irc@azure.humbug.org.au> joeyh: second warning. this channel's for technical discussions, eg "here's what broke: ...", not accusations, eg "you broke it" "why'd you have to break it" "yes one did".
@1130345869 <aj!aj-irc@azure.humbug.org.au> joeyh: if you want, there's still time to put 0.3.1.9 into testing
* Logging finished Wed, 26 Oct 2005 12:58:19 -0400

It's worth noting that the d-i release in question was etch beta 1, which eventually released 2 weeks after the above conversation.

Probably my fault for not being a big believer in ridigly defined topics for communications channels. After all, I still filter all of my 20-some Debian mailing lists into a single folder; I'll happily talk about anything on the one irc channel (typically #debian-boot) that I nowdadys limit myself to; and so #debian-tech seemed like the obvious place to bring up the issue since aj, sledge, and other relevant people were active on it at the time.

The technical details remain as irrelivant today as they were at the time, the relevant problem being that developers who are not involved in the installer development rarely consider how their actions can affect it.

When a policy gets int the way of solving a problem, it's time to leave, that's all.