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