mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
Rename project and elements #1
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joshuaboniface on GitHub (Dec 9, 2018).
With this fork being named
jellyfin, we'll need to differentiate this repo by renaming anything we reasonably can. This might just be the README for now, but long-term anything referencing Emby should be updated.@anthonylavado commented on GitHub (Dec 9, 2018):
I can work on at least the README. Ideally we’ll want to move a lot of it (the statements on why the project exists, etc) out to the Wiki. We’ll probably need to take out the screenshots too.
@JustAMan commented on GitHub (Dec 9, 2018):
I think that motivation for the project should stay in the Readme along with what the project is about.
Screenshots definitely belong to a wiki page (linked to in the readme, though, so ppl would be able to find them easily).
@anthonylavado commented on GitHub (Dec 9, 2018):
@JustAMan - I’ll talk with @joshuaboniface on this too, but would a statement, followed by “Read more” with a link to the wiki be good?
I’m just thinking ahead to people that might come across this, so I would want to have a nice quick page that briefly tells them about the project, and how to get started.
Admittedly I’m not a master at this. You can see a README for a project I help maintain: https://github.com/mike-grant/haaska/blob/master/README.md
Here’s a good example from a semi-popular template:
https://gist.github.com/PurpleBooth/109311bb0361f32d87a2
@anthonylavado commented on GitHub (Dec 9, 2018):
Linking here: there is some work in #6
@JustAMan commented on GitHub (Dec 9, 2018):
I had a look at your readme and now I get your point. I think we can safely move "motivation" to wiki leaving a link in readme. Ideally it might just be a paragraph about what is this project plus a few links for further reading.
@joshuaboniface commented on GitHub (Dec 9, 2018):
I agree, my essay doesn't need to be in the README 😆
@joshuaboniface commented on GitHub (Dec 10, 2018):
@nvllsvm 's PR #6 has been merged, which gets rid of the old Emby images and such from the README. I'm going to start splitting things out now to get the README condensed.
@anthonylavado commented on GitHub (Dec 10, 2018):
@joshuaboniface Don't know how far along you are, but here's a handy badge I found that you can use: https://matrix.to/img/matrix-badge.svg
@joshuaboniface commented on GitHub (Dec 11, 2018):
Suplemented by practical action in #25