Place for feedback?

dlharrison · March 2015

Where do we report typos or issues with LFS201 please? Nothing major to report, but it would be nice to offer feedback if possible.

adamherst · March 2015

This post suggests we send them to [email protected]:

http://www.linux.com/community/forums/lfs201-class-forum/welcome-to-the-lfs201-class-forum

Thanks,

Adam

dlharrison · March 2015

Thanks for the link Adam. I'd also asked Foundation via their social media pages, without any response. Lots of course promo but no clear channels for user interaction. Can't be the Linux way!

coop · March 2015

Hi sorry, I didn't realize I was supposed to be monitoring this. Indeed the best way to send us typos, corrections, etc is to mail [email protected] Please mention LFS201 in the subject.

We have been continually revising the class, fixing minor errors, typos and adapting students' suggestions and we welcome them.

Jerry Cooperstein
Training Program Director, Linux Foundation

dlharrison · March 2015

Hi,

Sorry too -- didn't mean to come across as critical. It really is a great course so far!

I have generated heaps of course notes so far and remembered to jot down a few glitches along the way. I will email them as suggested.

Thanks,

David Harrison

federicopenaranda · February 13

I tried to send an email to [email protected] with some feedback about the LFW211 course, but I get an automatic response with this message: "This email address is no longer accepting Training & Certification Customer Support Requests.". Is there another way to send feedback?. Thanks.

fcioanca · February 13

Hi @federicopenaranda

That email has been disabled for a couple of years. Content related feedback can be provided in this forum.

Thank you,

Flavia

federicopenaranda · February 13

Hi, I'm doing the LFW211 course, and I found a couple of things that could be an error:

1) In the page of the link below, the text mentions a flatstr package, but I couldn't find that package in the list of packages that the page shows.
https://trainingportal.linuxfoundation.org/learn/course/nodejs-application-development-lfw211/packages-dependencies/packages-dependencies?page=4

2) In the lab 2 on "Key Javascript Concepts" are some lines of code that validates the script with some assert statements:
https://trainingportal.linuxfoundation.org/learn/course/nodejs-application-development-lfw211/key-javascript-concepts/lab-exercises?page=2

assert(Object.getOwnPropertyNames(felixProto).length, 1)
assert(Object.getOwnPropertyNames(felixProtoProto).length, 1)
assert(Object.getOwnPropertyNames(felixProtoProto).length, 1)
assert(typeof felixProto.meow, 'function')
assert(typeof felixProtoProto.purr, 'function')
assert(typeof felixProtoProtoProto.hiss, 'function')
console.log('prototype checks passed!')

I believe that it should be like this (I put the change in bold text on the line with an arrow):

assert(Object.getOwnPropertyNames(felixProto).length, 1)
assert(Object.getOwnPropertyNames(felixProtoProto).length, 1)
---> assert(Object.getOwnPropertyNames(felixProtoProtoProto).length, 1)
assert(typeof felixProto.meow, 'function')
assert(typeof felixProtoProto.purr, 'function')
assert(typeof felixProtoProtoProto.hiss, 'function')
console.log('prototype checks passed!')

Just to let you know in case it can improve the course.

Regards.

federicopenaranda · February 13

Hi, I'm doing the LFW211 course, and I found a typo, double "the":

Using a caret on version numbers is basically the same as using an x in the MINOR and PATCH positions, so ^7.6.2 is the same as 7.x.x. However there are exceptions when using 0, for example ^0.0.0 is not the the same as 0.x.x, see the "Caret Ranges ^1.2.3 ^0.2.5 ^0.0.4" section of npmjs Documentation. For non-zero MAJOR numbers, ^MAJOR.MINOR.PATCH is interpreted as MAJOR.x.x.

https://trainingportal.linuxfoundation.org/learn/course/nodejs-application-development-lfw211/packages-dependencies/packages-dependencies?page=7

Regards.