On 17.07.18 16:26, Jean-Marc Lasgouttes wrote: > Le 17/07/2018 à 02:17, Uwe Stöhr a écrit : >>> So what can be done? In my opinion, we should - define the goal >>> of LyX together with our users. Maybe the result is to hide >>> background stuff, maybe it is the opposite. Whatever it might be, >>> that should be the base for future development. - setup a "board >>> of development" that take care of user feedback and who define >>> the things the next version of LyX should have. Such a board >>> should only be 50% consist of developers. Translators are not >>> treated as developers. The idea is to see what people really need >>> and to organize its development so that several developers >>> develop a certain feature. >> >> I only made these 2 proposals and thought they are worth to be considered. >> It is OK not to agree, but what about other ideas or do you think >> we should just continue as we did the last months? I mean criticism >> should be constructive. So I would her your ideas for future >> development. > > OK, here are my _final_ words on the subject then. Considering the > number of active developers, we do not have that much free goodwill > to spend on design by committee. I already have a day job, thanks. I > am not looking for a new boss telling me what I should be doing > during my free time. > > Despite your insistence that we do not love our users, I do my best. > If it is not good enough for you, so be it. > > I hope this is a clear enough answer, it is as constructive as I can > be. > > JMarc > > PS: remember that LyX is a platypus: something so weirdly designed > that everybody is surprised that it even exists. I understand you > would better have something useful like a cow or a duck. However, > these are boring animals and everybody loves platypuses :)
What would be some middle ground here? I certainly do not want to impose my will on a dev, do not want to be a member of a committee. But a lot of features I'd like to see implemented or bugs fixed (even readymade solutions I proposed) just do not materialize, certainly not in a timeframe that gets me excited. There is just not enough *systematic* user feedback. Error reports, user-ml private feedback are certainly not showing the devs a complete and accurate or representative picture. As can be seen in the email exchange above: Devs have quite distinct impressions and personal opinions on the situation. I do not suggest to conduct surveys or the like. --- Just an example: But the discussion about the win-Installer has demonstrated quite a bit that there is apparently no objective basis to come to a solution. We never knew how many people use actually use Lyx-Win_MikTex compared to the less problematic (for that "issue") Lyx-Win-TexLive. --- end of example I think a compromise might involve a more quantified user feedback, maybe for the ticket tracker? Currently only the devs assign priority to a ticket. How about adding a running counter on which users might then vote? In any case I think Uwe's idea should be reconcilable with JMarc's stance on that. I see a benefit for everyone involved if that could be implemented. Devs still choose what to do next, what seems to them the most taxing problem or the nicest thing to add, but with an awareness of a more objective quality of what others think about that. greetings mn
