Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blogpost validation #13

Closed
DavidBruant opened this issue Feb 23, 2017 · 2 comments
Closed

Blogpost validation #13

DavidBruant opened this issue Feb 23, 2017 · 2 comments

Comments

@DavidBruant
Copy link
Member

It's been a few days #10 is in queue with no review (we briefly talked about it with @ClementineHahn ).

What about a 2-phase review system ?

  1. does the blogpost threaten dtc (image, reputation, financially, values, etc.)? If no, publish
  2. send PRs as things go to change/fix the content
@thom4parisot
Copy link
Contributor

I skimmed though it and totally forgot to go back to it later, my bad.

If it's done in 2 phases as described above, it kind of defeats the purpose of the review – which is to add value to what is brought through the writing.

I feel more comfortable with the idea of publishing it together rather than having to fix stuff in the rush because the blog post has been sent off the fence.

That being said, the exact same situation happened when I assembled a few pieces about the website. Some nods were sent but after publication… But again, I don't think the 2-phases review system brings us into doing authoring together. It makes the publishing phase going faster for sure. But are we talking about speed or about collaboration?

@DavidBruant
Copy link
Member Author

was a bad idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants