14:04:29 #startmeeting Fedora DotNet (2017-07-27) 14:04:29 Meeting started Thu Jul 27 14:04:29 2017 UTC. The chair is Rhea. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:04:29 The meeting name has been set to 'fedora_dotnet_(2017-07-27)' 14:04:31 #meetingname dotnet 14:04:31 The meeting name has been set to 'dotnet' 14:04:34 #nick dotnet 14:04:37 #chair omajid aslice pcreech nmilosev davem axels 14:04:37 Current chairs: Rhea aslice axels davem nmilosev omajid pcreech 14:04:41 #topic Agenda 14:04:43 #link https://fedoraproject.org/wiki/Meeting:DotNet_latest 14:04:46 #info (1) Roll Call 14:04:49 #info (2) Announcements 14:04:52 #info (3) Action items and Tickets 14:04:55 #info (4) Packaging progress / Open Floor discussion 14:05:02 #topic Roll Call 14:05:03 #info Name; Timezone; Sub-projects/Interest Areas 14:05:07 #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ https://fedoraproject.org/wiki/SIGs/DotNet ] 14:05:12 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. 14:05:43 .hello aslice 14:05:44 aslice: aslice 'Andrew Slice' 14:05:45 .hello pcreech17 14:05:47 pcreech: pcreech17 'Patrick Creech' 14:06:14 Andrew Slice; EST; C#, C++, perl 14:06:37 .hello axels 14:06:39 axels: axels 'None' 14:06:43 Radka Janek; UTC+1; CommOps, Diversity, DotNet, OpenShift,... 14:07:09 .hello omajid 14:07:10 omajid: omajid 'Omair Majid' 14:07:12 #topic Announcements 14:07:16 #info === New FAS group dotnet-team - for all members - please join === 14:07:18 #link https://admin.fedoraproject.org/accounts/group/view/dotnet-team 14:07:35 There was a bit of chaos fixing that stuff, sorry about that :D 14:07:45 (and email spam, i think that i got like 50 emails from that) 14:07:47 Rhea: so how do the groups work now? -sig is for packagers? -team is for anyone? 14:07:55 Yep, that is correct 14:08:32 * pcreech not in -team... just applied 14:08:35 RUnning with just one group ain't gonna cut it in case of Fedora for several reasons, ad 1) wiki editing requires a group, 2) if you ever need to show people that you've been contributing, you do that by being in a group... 14:09:20 #info === New copr group dotnet-sig === 14:09:22 #link https://copr.fedorainfracloud.org/groups/g/dotnet-sig/coprs/ 14:09:24 #link https://copr.fedorainfracloud.org/coprs/g/dotnet-sig/dotnet/ 14:09:42 This is where we should have all our actual packages from now on. 14:10:03 Rhea: thanks for setting it all up! 14:10:06 I'm gonna quickly go through action items and then would get back to this under packaging... 14:10:19 #topic Action items and Tickets 14:10:21 #link https://meetbot.fedoraproject.org/teams/dotnet 14:10:23 #link https://pagure.io/fedora-dotnet/issues?tags=meeting 14:10:26 #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. 14:10:30 #info === [WIP] developer.fedoraproject.org update #17 === 14:10:35 #link https://pagure.io/fedora-dotnet/issue/17 14:10:37 #link https://github.com/Fedora-dotnet/developer-portal-content 14:11:08 Soooo... after I'm done talking for Microsoft I'll adapt some bits of my talk for the portal, at least some deployment examples, systemd, proxy... 14:11:33 axels: was working on the dotnet-usage page, this is a bit of a "how does the dotnet command work" type of thing 14:11:43 #info === [INCOMPLETE] axels - continue improving the dotnet-usage dev portal page === 14:11:45 #action axels - continue improving the dotnet-usage dev portal page 14:11:50 Yes, ma'am :D 14:11:58 That could use a bit worded description 14:12:13 After I'm back home from the hospital though (._.') 14:12:32 It's in a branch, not in master by the way: https://github.com/Fedora-dotnet/developer-portal-content/tree/dotnet-usage 14:12:45 Oh, alright. 14:12:47 noted 14:12:55 Yup of course axels, no worries, get better... 14:13:13 #info === [INCOMPLETE] Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration === 14:13:15 #action Rhea - create dev portal pages with example systemd service for ASP.NET Core, and example Apache/NGINX proxy configuration 14:13:37 omajid we had for you the... "write down brief instructions / guide to building and testing in the ticket #19" 14:13:44 Do we still even need that? 14:14:18 Rhea: spec file has all the instructions. if i put it in a doc, it will only diverge from the source of truth (spec file) 14:14:35 Yup okay 14:15:02 i did write up how to build in copr here: https://pagure.io/fedora-dotnet/branch/f26 14:15:07 By the way since we are talking about tickets... a design ticket #533 14:15:18 #info T-Shirts and stickers "fedoraloves.net" in progress 14:15:23 #link https://pagure.io/design/issue/533 14:15:30 nice! 14:15:52 I've sent the trademark license thing today for the domain as well, Council approved that yesterday in their meeting. 14:16:07 in a ticket #128 https://pagure.io/Fedora-Council/tickets/issue/128 14:16:13 \o/ 14:16:37 There was a bit of confusion - apparently non-dotnet-developers don't immediately get the .net TLD as a .net ... joke? 14:16:45 hehe 14:17:55 If you've not seen the redhat version, you can see a photo in my blog: http://rhea-ayase.eu/articles/2017-07/Microsoft-TechTalks-Prague 14:18:08 I'd like them to be similar, but blue heart and with Fedora labels 14:18:29 This: https://cloud.rhea-ayase.eu/s/vnMbGsZMIyDBC6w 14:18:39 :] 14:18:50 Okay err... packaging? 14:19:00 #topic Packaging progress / Open Floor discussion 14:19:02 #info === Package doesn't install on F26 (expects lldb 3.9, has lldb 4.0) === 14:19:04 #link https://pagure.io/fedora-dotnet/issue/21 14:19:18 I think that this was "can not reproduce" as of latest? 14:19:37 Rhea: more like doesnt matter now that we migrated to new copr and did rebuilds 14:19:50 okay :D 14:19:58 actually, i am going to go ahead and close it 14:20:06 Do we close it or keep it open with a note.. 14:20:08 Okay 14:20:22 i will leave a comment 14:20:50 Okay that's awesome then... 14:21:04 What was the issue with rawhide build? 14:21:55 coreclr depends on glibc internals that changed. i filed a bug upstream https://github.com/dotnet/coreclr/issues/13009 14:22:02 but no movement on that yet 14:22:18 Oh right, remember now 14:23:00 Hmm... 14:23:23 So on the topic of our new copr... can I replace all the references and update the wiki and dev.portal with it? 14:23:32 Is the 26 package fine for that? 14:23:48 Whoever got f26 go ahead and give it a test spin please :D 14:23:48 * pcreech has been playing aroudn with it, seems to work 14:24:01 generated a web-api project, and modified it with rider 14:24:06 dotnet run worked 14:24:24 * omajid has been dogfooding f26 builds for a few days now too 14:24:47 package even has man pages now :) 14:24:54 I'm gonna update my Fedora after the first august, finally 14:25:57 Okay i'll go ahead and update these pages and poke Pavel again to make it go live before the next conference x.x 14:26:48 One more thing I wanted to ask, omajid are there many issues that we need to resolve? Like... what prebuilt binaries are we still using? 14:27:20 Rhea: the build-related issues are all still valid : https://pagure.io/fedora-dotnet/pull-request/20 14:27:41 well, aside from last one. it does use upstream packaging layout now 14:28:01 but other problems still exist. bundled deps, prebuilt binaries and so on 14:28:13 yup 14:28:27 I'm happy that we got it on copr at least, not far behind RHEL \o/ 14:28:52 Hopefull we can make it relatively fast for 2.0 release as well, should be a bit easier I hope 14:30:14 #action Rhea - update the wiki and dev portal with the new copr repo. 14:30:24 Okay, lets call it then? =) 14:30:46 works for me. 14:30:49 * pcreech seconds 14:31:07 I've got nothing to add. 14:31:16 =) 14:31:19 #endmeeting