On April 19, 2012 03:00:40 PDT, Pete Batard wrote: > All, > > To "celebrate" the 2 year anniversary of the last public release of > libusb, which we think is proof enough that libusb is a dead > project, even more so as far as the general public is concerned, > quite a few of us (Segher, Vitali [before he went to pursue other > endeavours], myself, Hans, Ludovic, Xiaofan, Travis, Michael, > Nathan, Kusti, Sean...) have decided that we cared enough about > users to decide to participate in a fork of libusb. > > This fork, called libusbx and crafted as a drop in replacement of > the current libusb, contains pretty much all the improvements and > bugfixes that one would expect to find in the next libusb release... > were it ever to happen, as well as a few other improvements. As you > will find out, we have a clear yet ambitious roadmap [1], with a > couple releases under our belt already (v1.0.9 was released > internally 2 weeks ago and v1.0.10, which can be downloaded from > [2], was released this Monday), and we will do our best to deliver, > where libusb failed to. > > Therefore, if you are tired of the lack of progress/releases from > libusb, or from having to deal with a project that doesn't seem to > go anywhere, you are very much invited to visit http://libusbx.org, > or our SourceForge page at https://sourceforge.net/projects/ > libusbx/, to check libusbx out. > > As subscribers of libusb-devel, you are also very much welcome to > join our own mailing list (libusbx-devel@lists.sourceforge.net) by > registering at https://lists.sourceforge.net/lists/listinfo/libusbx-devel > . > > With Hans onboard, libusbx is already set to replace libusb on the > next Fedora release, and we expect other distros to follow suit, as > we become more and more relevant to the USB developer community. > > Finally, in order to concentrate fully on libusbx, I will add the > following related to my personal involvement with libusb, taking > effect immediately: > - I am ceasing all maintenance & support activities for the Windows > implementation of libusb. With libusbx containing a libusbx-pbatard > branch (though much of its relevant content has already been merged > with mainline libusbx), if you are interested in Windows support and > development, you should head to libusbx, as this is where it's going > to happen. > - I will also cease participating in libusb-devel (i.e. this list), > though I plan to reply to this specific thread if there are questions. > > With libusbx as a serious contender, we hope that the deplorable > libusb situation, which prompted this fork, will become a thing of > the past and that regardless of what libusb chooses to do (or not to > do), libusbx will solve all concerns you have with regards to the > future of the library, and in a most effective manner! > > Oh, if you are interested in submitting patches, please be aware > that libusbx will soon have Gerrit+Jenkins operational, to greatly > enhance the patch submission process (it's pretty much operational > now on a test branch [3], but still missing quite a lot of > finalization) > > Regards, > > /Pete > > [1] https://sourceforge.net/apps/trac/libusbx/roadmap?show=all > [2] https://sourceforge.net/projects/libusbx/files/releases/1.0.10/source/ > [3] http://review.libusbx.org:8080/#/q/status:open,n,z
Nice work! :) There's now a repo.or.cz automatic mirror of libusbx at: gitweb: http://repo.or.cz/w/libusbx.git clone: git://repo.or.cz/libusbx.git graphiclog: http://repo.or.cz/git-browser/by-commit.html?r=libusbx.git ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
