Hi all!
The goal is to do most work to organize EPEL (aka "keep EPEL running and improve it in the long run") on the list and just a bit the meetings; there is also the EPEL mantra "Power to the people with no delay." and "make Steering Committee nearly unimportant" -- those mean in other words: if you want to improve/realize something in EPEL you don't need to be part of the steering committee to realize it; just post to the list, ask for options, act in the open and if you got positive feedback and if nobody yells after a few days consider your plans kind of accepted normally.
But EPEL has a steering committee and needs one if it comes to "somebody needs to do a decision how to move forward" situations. The goal was to have seven members in the EPEL Steering Committee, but for some months we were only six: http://fedoraproject.org/wiki/EPEL/SteeringCommittee
Another member from the Steering committee plans to leave sooner or later (likely sooner afaics). That means we have two vacant seats now that we should fill. We could do a election for these seats or even do a real Steering Committee election like FESCo does, but I think the number of people that want to join the Steering committee is quite small and the overhead of a election is not worth the trouble.
Thus I'd suggest: if you want to be part of the EPEL steering committee then please self-nominate (either a reply in private or on the list; or join the meeting tomorrow). Then we form a new steering committee out of the existing members and those that self-nominated. If the total number of people in the Committee is a bit bigger then 7 in the end we just live with it if that's fine for everybody. Same if it's a bit smaller (like it's now).
How much work is it to be on the Steering Committee? Well, the answer depends on the fact how good you'd like to do the job. But here are some of the things that Steering Committee members IMHO should do:
- make sure EPEL most contributers and users are happy
- make sure EPEL runs well
- try to improve EPEL in the long run
- do do the above you should try to join the meetings now and then and participate in the discussions on the list
Cu knurd
On Jan 29, 2008 11:53 AM, Thorsten Leemhuis fedora@leemhuis.info wrote:
Hi all!
The goal is to do most work to organize EPEL (aka "keep EPEL running and improve it in the long run") on the list and just a bit the meetings; there is also the EPEL mantra "Power to the people with no delay." and "make Steering Committee nearly unimportant" -- those mean in other words: if you want to improve/realize something in EPEL you don't need to be part of the steering committee to realize it; just post to the list, ask for options, act in the open and if you got positive feedback and if nobody yells after a few days consider your plans kind of accepted normally.
But EPEL has a steering committee and needs one if it comes to "somebody needs to do a decision how to move forward" situations. The goal was to have seven members in the EPEL Steering Committee, but for some months we were only six: http://fedoraproject.org/wiki/EPEL/SteeringCommittee
I didn't know there was an empty seat. I can volunteer my time for this at this point.
On Tue, 29 Jan 2008 12:04:58 -0700 "Stephen John Smoogen" smooge@gmail.com wrote:
I didn't know there was an empty seat. I can volunteer my time for this at this point.
I will second smooge's self nomination.
2008/1/29 Jesse Keating jkeating@redhat.com:
On Tue, 29 Jan 2008 12:04:58 -0700 "Stephen John Smoogen" smooge@gmail.com wrote:
I didn't know there was an empty seat. I can volunteer my time for this at this point.
I will second smooge's self nomination.
By the way, could someone give me some tips (as in hey dumb-ass why havent you read this and this most obvious that)on 'replicating' the build system with plague. I need to make a set of EL-3 ones and I might as well experiment on my own first to see what the work load for this would be.
On Tue, 29 Jan 2008 12:28:46 -0700, Stephen John Smoogen wrote:
By the way, could someone give me some tips (as in hey dumb-ass why havent you read this and this most obvious that)on 'replicating' the build system with plague. I need to make a set of EL-3 ones and I might as well experiment on my own first to see what the work load for this would be.
EL-3 as the host or target system? As the host sys it might be that some requirements are too old (pyOpenSSL maybe?) or n/a.
Some documentation is in the packages, a few more pages are in the Wiki (I just noticed I don't know them): http://fedoraproject.org/wiki/Projects/Plague
EL-4: http://mschwendt.fedorapeople.org/plague/plague-0.4.4.1-10.el4.src.rpm EL-5: http://mschwendt.fedorapeople.org/plague/plague-0.4.4.1-10.el5.src.rpm are basically what the EPEL build machines run.
The various noarch packages are: plague-client plague-common plague-builder plague-utils : for certhelper, user-manager plague : the server
Hints? Start the builder and server services as early as possible to let them write the default config files once. When they fail to start during configuration attempts, they either complain on console or in the logs (/var/log/plague*). Starting the server programs manually may be helpful (e.g. /usr/bin/plague-builder -c /etc/plague/builder/plague-builder.cfg instead of "service plague-builder start") till the config files and target files are set up. The www files are only in the source tarball.
On Jan 29, 2008 2:07 PM, Michael Schwendt bugs.michael@gmx.net wrote:
On Tue, 29 Jan 2008 12:28:46 -0700, Stephen John Smoogen wrote:
By the way, could someone give me some tips (as in hey dumb-ass why havent you read this and this most obvious that)on 'replicating' the build system with plague. I need to make a set of EL-3 ones and I might as well experiment on my own first to see what the work load for this would be.
EL-3 as the host or target system? As the host sys it might be that some requirements are too old (pyOpenSSL maybe?) or n/a.
Sorry target system. All the sites I help with are still primarily EL-3 so I am going to play with setting up an EL-5 bot that will basically take Fedora SRPMS, subtract the packages that don't exist in EL-3, and recompiling them and then putting them in an 'alpha' channel. From there I will promote the ones that I need to a 'beta' and focus on them. Those ready will move to a gamma channel. Old packages will be moved to an delta channel, and retired to an epsilon channel. I figure if I get it working.. and from the notes I need for it, I can self-publish a PDF book to be sold on Lulu.
Some documentation is in the packages, a few more pages are in the Wiki (I just noticed I don't know them): http://fedoraproject.org/wiki/Projects/Plague
EL-4: http://mschwendt.fedorapeople.org/plague/plague-0.4.4.1-10.el4.src.rpm EL-5: http://mschwendt.fedorapeople.org/plague/plague-0.4.4.1-10.el5.src.rpm are basically what the EPEL build machines run.
The various noarch packages are: plague-client plague-common plague-builder plague-utils : for certhelper, user-manager plague : the server
Hints? Start the builder and server services as early as possible to let them write the default config files once. When they fail to start during configuration attempts, they either complain on console or in the logs (/var/log/plague*). Starting the server programs manually may be helpful (e.g. /usr/bin/plague-builder -c /etc/plague/builder/plague-builder.cfg instead of "service plague-builder start") till the config files and target files are set up. The www files are only in the source tarball.
Thanks.
epel-devel@lists.fedoraproject.org