19:02:44 <Rhea> #startmeeting Fedora DotNet (2017-03-07)
19:02:44 <zodbot> Meeting started Tue Mar  7 19:02:44 2017 UTC.  The chair is Rhea. Information about MeetBot at
19:02:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:02:44 <zodbot> The meeting name has been set to 'fedora_dotnet_(2017-03-07)'
19:02:49 <Rhea> #meetingname dotnet
19:02:49 <zodbot> The meeting name has been set to 'dotnet'
19:03:02 <Rhea> #nick dotnet
19:03:08 <Rhea> #chair <given to approved members of FAS group at meeting>
19:03:08 <zodbot> Current chairs: <given FAS Rhea approved at group meeting> members of to
19:03:12 <Rhea> #topic Agenda
19:03:20 <Rhea> #link
19:03:31 <Rhea> #info (1) Roll Call
19:03:33 <Rhea> #info (2) Announcements
19:03:42 <Rhea> #info (3) Action items and Tickets
19:03:44 <Rhea> #info (4) Packaging progress
19:03:47 <Rhea> #info (5) GSoC
19:03:58 <Rhea> #topic Roll Call
19:04:00 <Rhea> #info Name; Timezone; Sub-projects/Interest Areas
19:04:06 <Rhea> #action dotnet New members, make sure you introduce yourself on the DotNet mailing list [ ]
19:04:14 <Rhea> 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.
19:04:54 <nmilosev> .fas nmilosev
19:04:55 <zodbot> nmilosev: nmilosev 'Nemanja Milosevic' <>
19:05:13 <omajid> hello!
19:05:26 <tmds> hi everyone
19:05:39 <amitosh> Hi
19:05:48 <Rhea> .hello rhea
19:05:49 <zodbot> Rhea: rhea 'Radka Janek' <>
19:05:56 <Rhea> #info Radka Janek; UTC+1; CommOps, Diversity, DotNet,...
19:06:24 <Rhea> Not sure if anyone else shows up o.o
19:06:25 <amitosh> #info Amitosh Swain Mahapatra; UTC+5:30; DotNet, Python, Go, Docs
19:06:33 <nb> .hello nb
19:06:35 <zodbot> nb: nb 'Nick Bebout' <>
19:07:01 <Rhea> uaaa whitespace python!
19:07:05 * Rhea runs away from amitosh
19:07:39 <tmds> .hello tmds
19:07:40 <zodbot> tmds: tmds 'Tom Deseyn' <>
19:08:17 <Rhea> #topic Announcements
19:08:19 <Rhea> #info === "Announcing .NET Core Tools 1.0" ===
19:08:22 <bt0> .hello bt0dotninja
19:08:23 <zodbot> bt0: bt0dotninja 'Alberto Rodriguez Sanchez' <>
19:08:26 <Rhea> #link
19:08:33 <Rhea> #info VS2017:
19:08:41 <Rhea> #info === "1.0.4 & 1.1.1 release" ===
19:08:46 <Rhea> #link
19:08:50 <Rhea> #link
19:09:09 <Rhea> Anything else? =)
19:09:28 <nmilosev> #link
19:09:36 <nmilosev> :)
19:09:40 <Rhea> well that's not an announcement :D
19:09:50 <nmilosev> f26 forked, so we are building also for f27! :D
19:09:50 <Rhea> And you didn't give it a title :P
19:09:58 <nmilosev> darn
19:10:14 <Rhea> I have it in tickets..
19:10:16 <Rhea> #undo
19:10:16 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x3d320c10>
19:10:21 <Rhea> #topic Action items and Tickets
19:10:29 <Rhea> #link
19:10:32 <Rhea> #link
19:10:37 <Rhea> #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.
19:10:52 <Rhea> #info === [COMPLETE] nmilosev create dotnet-sig copr repository for our current and future packages. ===
19:10:57 <Rhea> nmilosev: paste it please :D
19:11:07 <nmilosev> #link
19:11:22 <Rhea> Also about this one...
19:11:24 <Rhea> #info === [INCOMPLETE] nmilosev create a ticket tracking source build for f26 (25) ===
19:11:44 <Rhea> I suppose given the time, we can make it "for F25-27" or ... whatever, just generally source build
19:11:56 <nmilosev> forgot that one, sorry, but no progress so far, apart from a few emails with MS
19:12:03 <nmilosev> nothing new
19:12:06 <Rhea> no worries hehe
19:12:21 <nmilosev> Just a note here:
19:12:45 <nmilosev> For the 1.1.1 and 1.0.4, we *should* be able to build them with rover and provide an update, also new tools, correct?
19:12:54 <nmilosev> I only need change commit id's
19:13:11 <Rhea> Yes, if that's what the current package was (i'm a little confused which one was which)
19:13:19 <Rhea> the -clean was rover, -sig is -clean ?
19:13:30 <Rhea> i think
19:13:33 <nmilosev> yep
19:13:36 <nmilosev> same SRPM even
19:13:50 <nmilosev> I will try to build it for the next meeting, you can action it.
19:13:52 <Rhea> Yeah just a quick update hopefully without any issues
19:14:11 <Rhea> Do we even have 1.0?
19:14:14 <nmilosev> However, we will probably need new payload from omajid
19:14:21 <nmilosev> We don't have 1.0 now
19:14:26 <Rhea> #action nmilosev update packages to 1.1.1
19:14:43 <Rhea> #action omajid fetch new stuffs for nmilosev for 1.1.1
19:14:45 <Rhea> :D
19:14:49 <Rhea> Like that?
19:14:59 <Rhea> Sorry i'm in slightly crazy mood heehe:P
19:15:07 <nmilosev> We maybe don't need it, if we can build 1.1.1 with 1.1.0
19:15:12 <nmilosev> I will try
19:15:13 <omajid> RHEL packages are blocked because of compatiblity/support concerns :(
19:15:56 <Rhea> #action nmilosev create a tracking ticket for future source build (F25+)
19:15:56 <omajid> nmilosev: rover only builds parts of corefx and coreclr. afaik you wont get all the fixes in 1.1.1 if you use rover.
19:16:14 <nmilosev> omajid: what about sdk?
19:16:19 <nmilosev> that get carried over
19:16:20 <nmilosev> ?
19:16:36 <Rhea> Well maybe it's time to go all source?
19:16:53 <nmilosev> Rhea: really difficult since only F23 is doable
19:17:02 <omajid> last i looked rover took everything from the original payload and replaced the native parts of corefx and coreclr. sdk gets carried over too, i think.
19:17:15 <omajid> rover is more for solving bootstrapping issues, not for actual builds, i think.
19:17:17 <Rhea> nmilosev: i might be able to help, finally free of nonsnese called life
19:17:32 <omajid> free of .. life?
19:17:47 <Rhea> Hmm... Yes.
19:17:55 * Rhea makes serious face.
19:18:02 <Rhea> :D
19:18:04 <nmilosev> vampiress
19:18:07 <nmilosev> :D
19:18:11 <Rhea> #info === [COMPLETE] Rhea issue to dotnet/core-setup - Linux Packaging ===
19:18:13 <Rhea> #link
19:18:24 <nmilosev> Shall I split the package
19:18:36 <Rhea> Dude don't even joke about it, i bought new vibrant red makeup for blood, got a new dress, etc... going to a party as a vampire in two weeks :D
19:18:42 <nmilosev> sdk in a separate one?
19:19:08 <Rhea> Well if you see my last comment... we can aim towards that, will see if anyone has some other ideas, if we can improve it...
19:19:22 <Rhea> In our case it would be `dotnet-devel` I suppose
19:19:30 <nmilosev> Okay, let's wait then until a consensus is reached
19:19:41 <nmilosev> yeah: dotnet == runtime, dotnet-devel == sdk
19:19:47 <nmilosev> dotnet-devel requires dotnet
19:19:56 <nmilosev> seems cool if it like that
19:19:59 <amitosh> +1 for dotnet-devel
19:20:18 <amitosh> seems consistent, most other SDKs follow this
19:20:49 <amitosh> (though they are C++ headers etc, etc)
19:21:09 <omajid> if upstream suggests calling it dotnet-sdk, i suggest going with that over -devel.
19:21:35 <rkieley> +1 for following upstream
19:21:47 <tmds> +1
19:21:50 * pcreech late :(
19:22:11 <nmilosev> yeah, if everyone is calling it sdk, however -devel is more fedora-like
19:22:25 <Rhea> Yup omajid that's why I'm bringing that option there, that it can be swapped for -dev or -devel as per distros conventions
19:22:43 <Rhea> I'd like to come to some guidelines in that ticket
19:22:54 <Rhea> So it's more consistent between different distributions
19:23:05 * omajid understood that ticket as literally suggesting dotnet-sdk, not dotnet-devel or dotnet-dev
19:24:52 <omajid> i suggest deferring the naming until that ticket is resolved, then.
19:25:03 <Rhea> Yup
19:25:04 <Rhea> that
19:25:17 <nmilosev> omajid, yes
19:25:25 <Rhea> Sooo
19:25:32 <Rhea> #topic Packaging progress
19:25:42 <Rhea> Do we actually have anything here since last time?
19:25:53 <nmilosev> I have a question
19:25:54 <Rhea> Source-build-wise you said  you didn't have time right nmilosev
19:25:57 <Rhea> ASK!!
19:26:03 <nmilosev> so sdk is 1.0.0
19:26:03 <Rhea> >_<
19:26:08 <nmilosev> how do we actually get it
19:26:11 <nmilosev> in f25
19:26:20 <nmilosev> apart from taking it from binary ms packages
19:26:21 <Rhea> By... waiting for nmilosev to build it.
19:26:25 <Rhea> xD
19:26:28 <nmilosev> Rhea who's that guy :D
19:26:35 <Rhea> I don't know!
19:26:52 <nmilosev> Seriously though :(
19:27:01 <Rhea> Nah seriously tho we can look at it some time this week, ping me on telegram to be sure that i get it (not always on irc)
19:27:06 <nmilosev> Up until now, we god our sdk from rhel build
19:27:09 <nmilosev> got*
19:27:13 <Rhea> We can pick it up issue by issue
19:27:59 <nmilosev> okay, hopefully I will have time to look into it
19:28:05 <nmilosev> Oh, hey another thing
19:28:13 <nmilosev> does this work
19:28:16 <nmilosev> .fasinfo nmilosev
19:28:18 <zodbot> nmilosev: User: nmilosev, Name: Nemanja Milosevic, email:, Creation: 2015-11-06, IRC Nick: nmilosev, Timezone: Europe/Belgrade, Locale: en, GPG key ID: F8E8597F4E08DC87A6EF90BCE7E2F6DBB9CB3A1D, Status: active
19:28:21 <zodbot> nmilosev: Approved Groups: fedorabugs packager campusambassadors ambassadors freemedia cla_done cla_fpca
19:28:29 * nmilosev is a packager now
19:28:40 <nmilosev> :)
19:28:53 <omajid> congrats!
19:29:04 <Rhea> Oh already?
19:29:14 <Rhea> Join our FAS group then, and err...
19:29:21 <Rhea> dotnet-packagers list
19:29:24 <nmilosev> I went and packaged a smaller package, to see how the process is
19:29:35 <nmilosev> thanks omajid!
19:31:11 <Rhea> #topic GSoC
19:31:16 <Rhea> uaaa
19:31:28 <Rhea> There are about... three or four I think students interested
19:31:37 <nmilosev> wow!
19:31:39 <Rhea> I believe that it's 2/2 split for the ideas
19:31:49 <Rhea> + nmilosev whom I don't count as a student lol
19:31:52 <Rhea> :D
19:31:56 <nmilosev> aww
19:32:54 <nmilosev> Rhea: when are the applications starting?
19:32:56 <amitosh> A GSoC student is here ...
19:33:01 <amitosh> March 20
19:33:07 <Rhea> =)
19:33:12 <Rhea> Yup indeed, 20th
19:33:45 <Rhea> In the meantime as I replied to a few of them/you - I recommend getting familiar with the application process
19:34:11 <Rhea> #link
19:34:30 <Rhea> And the usual suspects - we will be using git, you should know that, no big deal...
19:34:46 <Rhea> And you should know something about C# and in case of the systemd thing, be familiar with that / dbus
19:34:59 <Rhea> Cause that idea is a bit tougher than the one
19:35:10 <Rhea> Anyway, any questions about GSoC/
19:35:13 <Rhea> ?
19:35:19 <nmilosev> Is it possible to apply for more than one project?
19:35:26 <nmilosev> (and get only one)
19:35:27 <amitosh> Proposal format?
19:35:31 <Rhea> Not sure there... jwf you still here?
19:35:39 * jwf peeks in
19:35:43 * Rhea summoning Justin
19:35:48 <Rhea> HI
19:35:56 <Rhea> There, question, if you have an answer
19:35:57 <amitosh> nmilosev: Got the same question
19:36:14 <jwf> nmilosev: I don't think it would be an issue to put another proposal in so long as it's before March 20th. Just know that there's a chance there might not be enough student slots we receive from Google for all project ideas.
19:36:28 <jwf> I would just try to expedite getting a new project idea onto the wiki before March 20.
19:36:35 <Rhea> It's more of a student side question
19:36:41 <Rhea> whether the student can apply for two
19:36:45 <jwf> Oh, *apply for*
19:36:48 <jwf> Hmmm.
19:37:11 <amitosh> So If I opt to apply for 2 different Fedora projects, is it okay?
19:37:32 <jwf> I think it's possible, so long as the applicant communicates this up front to both mentors during the application process. What we don't want to do is accept the same student for two different projects. I would make this clear to both project mentors when going through the application process.
19:37:59 <jwf> Just know that you can only be accepted for one project (and the application is pretty intense just for one)!
19:38:14 <jwf> I would suggest it as a better aim and focus of your time to go for a single project instead of two.
19:38:27 <jwf> Otherwise, you'll have to apply for both, and you have to create a timeline for both project proposals.
19:38:49 <nmilosev> Nah, getting one is great, but I wondered if one can apply for more than one.
19:39:06 <nmilosev> And do only one.
19:39:51 <Rhea> heehe
19:39:55 <amitosh> Google says you can apply upyo 5, but as jwf said, writing a proposal for a single project is quite a difficult task
19:39:59 <Rhea> Like bigger chances
19:40:13 <amitosh> s/upyo/upto/
19:40:35 * amitosh shooed python away from the head
19:41:44 <Rhea> =]
19:41:49 <Rhea> Anything else guys?
19:42:17 <Rhea> theee end in 3 seconds
19:42:37 <amitosh> I have some questions about the systemd idea
19:42:52 <amitosh> wondering if it should be discussed here
19:44:19 <Rhea> Well, here or in our channel anytime, but i'm leaving after this meeting is over
19:44:29 <Rhea> (i'm in the office, i have to go home!)
19:45:02 <Rhea> #endmeeting