10:13:43 <ErCiccione> .merge+ 1309
10:13:43 <xmr-pr> Added
10:21:20 <ErCiccione> binaryFate please update the website when you have a chance
10:33:38 <binaryFate> done
10:41:42 <ErCiccione> thanks
12:00:19 -xmr-pr- l33d4n opened pull request #1318: Add 'Veldt Gold' to the list of merchants
12:00:20 -xmr-pr- > https://github.com/monero-project/monero-site/pull/1318
13:01:42 <cohcho> .
13:05:07 <cohcho> CCS should have the following rule:
13:05:09 <cohcho> if an observer has found problem in implementation of CCS author then (0%, 100%] of milestone funds must be subtracted and paid to that observer.
13:05:36 <cohcho> Is it possible?
13:07:44 <cohcho> It will only harm stupid-lazy-slow-pokes that write bullshit code. In allother cases everything will go as usual.
13:10:32 <cohcho> And it will help to get non-zero compensation for their time to those who are good at writing code/fixing bugs but bad at self advertising.
13:18:44 <moneromooo> Oh, I'd misread as CSS :D
14:32:57 <cohcho> moneromooo: and the best place for CCS ?
14:34:18 <moneromooo> Here also or -dev I guess.
14:34:22 <cohcho> this room has all required people to make a decision regarding rules
14:34:33 <asymptotically> maybe the best place to bring it up is during a meeting in -community
14:34:48 <cohcho> -community is completely unrelated
14:35:00 <asymptotically> to the CCS?
14:35:31 <cohcho> to the rules of CCS ^
14:35:48 <asymptotically> well it's the channel where people talk about approving new funding requests, and people chat about their progress. so i wouldn't call it completely unrelated
14:36:33 <moneromooo> I've never done that. When I was there, -community was mostly banter and people whining about no PR.
14:36:43 <moneromooo> That's why I never came back :)
14:37:39 <asymptotically> you're also not in the main innovation hub, -pools :o
14:41:02 <cohcho> binaryFate: you're likely the best person in the Monero hierarchy for this question
14:42:27 <moneromooo> FWIW, I htink this should (1) discourage paid contributors and DoS the core team with spurious claims by opportunists (we have some of it on hackone).
14:45:32 <cohcho> (~strikethrough~ discourage) motivate to think before commiting milestone ^
14:46:11 <cohcho> no potential to DoS since peopel behand CCS will just proxy problem to CCS author and arbitrate communication between observer and CCS author
14:46:27 <cohcho> no potential DoS since peopel behind *
14:46:36 <cohcho> people*
14:47:32 <cohcho> and if peopel behind CCS really trust to CCS author then may just release all money before completed milestones
15:06:08 <cohcho> also unlike hackerone communication between observer and CCS peopel can be public (e.g. irc/github/gitlab)
15:06:40 <cohcho> since code of CCS idea will not be in release at that time
15:07:56 <cohcho> It's about new bugs/vulnerabilities but not about already present.