Le 16/10/2015 18:10, Guenter Milde a écrit :

We are talking about a one time effort of at most half an hour for one
person only. Subscribing to lyx-cvs with lyx.org addresses works in general
(one could ask Guillaume how he did it if it is unclear how it works), and
setting up a filter in the google mail account is easy as well.

I can try.


Please relate this effort to the time which is wasted by requiring other
developers to work around that personal preference.

I tried to play nice. It actually took months (if not years) until the known
preconditions for comitting to the LyX repo were up and working (of course
I did also something else inbetween).
I spend hours setting up, activating, reactivating this lyx.org mail
account and setting up a forwarding, because I was told this is required
to get commit rights.

After my first commit, I was told: you must also subscribe to lyx-cvs (a
list I don't want to get). Reluctantly, I tried also to hop through this
next loop but failed. Also, my fixes were incomplete, because some tests did
not run any more. There was no documentation about tests, no documentation
about the need to subscribe to lyx-cvs.

So, if I understand correctly, your issue comes from the fact that you wish to use a different e-mail address than the lyx.org one. What about having git signing the patches with your lyx.org address, and subscribing your lyx.org address to lyx-cvs, not your main address? Then on the gmail interface, you open any e-mail from lyx-cvs, go to “More ▷ Filter messages like these” and tell it to delete them.

I cannot see what can go wrong with subscribing to lyx-cvs. Tell us more if something went wrong.


Pausing and reconsidering, I come to the conclusion:

I can live with just supplying patches.


I don't know the complete picture of the LyX code, so someone has to go
through and audit my patches anyway, so 1) is the "safe bet".

I don't see the link with people anyway reading your code. Ultimately the other devels rely on you for code quality. “Audit” is a bit of an overstatement. For instance, the devel FAQ promised me “a lot of comments” about my code, but I have not seen that happen.


The patches are on the LyX bug-tracker ready for examination and
application.


By whom? As you may have noticed, LyX moves only when somebody takes an initiative. You will have to wait that somebody accepts to take the initiative for you every time. You are not going to like that, because even if you find a willing person once in a while (remember this is mostly a boring task and there is nobody “in charge”), your request is always going to be met with rolling eyeballs.

I am also afraid that you make your own task harder, because, in my experience, there are often last-minute fixes or reformatting, and I know that I would lose more time uploading the latest versions of my patches on trac than committing myself.

I understand that this bureaucratic stuff evokes bad memories for you, but you could give it one more try.



Guillaume

Reply via email to