Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] My resignation

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Sukneet Basuta <sukneet AT gmail.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] My resignation
  • Date: Fri, 20 Jul 2012 20:46:25 -0400

On Fri, Jul 20, 2012 at 3:44 PM, David Kowis <dkowis AT shlrm.org> wrote:
> What should I do differently? Should I tell you how to do everything?
> Should I start smashing glasses and just merge all the things, and risk
> breaking the systems of many people? Should I just do all the work
> myself? I simply don't have time to do all the work. I can't. If you
> want a leader who does all the work, I'm fine with that, no hard
> feelings. (really, this isn't some passive-aggressive thing)

I don't expect you to do all the work, but I do expect the project
lead to lead. i.e. stick your head in when its needed, outline what
needs to be done, etc. I don't mean this as a personal attack, but I
haven't seen you do too much of that. But, maybe you do a bunch behind
the scenes or on IRC that I don't see and I'm just blowing hot air.

> For the most part, people have done spell updates, and I've watched
> commits and complaints about things not being done, but nobody steps up
> to say, "If this meets <X> will that be good enough to get it merged?"
> And then when compliance is met, they would push to get it merged. Often
> someone says, "I made this branch and it works for me." Then someone
> else will post "Nope, it doesn't." And it often dies right there.

I feel that this where the project lead or grimoire lead, or some
other lead, should step in and say that. I don't exactly have
experience working in large groups, so maybe I just don't know how
these things work.

> The most recent glibc 2.15 branch should probably be merged in, it looks
> like due diligence has been done with that, but I'm not a dictator. If
> others have problems with merging it, we should discuss it. I think it's
> probably okay, but I'd like to personally knows which spells are known
> to compile and work against that version of glibc. I'm somewhat nervous
> about "Works for me" without any other specific information. I don't
> particularly want to break peoples boxes.

I agree, but imo we don't have enough people testing out branches to
go with something other than "Works for me".

> That being said, yeah we need people to do the hard work, and then ask
> for reviews of it, and we need to settle on what is allowed in for big
> changes like this.

> Cauldron scripts work, just nobody has bothered to take the time to
> build another iso. You want one? build it. Ask flux_control for help,
> he'll be more than happy to explain you how to do it. Make it, show that
> it installs for people, and we'll make it official.

If that's addressed to me, I don't really care about Cauldron. IMO
chroots > cauldron. If Cauldron is still the official method to
install Source Mage, then I guess we do need a new one, but given that
we have fairly recent chroots, I don't think it's currently necessary.

As I stated, I'm working on the stuff I think is important. I've spent
the past month or two trying to build up a test box so I can get
devel-xorg merged into test, but I've run into way to many broken
spells (I'm hitting yes to everything). If you think my attention is
better spent elsewhere, let me know.

Hopefully this email didn't make me come across as a complete bastard.




Archive powered by MHonArc 2.6.24.

Top of Page