Hi Joel, On 03/13/2017 10:56 PM, Joel Holdsworth wrote: > Dear Paul, Alexndra, Dan and Adrian, > > I recently discovered your work on the scopy software oscilloscope, and > its usage of code derived from PulseView. As the founding author of the > PulseView project, I wanted to reach out to you concerning your work on > scopy. > > It's really exciting to see our code being used as part of your project, > and I'm glad to see it being used to benefit other engineers. > > I hope you're getting some good use from this code. > > I wanted to ask what your plans are for the scopy project? Is it still > in active development? > > In the sigrok project, we do a lot of development to support various > test-and-measurement tools, and in many ways Analog Devices is already > our largest cooperate contributor. > > We would be interested inintegrating many of the features you have > produced. We would therefore be interested in exploring if any of the > code you have produced could be shared with the upstream sigrok project. > > I find it rather unfortunate that you felt the need to snapshot the > PulseView repository and fork it, rather than working with us on that > code. This has occurred more than once in PulseView's history, and both > the upstream and downstream projects miss out on an important > opportunity to mutually improve code quality.
I actually reached out to you (I believe it was you) on IRC before we started the work on the Scopy project. We talked about the possibility of having patches merged into Pulseview that refactor things so that the signal rendering component can be used standalone and independent from the application logic. The answer back then was a very definite no. So we went ahead with the current approach. As I said on IRC we are very happy to contribute as much code as possible back upstream. But that of course requires that those changes are in alignment with the development direction that upstream takes. If they are not we have to maintain them separately. Scopy is currently going through a phase of very active development, once things have calmed down a bit, we'll go through the list of changes and see what is appropriate for upstreaming and what is not. > > It would be good to open the lines of communication. Please don't > hesitate to talk to us. We're glad you're making use of this code, and > would like for both you and us to mutually benefit from your usage of it. > > I grabbed a copy of the scopy source code from github, but it appears to > have some problems building on Linux Mint. Is it known to build on any > specific Linux distro? What is the error? It should build fine. > > I can get the Windows build, but without hardware it doesn't seem to do > very much. If I were to test the software, is there any specific > hardware I would need? Where can I acquire this hardware? The hardware isn't available yet, it is still in development. The plan is to send you and other sigrok/pulseview developers a device once it is available. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
