Skip to content

Move to graphp organization #130

@clue

Description

@clue

Now that all components have been split off into separate packages under the graphp organization, we should eventually also move this repository.

Things to consider:

  • Does this involve any BC breaks? What about consumers of this package?
  • Should we rename this package to the "graphp" vendor?
  • If so, what package name should we assign?

I'd like to migrate previous issues, PR, among with all watchers and stargazers, so forking does not seem to be an option.

Any input would be much appreciated!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions