I am looking for a handful of people to help write blog posts for the LLVM blog (blog.llvm.org) or to help recruit volunteers to write blog posts. The LLVM Project blog is a great place to share details about recent changes to LLVM, Clang, and related sub-projects. It also is a great place to highlight users of LLVM. You can write about your work or the work of others that has gone into the tree recently.
If you are interested in volunteering for this position OR if you are interested in writing a blog post, please send me an email.
Why don't we communicate the releases, candidates, problems, and dates
on the blog, too? Thorough discussions still go on the list, but
status update could go on the blog, at least one for each RC.
Some people complained we don't communicate as efficiently as we
should, maybe that could be an official channel to interact with our
users, not just via the mailing list (which has very high volume).
I was going to reply that I do post the release announcements on the
blog, but now I see I forgot to do that for 3.8 :-/
Last time, I talked about posting to llvm-announce about release
candidates, etc., but never actually followed through as I was
ambivalent about how people would perceive the signal-to-noise ratio.
It's similar for the blog: is info about release candidates valuable
for those not involved enough to read llvm-dev, or would it be
perceived as noise, hiding more important contents? I'm pretty
undecided...
If you are interested in volunteering for this position OR if you are
interested in writing a blog post, please send me an email.
Why don't we communicate the releases, candidates, problems, and dates
on the blog, too? Thorough discussions still go on the list, but
status update could go on the blog, at least one for each RC.
Some people complained we don't communicate as efficiently as we
should, maybe that could be an official channel to interact with our
users, not just via the mailing list (which has very high volume).
I was going to reply that I do post the release announcements on the
blog, but now I see I forgot to do that for 3.8 :-/
Last time, I talked about posting to llvm-announce about release
candidates, etc., but never actually followed through as I was
ambivalent about how people would perceive the signal-to-noise ratio.
It's similar for the blog: is info about release candidates valuable
for those not involved enough to read llvm-dev, or would it be
perceived as noise, hiding more important contents? I'm pretty
undecided...
I think blog posts about it would be of value to the crowd that comes in through sites like HN / Reddit.
I agree that posting release announcements to the blog is a good thing. I’m also on the fence about release schedule, candidates, problems, etc because I view the blog as a way to advertise our work and successes to those who aren’t necessarily a part of the LLVM community. I think we could improve the website to more adequately communicate some of this information. We do also have the release-testers mailing list now which is much lower volume.
- Deoptimization support in LLVM: covering how operand bundles,
llvm.experimental.deoptimize, llvm.experimental.guard and
llvm.experimental.gc.statepoint come together to provide a first-class
representation for deoptimization state, and how we can write
speculative optimizations within the LLVM framework.
I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog.
However, I can’t omit bike-shedding
Forgive me my directness, but current blog doesn’t look like something close to 2016.
The blog already has lots of great articles. But it’s so hard to grasp valuable information when you have to read non-highlighted C++ code.
I think I managed to read this great article[3] from third or fourth attempt just because of the UI.
I’d focus not on content only, but on appearance as well. I think we can agree that this is important.
Tanya, I’d be more than happy to help if this is something considerable.
Sorry for the bikeshedding, but the readability of the blog is also hampered considerably by re-posting all of the LLVM Weekly entries there. It’s already easy to subscribe to them at http://llvmweekly.org (which has its own RSS feed and is a great resource), but having copies of them make up 90% of the posts on blog.llvm.org makes it very difficult to find the remaining 10%.
Please can we stop cross-posting LLVM Weekly to the LLVM blog instead promote links to llvmweekly.org (and, ideally, to the most recent 4-5 articles) to the front page of llvm.org and to the blogs.llvm.org?
I'd be happy with that. Blogger's view counts indicate there is an
audience for these posts, but I agree with the current blog setup they
can drown out other posts
I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog.
However, I can’t omit bike-shedding
Forgive me my directness, but current blog doesn’t look like something close to 2016.
I will not disagree about that.
The blog already has lots of great articles. But it’s so hard to grasp valuable information when you have to read non-highlighted C++ code.
I think I managed to read this great article[3] from third or fourth attempt just because of the UI.
I’d focus not on content only, but on appearance as well. I think we can agree that this is important.
Yes. It is very important.
Tanya, I’d be more than happy to help if this is something considerable.
I’d be open to any and all help. I’m also looking into contracting a web designer to help with design of llvm website (of course working with the community but it hasn’t bubbled up to the top of my pile yet).
This is a reasonable suggestion. LLVM Weekly is an amazing resource which is why we wanted it on the blog. However, it may be better to link directly to it from the website as you suggest.
I fully agree, and now that this effort to increase the the flow of
content to the LLVM blog is paying off, I think now is the time to
retire the LLVM Weekly cross-posts so as not to crowd-out all this new
content. As such, I've documented issue #130
(LLVM Weekly - #130, Jun 27th 2016 - The LLVM Project Blog) as
the last one that will be cross-posted in this way.
