[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 07:33:53 GMT 2023


Luke Kenneth Casson Leighton <lkcl at lkcl.net> changed:

           What    |Removed                     |Added
                 CC|                            |sadoon at albader.co,
                   |                            |shriya.sharma at redsemiconduc
                   |                            |tor.com

--- Comment #29 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)

> can you both now have a conversation on IRC
> (placing links back here as you do so) recounting
> your recollection of what i said on the conf. call
> today?  it may take some time, it may take only minutes,
> but whatever happens you will see *and experience* the
> very issues that then need themselves to be documented.

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*.

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.

everyone: it is *also* your responsibility to follow these procedures
so that Andrey is not overwhelmed. it is extremely tedious to keep chasing
people, and i can tell you right now it is exhausting to keep doing for years.

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

More information about the libre-soc-bugs mailing list