Hi there. That's great to hear. We can certainly use more help with making our exporters more robust. There is certainly a number of exporter related open issues. Are the aspects of the library your consider yourself fairly familiar with, or a component of the library you feel you can give more needed attention?
Ogi On Mon, Feb 8, 2021 at 08:21 Trifon Trifonov <[email protected]> wrote: > Hi Ognyan! > > I would be happy to join the team! I must clear some projects off my desk > first, but I promise to help with whatever is needed. At least I will try > to fix my own git-hub "issues" :) I think within a month or so, I should be > able to find time for pyqtgraph. > > > On Sunday, February 7, 2021 at 6:17:20 AM UTC+1 [email protected] wrote: > >> Hey everyone, >> >> My name is Ogi (j9ac9k on github). I'm one of the maintainers of >> pyqtgraph. I am writing here to solicit for volunteers to help maintain >> the library. >> >> In case you haven't been following the project recently, we've done a few >> releases this last year (we're trying to migrate to a faster release >> cycle), and thanks to some amazing contributors, we have Qt6 support, >> optional CuPy support, expanded documentation (thanks readthedocs), >> expanded our test suite, and made countless bug-fixes and performance >> improvements. >> >> Almost 2 years ago we were coming up on 200 open pull requests, and as I >> write this email, we are down to 24. The library was stagnant for a long >> time, and as the PR count is trending downward, there is still work to be >> done from unifying the API, deprecating older methods, expanding the >> documentation, profiling "slow" parts of the library, investigating issues >> created; and general steering the course for where the library should go >> from now. >> >> Ideally you will have contributed to the library beforehand, be >> comfortable with git (primarily for switching to branches of pull request >> authors, and be able to use git bisect to track down regression bugs), have >> working knowledge of numpy and some familiarity with Qt. You wouldn't have >> to be an expert, just have some familiarity, and the capability and >> willingness to spend time working on the library. There are other active >> maintainers, so you would not be isolated. >> >> If you are a long-time user of pyqtgraph, but don't think you have the >> bandwidth to contribute to the library on a semi-regular basis, we can use >> your help too!. If you could take a look at the list of current open pull >> requests, and if you have input to any of them (such as this would be >> useful, or not because functionality already exists), or want to test them >> out to see if they function, that would be a huge help! >> >> If you want to be a volunteer to help make the library healthier/better, >> or if you have any questions, please reach out. >> >> Thanks, >> Ogi >> > -- > You received this message because you are subscribed to the Google Groups > "pyqtgraph" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pyqtgraph/123af567-7063-4170-9968-488e67861d2dn%40googlegroups.com > <https://groups.google.com/d/msgid/pyqtgraph/123af567-7063-4170-9968-488e67861d2dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "pyqtgraph" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTEP7KeN5Wi6CN8XCEn3-retBmAHhcFNSu17ZFv7oHKwYw%40mail.gmail.com.
