Add Faker::TvShows::TheOfficeOriginal

[tardate]

Issue#

No-Story

Description:

Because, you know, I saw Faker::TvShows::TheOffice get added yesterday in #2320 and couldn't resist placing a tombstone for the original (although selecting SFW quotes proved a little more difficult than I expected/remembered!). As Ricky Gervais himself has said:

He was a jobbing actor, career not going that well if I'm being perfectly honest, who got his big break when I cast him in a show called 'The Office.' He is now leaving that show, and killing a cash cow for both of us. Please welcome the wonderful Tina Fey, and the ungrateful Steve Carell!”

[psibi]

I'm slightly nervous about adding multiple similar like modules, Instead can we have a single module with a single yaml file but with different entries for various variations: https://en.wikipedia.org/wiki/The_Office#Counterparts

I guess in the new setup, the code will look like this:

Faker::TvShows::TheOffice.character_uk

[itay-grudev]

Maybe this belongs in the Faker::TvShows sister project.

[psibi]

I'm not sure how maintained that sister project is, and I'm fine with this residing in this package. But I think this should be under a single namespace instead of having various different variations and module.

[fakefarm]

This is great!

[stefannibrasil]

Hey there. In an effort to lighten our load as maintainers and be able to serve you better in the future, the faker-ruby team is working on cleaning out the cobwebs in this repo by pruning the backlog. As there are few of us, there are a lot of items that will simply never earn our attention in a reasonable time frame, and rather than giving you an empty promise, we think it makes more sense to focus on more recent issues. That means, unfortunately, that we must close this PR.

Don't take this the wrong way: our aim is not to diminish the effort people have made or dismiss problems that have been raised.

If you feel that we should reopen this PR, please do the following first:

• rebase with master to fix any conflicts
• verify this contribution is still relevant (i.e. hasn't been implemented/solved yet)
• run tests again

Then please let us know so that we can re-prioritize it. Thanks!