Fedora DotNet Team Meeting Minutes 2017-02-07

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-02-07
- #info (1) Roll Call
- #info (2) Announcements
- #info (3) Action items and Tickets
- #info (4) Packaging progress
- #info (5) Open Floor

#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 === "Update for ASP.NET Core 1.1" ===
  - #link https://blogs.msdn.microsoft.com/dotnet/2017/01/30/january-2017-update-for-asp-net-core-1-1
  - #info Security update - if you're using asp.net core you might want to update :P
- #info === "Announcing .NET Core, .NET Native and NuGet Updates in VS 2017 RC" ===
  - #link https://blogs.msdn.microsoft.com/dotnet/2017/01/30/announcing-net-core-net-native-and-nuget-updates-in-vs-2017-rc
  - #info ...
- #info === ".NET Core Image Processing" ===
  - #link https://blogs.msdn.microsoft.com/dotnet/2017/01/19/net-core-image-processing
  - #info ...
- #info === "The .NET Language Strategy" ===
  - #link https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy
  - #info A little bit about different languages in dotnet

#topic Action items and Tickets
- #link https://meetbot.fedoraproject.org/teams/dotnet/dotnet.2017-01-17-19.04.html
- #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 === [COMPLETE] Rhea Finalise the fas-group and pagure setup. ===
    - #info Kinda done there, except that we can't reaaally finish all that until we get nmilosev into the group, which would be done only when we submit package, so it's kinda weird.
- #info === GSoC ===
  - #idea Do we want to mentor a Google Summer of Code project?