Re: proposed meeting [was Re: Assigned responsibilites, again]

On Thu, 2005-07-14 at 10:34 -0600, Elijah Newren wrote:
> On 7/13/05, Luis Villa <luis villa gmail com> wrote:
> > > I think people should start putting there names against some of these
> > > tasks.
> > 
> > I've put my name against a couple 'delegated' tasks, which I think we
> > should do for all 'delegated' tasks.
> >
> > Now for the scary part... should we have a call or IRC meeting next
> > week to get names next to all of these?
> Sounds like a good idea to me, also:
> Although the page mentions putting one name to each, I think it'd may
> be good to have an official backup name for each while still having it
> understood that the whole team and community are as involved as
> possible.[1]

Yes, of course, it's just to have one person who's responsible for it
actually getting done. The hope is that stuff will then get done.

> As a slight tangent (though related), I'd like to be able to help out
> with all the tasks if needed.  Most things I can just watch others do
> it in order to learn, and last release cycle I asked tons of questions
> about patch review, but that still leaves on thing out: making a
> release.  Vincent also asked about this recently.  Is there any chance
> I (and any others that want to know but don't yet, e.g. Vincent) could
> be shown the steps for making a release, whether it be for the stable
> or unstable series?  I'll volunteer to document it for future
> reference.  ;-)

The last time I tried to get that information, I did get this:

Now that we have the wiki, that's the right place for it.

I also got a sample versions file at some time, but I don't seem to have
it anymore.

I naver actually tried this, because it's obviously destructive if you
get it wrong, and I only guess that Kjartan uses the same system. Jeff's
script has probably been updated now too.

I'm currently testing the current garnome snapshot. If that works, I'll
try to update it to the latest tarball versions.
> [1]  I know that I have frequent enough busy periods that signing up
> for the often occuring items on the list (tarball nagging, showstopper
> bug reminder, etc.) would result in multiple times per release cycle
> where it becomes everyone elses responsiblity--which all too often
> means no one's responsibility.  I think it'd help get things done
> sooner, while someone from the everybody category could still jump in
> if things are running a week or more late.  Examples of how it would
> help: if I know I'm going to be busy, it gives me somebody to pick on
> (er, delegate to) to help get tasks that I'm responsible for done more
> quickly; I'd be less scared to sign my name to some of the tasks if
> there's a backup or if I'm the backup; if I notice another task has
> slid for a while without being done, as someone in the everybody
> category I only need to get a hold of one of either of two people.
Murray Cumming
murrayc murrayc com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]