Re: Bug#378404: installation guide: one more additional proposal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Jul 20, 2006 at 02:54:14PM +0200, Frans Pop wrote:
> On Thursday 20 July 2006 11:37, Geert Stappers wrote:
> > On Tue, Jul 18, 2006 at 11:23:13PM +0200, Holger Wansing wrote:
> > > --- partman-crypto.xml 2006-07-09 21:21:07.000000000 +0200
> > > +++ partman-crypto.xml.workingcopy 2006-07-18
> > >
> > > -First, let's have a look at available options available when you
> > > +First, let's have a look at the options available when you
> >
> > That is applied.
>
> As was announced in [1], the manual us currently frozen for its next
> release. This means _no_ commits to the English original. Because of that
> I have reverted this commit (and had to do several other things to
> minimize the effect on the status of translations). I will apply the
> patch again _after_ the release.
>
> Geert, I know your intentions are good, but unfortunately this is not the
> first time commits by you to the SVN repository cause more work than that
> they help.
>
> Please do not do random things you pick up from the mailing lists just
> because you think "hey, I can do this" when there are normally other
> people who take care of them _before talking to those other people_.
>
> The next time something like this happens, I will be forced to revoke your
> commit access to the repository.
>
> Cheers,
> FJP
>
> [1] http://lists.debian.org/debian-boot/2006/07/msg00405.html
I understand only the short term message. [2]
What I don't get is the long term policy. I only have questions about it.
* How to tag a bugreport like #378404 with 'fix after string freeze'
* Why leave typos in the original text? Why should translators all see
(or ignore) the same typo?
* Why leave out additions like 'or <userinput>fb=true</userinput> for
short.' from the original text? Why not allow the improvement in the
translations.
* Why a very very strict string freeze? ( Proposal: allow the Release
Manager to modify strings during a freeze )
* Would a "state flag" help to indicate a status like a freeze?
So that when a 'update translations' message is skipped/missed/whatever
there is still the state flag. Perhaps also include that flag in /topic?
* How much "revert work" was/is needed after a "considered harmless"
"Hey, this patch shouldn't be ignored action"? Telling all the things
that need to be done for a cleanup, shows how much harm actually was
done.
* What about a "Hey, you created this mess, follow the procedure at URL
to clean it up" approach? Or "Your action harmed this list of people,
say sorry to them"?
Or another thing that has much learning in itself.
My appology for the harm I did.
Geert Stappers
[2] Nevertheless the good reason you had for your action,
the impact wasn't that good. "Because" there are no resources
to explain what went wrong, it is chosen to kick _you_ out,
it will prevent further harm from _you_.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFEwM82OSINbgwa/7sRAu/AAJ0SXw69Xfle0/T+/x/dqVa7AQdvNwCeJUQo
4HXDr8W6ttzKv/dq47wLIm4=
=F4Lo
-----END PGP SIGNATURE-----
Reply to: