#fedora-meeting: Fedora DotNet (2017-01-17)

Meeting summary

1. Agenda (Rhea, 19:04:12)
   1. https://fedoraproject.org/wiki/Meeting:DotNet_2017-01-17 (Rhea, 19:04:18)
   2. (1) Roll Call (Rhea, 19:04:21)
   3. (2) Announcements (Rhea, 19:04:24)
   4. (3) Action items and Tickets (Rhea, 19:04:30)
   5. (4) Packaging progress (Rhea, 19:04:32)
   6. (5) Open Floor (Rhea, 19:04:36)
   
   
2. Roll Call (Rhea, 19:04:39)
   1. Name; Timezone; Sub-projects/Interest Areas (Rhea, 19:04:44)
   2. ACTION: dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/DotNet ] (Rhea, 19:04:46)
   3. Radka Janek; UTC+1; CommOps, Diversity, DotNet,... (Rhea, 19:04:55)
   4. Filip Vukovinski; UTC+1;DotNet, Haskell (vukovinski, 19:05:17)
   
   
3. Announcements (Rhea, 19:06:51)
   1. === "Engineering changes for corefx #15135" === (Rhea, 19:06:54)
   2. Tim Orling; UTC-9; DotNet, Modularity, Eclipse, Python, Perl (moto-timo, 19:06:55)
   3. https://github.com/dotnet/corefx/issues/15135 (Rhea, 19:06:57)
   4. Build from source, Package reduction (.NET Core is now 1 package instead of 100's of tiny packages) etc... (Rhea, 19:07:00)
   
   
4. Action items and Tickets (Rhea, 19:09:37)
   1. https://meetbot.fedoraproject.org/teams/dotnet/dotnet.2016-12-06-19.11.html (Rhea, 19:09:41)
   2. https://pagure.io/fedora-dotnet/issues?tags=meeting (Rhea, 19:09:45)
   3. 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. (Rhea, 19:09:48)
   4. === [COMPLETE] dotnet Attempt to create F25 package. === (Rhea, 19:10:02)
   5. https://pagure.io/fedora-dotnet/commits/f25 (Rhea, 19:10:29)
   6. https://copr.fedorainfracloud.org/coprs/nmilosev/dotnet-clean/ (vukovinski, 19:12:16)
   7. https://copr.fedorainfracloud.org/coprs/nmilosev/dotnet-clean/ (nmilosev, 19:12:50)
   8. https://github.com/dotnet/core-setup/issues/680 interesting for anyone who wants to see upstream's perspective on how distrbiutions should package .net core applications (omajid, 19:29:35)
   9. ACTION: dotnet Look into the new build system and see if we can build unstable (Rhea, 19:32:03)
   
   
5. Packaging progress (Rhea, 19:33:50)
   1. nmilosev created an F25 package using the discussed RHEL+Rover approach. (Rhea, 19:33:59)
   2. https://copr.fedorainfracloud.org/coprs/nmilosev/dotnet-clean (Rhea, 19:34:02)
   3. We will have another fas group for packagers that will serve as permission to commit to our pagure repo. (Rhea, 19:34:53)
   4. AGREED: Pagure branches should follow the F:n naming scheme (Rhea, 19:38:29)
   5. https://github.com/vivekanand1101/pagure-importer (omajid, 19:45:48)
   6. ACTION: Rhea Create the dotnet-packagers fas group (Rhea, 19:46:26)
   7. ACTION: Rhea import issues to pagure, create tags, etc... ref: https://github.com/vivekanand1101/pagure-importer (Rhea, 19:48:51)
   
   
6. Open Floor (Rhea, 19:49:14)

Action items

1. dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/DotNet ]
2. dotnet Look into the new build system and see if we can build unstable
3. Rhea Create the dotnet-packagers fas group
4. Rhea import issues to pagure, create tags, etc... ref: https://github.com/vivekanand1101/pagure-importer

Action items, by person

1. dotnet
   1. dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/DotNet ]
   2. dotnet Look into the new build system and see if we can build unstable
   3. Rhea Create the dotnet-packagers fas group
2. Rhea
   1. Rhea Create the dotnet-packagers fas group
   2. Rhea import issues to pagure, create tags, etc... ref: https://github.com/vivekanand1101/pagure-importer

People present (lines said)

1. Rhea (81)
2. nmilosev (65)
3. omajid (28)
4. moto-timo (28)
5. zodbot (15)
6. vukovinski (11)
7. rmartinelli (7)
8. tmds (2)
9. bt0 (1)
10. Southern_Gentlem (1)
11. threebean (1)
12. dotnet (0)