EPEL meeting minutes
by Stephen John Smoogen
17:00:57 <smooge> #startmeeting EPEL
17:00:57 <zodbot> Meeting started Fri Apr 24 17:00:57 2015 UTC. The chair
is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link
#topic.
17:01:02 <smooge> #meetingname epel
17:01:02 <zodbot> The meeting name has been set to 'epel'
17:01:14 <smooge> #chairs avij nirik bstinson dgilmore Evolution
17:01:22 <smooge> #chair avij nirik bstinson dgilmore Evolution
17:01:22 <zodbot> Current chairs: Evolution avij bstinson dgilmore nirik
smooge
17:01:40 <smooge> #topic Robot Roll Call
17:01:49 <smooge> Tom Servo here as your majordomo
17:01:57 <nirik> hey all
17:02:13 <bstinson> yay epel meeting!
17:03:13 <Evolution> here.
17:03:31 <smooge> #topic New Meeting Time
17:04:00 <smooge> So one of the issues with EPEL meetings is trying to find
a time where they can occur when people are able to focus on them versus
other scheduled tasks
17:04:26 <nirik> always a struggle with all meetings.
17:04:55 <smooge> lesson 1. whenisgood.com is not the place for me to set
this up. whenisgood.net is the correct place
17:05:14 <smooge> does anyone currently have a whenisgood account?
17:05:38 <nirik> nope. There was also some more open source one someone
mentioned a while back, but I can't recall the name now
17:08:48 <nirik> http://doodle.com/
17:08:51 <nirik> I think that was it
17:11:07 <smooge> lesson 2. these things are pain in the ass
17:11:32 <nirik> yeah
17:12:04 <bstinson> ^^this, /me is digging to see if i have an old doodle
account
17:12:25 <smooge> bstinson, you ok setting up the invitations? Or do you
want me to?
17:13:06 <bstinson> if you're already in go ahead, i'm waiting on a
password reset email from doodle
17:15:50 <smooge> I am not setting up an account but was doing the complete
free thing
17:18:00 <smooge> could someone pm me avij's email
17:19:34 <smooge> .fasinfo avij
17:19:35 <zodbot> smooge: User: avij, Name: Anssi Johansson, email:
rhbugs(a)miuku.net, Creation: 2012-06-16, IRC Nick: avij, Timezone:
Europe/Helsinki, Locale: en, GPG key ID: , Status: active
17:19:38 <zodbot> smooge: Approved Groups: cla_fpca cla_done
17:20:39 <smooge> ok so the poll in doodle is absolutely useless from the
free account settings
17:20:46 <smooge> I can only ask you what day to use
17:20:56 <nirik> ah, bah
17:20:58 <Evolution> that's... suboptimal
17:21:18 <smooge> bstinson, might have more options when his account gets
reopened
17:21:36 <smooge> ok I will work on something but let us move to the next
time
17:21:41 <smooge> s/time/item/
17:21:46 <bstinson> you can action that to me
17:21:51 <bstinson> still waiting on the reset email
17:22:13 <smooge> #action bstinson will create meeting invite for upcoming
meetings in doodle or whenisgood depending on what is possible
17:22:54 <smooge> bstinson, please use UTC so people don't have to deal
with "did this send in my time zone or bstinson's timezone" type worries
17:23:12 <smooge> #topic New Chair System
17:23:36 * nirik proposed rotating chair on the list.
17:23:41 <nirik> what do folks think?
17:23:58 <smooge> I personally think that this is a good idea
17:24:14 <bstinson> i think that would spread out the load a little bit
17:24:16 <Evolution> worksforme
17:24:16 <bstinson> +1 from me
17:25:01 <smooge> 3 votes for rotating chair, 2 abstains
17:25:29 <smooge> #agreed EPSCO will use rotating chair system to host
future meetings. 3 +1 votes 2 abstains
17:25:48 <smooge> #topic Status of python3
17:26:03 <smooge> nirik, I think you had some status on this
17:26:05 <nirik> I need to work on epel-rpm-macros.
17:26:08 <nirik> it's still on my list.
17:26:15 <nirik> just havent had time
17:26:36 <smooge> okie dokie
17:26:47 <nirik> so, thats all really... will try and get er done
17:26:52 <smooge> #topic Open Floor
17:26:59 <smooge> Any other issues?
17:27:27 <Evolution> are there anough packages to warrant another killing
spree
17:27:32 <Evolution> *orphaned*
17:28:30 <Evolution> also, is there any reason for epel-specific
involvement in the upcoming FAD?
17:28:45 <Evolution> </end random thought from my side>
17:29:00 <nirik> I think tyll_ has been culling orphans with the >6weeks
orphaned thing still.
17:29:07 <nirik> and we are getting down to a small list.
17:29:35 <Evolution> oh, I didn't realize he was actively dealing with it.
that's good news.
--
Stephen J Smoogen.
9 years
Meeting Logs for 2015-04-17
by Stephen John Smoogen
Hi we held a meeting
===========
#epel: EPEL
===========
Meeting started by nirik at 17:00:11 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/epel/2015-04-17/epel.2015-04-17-17.00....
.
Meeting summary
---------------
* roll call (nirik, 17:00:32)
* avij will replace smooge on the committee at the end of this session
(smooge, 17:18:00)
* avij will replace smooge on the committee at the end of this session
(+4 votes/1 absent) (smooge, 17:20:38)
* Python 3 (smooge, 17:20:47)
* XFCE 4.12 in EL7 (smooge, 17:25:38)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1201124 (nirik,
17:28:37)
* https://bugzilla.redhat.com/show_bug.cgi?id=1201124 tracker bug for
XFCE-4.10 in EL-7 (smooge, 17:29:56)
* Third party repos with CentOS and EPEL (smooge, 17:34:54)
* LINK: https://gist.github.com/cgtx/b854281462a18007f509
(Evolution, 17:35:36)
* LINK:
http://lists.centos.org/pipermail/centos-devel/2015-April/013180.html
(bstinson, 17:40:19)
* open floor. (smooge, 17:45:24)
Meeting ended at 17:49:23 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* smooge (65)
* nirik (53)
* Evolution (34)
* bstinson (9)
* dgilmore (7)
* zodbot (6)
* avij (5)
* carlgeorge (3)
* orionp (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
http://meetbot.fedoraproject.org/epel/2015-04-17/epel.2015-04-17-17.00.lo...
--
Stephen J Smoogen.
9 years
Call for EPEL meeting Agenda Items 2015-04-17
by Stephen John Smoogen
We will be having a meeting of the EPEL Steering Committee on 2015-04-17 at
17:00:00 UTC in Freenode IRC channel #epel
To determine what time that is in your timezone please use the following
command:
$ date -d '2015-04-17 17:00:00 UTC'
Fri Apr 17 11:00:00 MDT 2015
Items to be discussed:
1. Replacing Stephen Smoogen on EPSCO board.
2. XFCE 4.12 in EPEL-7?
3. Python-3 in EPEL-6/7?
--
Stephen J Smoogen.
9 years
Open Slot on EPEL Steering Committee
by Stephen John Smoogen
I am stepping down from the EPSCO for a time and we have a slot open for
someone to sit on the EPSCO and help the project. While I am currently the
chair it is more of a 'pass around the baton' seat. Please cc on this email
if you are interested.
Time commitments are up to 1 hour meeting per week and helping various
packages get into or out of EPEL.
http://fedoraproject.org/wiki/EPEL_Steering_Committee
The EPEL Steering Committee tries to work in the open and doesn't want to
use it's influence as governing body. That means:
if you want to do something "new" in EPEL-land just tell the others about
it on the mailing list about it. If nobody yells for a few days consider
you plans accepted and go ahead
Topics in EPEL-land are discussed and decided in open-to-all IRC meetings
and on the mailing lists; all EPEL contributers can send in their vote ot
their options via mail if they cannot make the meeting.
Important topics are discussed on the list (
epel-devel(a)lists.fedoraproject.org) before they being voted upon. The goal
is to find a consensus that seems to works for the majority of people
involved.
Meeting summaries are sent to the meeting list, epel-devel and epel-users
lists.
Decisions made by the EPEL steering committee may be re-discussed in FESCo
meetings, if necessary. FESCo retains authority over EPEL decisions and can
exercise a veto on a voted-upon topic. FESCo can exercise this veto in the
FESCo meeting that follows the release of the public summary that included
the decision under veto. FESCo is guaranteed at least 24 hours for
research, deliberation, and discussion, regardless of meeting schedules.
This procedure is similar to the interaction between FESCo and the
Packaging Committee.
Each point that receives strong opposition on the list after it got decided
will get revisited once in the next meeting if someone asks for it
if it comes to hard decisions where no agreement can be found only the
votes from the steering committee members count; for an item under vote to
gain approval, a minimum of four members must agree on it to form a
consensus. If that can't be reached (contentious votes where people are
abstaining can create such situations) then all Steering Committee members
have to vote and then the majority of votes wins. The goal is to have a
consensus between Committee members; sometimes that isn't possible.
The EPEL Steering Committee does not handle issues around theoretical
Packaging, for example, everything around writing specfiles. This is the
purview of the Packaging Committee to manage. On the other hand, practical
packaging, for example, maintenance and update policy for EPEL, is
regulated by the EPEL Steering Committee.
The goal is to let the EPEL Steering Committee work on it's own, that is,
without FESCo involvement, for all things that are specific to EPEL.
Sometimes it might be necessary to solve issues hand-in-hand with FESCo or
other SIGs, for example, resolving conflicts between EPEL and the Packaging
Committee.
General discussions occur on-list before voting. However, large-scale and
controversial topics require extra care. To make sure all steering
committee, SIG, and community members have time to provide their voice on a
topic, scheduled votes on such topics are announced 24-hours in advance of
the vote. Small items may be brought to vote in a meeting or on-list
without a prior announcement; this keeps the project moving swiftly without
needless bureaucracy. Decisions may always be revisited, if there is a need
to.
Steering Committee Chair
The EPEL Steering Committee is conducted by the Steering Committee
Chairmen. The chair's responsibilities are:
Keep the pieces together
Prepare and run the SIG meetings
Issue and coordinate the votings in the meetings and in the wiki, to
prevent chaos that might arise if anybody would issue votings
Write the meeting and general "what happened" summaries, then send the to
the list and FESCo for discussion
Report to FESCo, try to be available for questions in FESCo meetings and on
the lists
Make sure all requests on the mailing lists regarding EPEL feel heard
Make sure EPEL is running fine, which includes "make contributors and users
happy"
Note that the chair doesn't have to do all of the above personally. The
chair is responsible for making sure someone does these roles. ;-)
--
Stephen J Smoogen.
9 years