[PATCH v4 00/16] Render READMEs inline in tree view

[Andy Green]

On 06/28/2018 06:46 AM, Jason A. Donenfeld wrote:
> Hi Andy,
> 
> I'm happy to engage technically here in order to find the best way of
> going about this. However,
> 
>> Nobody is paying me to do it and I don't have an endless budget of time
>> to lavish on it (and it seems, neither do you...).
>> If cgit can't do what I need in a reasonable timescale, even with my
>> contribution, my choices are:
>> been shaped only by github.  It's not that hard to overstate its
>> importance but in a few ways, unless something in cgit is really better,
>> the way forward is to align, or align and improve... IMHO.
> 
> I don't see the relevance of whether or not you're paid and how much
> time you have to implement things, or what predictions are about sink
> or swim with regards to Github.

Mmm I could tell from your reply it's irrelevant to you.

That's why I pointed it out, because it's very relevant to me and will 
inform what I choose to do.

> I think the general ideas you've presented in these patchsets are good
> ones, and now it's time to collaborate on the best way to go about
> doing it. Part of what we're encountering here is the fact that cgit
> hasn't originally had a robust display/hosting intent; it was mostly
> around showing the state of the git repository. Now we're trying to
> grow beyond that. Hence, I'd like to organize this in a sensible way
> so that such rendering capabilities are available at the heart of
> cgit, rather than haphazardly added on with a smattering of

It's not that I don't understand the reasoning.  There is a lot of cruft 
because the project has been around a long while.  But it's not my cruft.

> contradictory configuration switches. In spite of your pay grade, your
> time budget, or your timescale, I'm going to make sure this gets done
> in the right way.
I also run a FOSS project that has been around for years and have dealt 
with hundreds of contributions.

These features have been around for 10 years in github and still not in 
cgit, done right or wrong.  I think everyone will be better off if we 
can find a way.

-Andy

> Jason
>