2

There is a github php library which is used quite a lot, but the problem is the original author seems to have gone AWOL and despite myself and other members of the dev team (who themselves are not particularly active due to time constraints) trying to contact him many times over a long period (several months now) he has been totally unresponsive.

Meanwhile there is a very large backlog of open PRs and issues for this repository, and it is used by many people.

I want to make a "hard fork" of it - with the following requirements

  • Must start from the latest code that's there now

  • Must be able to be used by other people with a simple package name change in the composer file (so should be distinguishable from the original package in packagist without having to override repo source)

  • Ideally, would be possible to merge it back into main repo if the author ever wakes up from his slumber

I am looking for any other tips from people who may have been in the same situation.

I am quite happy to continue maintaining this repo as I use it in many personal projects as well as at work in commercial projects.

As far as I understand my main 2 avenues would be:

  • Change the composer.json file in my fork of the repo (up to date) to rename the package to coincide with my GitHub user and register it on packagist;

  • Create a new repository with a different name, using latest code as starting point, and register it on packigist.

Any advise appreciated, thanks.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
user2627591
  • 31
  • 1

1 Answers1

0

To avoid any future issue, you should create a new repository in an organization, because there:

  • you can fork a fork (in an organization): if that new repo is no longer (later on) the active one, you can fork it.
  • you can make it depend on a theme, represented by the organization, as opposed to an author (which is problematic today)

In both instances, you do need to register a new reference to packagist.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250