> I think, as I mentioned before, that someone (I guess that's you :)) > should write up an actual proposal (maybe, for example, the start of a > new manual section) that can be examined and commented on. Endless > streams of mailing list responses quickly give diminishing returns. My > experience is that it's much easier to come to conclusions when there > is a concrete plan to start from.
Challenge accepted! What is the best form to choose... maybe creating a branch of the source and adding a new manual page there that anyone can render? > I do want to reiterate something I mentioned initially: any effort of > this size will require copyright assignment to the FSF / GNU project. > Please be sure you are OK with that. Getting that in motion earlier > will avoid delays at the end. Where can I find more information about this? And where do I do it? > We can always use evaluation so you could just implement the basics > first and get grouping via evaluation for free, then add explicit > grouping as a next step if you want. Yes incremental changes sound good. Would you recommend first trying to agree on a proposal and then attempt some implementation? Or to do these things together?