Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re^2: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)

by nysus (Parson)
on May 29, 2020 at 12:13 UTC ( #11117458=note: print w/replies, xml ) Need Help??


in reply to Re: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)
in thread Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)

And based on the issue queue which looks to be largely ignored, I'd say this ParseXLSX is abandonware.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate Priest Vicar";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

  • Comment on Re^2: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)

Replies are listed 'Best First'.
Re^3: Looking for assistance for proper fix for Spreadsheet::XLSX bug(?)
by Tux (Canon) on May 29, 2020 at 17:18 UTC

    IMHO it shows two things:

    1. People use it
    2. It needs more people to help fixing the issues

    Don't moan, help!


    Enjoy, Have FUN! H.Merijn

      There is a difference between moaning and pointing things out. The two shouldn't be confused.

      $PM = "Perl Monk's";
      $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate Priest Vicar";
      $nysus = $PM . ' ' . $MCF;
      Click here if you love Perl Monks

        Concluding software is abandonware if the ticket-queue is to long to your liking is IMHO moaning. Pointing to a ticket queue that might need attention as it is longer than should be is pointing out. There is a huge difference in perception there on the reader side.

        I notice your frustration, and I understand it, but try to make your posts inviting for help instead of using text that migh be interpreted as a complaint.

        Next step: create an xlsx file that shows your problem and attach it to a post where you show the full code that makes the problem show here (inside code tags).

        Then add some comments about what you expect and what you get and why you thing your opinion is correct (which might be obvious to you, but not to the reader). Even if it is a bug that is too obvious to be interpreted as not-a-bug, still do this. FWIW, this is also how you would create a tichet where the maintainer would take action upon).

        If I get tickets lile "You code sucks, as it doesn't do what I expect it to do", I won't be motivated to do anything about it.

        If you don't feel safe/competent/motivated/whatever enough to create a ticket like that, you can start here, and the Monks will most likely be more than happy to help you to:

        • Reword that problem statement if needed
        • Come up with workarounds
        • Create a PR to the module that fixes the problem. (added value: you can merge the PR yourself and ignore the other tickets in the queue)

        As we monks do not encounter your problem, we need a ready-to-test set of things to start from if you want help. Perlmonks is not a group of people to code for free or fix problems on command, but most of the monks are eager problemsolvers.


        Enjoy, Have FUN! H.Merijn

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11117458]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (3)
As of 2022-05-16 18:15 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (63 votes). Check out past polls.

    Notices?