Imakeidx maintenance

  • Creatore
    Topic
  • #98363
    Up
    0
    Down
    ::


    This message is about the maintenance of imakeidx.

    I have found a bug in this package, when used in the same time as the bidi package. I have send a proposition to Enrico Gregorio, the author of the package. He didn’t answer to me, as in the past. Claudip Beccari, who was co-maintenor, wrote to me that he doesn’t want to continue to maintain it.

    That is why, in conformity with the LPPL1.3, I send a public message, to ask to Enrico Gregorio if he still maintains the work, or if he wants to let me be the maintainer.

    This message was also posted in http://tex.stackexchange.com/q/212188/7712 and in comp.text.tex.

Visualizzazione 2 filoni di risposte
  • Autore
    Risposte
    • #98364
      Up
      0
      Down
      ::

      maieul” post=97883This message is about the maintenance of imakeidx.

      I have found a bug in this package, when used in the same time as the bidi package. I have send a proposition to Enrico Gregorio, the author of the package. He didn’t answer to me, as in the past. Claudip Beccari, who was co-maintenor, wrote to me that he doesn’t want to continue to maintain it.

      That is why, in conformity with the LPPL1.3, I send a public message, to ask to Enrico Gregorio if he still maintains the work, or if he wants to let me be the maintainer.

      This message was also posted in http://tex.stackexchange.com/q/212188/7712 and in comp.text.tex.

      Enrico may answer later for what concern the maintenance.

      To me, posting these kind of messages everywhere is not the best practise to handle such a case. If an author/maintainer does not answer to private e-mail, the LPPL1.3 does not forbid to create a derived work. However, but this is only a personal opinion on how I would have handled the case if I were you, the most “politically correct” thing after having contacted the authors is to cook up a minimal non-working example and post it on TeX.SX. Then the author(s) become(s) aware that the problem has a practical relevance and can decide what to do. If no answer is provided and you have one, just post it: the community would benefit anyway.

      Just for reference, have a look to TikZ 3.0.0 and Hobby.

      Claudio Fiandrino

    • #98365
      OldClaudio
      Partecipante
        Up
        0
        Down
        ::



        @cfiandra
        , il tuo suggerimento è ottimo, ma Maïeul stava cercando di trovare una risposta alla sua offerta di fornire una soluzione del problema che ha evidenziato, soluzione che ha già i mano.
        Non ricevendo risposta ha dovuto avvalersi di quanto stabilito dalla LaTeX Project Public Licence. Siccome Enrico ha risposto di NO su stackexchange, Maïeul ora farà quello che ritiene più opportuno.

      • #98366
        Up
        0
        Down
        ::


        Dal mio punto di vista Maïeul ha agito correttamente, ad eccezione di questi messaggi. In particolar modo su TeX.SX: mi ricordo di avere votato la chiusura di altri post in precedenza perché TeX.SX non è un forum! Non si possono postare risposte che dicono “Tienimi informato”: quei messaggi non rispondono alla domanda chiaramente. Allo stesso modo ho contribuito alla chiusura della domanda in oggetto perché “I send a public message, to ask to Enrico Gregorio if he still maintains the work” non è una domanda di interesse generale.

        Detto questo, si può lo stesso ovviare ai paletti imposti ed è anche relativamente semplice. Basta creare un esempio minimo, postare la domanda e la risposta contemporaneamente. In questo modo chi ha lo stesso problema e cerca su google viene subito indirizzato nel posto corretto. Se è un problema concreto e di larga applicazione, avrà un alto numero di voti. Non mi sembra complicato.

        L’altro metodo è ovviamente scrivere un secondo pacchetto. E ovviamente capisco che sarebbe meglio avere le funzioni che risolvono il problema direttamente in imakeidx. Dobbiamo organizzare uno sciopero per convincere Enrico a rispondere alle e-mail 😉 (il che potrebbe essere divertente: sia lo sciopero, sia veder rispondere Enrico).

        English Version

        To me, Maïeul did everything right except for these messages, in particular speaking of the one posted on TeX.SX. I remember having contributed to cast close votes to other of his posts before because TeX.SX is not a forum! It is not possible to publish answers that merily say “Keep me informed about this”: those messages obviously do not answer any question. In the same way I contributed to close the question we are speaking about since “I send a public message, to ask to Enrico Gregorio if he still maintains the work” it is cleary a question not of general interest to a general audience nor to future visitors.

        That said, it is still possible to navigate through the rules they have and it is quite easy. Just create a example demonstrating the issue, post it in form of a question and answer right way. As a result, people with the same problem looking on google for answers will be immediately redirected to the Q/A. In addition, if the problem is a true one and potentially may be of a large interest, the Q/A will get lot of upvotes.

        The other method is of course to write another package. Of course I understand it would be better to have the patch solving the issue directly in imakeidx. We should organize a strike to force Enrico start answering e-mails.. after all it may be fun 😉 (both the strike and having Enrico answering e-mails).

        Ciao
        Claudio (F)

    Visualizzazione 2 filoni di risposte
    • Devi essere connesso per rispondere a questo topic.

    Go to top