On Thu, 2 Jan 2014 12:35:49 +0000 Justin B Rye <justin.byam....@gmail.com> wrote:
> Christian PERRIER wrote: > > Template: kinect-audio-setup/accept_eula > > Type: boolean > > Default: false > > +#flag:translate!:3 > > _Description: Do you accept the Microsoft KinectForWindows EULA? > > + In order to fetch the binary firmware needed by the kinect-audio-setup > > package, you need > > + to agree to the End User License Agreement (EULA) of the Microsoft > > + KinectForWindows Software Development Kit: > > I don't see any sign of upstream styling the product as > "KinectForWindows" (beyond the URL being alloneword); it's always > "Kinect for Windows". > "Kinect for Windows" is better, thanks. > It seems a shame that users need to open a browser to read this EULA > when you're already fetching stuff for them, but I suppose it's not as > if there's any hope you could cram the text into a debconf dialogue. > > Foolishly, perhaps, I've tracked down and looked at the actual EULA > (http://www.microsoft.com/en-us/kinectforwindows/develop/sdk-eula.aspx). > It doesn't license using the downloaded files in order to run the > Kinect hardware under Linux; only "to design, develop, and test your > programs that run specifically on a Microsoft Windows operating > system". Asking end-users to agree to it seems a bit pointless. > I think the terms changed since the very first EULA I remember, which was the one originally at the old URL. I didn't check lately, my bad. I agree that it's now odd to ask to agree to a text which says that the software can only be used under Windows. > [...] > > Template: kinect-audio-setup/eula_not_accepted > > -Type: note > > +Type: error > > _Description: EULA not accepted > > - You need to accept the EULA of Microsoft KinectForWindows SDK in order > > - to fetch the binary firmware needed by this package. > > + You need to accept the End User License Agreement (EULA) of Microsoft > > KinectForWindows Software Development Kit in order > of the Microsoft > Kinect for Windows Software Development Kit > > (And let's do some re-wrapping.) > > In the control file: > > > Description: helpers to setup audio input from the Microsoft Kinect sensor > > The noun is "setup", but the verb is separable ("set it up") and > therefore written with a space as "to set up". Or since that's > getting a bit long, we could turn it into a noun-pile as: > > Description: Microsoft Kinect audio sensor setup helpers > I'd write "Microsoft Kinect sensor audio setup helpers" that is inverting "sensor" and "audio"; "Kinect audio sensor" could give the idea of a different product in the Kinect line. > > When the Kinect is first plugged in the USB port it shows up as > > Why do we need to specify the port? > I agree it's unnecessary. > > a generic USB device with a bulk endpoint; after uploading a certain > > Should that be "a bulk transfer endpoint"? And either way, is there > really any need to mention anything this technical? > I can leave out these technical details, thanks. > > firmware a reenumeration takes place and a USB Audio Class device > > becomes available. > > "A certain firmware" is treating a mass noun as a count noun, and > "uploading" is confusing (especially given that the only subject the > sentence has had so far is the Kinect device). > > I'm not sure about this, but isn't the device stack "reenumeration" > technically a separate event from the reset that makes the device > change class? And it should probably at least be hyphenated... > > So: > When the Kinect is first plugged in, it shows up as a generic USB device > with a bulk endpoint; after the appropriate firmware is installed, a > re-enumeration takes place and a USB Audio Class device becomes available. > I'd say "the appropriate firmware is loaded" because "installed" is a bit too generic. About the USB events I believe that the USB device itself is reset and that makes the USB bus to be re-enumerated. I can just mention the "reset" event and leave out the word re-enumeration. > > kinect-audio-setup provides tools to download the firmware off the net > > + at installation time (since the firmware is not redistributable), and > > it sets up udev rules to call the firmware loader when the device is > > plugged in to finally get the USB Audio Class device. > > Say "from the Internet" (since it won't let you fetch a copy from > http://server.local), and rearrange slightly to reduce repetition and > avoid initial lowercase: ACK. > Since the firmware is not redistributable, kinect-audio-setup provides > tools to download it from the Internet at installation time, and sets up > udev rules to call the firmware loader when the device is plugged in to > finally get the USB Audio Class device. > > > . > > + The UAC firmware is downloaded from the Microsoft Kinect Software > > + Development Kit at http://www.kinectforwindows.org, the license > > + of which can be found at http://www.kinectforwindows.org/download/EULA.htm > > The main problem remaining here is the fact it isn't true. I am applying your changes, and then I am going to ask again to debian-legal for advice. Thanks for your time. Regards, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
