<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/MwithM/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/MwithM">@MwithM</a> wrote:</p>
<blockquote>
<p>Should Compensation Maintainer wait a few days before cleaning the board? Otherwise, the "closed" column is pretty irrelevant.<br>
I would prefer to wait something like 5 days before cleaning the "closed" column.</p>
</blockquote>
<p>Echoing what I wrote above in <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="566142343" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/projects/issues/7" data-hovercard-type="issue" data-hovercard-url="/bisq-network/projects/issues/7/hovercard?comment_id=584741216&comment_type=issue_comment" href="https://github.com/bisq-network/projects/issues/7#issuecomment-584741216">#7 (comment)</a>, I believe the compensation maintainer should close issues with the appropriate <code>was:accepted</code> / <code>was:rejected</code> label and a corresponding comment as soon as possible after the vote reveal. This simply reflects the real state of the compensation request. At that point, the issues will automatically transition to the <code>Done</code> column, where they can stay in place for 5 days if you like, or perhaps until the next cycle's issue submission deadline, at which point the contents of the <code>Done</code> column can be <em>Archived</em> (this is a feature of GitHub project boards, not sure whether you're aware of it). This is what I meant by leaving the board "clean" for the next cycle. Again, the main point here is that comments and discussion can still occur on closed issues, there's nothing stopping that, but it's better to reflect that they were accepted or rejected as soon as we know the results.</p>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> If that works for you, please update the documentation accordingly and mention that you've done so here. Thanks.</li>
</ul>
<blockquote>
<p>I thought that it might be nice to announce deadlines for submitting reviews and submitting DAO proposals at Compensation Board, with a note at the "In review" and "Proposal submitted" columns, and that BSQ rates for the current cycle announcement will be a pinned issue at Compensation repository.</p>
</blockquote>
<p>I think that's a nice use of the "Card" feature of GitHub project boards, good idea. I do think we also need to announce the compensation request issue deadline and BSQ exchange rate <em>outside</em> the board as well, though. I see that you've mentioned this on the wiki with the following line from <a href="https://bisq.wiki/Compensation#Compensation_Maintainer" rel="nofollow">https://bisq.wiki/Compensation#Compensation_Maintainer</a>:</p>
<blockquote>
<p>The exact date and reminders will be announced at <a class="team-mention js-team-mention" data-error-text="Failed to load team members" data-id="3611645" data-permission-text="Team members are private" data-url="/orgs/bisq-network/teams/dao/members" data-hovercard-type="team" data-hovercard-url="/orgs/bisq-network/teams/dao/hovercard" href="https://github.com/orgs/bisq-network/teams/dao">@bisq-network/dao</a> team and the Compensation board</p>
</blockquote>
<p>... but I just want to double-check it here.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/projects/issues/7?email_source=notifications&email_token=AJFFTNQMDHZOOL4U4S5VO53RDVACDA5CNFSM4KWNAD7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIDXKI#issuecomment-588266409">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNVJ4KHQDLLWCN3JI63RDVACDANCNFSM4KWNAD7A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQ73ULW7XUHM3VSQYLRDVACDA5CNFSM4KWNAD7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIDXKI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/projects/issues/7?email_source=notifications\u0026email_token=AJFFTNQMDHZOOL4U4S5VO53RDVACDA5CNFSM4KWNAD7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIDXKI#issuecomment-588266409",
"url": "https://github.com/bisq-network/projects/issues/7?email_source=notifications\u0026email_token=AJFFTNQMDHZOOL4U4S5VO53RDVACDA5CNFSM4KWNAD7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIDXKI#issuecomment-588266409",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>