amazon-archives / aws-week-in-review Goto Github PK

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

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):

Monday is Sep 26 and so on

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

Thanks!

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.

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.

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

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.

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

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

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?

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

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

no commits since 11.21.2016

Are we still using this?

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.

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.

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.

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.