amazon-archives/aws-week-in-review

ARCHIVED: These files are used to produce the AWS Week in Review.

Archived

The Week in Review is no longer being published. You can visit https://aws.amazon.com/new/ to track the latest product, service, and feature announcements from AWS.

---

The files in this GitHub Repo are used to produce the AWS Week in Review.

Contributing is easy; you can simply create a GitHub account and make edits to the current week-in-review/YYYY/MM/week-in-review- file from the comfort of your web browser. You can add your own content, or content from others. Read this post for step-by-step directions.

History

In the early days of AWS, Jeff Barr wrote the Week in Review each week. Initially this took just 5 or 10 minutes, but as the pace of innovation quickened and the size of the AWS community grew, Jeff sometimes spent 4 or 5 hours finding and formatting the content.

The new model, introduced in August of 2016, is crowdsourced. AWS fans, users, bloggers, and partners are all invited to contribute to the project and to the AWS Week in Review.

Content & Style Guidelines

Here are the guidelines for making contributions:

• Relevance - All contributions must be directly related to AWS.
• Ownership - All contributions remain the property of the contributor, but you grant AWS an unlimited license.
• Validity - All links must be to publicly available content (links to free, gated content are fine).
• Timeliness - All contributions must refer to content that was created on the associated date.
• Neutrality - This is not the place for editorializing. Just the facts / links.

Here are the guidelines for style:

• Content from the AWS Blog is generally prefixed with "I wrote about POST_TITLE" or "We announced that TOPIC."
• Content from other AWS blogs is styled as "The BLOG_NAME wrote about POST_TITLE."
• Content from individuals is styled as "PERSON wrote about POST_TITLE."
• Content from partners and ISVs is styled as "The BLOG_NAME wrote about POST_TITLE."

There's room for some innovation and variation to keep things interesting, but keep it clean and concise.

Weekly Schedule

Here's the plan (all times are PT):

• Monday, 8:30 AM - HTML for previous week copied to WordPress and finalized.
• Monday, 10:00 AM - Week in Review published.
• Monday, 10:00 AM - HTML for current week created in GitHub.
• Monday to Monday - Current week edited by contributors and pull requests created.
• Monday to Monday - Pull requests accepted.

Week in Review Sections

Each Week in Review contains the following sections:

• Daily Summaries - content from the main AWS Blog, other AWS blogs, and everywhere else.
• New & Notable Open Source.
• New SlideShare Presentations.
• New YouTube Videos including APN Success Stories.
• New AWS Marketplace products.
• New Customer Success Stories.
• Upcoming Events.
• Help Wanted.

The OPML file (feeds.opml) in this repo contains a list of sources. Feel free to use it to find content, and add your own sources as well.

Short Codes

Please use the folllowing "short codes" when you refer to content in other AWS blogs:

• [iotblog] - The Internet of Things on AWS Blog.
• [devblog] - AWS Developer Blog.
• [gamedevblog] - Amazon GameDev Blog.
• [cliblog] - AWS Command Line Tool Blog.
• [govblog] - AWS Government, Education, & Nonprofits Blog.
• [javascriptblog] - AWS JavaScript Blog.
• [phpblog] - PHP Developer Blog.
• [rubyblog] - AWS Ruby Development Blog.
• [secblog] - AWS Security Blog.
• [startupblog] - AWS Startup Collection.
• [entblog] - Enterprise Blog.
• [javablog] - AWS Java Blog.
• [mobileblog] - AWS Mobile Development Blog.
• [netblog] - AWS Windows and .NET Developer Blog.
• [appmgmtblog] - AWS DevOps Blog.
• [archblog] - AWS Architecture Blog.
• [bigdatablog] - AWS Big Data Blog.
• [computeblog] - AWS Compute Blog.
• [sesblog] - Amazon Simple Email Service Blog.
• [apnblog] - AWS Partner Network Blog.

For example, an entry might look like "The [iotblog] talked about ...."

Also, please feel free to invent similar codes for the non-AWS blogs. Put them in the file shortcodes.txt.

Contributing

You can contribute to this project (and to the AWS Week in Review) by cloning the repo, adding content to the current week-in-review- file, and then submitting a pull request. Over time, there may be other avenues, such as issues.

Please feel free to suggest improvements to the process and to the use of GitHub as well.

aws-week-in-review's Issues

Add labels to issues

@jeffbarr You might considering adding one of the built in labels to each of the issues as a visualization aid.

Since there are only a handful of issues, now and likely in the future, this might be overkill, so feel free to close this if that's the case. If we end up having a development branch with a significantly different workflow, the number of bugs/enhancements are likely to increase, so there's that.

