On Sat, Apr 13, 2013 at 12:14 AM, Toby Gray <toby.g...@realvnc.com> wrote:
> Sorry, I didn't realise it was a common discussion point. I was trying
> to avoid doing what I did with the WinCE backend of going ahead and
> implementing something and only talking to the community when it
> was done.

Yes I think this is a good move.

> I think the summary from all the replies seems to be:
> * any changes to event handling will not be considered for merging until
> after hotplug is done (at least 10 months time)

The 10 months time is an estimate. If there are more contributors
from the community (like you), it could be faster.

We can also shuffle the milestones depending on the request
of the community. Right now hotplug seems to have the
highest demand, so it is in Milestone 2.1. If the event handling
is next in line, we can make it Milestone 2.2. And personally
I think event handling is also very high on the demand based
on past discussions.

If you look at the current Milestone 2.2, #15 is the only one
relatively important feature but it could be a minor effort since
we can potentially leverage the commit by Nathan in libusb-darwin.
The other two are just minor. So we could just combine Milestone
2.2 and 2.3 to make it Milestone 2.2.

> * any work on event handling is likely to be unusable once hotplug
> starts to be implemented (as it is likely to also modify event handling
> code)

This may or may not be true depending on how hotplug is implemented.

> * if I'm contributing time to libusbx development that it would be more
> useful if it was working on hotplug (or other features in the next
> milestone)

Since hotplug could potentially affect the event handling part, it
is better to work on hotplug first.

But you can also work on future milestone items if it is kind
of independent to other features, eg, the USB 3.0 descriptor
parsing.

> * don't send apis, send working code :)

Not really true. I think both are needed. Usually the API proposals
come first. On the other hand, API proposals need to consider
the potential implementation hurdles at least in the three major
platforms (Linux, Mac OS X and Windows).


-- 
Xiaofan

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to