[Libre-soc-bugs] [Bug 1126] How to document new bugs/issues

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Sun Nov 5 17:14:09 GMT 2023


--- Comment #30 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
(In reply to Luke Kenneth Casson Leighton from comment #29)
> so, Andrey: can you now remember, just over three months later,
> what the contents of that verbal conversation was? can you recall
> what i said? because i can't!
> and did you have the conversation on IRC as i instructed? and
> can you find the link easily without a lot of hassle and
> searching through pages and pages of other IRC conversations?
> which should hammer home precisely and exactly why i set the
> project management rule that requires that the conversation
> take place immediately *and be linked to the bug*.

I'm going to add the process procedure which I showed you last week, and see
what else is outstanding on this bug. I apologise for not tracking it sooner.

However I will *start doing this later in the week* (there's enough to do

> Andrey: this is now your responsibility to ensure that everyone follows
> these procedures, and the amount of hassle involved in the *retrospective*
> sourcing of the information discussed three months ago should neatly hammer
> home why it is necessary to follow these procedures immediately, at the
> time that the conversations take place.

Yes, I know that.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-soc-bugs mailing list