On Fri, 4 Jun 2010, Yury V. Zaytsev wrote:
Hi!
On Thu, 2010-06-03 at 17:23 -0400, David Steinbrunner wrote:
It seems to me things become lost in the mailinglist which would likely
not in a issue/ticket/bug tracking system. Another thing is, Dag
appears to be a single point of failure for the issues noted above so
what would happen if he was permanently indisposed?
Of course I personally would very much appreciate if we threw away the
weird half-broken wiki that's been running unused for several years and
install a Trac instance just like everybody else to have a wiki,
bugzilla and integrated repo browser in one and the same place. Trac
does have its limits, but come on, RPMForge is such a special project
that it seems to me highly unlikely that we will ever hit the limits of
any rudimentary version control system (in fact, we're not using even
10% of svn features I would guess), wiki and bug tracking system. But
here you get everything at one place and it's tightly integrated.
However, to my mind the biggest issue is of course Dag being the single
point of failure rather then things getting lost on the mailing list.
The historical reasons on why this happened are quite clear and the
reasons why it stays this way are also not a terrible secret.
We've been talking about organizing an independent build host with
documented setup for the committers for quite awhile, so that everybody
who has commit access to the repo can trigger builds and maybe even
rights to promote the packages to the central repo. Also in case if one
person disappears for any reason, the rest can re-create the missing
piece of the infrastructure using the documentation.
However, we only have a handful of people and most of them are
overloaded with other issues. That's why it's moving on so slowly. The
only way to really push it forward is to get involved. Sorry for this.
For instance, nowadays I am employed full-time doing something which has
nothing to do with RHEL per se and therefore I can only contribute
updates to the packages which I personally need or there's a huge need
for our internal infrastructure.
Good lord :-) Yet another rant about nothing... Hmmm... to summarize: we
are aware of the current situation and everybody's working on getting
this fixed, but no one knows when we'll be able to actually fix it.
You summarized it very well. Even though I would love to spend more time
fixing the things listed. We lack the time and infrastructure (money) to
provide more people to collaborate. Sure opening subversion to more
people is the easy part. Trusting people the key to sign and giving them
access to modify repositories makes things more complicated.
Personally I switched jobs (commuting almost 3 hours every day by train),
becoming a dad, buying a house and trying to finance this :-/ And RPMforge
is not the only project I am working on.
I started to lease a new system in February at Hetzner that I intended to
use for the new build infrastructure, but at FOSDEM another course was
decided which I do not completely agree with for various reasons.
So the system at Hetzner will slowly become my new buildsystem
instead (since I have to make room for a baby real soon and get rid of the
noise as well).
So hopefully the dust will settle at some point in the future, but at the
moment I cannot say when.
I fixed a few of the problems you reported, but I can tell you that if you
send a long mail with potentially many things to reply and do, I often
simply postpone it because I cannot oversee what time it will consume.
While instead if you send me small questions/mails with a single (short)
answer or action it is much easier to do it right away.
--
-- dag wieers, [email protected], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
