Evaluate Job Publishing Permissions and Approval Chain

[glogiotatidis]

Currently we have the Django Permission System to control:

1. who's allowed to create new Content (i.e. new Snippets) and
2. who's allowed to publish Content (i.e. new Jobs)

We want to make this process better from a content approval perspective, by allowing the system to enforce content approval before it goes public.

While technically this is solvable, the main issue we face is to find a practical solution that fits the team's workflow and limitations on people and availability.

[glogiotatidis]

Suggested solution One:

• New Snippet is in Draft status
• When User is done with Editing requests another User to Approve
• Jobs can be created only for Approved Snippets
• If User makes changes to an already Approved Snippet, Snippets goes back to Draft status and another User needs to Approve. Meanwhile the previous approved content of the Snippet continues to be served.

Pros:

• Proper, enforced Content Approval Chain
• Less content errors and mistakes

Cons:

• Two Users (Approver with Publishing Permissions) must be involved to get new content out. Snippets Team is currently a team of two and thus the process won't work if one of two is AFK. This is a blocker.

[glogiotatidis]

We discussed Solution One and we can't overcome the blocker yet. We will reach out to other teams that publish content to learn more about their content approval procedures.

As far as the milestone goes, we will continue to discuss this the coming months and this will be included in future milestones for implementation.

[glogiotatidis]

/remind me to check in 3 weeks

[reminders]

@glogiotatidis set a reminder for Oct 23rd 2019

[reminders]

👋 @glogiotatidis, check