Broken "pull request" link in CONTRIBUTING.md

CONTRIBUTING.md has a "pull request" hyperlink to https://help.github.com/send-pull-requests/ which does not exist.

Update directory structure.

Update the directory structure to ensure that the root does not grow cluttered over time.

Need a cutoff date (& time?) in CONTRIBUTING.md

It's unclear when contributors should stop submitting PRs for the current file and start using the next iteration.

It may make sense to have both this week's and the next week's files up with some guidance added to CONTRIBUTING.md.

Simplify submission process

Managing the creation of this document in Git/GitHub is a cool idea, but after doing it once, I see some drawbacks:

1. It is difficult to see if a pull request has already been created for the resource I am thinking of adding, especially since pull requests could take days to be merged into the primary repo.
2. It is a fair amount of work to fork, create a branch, clone, edit, commit, push, create pull request just to submit a line of text with a couple links.
3. I'm guessing that having 10 people submit pull requests to change the same "???" line in the Monday section creates a lot of conflicts and makes accepting all of the new submissions non-trivial.

Ideas?

Volunteer(s) to accept simplified submission proposals and incorporate into a unified pull request?

Broken links

In Section "New & Notable Open Source" in "AWS Week in Review – October 10, 2016" couple of links are broken links

• Links to node-aws-sqs-redriver is broken.
• Link to awsm incorrect.

Open links in new tab

I think it would be useful if links in the Week in Review opened in a new tab. It would make navigating easier than having to use the back-button to return to the page or having to manually choose to open in a new tab.

Organise submissions by topic not date

Having the week in review organised by date makes it very difficult to find the wood from the trees. Also creates lumps of submissions for Monday.
Can you please consider having submissions ordered by topic? The topics could be organised like the AWS Blog (Architecture, DevOps, PHP Development, .NET Development, Ruby Development, Mobile Development, Java Development, Security, Startup, Big Data, Database Blog, Partner Network, Compute, AWS for SAP, SES, Internet of Things, Public Sector).
This could also be used to allocate review of submissions to the appropriate AWS department.

AWS Whitepapers - Example Jenkins on AWS

@jeffbarr
I'm not sure how you want to handle AWS authored WPs such as Jenkins on AWS - pdf.

I'd propose that a useful resource like this gets included, but I'm not sure who would include the reference and the format for the pointer, especially since it's a PDF. (Hoping it would be someone from AWS.)

Suggestion to enforce guidelines

Hi,

I just saw your tweet and after checking the README file, noticed there was some contribution guidelines mixed in there.

I'd like to suggest using CONTRIBUTING.md to put those guidelines as GitHub will automatically show a link to them to everyone submitting a new PR.

I would also like to take this opportunity to present something I am directly affiliated with and that could help enforcing those guidelines: https://var.ci

The reason I say that is because it would help contributors automatically know of mistakes they've made while saving you time from having to manually do it yourself.

I hereby volunteer to create the initial PR to get things set up if you give me the OK.

Best,

Jad

week-in-review-2016-09-27.html - Date off by one

Monday is Sep 26 and so on

Week in review 2016-11-28

Hello - will there be a week in review 2016-11-28? I couldn't see the template for it.

Thanks!

Refactor Contributing and ReadMe: Move Short Code Info to Contributing

All the information needed to contribute might better be in Contributing, rather than in ReadMe.

One change would be to move the short code information to Contributing.

Can we use template engine instead of pure HTML?

Hi everyone,
just as a suggestion can we use template engine, or Markdown instead of writing pure HTML?

Rigor of content has declined since it went crowdsourced

In reading a couple of the articles linked in this week's post, I realize that the content curation aspect of this blog is gone. There are no checks and balances for the quality of content linked. I'm not going to call out any contributors by name, but by watering down the quality of the content, @jeffbarr, you're drastically reducing the value of this previously very exciting weekly feature.

Alternative list of sources

I've found this repo while ago that compile a (huge) well categorized list of engineering blogs and generates an OPML.
I'm not sure if something like this worth to be mentioned as an alternative list of sources in the readme.

Just let me know and I'll send a pull request adding this.

BTW, what RSS reader are you using?

Thanks.

Is week in review git publishing still maintained?

no commits since 11.21.2016

Are we still using this?

re:Invent 2016 Lunch Plan

As promised, there will be a contributor's lunch at re:Invent. With the opening just a week away, I need to figure out the logistics.

If you will be a re:Invent and you are one of the top contributors, please fill in your availability for a lunch (lets say Noon to 1 PM):

Contributor	Mon	Tue	Wed	Thu	Fri
jeffbarr	Y	N	Y	Y	Y