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

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1126

--- Comment #48 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
(In reply to Luke Kenneth Casson Leighton from comment #45)
> i also require that a procedure for notifying NLnet and myself be written and
> documented so that NLnet can immediately *FREEZE* the RFP system to prevent
> fraudulent RFPs in the event of someone publishing the plaintext
> passwords / URLs.
Added in bug #1233.

> 
> actually it would be good to have a "canary" button, which we can activate
> ourselves rather than have to wait for NLnet. can you raise that as a
> bugreport
> and link to this comment? i will then assign it to NLnet.
Bug #1232


(In reply to Luke Kenneth Casson Leighton from comment #46)
> (p.s. i think tnis bugreport has gone on long enough for the $, let's
> close it, RFP it, and continue on a new one. the process jacob
> came up with is to chnge TODO (comment #0) to "MOVED TO bug #Nnnn"
> and we can put that bug into one of the new grants)
Bug #1233 created.
Comment #0 updated.

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