Re: [SoC RFC] git statistics - information about commits

From: alturin marlinon <alturin@gmail.com>
Date: Mar 23, 2008, 21:32 UTC
Message-ID: <bd6139dc0803231432s4a1f9d86r7ec97847fa70ca82@mail.gmail.com>
In-Reply-To: <7vzlsp73fs.fsf@gitster.siamese.dyndns.org>

On Sun, Mar 23, 2008 at 6:31 PM, Junio C Hamano <gitster@pobox.com> wrote:

>  Hey, don't get me wrong.  Please do not start your thought with "which of
>  these features".  Proposed feature set should come from you.  It's your
>  project after all.

Ah, perhaps I should have phrased it more like "which of these features are of most interest to the community".

Show 7 quoted lines

>  I was NOT giving you an instruction "You should do all of these" (I am not
>  your mentor), an opinion "These are all important" (I haven't thought
>  things through), nor criteria "Unless you do your feature this way, you
>  fail" (I am not GSoC admin to judge your application nor evaluate at the
>  end of project).  Nothing of that sort.  They are just random ideas, I
>  haven't even thought through the feasibility of, and/or possible approach
>  to solution for, some of them.

Even so, most of them are very interesting, although I agree that the feasibility should perhaps be looked at more closely.

>  If you find any of them interesting, you are welcome to include them in
>  your target feature set.  Other uninteresting ones and unrealistic ones
>  you can discard without even commenting.

I think I will divide the features into subsets and list the dependencies between them. Then based upon 'popularity' an easy selection could be made. Johannes said:

> I think it can be vague about the order in which things will be
> implemented.  And the features which you think might be too complicated
> should be marked as such: "possible extension (which might not be finished
> within this project): <blabla>".

Would such a list be allowed to include such a list of grouped features which then can be selected later on?