Is there no other second level directory that makes sense for this component to be moved under? Also, anybody else who might have an opinion on where this sub-component lives? 

Re. second level: Currently we have Blink>MediaStream>Recording,
but, as I say in the description, this is non intuitive for the
users and testers, since MS is the source of data, whereas users 
look at this for the PoV of what they want to achieve, i.e.
record. 

Also this particular area has bugs related to e.g. hardware support
for encode acceleration that do not relate to MediaStream, hence the
move.

Adding two peeps that might want to toss an opinion.

Principled: Do we have recording features that don't use MediaStream?

I'm afraid the component might be a magnet for things like event recording, timing trace recording and other stuff that records non-media.

I'm not afraid of attracting stuff like "how do I record output of WebAudio" where the MediaStream-based recorder is actually a good answer.

Do we have example bugs that were misclassified due to the "hiding"?

#3: I propose then to call the new component Blink>MediaRecorder,
which would prevent the wrong stuff from being attracted.

Re. misclassification: I strongly believe that hiding Recorder
under MediaStream relates to the way things are implemented.
E.g. in the near future we'll have Streams (the "other" streams)
of video/audio being recorded as well, by the same underlying
infrastructure.

Discussed briefly offline w/ hta@ and I think he agrees with this component reshuffling; quoting myself:

> [...] part of the reason of moving this thing up is to make it more evident for testers to classify things... if we call it MediaRecorder, I think your concerns would be addressed.

> IOW I have seen that only a minority of developers are familiar with the concept of a MediaStream{Track}. And those that are, are mostly those working on Specs. MS is almost an abstract concept. Most of the bugs get misclassified as WebRtc or GetUserMedia. 

> (I would also recommend trying to remove the Blink>MediaStream component in the long term, because is confusing in its overlap with Blink>GetUserMedia and Blink>WebRtc)

So, what is the component name agreed upon between mcasas@ and hta@?

Blink>MediaRecording

(happens to be also the name of the main JS
class/idl and the caniuse entry [1])

[1] http://caniuse.com/#feat=mediarecorder

I concur with Blink>MediaRecording.

If I read it correctly, the remaining subcomponent is Blink>MediaStream>CaptureFromElement - I wouldn't mind Blink>MediaCaptureFromElement either, leaving Blink>MediaStream strictly for issues dealing with media-stream infrastructure.

+1 to #9, but we should file another Component request for it:
http://www.chromium.org/issue-tracking/requesting-a-component-or-label

Created Blink>MediaRecording and made mcasas@ and hta@ admins for it. Please make sure to add a good description to the component asap. Thank you! Closing this bug, please reopen if there is any error.

sshruthi@ I moved all the component:Blink>MediaStream>Recording
bugs to component:Blink>MediaRecording.

Could you please remove component:Blink>MediaStream>Recording ?

Thanks!

Done, could you please verify we have everything we need and close this bug, if so? Thank you!

#13: done, thanks!