Naming any SBF's you create
I removed the "MC1_A855_1283756080_BL-Logo-Only-storm.zip" attachment from jlutz555's post and wanted to explain why briefly. You'll notice that any SBF's I release have a fairly structured file name that's pretty long. I keep a registry of the files that I have released and all those parts of the name mean things. Among other things, the "MC1" at the beginning implies that I made it, the A855 says it is for a Motorola Droid 1, the 1283756080 is an encoding of part of the internals of the SBF, and the rest is descriptive of the contents.
While I have only limited ability to enforce this, if you start with one of my SBF's and modify it, please do not name the result MC1something. Also, leaving the 1283756080 part in there is going to be somewhat confusing because it's not going to match the internals of your file. Bad information is worse than no information. I take such structured approach because my SBF's tend to have a fairly wide distribution (almost 4000 people have downloaded the "recovery only" SPRecovery SBF) so I need a way to keep track of what's what.
Thanks for accommodating my preferences about this.
P.S. Obviously I'm not implying that jlutz555 did something to intentionally mislead anybody, or did anything wrong, etc. I've never explained my file naming standard before, so he did a sensible thing -- he changed the end of the filename to reflect the changes he had made and left the rest alone. Now that I've explained what the rest means, hopefully my position makes sense.