A new name for the project

[joshuaboniface]

I'm looking for suggestions for a new project name to separate this project from the parent Emby project.

My current personal thoughts:

• Openby
• Libremby
• OpenMB

[anthonylavado]

OpenBY is unused, but it also sounds like “Open By”.

I like it best out of the choices however. I have no other suggestion.

[PrplHaz4]

+1 for OpenMB - historical context, but not as ....litigious

[AYANE-69]

+1 OpenMB

[angrymbadmin]

+1 OpenMB, everything containing "emby" (or something phonetically similar like OpenBy) should be avoided, this would be one of the ways L**e could possibly cause legal problems.

[AYANE-69]

I did say "+1 OpenMB" but the more I think about it the more I dislike the idea.
Open + two capitalised letters is very much a Khronos thing and although that in itself isn't bad I just think its another point of possible future conflict that could be avoided.

I also think that perhaps a total separation from "emby" which is MB which is Media Browser should be taken. I personally don't think "media browser" is an apt title for this kind of software anyway as it only speaks to half it's functionality and not really the half that makes it special (although I guess that is very much opinion). This software is a media database server with front end clients that consume the media served. If anything the core name should relate to the server and clients use that name plus a postfix of "Player" or some thing similar.

That said I would like to go out on a limb and throw a few more generic names into the mix to help get the creative juices flowing:
SVDB - Sound and Vision Database
SVS - Sound and Vision System
OMS - Open Media System
OMO - Open Media Organiser
MIMO - Media In Media Out

[zacharyrs]

+1 to OMO

[junnotpiper]

How is the name proposal coming along?

[JustAMan]

+1 to OMO

@joshuaboniface
What's the current intention - keep the fork based on 3.4 or follow @dcrdev route and rebase from 3.5 to build on .net core?

[joshuaboniface]

I think OpenMB is the way to go here, I like it a lot more than OMO to be honest.

@JustAMan I focused on 3.4 due to it having less closed off, but @dcrdev has done a bunch more work on 3.5 that would be valuable here, so I'm going to follow his rebase.

[nvllsvm]

OpenMB is already used for something that appears to be multimedia related.

[joshuaboniface]

Well then... scrap that one!

LibreBrowser, LibreMedia, couple more ideas off the top of my head.

[nvllsvm]

Libre and open prefixes always came off as a little cheesy as it comes off as a reimplementation of something. We can make our fork better than the original so our name should be our own.

Some of the streaming/water/sea themed ideas of mine are jellyfin, cuttlefin, mediamarsh. I'm quite fond of Jellyfin :P

[joshuaboniface]

Ooh, I like Jellyfin and MediaMarsh.

[anthonylavado]

Vote for JellyFin

[nvllsvm]

I've registered both jellyfin and jellifyn organizations on GitHub.

[joshuaboniface]

It's fantastic @nvllsvm ! Works fantastic both as a place for the former Emby today, and a place for a possible new alternative (or three) in the future to live.

Based on the discussions in #11 we can probably fork @JustAMan 's copy to there - I'm going to try building it this weekend and go from there. We can then merge in any changes from @dcrdev 's repo that might be missing (I'm not sure how much you guys based off each other). Hope that sounds good to everyone!

[joshuaboniface]

I think a good repo name is jellyfinby for the Emby fork. Emphasizing that connection while not locking the name entirely to the codebase that is Emby (see #11 and my thoughts there).

[nvllsvm]

That's a lot to look at. I'd rather we stick with plain jellyfin for now and change it in the future if we rewrite or something. The name should be simple, but catchy for normal users. I already know a number of people who say "embry".

[nvllsvm]

Also - I registered a jellyfin organization on Docker Hub.

[joshuaboniface]

@nvllsvm Sounds good to me!

[joshuaboniface]

Rename completed - the project is available at https://github.com/jellyfin/jellyfin.

[joshuaboniface]

@nvllsvm It seems Jellyfin conflicts with another project: https://github.com/jelly-fin/jelly-fin-native (thanks to @bobmarley2021 in #11 for pointing that out) That might cause us some issues in the future, so shall we bite the bullet today and try something else? We can rename the org and repo pretty easily at this point, but let me know what you think. MediaMarsh seems like it's available software-wise (someone else has that on twitter, and there's a business with the words reversed, but those should be OK IMO). Or another option - something similarly short and catchy?

[JustAMan]

MediaHog? Or... Hedgehog (see it as a hedgehog gathering apples and mushrooms and carrying all that on the back... in our case instead of apples there would be media files)

[joshuaboniface]

MediaHog with a hedgehog logo (so people don't think "pig", though TBH that works too!) works for me, and seems free from a quick search.

[dcrdev]

Hmm seems like I've missed a lot - so not sure if this is the correct medium to post this. In any case I for one am glad Emby has gone closed source, they can finally stop masquerading as an GPL project.

The reason I've been quiet as of late is because I really haven't had the time to pursue my fork on my own. That said it looks like that situation is changing and you guys are really interested in continuing development.

I've been solely acting acting as a .NET developer in my day job for the past 6/7 months - so let me know any way I can help!

Really good to see people coming together on this!

[joshuaboniface]

@dcrdev Glad to hear! TBH I feel the same way, their attitudes were not compatible with Free Software ideals for a long time before this, and it is a bit of a kick in the pants to get us thinking about this again, which is ultimately a good thing IMO.

We've given you full access to the jellyfin repo (along with @JustAMan, @nvllsvm and I) so feel free to let us know how that copy looks. It was based on @h3ge's fork, but when I tried a simple merge last night it had a lot of conflicts with yours and my forks.

[joshuaboniface]

Discussed the naming on Riot, @nvllsvm and I agree the dash is enough to differentiate us. Pushing ahead with the name.