Why not merging features to ViMusic ?

[KaKi87]

Hi,

I'm wondering what's the reason why this fork and its interesting features are distributed in a separate product instead of merging these in ViMusic ?

Also, it would be nice to highlight those features that are differenciating Ri from Vi in the README.

Thanks !

[ikanakova]

As far as I know, ViMusic is abandoned by its devoper, so it would be pointless to do pull requests because the merge would never happen.

[ikanakova]

Distinguishing the new RiMusic features from the original ViMusic features in the Readme is a good idea.

[KaKi87]

Indeed, well I guess I missed it because I'm not actually using either app, but recommended Vi from time to time to people who'd be interested in it, until someone made me discover Ri today.

I suppose I'll be recommending Ri from now on. ^^

[KaKi87]

Distinguishing the new RiMusic features from the original ViMusic features in the Readme is a good idea.

Well, now knowing that Vi is unmaintained, I don't find differenciating from it to be as much useful anymore, since this difference alone makes it an obvious choice. ^^

[ghost]

This'd make a good entry in the FAQs. As soon as I see "forked from ..." on a repo, I wonder why.

[KaKi87]

Usually not independently, no, but rather to submit PRs, hence my question.

Which have been answered of course, but having the answer in README instead of having to look for it here would be better indeed.

Most projects don't need an FAQ entry though : "forked from the abandoned ViMusic" should suffice.

[ikanakova]

Usually not independently, no, but rather to submit PRs, hence my question.

No, that's definitely not true - see https://en.wikipedia.org/wiki/Fork_(software_development)

[KaKi87]

From the very page you linked :

GitHub uses "fork" as its term for this method of contribution to a project.

[ikanakova]

According to GitHub, forks serve two purposes: Propose changes to someone else's project & Use someone else's project as a starting point for your own idea. That's the end of our discussion, because this is pointless, I think most people on GitHub understand what a fork is, so there's no point in explaining it in the readme or faq.

[KaKi87]

There's a reason why the part you highlighted is the second one : the first one is more frequent.

So, when the second happens, it does for a reason, which is good to be explained in READMEs.

Feel free not to reply, BWPanda and I already made our point.