Fedora DotNet Team Meeting Minutes 2017-06-06

Meeting Time

This week's DotNet Meeting will be led by Rhea.

To help improve the flow of the meeting, using the IRC Meeting Protocol is encouraged, as modeled by the EMEA Ambassadors.
Please follow the Meeting Protocol where possible.

#topic Agenda
- #link https://fedoraproject.org/wiki/Meeting:DotNet_2017-06-06
- #info (1) Roll Call
- #info (2) Announcements
- #info (3) Action items and Tickets
- #info (4) Packaging progress / Open Floor discussion

#topic Roll Call
- #info Name; Timezone; Sub-projects/Interest Areas
- #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ]
- If this is your first time at a DotNet meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.

#topic Announcements
- #info === "Microsoft Blog: .NET & Docker" ===
  - #link === https://blogs.msdn.microsoft.com/dotnet/2017/05/25/using-net-and-docker-together/
- #info === "JetBrains Blog: All kinds of tips for Rider" ===
  - #info Working with TODO items
    - #link https://blog.jetbrains.com/dotnet/2017/05/11/working-todo-items-rider/
  - #info Local History in Rider: undo and redo on steroids
    - #link https://blog.jetbrains.com/dotnet/2017/05/17/local-history-rider-undo-redo-steroids/
  - #info Incremental build
    - #link https://blog.jetbrains.com/dotnet/2017/05/24/incremental-build-rider/
  - #info Rider EAP 22: Xamarin iOS, unit testing improvements, compound run configurations and more
    - #link https://blog.jetbrains.com/dotnet/2017/05/18/rider-eap-22-xamarin-ios-unit-testing-improvements-compound-run-configurations/
  - #info F# in Rider
    - #link https://blog.jetbrains.com/dotnet/2017/05/08/rider-is-now-also-an-fsharp-ide-adding-fsharp-support/

#topic Action items and Tickets
- #link https://meetbot.fedoraproject.org/teams/dotnet
- #link https://pagure.io/fedora-dotnet/issues?tags=meeting
- #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
  - #info === [WIP] Rhea rewrite the C# developer pages based on pagure #17 ===
    - #link https://pagure.io/fedora-dotnet/issue/17
    - #link https://github.com/Fedora-dotnet/developer-portal-content