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

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

On 5/17/16 4:41 PM, Hans Wennborg via llvm-dev wrote:
> 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...
I think blog posts about it would be of value to the crowd that comes in 
through sites like HN / Reddit.


Jon
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-- 
Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded

> On May 17, 2016, at 3:41 PM, Hans Wennborg <hans at chromium.org>
wrote:
> 
> 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…
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.

I’m open to other opinions on the subject. :) 

-Tanya

Hi Tanya,

I can volunteer to contribute a post each on the following two topics
if there is sufficient interest:

 - Why IPO over comdats (C++ inline functions etc.) is difficult:
mainly summarizing the issues discussed in
http://lists.llvm.org/pipermail/llvm-dev/2016-February/095833.html

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

Thanks,
-- Sanjoy




On Tue, May 17, 2016 at 3:49 PM, Tanya Lattner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
>> On May 17, 2016, at 3:41 PM, Hans Wennborg <hans at chromium.org>
wrote:
>>
>> 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…
>
> 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.
>
> I’m open to other opinions on the subject. :)
>
> -Tanya
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


-- 
Sanjoy Das
http://playingwithpointers.com