llvm dev - May 2016 - Interested in writing for the LLVM blog?

Hello! 

I am looking for a handful of people to help write blog posts for the LLVM blog
(blog.llvm.org <http://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.

Thanks,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160517/e9e03b99/attachment.html>

On 17 May 2016 at 22:41, Tanya Lattner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> If you are interested in volunteering for this position OR if you are
> interested in writing a blog post, please send me an email.
Hi Tanya,

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).

Just a thought...

cheers,
--renato

On Tue, May 17, 2016 at 2:46 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 17 May 2016 at 22:41, Tanya Lattner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> 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...

Hi everybody,

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.

[1] http://lowlevelbits.org/categories/clang/
[2] http://lowlevelbits.org/categories/llvm/
[3] http://blog.llvm.org/2013/07/using-mcjit-with-kaleidoscope-tutorial.html
> On 17 May 2016, at 23:41, Tanya Lattner via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Hello!
> 
> 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.
> 
> Thanks,
> Tanya
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
--
AlexDenisov
Software Engineer, http://lowlevelbits.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160518/c7b9da13/attachment.sig>

On 18 May 2016, at 07:45, Alex Denisov via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Hi everybody,
> 
> 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.
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?

David

> On May 17, 2016, at 11:45 PM, Alex Denisov <1101.debian at gmail.com>
wrote:
> 
> Hi everybody,
> 
> 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).

-Tanya
> 
> [1] http://lowlevelbits.org/categories/clang/
> [2] http://lowlevelbits.org/categories/llvm/
> [3]
http://blog.llvm.org/2013/07/using-mcjit-with-kaleidoscope-tutorial.html
> 
>> On 17 May 2016, at 23:41, Tanya Lattner via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>> 
>> Hello!
>> 
>> 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.
>> 
>> Thanks,
>> Tanya
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
> --
> AlexDenisov
> Software Engineer, http://lowlevelbits.org
>