Meeting:DotNet 2016-11-04

Fedora DotNet Team Meeting Minutes 2016-11-04

Meeting Time

• 2016-11-04 13:00 UTC
• #fedora-meeting on freenode

Participants

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

• The participants will be posted after the meeting.

Meeting Protocol

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

Agenda

• #startmeeting Fedora DotNet (2016-11-04)
• #meetingname dotnet
• #nick dotnet
• #chair <given to approved members of FAS group at meeting>

• #topic Agenda
  • #link https://fedoraproject.org/wiki/Meeting:DotNet_2016-11-04
  • #info (1) Roll Call
  • #info (2) Announcements
  • #info (3) Action items from our previous meeting
  • #info (4) Tickets
  • #info (7) 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/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 === "Announcing .NET Core 1.1 Preview 1" ===
    • #link https://blogs.msdn.microsoft.com/dotnet/2016/10/25/announcing-net-core-1-1-preview-1
    • #info DotNet Core 1.1 preview1 was released a week ago.
  • #info === ".NET Core Tooling" ===
    • #link https://blogs.msdn.microsoft.com/dotnet/2016/10/19/net-core-tooling-in-visual-studio-15/
    • #info The final release of .NET Core tools will provide a build and project system that are unified with the rest of .NET project types, moving away from the project.json infrastructure that was specific to .NET Core. While this means we need to move away from the straightforward JSON format for project files and embrace the XML format used in MSBuild, this change will bring significant benefits in the overall experience.

• #topic Action items from our previous 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] Establish basic structure and organization. ===
    • #info Wiki page for the team was created, although it will require changes. Mailing list and the FAS group are in place as well, however this may change as well in the future (dotnet-devel would be created if necessary) We will be using Pagure for organization and GitHub for code - if any.
    • #link https://fedoraproject.org/wiki/DotNet
    • #link https://lists.fedoraproject.org/admin/lists/dotnet-sig.lists.fedoraproject.org
    • #link https://pagure.io/fedora-dotnet
    • The wiki/dotnet page should contain some info about dotnet in Fedora and dotnet in general, while our team and organization should be under wiki/SIGs/dotnet (or wiki/dotnet/join instead?) Any suggestions or ideas?

• #topic Tickets
  • #link https://pagure.io/fedora-dotnet/issues?tags=meeting
  • #info === Ticket #1 ===
  • #info "Set-up meeting schedule" ===
    • #link https://pagure.io/fedora-dotnet/issue/1
    • #info Minutes and agenda will be published, as you can see we are using the MeetBot.
    • #link https://fedoraproject.org/wiki/Meeting:DotNet_2016-11-04
    • #link https://apps.fedoraproject.org/calendar/SIGs/2016/11/4/#m4933
    • Does anyone have a problem with this time? (Is there any better time available?)
    • #action dotnet Import the meeting to your calendar.
    • #action Rhea Update the wiki page with information about meetings.

• #topic Open Floor
  • #info What is our long-term goal?
  • #info What should be our next steps?

Next Meeting

• 2016-11-11 13:00 UTC in #fedora-meeting