You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking about what to do with the main Twitter account a bit and even though the firehose is useful, I do think it’ll put people off from following if we funnelled every package update through to the main account.
I think my favourite plan for the account is some kind of daily summary. We make a page on the site that generates a daily summary. What packages were added, what new versions were released, grouped by the major/minor/patch, what new beta releases there were, etc… That replaces, or complements the current lists on the home page, and also is where we link to from the Twitter updates.
I've been thinking about what to do with the main Twitter account a bit and even though the firehose is useful, I do think it’ll put people off from following if we funnelled every package update through to the main account.
I think my favourite plan for the account is some kind of daily summary. We make a page on the site that generates a daily summary. What packages were added, what new versions were released, grouped by the major/minor/patch, what new beta releases there were, etc… That replaces, or complements the current lists on the home page, and also is where we link to from the Twitter updates.
Example tweet:
“There were 13 package releases today, including 4 major versions. See a summary of yesterday’s release on the site: https://swiftpackageindex.com/updates/2020-12-03”
Opening an issue for discussion, and also to start tracking it.
The text was updated successfully, but these errors were encountered: