[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SPAM] Re: GSoC 2014
From: |
David Kastrup |
Subject: |
Re: [SPAM] Re: GSoC 2014 |
Date: |
Wed, 19 Feb 2014 23:21:38 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Janek Warchoł <address@hidden> writes:
> 2014-02-19 18:41 GMT+01:00 David Kastrup <address@hidden>:
>> Urs Liska <address@hidden> writes:
>>> Janek's Tie Crusade?
>>
>> There is a three-month limit as far as I can see. There seems little
>> point in proposing stuff that a student cannot realistically be expected
>> to wrap his head around in the given time frame.
>> [...] With something vague and complicated
>> like "tie crusade" or "slur formatting", I don't see anything happening
>> with a tangible result.
>
> I estimate the time needed for fixing tie formatting to be 120-200
> hours (for someone roughly familiar with LilyPond codebase).
What does "fixing tie formatting" mean? That no tie needs tweaking any
more?
> When we take into account that such estimates usually are 50% off, and
> add 100 hours for getting familiar with the codebase,
100 hours for getting familiar with the codebase. To get to a state
where you can sensibly design a new tie formatting strategy that fits
into the current code and interacts with it.
> we get 400 hours = 10 weeks of full-time work. Seems to be a
> reasonable fit for GSoC time frame.
Consider me unconvinced.
> 2014-02-19 20:16 GMT+01:00 David Kastrup <address@hidden>:
>> Urs Liska <address@hidden> writes:
>>> That may well be true, and my suggestion wasn't too educated.
>>> But I had the impression that at least the Tie project was of a
>>> reasonable size,
>>
>> What _is_ the "tie project"? There are lists of ugly ties. That's not
>> a project.
>>
>>> and equipped with enough pre-research.
>>
>> I don't see anything that would serve as either a direction or a
>> starting point.
>
> You know what? It's VERY frustrating to spend 200+ hours (during the
> last 2 years) collecting examples and researching tie formatting, and
> then see someone - especially an involved developer like you - say
> "what tie project? what research? i don't see any".
I did not say "what tie project?", I said "What _is_ the tie project?".
That does not mean that I am of the opinion that nothing has been done,
but that there is no specific objective spelled out that would be a
suitable target for a limited-time project.
> And i didn't only collect lists of ugly ties. I already have a spec
> draft, and a pretty good idea how to approach the issue.
You have a "spec draft" and yet you claim that the project is
well-defined in a manner where everybody should know what it entails,
making the question "what _is_ the tie project?" an insolence?
> Several times i have offered to share my research. Usually it seemed
> that noone cared to see it.
>
> So, I am really angry because of what you said and how you said it.
So if what I had written was so foolish, how about you write a short
GSoC proposal spelling out specifically what a student is supposed to
achieve exactly in the three months assigned to the project? There may
be something like 2 to 4 hours left before the proposal time window
closes.
--
David Kastrup
- GSoC 2014, David Kastrup, 2014/02/19
- Re: GSoC 2014, Urs Liska, 2014/02/19
- Re: GSoC 2014, David Kastrup, 2014/02/19
- Re: [SPAM] Re: GSoC 2014, Janek Warchoł, 2014/02/19
- Re: [SPAM] Re: GSoC 2014,
David Kastrup <=
- Re: [SPAM] Re: GSoC 2014, Janek Warchoł, 2014/02/19
- Re: GSoC 2014, Jan-Peter Voigt, 2014/02/20
- Re: GSoC 2014, David Kastrup, 2014/02/20
- Re: GSoC 2014, Jan-Peter Voigt, 2014/02/20
- Re: GSoC 2014, David Kastrup, 2014/02/20
- Re: GSoC 2014, Urs Liska, 2014/02/20
- Re: GSoC 2014, David Kastrup, 2014/02/20
- Re: GSoC 2014, Janek Warchoł, 2014/02/22