5 ms·

It's unfortunate that people often forget to include context like this in announcements. Thanks for sharing!

eatbitseveryday 9y ago
The announcement is on edwardlib.org (the URL shared on HN). Wouldn't that be an obvious connection? A project making an announcement about itself on its own website, seems natural to me.
- foepys 9y ago
  The announcement should at least include a link to an explanation on the main project page. Due to only being posted on discourse, there is no direct link to go to the main project page, only by manually editing the URL or googling for Edward. Even the logo in the top-left corner only leads to the discourse overview page. Edit: Just editing the URL leads to an HTTPS error because the certificate is only valid for *.github.io; you need to use HTTP.
  - eatbitseveryday 9y ago
    I agree the connection could be smoother to get there... shrugs not really something I'm spending cycles being concerned about.
- thejosh 9y ago
  Yes, but it's always nice when a project gives a tldr on their blog about what they are.
- mwexler 9y ago
  Even more natural: Edward (probabilistic modeling library in Python) is officially moving into TensorFlow. But I see your point.
petercooper 9y ago
It could be parenthesized into the HN title but then stuff like that just gets edited back out :-D
- michaelmior 9y ago
  What I meant is that if you have a major announcement about your project that you can reasonably expect to be shared, it's nice to give some context within the announcement. I think this also applies to people on your mailing list. So often I get announcements sent out to a mailing list I signed up for where I forgot what the project is. Just having a sentence or two with a reminder goes a long way toward keeping me interested.
  - petercooper 9y ago
    I totally agree. But in absence of that, I think tweaking headlines or adding parenthesized descriptions is good form, despite being against current HN policy.

The announcement is on edwardlib.org (the URL shared on HN). Wouldn't that be an obvious connection? A project making an announcement about itself on its own website, seems natural to me.

foepys 9y ago
The announcement should at least include a link to an explanation on the main project page. Due to only being posted on discourse, there is no direct link to go to the main project page, only by manually editing the URL or googling for Edward. Even the logo in the top-left corner only leads to the discourse overview page. Edit: Just editing the URL leads to an HTTPS error because the certificate is only valid for *.github.io; you need to use HTTP.
- eatbitseveryday 9y ago
  I agree the connection could be smoother to get there... shrugs not really something I'm spending cycles being concerned about.
thejosh 9y ago
Yes, but it's always nice when a project gives a tldr on their blog about what they are.
mwexler 9y ago
Even more natural: Edward (probabilistic modeling library in Python) is officially moving into TensorFlow. But I see your point.

petercooper 9y ago

It could be parenthesized into the HN title but then stuff like that just gets edited back out :-D

michaelmior 9y ago
What I meant is that if you have a major announcement about your project that you can reasonably expect to be shared, it's nice to give some context within the announcement. I think this also applies to people on your mailing list. So often I get announcements sent out to a mailing list I signed up for where I forgot what the project is. Just having a sentence or two with a reminder goes a long way toward keeping me interested.
- petercooper 9y ago
  I totally agree. But in absence of that, I think tweaking headlines or adding parenthesized descriptions is good form, despite being against current HN policy.