Re: Issue Tracker Used? Git migration checklist.

[Fred Cooke <fred dot cooke at gmail dot com>]

Chicken, meet egg.

People who know how/what/have privilege are not or can not do these things.

People who can and/or would do not know what/how/don't have privilege.

Either new people are needed. I could be one of them, if I'm not
driven back into my busy little hole by this palaver.

Or, those who know/can need to start.

Without one of these two things, nothing will happen. The latter is
not going to happen, based on 2 years of history.

The former won't happen without clear objectives and a clear plan in place.

Of course it's not the hard part of the problem; it's just a way to
break the big problem down.

In order for someone like me to start executing tasks, they have to be
there, and clear. I'm not going to waste my precious time doing some
script that's going to be deprecated or is just an exercise or
initiation ceremony; I already work 20 hours a day, every day. If a
clear path lays ahead, maybe someone will step up to fill a role. If
not, no one can.

Fred.

On Fri, Oct 26, 2012 at 5:54 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Fri, Oct 26, 2012 at 8:42 AM, Fred Cooke <fred.cooke@gmail.com> wrote:
>>
>>> There is nothing wrong with doing that, it just won't help.
>>
>> So you're saying that I should give up and leave this thread here as a
>> warning for other hopeful souls to also not bother?
>>
>> I can't see how it can not help. Any action requires some sort of game
>> plan. And provided it's sufficiently distributed and fragmented, you
>> keep a barrier to entry up. Perhaps that's what some want? I doubt all
>> want it, though. A clear "what's needed" collated in ONE place in a
>> readable format with ordering almost can't not help. It identifies the
>> first step, whatever it may be. That first step is currently drowned
>> in a barrel of a thousand unordered steps, which in-crowders know
>> about, and the order of, but anyone else wanting to help is powerless
>> to find out about.
>
> Creating a task list is a great start if you then start executing the
> tasks.  But creating a task list and not proceeding to execute them
> won't help because things change.  If somebody decides to tackle the
> job a year from now, they will have to revisit the whole thing anyhow.
>
> I guess I shouldn't say that it won't help at all.  It will a help a
> little, in that it will provide yet another starting place for that
> hypothetical person a year from now.  But it won't help very much.
> It's not the hard part of the problem.
>
> Ian