<div dir="ltr"><a href="http://meetbot.fedoraproject.org/epel/2015-01-09/epel.2015-01-09-17.00.log.html">http://meetbot.fedoraproject.org/epel/2015-01-09/epel.2015-01-09-17.00.log.html</a><br clear="all"><div><pre><span class="">17:00:44</span><span class=""> <smooge></span> <span class="">#startmeeting </span><span class="">epel</span>
<a name="l-2"></a><span class="">17:00:44</span><span class=""> <zodbot></span> Meeting started Fri Jan 9 17:00:44 2015 UTC. The chair is smooge. Information about MeetBot at <a href="http://wiki.debian.org/MeetBot">http://wiki.debian.org/MeetBot</a>.
<a name="l-3"></a><span class="">17:00:44</span><span class=""> <zodbot></span> Useful Commands: #action #agreed #halp #info #idea #link #topic.
<a name="l-4"></a><span class="">17:00:52</span><span class=""> <smooge></span> <span class="">#meetingname </span><span class="">epel</span>
<a name="l-5"></a><span class="">17:00:52</span><span class=""> <zodbot></span> The meeting name has been set to 'epel'
<a name="l-6"></a><span class="">17:01:13</span><span class=""> <smooge></span> <span class="">#chairs </span><span class="">smooge nirik dgilmore bstinson</span>
<a name="l-7"></a><span class="">17:01:28</span><span class=""> <smooge></span> Nirik I believe is going to be absent
<a name="l-8"></a><span class="">17:01:32</span><span class=""> <smooge></span> Evolution is absent
<a name="l-9"></a><span class="">17:01:51</span><span class=""> <smooge></span> and dgilmore might be on snowed in absense
<a name="l-10"></a><span class="">17:01:59 </span><span class="">* nirik</span> <span class="">is actually here right now...</span>
<a name="l-11"></a><span class="">17:02:04</span><span class=""> <nirik></span> but I might have to leave early
<a name="l-12"></a><span class="">17:02:05</span><span class=""> <smooge></span> <span class="">#topic </span><span class="">Roll Call</span>
<a name="l-13"></a><span class="">17:02:12</span><span class=""> <smooge></span> nirik, I expect this will be a short meeting
<a name="l-14"></a><span class="">17:02:17</span><span class=""> <nirik></span> cool.
<a name="l-15"></a><span class="">17:02:32</span><span class=""> <bstinson></span> hi all
<a name="l-16"></a><span class="">17:02:39</span><span class=""> <smooge></span> hi bstinson
<a name="l-17"></a><span class="">17:03:04</span><span class=""> <smooge></span> <span class="">#topic </span><span class="">Old Business</span>
<a name="l-18"></a><span class="">17:03:30</span><span class=""> <smooge></span> OK we don't have much old business from the last meeting because it was a couple of weeks ago
<a name="l-19"></a><span class="">17:03:45</span><span class=""> <smooge></span> We had the orphaning and tyll found some bugs in his script that didn't show all the orphans
<a name="l-20"></a><span class="">17:03:52</span><span class=""> <smooge></span> so we have another batch.
<a name="l-21"></a><span class="">17:04:23 </span><span class="">* bstinson</span> <span class="">hasn't had a chance to look through the email yet, how bad is it looking?</span>
<a name="l-22"></a><span class="">17:04:36</span><span class=""> <smooge></span> nirik, bstinson do we want to have another orphan day or just have tyll do them when he has a chance?
<a name="l-23"></a><span class="">17:04:48</span><span class=""> <smooge></span> bstinson, it isn't any better than it was before the last one :)
<a name="l-24"></a><span class="">17:04:54 </span><span class="">* Jeff_S</span> <span class="">here a bit late</span>
<a name="l-25"></a><span class="">17:05:16</span><span class=""> <nirik></span> did we say 6 weeks or something? or has the timeout already expired.
<a name="l-26"></a><span class="">17:05:33</span><span class=""> <smooge></span> nirik, most of these packages are over 6 weeks (some are 22)
<a name="l-27"></a><span class="">17:05:48</span><span class=""> <nirik></span> perhaps one last warn email and do them next week?
<a name="l-28"></a><span class="">17:05:57</span><span class=""> <bstinson></span> +1
<a name="l-29"></a><span class="">17:06:06</span><span class=""> <smooge></span> ok will send out an email and ask tyll to do them next week around Thursday?
<a name="l-30"></a><span class="">17:06:35</span><span class=""> <smooge></span> alright anyone else have any other old business?
<a name="l-31"></a><span class="">17:07:06</span><span class=""> <bstinson></span> none here
<a name="l-32"></a><span class="">17:07:17</span><span class=""> <nirik></span> nada
<a name="l-33"></a><span class="">17:07:30</span><span class=""> <smooge></span> ok next up
<a name="l-34"></a><span class="">17:07:35</span><span class=""> <smooge></span> <span class="">#topic </span><span class="">New Business</span>
<a name="l-35"></a><span class="">17:07:55</span><span class=""> <smooge></span> we have a non-responsive maintainer issue with kanarip
<a name="l-36"></a><span class="">17:08:21</span><span class=""> <Evolution></span> ack. sorry I'm late
<a name="l-37"></a><span class="">17:09:02</span><span class=""> <nirik></span> well, last time I talked to him he was busy, but wanted to keep being co-maintainer.
<a name="l-38"></a><span class="">17:09:05</span><span class=""> <smooge></span> ಠ_ಠ
<a name="l-39"></a><span class="">17:10:40</span><span class=""> <smooge></span> nirik, did someone make Marriane the maintainer of the package?
<a name="l-40"></a><span class="">17:11:06</span><span class=""> <nirik></span> hum? I'm not sure even what package we are talking about...
<a name="l-41"></a><span class="">17:11:09</span><span class=""> <smooge></span> .whoowns perl-XML-TreePP
<a name="l-42"></a><span class="">17:11:10</span><span class=""> <zodbot></span> <span class="">smooge:</span> kanarip
<a name="l-43"></a><span class="">17:11:39 </span><span class="">* nirik</span> <span class="">looks</span>
<a name="l-44"></a><span class="">17:11:46</span><span class=""> <nirik></span> .branches perl-XML-TreePP
<a name="l-45"></a><span class="">17:11:48</span><span class=""> <zodbot></span> <span class="">nirik:</span> el5 el6 epel7 f20 f21 master
<a name="l-46"></a><span class="">17:12:02</span><span class=""> <smooge></span> the email was about the above which he is sole maintainer of. I don't mind keeping him but since he is busy making someone a comaintainer makes sense
<a name="l-47"></a><span class="">17:12:23</span><span class=""> <nirik></span> they seem to own the epel7 branch
<a name="l-48"></a><span class="">17:12:32</span><span class=""> <nirik></span> so, I think they went ahead as they should have.
<a name="l-49"></a><span class="">17:12:51</span><span class=""> <nirik></span> You are supposed to ask the fedora maintainer, wait a week, if no answer:: drive on
<a name="l-50"></a><span class="">17:13:09</span><span class=""> <smooge></span> <a href="https://lists.fedoraproject.org/pipermail/devel/2014-December/205902.html">https://lists.fedoraproject.org/pipermail/devel/2014-December/205902.html</a>
<a name="l-51"></a><span class="">17:13:39</span><span class=""> <nirik></span> so, I think it all got sorted
<a name="l-52"></a><span class="">17:13:50</span><span class=""> <smooge></span> nirik, ah ok.. I did a whoowns which used to say something like epel7 (mmm)
<a name="l-53"></a><span class="">17:14:03</span><span class=""> <smooge></span> and it just said kanarip so I thought it was still waiting
<a name="l-54"></a><span class="">17:14:05</span><span class=""> <nirik></span> that might be cached.
<a name="l-55"></a><span class="">17:14:06</span><span class=""> <smooge></span> my apologies
<a name="l-56"></a><span class="">17:14:13</span><span class=""> <Jeff_S></span> So what was the problem? Did the bug just not have the right flag set to get attention?
<a name="l-57"></a><span class="">17:15:00</span><span class=""> <nirik></span> I think they just were waiting forever, when the policy says wait a week and then just request it.
<a name="l-58"></a><span class="">17:15:10</span><span class=""> <Jeff_S></span> ok
<a name="l-59"></a><span class="">17:15:21</span><span class=""> <nirik></span> not sure how to make that any better. ;(
<a name="l-60"></a><span class="">17:15:31</span><span class=""> <smooge></span> will put that in a blog list of how to do things in EPEL
<a name="l-61"></a><span class="">17:16:00</span><span class=""> <smooge></span> ok any other new business?
<a name="l-62"></a><span class="">17:16:09</span><span class=""> <Jeff_S></span> Yeah, I don't think that's a big deal unless it's happening to a lot of requests
<a name="l-63"></a><span class="">17:16:59</span><span class=""> <nirik></span> more docs/blog posts on it should possibly help
<a name="l-64"></a><span class="">17:18:48</span><span class=""> <smooge></span> I am working on a couple.. I hope to get some time this weekend to get them out
<a name="l-65"></a><span class="">17:19:05</span><span class=""> <smooge></span> ok any other business we need to deal with?
<a name="l-66"></a><span class="">17:19:19</span><span class=""> <smooge></span> <span class="">#topic </span><span class="">Next Meeting Agenda Items</span>
<a name="l-67"></a><span class="">17:19:46</span><span class=""> <smooge></span> Ok please put in anything we want to have in the next meeting or thought about in coming meetings
<a name="l-68"></a><span class="">17:19:47</span><span class=""> <nirik></span> there was another person asking about the epel-release permlink again
<a name="l-69"></a><span class="">17:19:58</span><span class=""> <smooge></span> yeah.. another roundtuit I need to get on
<a name="l-70"></a><span class="">17:20:13</span><span class=""> <Jeff_S></span> ++ :)
<a name="l-71"></a><span class="">17:20:34</span><span class=""> <smooge></span> I hope to look at it next week
<a name="l-72"></a><span class="">17:20:47</span><span class=""> <Jeff_S></span> Thanks
<a name="l-73"></a><span class="">17:21:05</span><span class=""> <bstinson></span> should we brainstorm some topic ideas for the CentOS-EPEL meetup at fosdem?
<a name="l-74"></a><span class="">17:21:15</span><span class=""> <Jeff_S></span> <span class="">bstinson:</span> sure, rub it in...
<a name="l-75"></a><span class="">17:22:31 </span><span class="">* nirik</span> <span class="">notes he will not be there, but will be around on irc if needed.</span>
<a name="l-76"></a><span class="">17:22:38</span><span class=""> <Jeff_S></span> I've gotta run, thanks all
<a name="l-77"></a><span class="">17:22:47</span><span class=""> <bstinson></span> was hoping we could live stream it :) but i'm not sure if that's possible
<a name="l-78"></a><span class="">17:23:23</span><span class=""> <Evolution></span> yeah, sadly some of the key players won't be there
<a name="l-79"></a><span class="">17:23:28</span><span class=""> <Evolution></span> nirik, smooge, etc.
<a name="l-80"></a><span class="">17:24:25</span><span class=""> <smooge></span> yeah.. I think we are going to do better just having a public google hangout or something than try to do something at an event most can't get to
<a name="l-81"></a><span class="">17:24:51</span><span class=""> <smooge></span> not that I have been any better with some of the EPEL meetings at Flock/FUDcon when CentOS people couldn't attend
<a name="l-82"></a><span class="">17:26:14</span><span class=""> <smooge></span> so lets just say we need to come up with things for those who can make it to talk about and move on
<a name="l-83"></a><span class="">17:27:22</span><span class=""> <smooge></span> bstinson, most of the topics I would want to talk about sort of need the rest of EPEL do'ers on to better converse. Otherwise it could end up like my EPIC proposal.. lots of good ideas but no buy-in
<a name="l-84"></a><span class="">17:29:08</span><span class=""> <bstinson></span> that makes sense, it would be nice to do a hangout sometime
<a name="l-85"></a><span class="">17:29:35</span><span class=""> <smooge></span> ok lets see if we can get that arranged.
<a name="l-86"></a><span class="">17:29:57</span><span class=""> <smooge></span> anything else? I think we will lose nirik soon
<a name="l-87"></a><span class="">17:31:26</span><span class=""> <smooge></span> <span class="">#topic </span><span class="">Open Flood</span>
<a name="l-88"></a><span class="">17:31:36</span><span class=""> <smooge></span> Ok last call on topics and things to talk about.
<a name="l-89"></a><span class="">17:31:38</span><span class=""> <smooge></span> Last call
<a name="l-90"></a><span class="">17:31:51</span><span class=""> <bstinson></span> nothing here
<a name="l-91"></a><span class="">17:31:57 </span><span class="">* smooge</span> <span class="">wonders if Evolution will wake up to those words</span>
<a name="l-92"></a><span class="">17:32:09</span><span class=""> <Evolution></span> I'm here
<a name="l-93"></a><span class="">17:32:15</span><span class=""> <Evolution></span> I have nothing to contribute, but I'm here.
<a name="l-94"></a><span class="">17:32:19</span><span class=""> <dgilmore></span> sorry guys I slept in
<a name="l-95"></a><span class="">17:32:46</span><span class=""> <smooge></span> oh man.. I had a whole bar closing thing typed in too
<a name="l-96"></a><span class="">17:32:51</span><span class=""> <dgilmore></span> I should be at fosdem
<a name="l-97"></a><span class="">17:33:14</span><span class=""> <smooge></span> dgilmore, can you make the EPEL-CentOS meetup?
<a name="l-98"></a><span class="">17:33:23</span><span class=""> <dgilmore></span> <span class="">smooge:</span> should be able to yes
<a name="l-99"></a><span class="">17:34:38</span><span class=""> <smooge></span> cool. that should help answer some of the questions about build systems that will come up
<a name="l-100"></a><span class="">17:34:59</span><span class=""> <smooge></span> Evolution, do you know whats on kbsingh's mind for the meeting?
<a name="l-101"></a><span class="">17:35:17</span><span class=""> <Evolution></span> I believe interoperability.
<a name="l-102"></a><span class="">17:35:47</span><span class=""> <Evolution></span> packages that should be in epel coming from sigs, etc.
<a name="l-103"></a><span class="">17:36:09</span><span class=""> <dgilmore></span> for me its interoperability and working on finding ways to enable people to contribute to epel via either CentOS or Fedora
<a name="l-104"></a><span class="">17:37:10</span><span class=""> <smooge></span> ok I think then that if everything gets recorded we can get some stuff done then
<a name="l-105"></a><span class="">17:38:32</span><span class=""> <smooge></span> dgilmore, anything you want in the next meeting?
<a name="l-106"></a><span class="">17:39:56</span><span class=""> <dgilmore></span> <span class="">smooge:</span> we should look at the policy for branching packages from Fedora
<a name="l-107"></a><span class="">17:40:37</span><span class=""> <smooge></span> dgilmore, yes I agree. It comes up a lot
<a name="l-108"></a><span class="">17:40:49</span><span class=""> <dgilmore></span> It seems many people are not aware of it and quite a lot of people just go and request branches for packages. I had it happen to one of mine recently
<a name="l-109"></a><span class="">17:41:32 </span><span class="">* nirik</span> <span class="">wonders if we can somehow automate it.</span>
<a name="l-110"></a><span class="">17:41:56</span><span class=""> <dgilmore></span> when emailing the person that branched my package they thought anyone was free to branch any package
<a name="l-111"></a><span class="">17:42:12</span><span class=""> <dgilmore></span> <span class="">nirik:</span> we should find a way to do it
<a name="l-112"></a><span class="">17:42:40</span><span class=""> <dgilmore></span> <span class="">nirik:</span> moving branching into pkgdb should give us a way to do so
<a name="l-113"></a><span class="">17:42:43</span><span class=""> <nirik></span> yeah...
<a name="l-114"></a><span class="">17:44:02</span><span class=""> <smooge></span> ok so something for me to put on next weeks agenda? Can pkdb fix all our problems?
<a name="l-115"></a><span class="">17:44:22</span><span class=""> <dgilmore></span> <span class="">smooge:</span> its work that is underway
<a name="l-116"></a><span class="">17:45:08</span><span class=""> <dgilmore></span> we probably should make sure we get all the policy right then palk to pingu and make sure we automate the checks
<a name="l-117"></a><span class="">17:45:33</span><span class=""> <smooge></span> ok so I am not clear on how policy should be worded.. any examples and I can make a pass at something for EPEL?
<a name="l-118"></a><span class="">17:46:01</span><span class=""> <dgilmore></span> i think the existing polic is fine
<a name="l-119"></a><span class="">17:46:26</span><span class=""> <dgilmore></span> we need to reaffirm it and make sure its visable and people are aware of it
<a name="l-120"></a><span class="">17:47:04</span><span class=""> <dgilmore></span> automated enforcement would help with making people aware
<a name="l-121"></a><span class="">17:47:31</span><span class=""> <smooge></span> And the exisitng policy is the one you listed in the email yesterday?
<a name="l-122"></a><span class="">17:47:51</span><span class=""> <dgilmore></span> <a href="http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL">http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL</a>
<a name="l-123"></a><span class="">17:47:53</span><span class=""> <dgilmore></span> correct
<a name="l-124"></a><span class="">17:48:13</span><span class=""> <dgilmore></span> packagers can opt out of epel
<a name="l-125"></a><span class="">17:48:37</span><span class=""> <dgilmore></span> in which case people can freely request a branch
<a name="l-126"></a><span class="">17:49:18</span><span class=""> <smooge></span> and from what nirik said earlier.. if the packager doesn't respond in a week they can branch anyway?
<a name="l-127"></a><span class="">17:49:49</span><span class=""> <dgilmore></span> yep
<a name="l-128"></a><span class="">17:50:25</span><span class=""> <dgilmore></span> the one thing i think we could add is that sometimes a package really doesnt make sense in epel
<a name="l-129"></a><span class="">17:50:35</span><span class=""> <dgilmore></span> and there should be a way to say so
<a name="l-130"></a><span class="">17:50:48</span><span class=""> <smooge></span> yeah
<a name="l-131"></a><span class="">17:51:20</span><span class=""> <smooge></span> ok I will ponder how to do that and come back next meeting on it
<a name="l-132"></a><span class="">17:51:29</span><span class=""> <dgilmore></span> cool
<a name="l-133"></a><span class="">17:51:34</span><span class=""> <dgilmore></span> i have nothing else
<a name="l-134"></a><span class="">17:51:41</span><span class=""> <smooge></span> ok me either..
<a name="l-135"></a><span class="">17:51:47</span><span class=""> <smooge></span> my dog says I need to walk her
<a name="l-136"></a><span class="">17:51:51</span><span class=""> <smooge></span> so ..
<a name="l-137"></a><span class="">17:51:54</span><span class=""> <smooge></span> <span class="">#endmeeting</span></pre></div>-- <br><div class="gmail_signature"><div dir="ltr">Stephen J Smoogen.<br><br></div></div>
</div>