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

/posts/2022-05-13-are-determinacy-race-bugs-lurking/ #83

Open
behoppe opened this issue Jul 14, 2022 · 1 comment
Open

/posts/2022-05-13-are-determinacy-race-bugs-lurking/ #83

behoppe opened this issue Jul 14, 2022 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@behoppe
Copy link
Member

behoppe commented Jul 14, 2022

Task
Update this draft post

Assignee roles

@behoppe behoppe added the documentation Improvements or additions to documentation label Jul 14, 2022
@behoppe behoppe added this to the Version 1.0 milestone Jul 14, 2022
@behoppe
Copy link
Member Author

behoppe commented Jul 19, 2022

Thanks @angelee for your questions, which I have copied below with my responses inline.

I was able to log into Netlify and see the page. Honestly the overall writing is pretty good already, so I am wondering what kind of edits are you envisioning?

The main thing is to have the post written in your voice for today's audience.

I can see how we would want to rewrite it if the target audience is different. The post is written more for the general public, but not written for academics. I feel that someone might complain that we make it sound like detecting races is easy. If I am writing for academics, I'd write it differently (be more nuanced in my explanation of different types of races / how they arise depending on the choice of programming models) but also (related), I would want to know what concepts have been introduced rigorously in other blog posts and perhaps linking to them, because otherwise the blog gets too long.

In terms of other posts, the main two I recommend keeping in mind are #82 "what the $#@! is parallelism" by @cleiserson and #92 "introduction to Cilk programming" by me. Charles' post is mostly written, so you can see how he'll introduce basic terms you also use. My article is a tutorial, and I plan to base it on exactly the same fib example that's in your draft post. I plan to follow a streamlined version of the parallelism chapter in Intro to Algorithms -- maybe getting as far as introducing the idea of a trace?

So @angelee let's make sure your blog post and my tutorial complement each other. (E.g., maybe we want all the C code in my tutorial, and your blog post can have highlights of code as needed.)

In terms of audience, maybe try gently pitching it more towards the academics? Either way is fine, but I'm thinking about our "academic first" strategy -- initially to establish OpenCilk with professors and students, before we focus on professional app developers etc.

Is it that one can choose to edit via either Netlify or just pull the source from GitHub and then push? It's a bit ambiguous based on the instructions in the contribution.md page you pointed to.

If you're comfortable with Netlify CMS, please use that for now, to help with our editorial workflow (draft/in-review/ready). If you have troubles with Netlify CMS please let me know. (We are maybe about to switch to a different CMS per #100, fyi.)

What are taglines and are there a set of pre-determined taglines that we should use for blog posts?

"Tagline" is like a slogan for the article -- a sentence or two that persuades people to read your post. Each one will be unique for its article.

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

No branches or pull requests

2 participants