docs(aio): add Happy Angular Podcast to resources

[dornsebastian]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[dornsebastian]

I signed it!

…

________________________________ Sebastian Dorn Developer t. +49 89 1222831 0 f. +49 89 1222831 20 m. +49 151 42136753 virtual7 GmbH Reichenbachstraße 1 80469 München http://www.virtual7.de <http://www.virtual7.de/> Amtsgericht Mannheim, HRB 521946 Vertretungsberechtigte Geschäftsführer: Marcus Weiss, Jochen Rieg Ust-Id (gem. §27a UstG): DE812887109 JOIN US: [cid:virtual7_blog_25_bdb73ae6-ee62-4d3c-b653-ec78d1a130e5.png] <http://www.virtual7.de/blog> [cid:virtual7_twitter_25_a62c2621-ab81-45e1-ae42-b2b1bc634b1b.png] <http://www.twitter.com/virtual7> [cid:virtual7_xing_25__9c010afe-b9fe-47d3-822b-b59368e44b68.png] <http://www.xing.com/companies/virtual7gmbh> [cid:virtual7_linked-in_25_0c4fb9bc-e1f0-4e38-a4d5-1b50944662e0.png] <https://www.linkedin.com/company/virtual7-gmbh> [cid:ORACLE-PLATINUM_165_68e367d1-6f46-4822-92fe-2018d7912fbf.png] <http://www.virtual7.de/de/unternehmen/portfolio/>

________________________________ LEGAL NOTICE Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren, die unbefugte Weitergabe sowie die unbefugte Nutzung der Inhalte dieser Email ist nicht gestattet. This email may contain confidential and/or privileged information. If you are not the intended recipient (or have received the email in error) please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material or any other usage of the content of this email is forbidden.

________________________________ Von: googlebot <notifications@github.com> Antworten an: angular/angular <reply@reply.github.com> Datum: Montag, 28. Januar 2019 um 21:43 An: angular/angular <angular@noreply.github.com> Cc: Sebastian Dorn <Sebastian.Dorn@virtual7.de>, Author <author@noreply.github.com> Betreff: Re: [angular/angular] docs(aio): add Happy Angular Podcast to resources (#28407) Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). &#128221; Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

________________________________ What to do if you already signed the CLA Individual signers * It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>. Corporate signers * Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot<http://go/cla#troubleshoot> (Public version<https://opensource.google.com/docs/cla/#troubleshoot>). * The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>. * The email used to register you as an authorized contributor must also be attached to your GitHub account<https://github.com/settings/emails>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#28407 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AilmyNJFpEAvDGEtS0L-M8gwf4S43JhFks5vH2EKgaJpZM4aWvRZ>.

[googlebot]

CLAs look good, thanks!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}