Post 832259 by ben@mastodon.lubar.me
(DIR) More posts by ben@mastodon.lubar.me
(DIR) Post #831941 by Gargron@mastodon.social
2018-10-29T04:32:21Z
0 likes, 0 repeats
I gotta start writing the hype-oriented 2.6.0 announcement post
(DIR) Post #832028 by Mainebot@octodon.social
2018-10-29T04:43:01Z
0 likes, 0 repeats
@gargron gotta use a few !!!s and :Os
(DIR) Post #832036 by Gargron@mastodon.social
2018-10-29T04:43:44Z
0 likes, 0 repeats
@Mainebot never mind my reply was too cursed
(DIR) Post #832037 by Mainebot@octodon.social
2018-10-29T04:43:45Z
0 likes, 1 repeats
@gargron 2.6.0w0
(DIR) Post #832148 by Gargron@mastodon.social
2018-10-29T04:57:48Z
0 likes, 0 repeats
Honestly I'm always a bit struggling with which audience those blog posts should have in mind. There's like three types of changelogs I have to write: the point by point changelog included in the source files, the GitHub release changelog, which sysadmins will read to figure out how to upgrade and why to upgrade, and these hype-oriented blog posts.But if I'm not aiming at sysadmins there, does it mean I should omit writing about admin features, CLI utilities, fixes and all that stuff 🤔
(DIR) Post #832181 by Mainebot@octodon.social
2018-10-29T05:02:44Z
0 likes, 0 repeats
@gargron if you're aiming for end-user hype, take the time to talk about how these changes work in context with past developments and how they serve future ones. Paint a picture!
(DIR) Post #832233 by GeekAndDad@mastodon.social
2018-10-29T05:06:35Z
0 likes, 0 repeats
@Gargron my vote: yes. Include link to technical detail post but omit from the popular audience post.Like popular science articles that simplify and use nontechnical language to describe the scientific research or discovery or whatever but then link to the actual paper published in the scientific journal.
(DIR) Post #832249 by Gargron@mastodon.social
2018-10-29T05:08:22Z
0 likes, 0 repeats
Outline :thinkerguns:
(DIR) Post #832259 by ben@mastodon.lubar.me
2018-10-29T05:09:33Z
0 likes, 0 repeats
@Gargron no update note Mastodon will ever have will beat Dwarf Fortress's "stopped dogs from being depressed because they couldn't figure out how to practice their religion" or "fixed a bug where cats would die from alcohol poisoning if they walked into a tavern"
(DIR) Post #832320 by saxnot@chaos.social
2018-10-29T05:18:32Z
0 likes, 0 repeats
@Gargron if you have 3 clearly defined audiences then maybe you want to have 3 changelogs.But that would be sort of a mess…
(DIR) Post #832337 by nikdow@mastodon.social
2018-10-29T05:22:08Z
0 likes, 0 repeats
@Gargron sounds like you are doing the work of at least 3 people, right there.
(DIR) Post #832349 by senser@mastodon.social
2018-10-29T05:23:55Z
0 likes, 0 repeats
@GargronOne changelog with three main sections perhaps? Every section for the specific audience 🙂
(DIR) Post #832358 by trwnh@mastodon.social
2018-10-29T05:24:32Z
0 likes, 0 repeats
@Gargron no, don't omit it. it's still important to know "hey btw admins have an easier time now" and maybe some of the popular audience might be interested in admining their own instance down the road. a simple point-by-point of "hey these are some of the new changes that make it easier on admins" is enough.
(DIR) Post #832422 by neal@social.typica.us
2018-10-29T05:33:17Z
0 likes, 0 repeats
@Gargron It's okay to hype admins about upgrading.
(DIR) Post #832582 by apatters@mastodon.social
2018-10-29T06:04:52Z
0 likes, 0 repeats
@Gargron This might like it's coming from left field, but I would target the media. If the end goal is growth then the media can be your biggest ally (or enemy).Technical notes for developers and sysadmins are critical as well but don't have to be in the big announcement post (and you probably have enough trusted contributors by now that you can start to delegate these).
(DIR) Post #832758 by VioletPixel@mastodon.social
2018-10-29T06:22:36Z
0 likes, 0 repeats
@Gargron Doesn't this release have the API additions to make saving your place in third party apps viable? If so, that should be in there somewhere to entice/encourage developers.
(DIR) Post #833619 by WAHa_06x36@mastodon.social
2018-10-29T07:55:51Z
0 likes, 0 repeats
@Gargron Is preview data embedded in the stream JSON now?
(DIR) Post #833652 by Gargron@mastodon.social
2018-10-29T07:57:54Z
0 likes, 0 repeats
@WAHa_06x36 yea
(DIR) Post #833701 by WAHa_06x36@mastodon.social
2018-10-29T08:00:32Z
0 likes, 0 repeats
@Gargron Niiiiice. Going to have to get on with implementing that! Also go to sleep!
(DIR) Post #835812 by KevinMarks@xoxo.zone
2018-10-29T11:10:49Z
0 likes, 0 repeats
@Gargron If you want an extra pair of eyes on the rel=me stuff I'm very happy to help. The best writing advice on. release notes is Anna's at Slack: https://slackhq.com/a-little-thing-about-release-notes
(DIR) Post #836786 by ethan@fosstodon.org
2018-10-29T12:31:22Z
0 likes, 0 repeats
@GargronWhat about 3 separate posts that link to each other with a 1-2 sentence preview?
(DIR) Post #837132 by Tyler_roi@mastodon.social
2018-10-29T13:05:25Z
0 likes, 0 repeats
@Gargron Different industry (writing and game design) but have a similar problem. Do consumers care about our behind the scenes stuff? Do Game designers care about our consumer focused stuff? Tricky wicket.
(DIR) Post #848439 by persadon@mastodon.social
2018-10-30T00:12:00Z
0 likes, 0 repeats
@Gargron It's not that you are a release manager at Twitter and you're writing about Twitter admin dashboard (which only people at Twitter Inc are gonna use). Mastodon is decentralized, and admin stuff is part of the project output.Even for non-admin end-users, those admin features mean that their admin would have an easier life managing the instance.