feat: change package name

Author: iwaltgen

CONTRIBUTING.md

@@ -10,7 +10,7 @@ the [Proto.Actor gitter chat](https://gitter.im/asynkron/gam).
 Depending on which version (or sometimes module) you want to work on, you should target a specific branch as explained
 below:
 
-* `dev` – active development branch of Proto.Actor beta.
+- `dev` – active development branch of Proto.Actor beta.
 
 ## Tags
 
@@ -19,20 +19,20 @@ Proto.Actor uses tags to categorise issues into groups or mark their phase in de
 Most notably many tags start with a `t:` prefix (as in `topic:`), which categorises issues in terms of which module they
 relate to. Examples are:
 
-- [t:actor](https://github.com/asynkron/protoactor-go/labels/t%3Aactor)
-- [t:remote](https://github.com/asynkron/protoactor-go/labels/t%3Aremote)
-- [t:cluster](https://github.com/asynkron/protoactor-go/labels/t%3Acluster)
-- [t:router](https://github.com/asynkron/protoactor-go/labels/t%3Arouter)
-- [See all labels](https://github.com/asynkron/protoactor-go/labels)
+- [t:actor](https://github.com/keecon/protoactor-go/labels/t%3Aactor)
+- [t:remote](https://github.com/keecon/protoactor-go/labels/t%3Aremote)
+- [t:cluster](https://github.com/keecon/protoactor-go/labels/t%3Acluster)
+- [t:router](https://github.com/keecon/protoactor-go/labels/t%3Arouter)
+- [See all labels](https://github.com/keecon/protoactor-go/labels)
 
-In general *all issues are open for anyone working on them*, however if you're new to the project and looking for an
+In general _all issues are open for anyone working on them_, however if you're new to the project and looking for an
 issue
 that will be accepted and likely is a nice one to get started you should check out the following tags:
 
-- [community](https://github.com/asynkron/protoactor-go/labels/community) - which identifies issues that the core team
+- [community](https://github.com/keecon/protoactor-go/labels/community) - which identifies issues that the core team
   will likely not have time to work on, or the issue is a nice entry level ticket. If you're not sure how to solve a
   ticket but would like to work on it feel free to ask in the issue about clarification or tips.
-- [nice-to-have (low-priority)](https://github.com/asynkron/protoactor-go/labels/nice-to-have) - are tasks which make
+- [nice-to-have (low-priority)](https://github.com/keecon/protoactor-go/labels/nice-to-have) - are tasks which make
   sense, however are not very high priority (in case of other very high priority issues). If you see something
   interesting in this list, a contribution would be really wonderful!
 
@@ -54,15 +54,15 @@ issue is:
 
 The last group of special tags indicate specific states a ticket is in:
 
-- [bug](https://github.com/asynkron/protoactor-go/labels/bug) - bugs take priority in being fixed above features. The
+- [bug](https://github.com/keecon/protoactor-go/labels/bug) - bugs take priority in being fixed above features. The
   core team dedicates a number of days to working on bugs each sprint. Bugs which have reproducers are also great for
   community contributions as they're well isolated. Sometimes we're not as lucky to have reproducers though, then a
   bugfix should also include a test reproducing the original error along with the fix.
 
 # Proto.Actor contributing guidelines
 
-These guidelines apply to all Proto.Actor projects, by which we mean both the `asynkron/protoactor-go` repository,
-as well as any plugins or additional repositories located under the asynkron/protoactor*.
+These guidelines apply to all Proto.Actor projects, by which we mean both the `keecon/protoactor-go` repository,
+as well as any plugins or additional repositories located under the asynkron/protoactor\*.
 
 These guidelines are meant to be a living document that should be changed and adapted as needed.
 We encourage changes that make it easier to achieve our goals in an efficient way.
@@ -72,17 +72,17 @@ We encourage changes that make it easier to achieve our goals in an efficient wa
 The steps below describe how to get a patch into a main development branch (e.g. `dev`).
 The steps are exactly the same for everyone involved in the project (be it core team, or first time contributor).
 
-1. Make sure an issue exists in the [issue tracker](https://github.com/asynkron/protoactor-go/issues) for the work you
+1. Make sure an issue exists in the [issue tracker](https://github.com/keecon/protoactor-go/issues) for the work you
    want to contribute.
-    - If there is no ticket for it, [create one](https://github.com/asynkron/protoactor-go/issues/new) first.
-1. [Fork the project](https://github.com/asynkron/protoactor-go#fork-destination-box) on GitHub. You'll need to create a
+   - If there is no ticket for it, [create one](https://github.com/keecon/protoactor-go/issues/new) first.
+1. [Fork the project](https://github.com/keecon/protoactor-go#fork-destination-box) on GitHub. You'll need to create a
    feature-branch for your work on your fork, as this way you'll be able to submit a pull request against the mainline
    Proto.Actor.
 1. Create a branch on your fork and work on the feature. For
    example: `git checkout -b wip-custom-serialization-protoactor`
-    - Please make sure to follow the general quality guidelines (specified below) when developing your patch.
-    - Please write additional tests covering your feature and adjust existing ones if needed before submitting your pull
-      request.
+   - Please make sure to follow the general quality guidelines (specified below) when developing your patch.
+   - Please write additional tests covering your feature and adjust existing ones if needed before submitting your pull
+     request.
 1. Once your feature is complete, prepare the commit following
    our [Creating Commits And Writing Commit Messages](#creating-commits-and-writing-commit-messages). For example, a
    good commit message would be: `Adding compression support for Manifests #22222` (note the reference to the ticket it
@@ -92,21 +92,21 @@ The steps are exactly the same for everyone involved in the project (be it core
    is not a feature.
 1. Now it's finally time to [submit the pull request](https://help.github.com/articles/using-pull-requests)!
 1. If you have not already done so, you will be asked by our CLA bot
-   to [sign the Asynkron CLA](https://cla-assistant.io/asynkron/protoactor-go) online. CLA stands for Contributor
+   to [sign the Asynkron CLA](https://cla-assistant.io/keecon/protoactor-go) online. CLA stands for Contributor
    License Agreement and is a way of protecting intellectual property disputes from harming the project.
 1. Now both committers and interested people will review your code. This process is to ensure the code we merge is of
    the best possible quality, and that no silly mistakes slip though. You're expected to follow-up these comments by
    adding new commits to the same branch. The commit messages of those commits can be more lose, for
    example: `Removed debugging using printline`, as they all will be squashed into one commit before merging into the
    main branch.
-    - The community and team are really nice people, so don't be afraid to ask follow up questions if you didn't
-      understand some comment, or would like clarification on how to continue with a given feature. We're here to help,
-      so feel free to ask and discuss any kind of questions you might have during review!
+   - The community and team are really nice people, so don't be afraid to ask follow up questions if you didn't
+     understand some comment, or would like clarification on how to continue with a given feature. We're here to help,
+     so feel free to ask and discuss any kind of questions you might have during review!
 1. After the review you should fix the issues as needed (pushing a new commit for new review etc.), iterating until the
    reviewers give their thumbs up–which is signalled usually by a comment saying `LGTM`, which means "Looks Good To Me".
-    - In general a PR is expected to get 2 LGTMs from the team before it is merged. If the PR is trivial, or under
-      special circumstances (such as most of the team being on vacation, a PR was very thoroughly reviewed/tested and
-      surely is correct) one LGTM may be fine as well.
+   - In general a PR is expected to get 2 LGTMs from the team before it is merged. If the PR is trivial, or under
+     special circumstances (such as most of the team being on vacation, a PR was very thoroughly reviewed/tested and
+     surely is correct) one LGTM may be fine as well.
 1. Once everything is said and done, your pull request gets merged :tada: Your feature will be available with the next
    “earliest” release milestone (i.e. if back-ported so that it will be in release x.y.z, find the relevant milestone
    for that release). And of course you will be given credit for the fix in the release stats during the release's
@@ -131,26 +131,26 @@ For a pull request to be considered at all it has to meet these requirements:
 1. The commit messages must properly describe the changes, see further below.
 1. All Asynkron projects must include Asynkron copyright notices. Each project can choose between one of two approaches:
 
-    1. All source files in the project must have a Asynkron copyright notice in the file header.
-    1. The Notices file for the project includes the Asynkron copyright notice and no other files contain copyright
-       notices. See http://www.apache.org/legal/src-headers.html for instructions for managing this approach for
-       copyrights.
+   1. All source files in the project must have a Asynkron copyright notice in the file header.
+   1. The Notices file for the project includes the Asynkron copyright notice and no other files contain copyright
+      notices. See http://www.apache.org/legal/src-headers.html for instructions for managing this approach for
+      copyrights.
 
    Proto.Actor uses the first choice, having copyright notices in every file header.
 
 ### Additional guidelines
 
 Some additional guidelines regarding source code are:
 
-- Files should start with a ``Copyright (C) 2017 Asynkron.se <http://www.asynkron.se>`` copyright header.
+- Files should start with a `Copyright (C) 2017 Asynkron.se <http://www.asynkron.se>` copyright header.
 - Keep the code [DRY](http://programmer.97things.oreilly.com/wiki/index.php/Don%27t_Repeat_Yourself).
 - Apply the [Boy Scout Rule](http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule) whenever you have
   the chance to.
 - Never delete or change existing copyright notices, just add additional info.
-- Do not use ``@author`` tags since it does not
+- Do not use `@author` tags since it does not
   encourage [Collective Code Ownership](http://www.extremeprogramming.org/rules/collective.html).
-    - Contributors , each project should make sure that the contributors gets the credit they deserve—in a text file or
-      page on the project website and in the release notes etc.
+  - Contributors , each project should make sure that the contributors gets the credit they deserve—in a text file or
+    page on the project website and in the release notes etc.
 
 If these requirements are not met then the code should **not** be merged into dev or master, or even reviewed -
 regardless of how good or important it is. No exceptions.
@@ -185,7 +185,7 @@ This must be ensured by manually verifying the license for all the dependencies
 
 Which licenses are compatible with Apache 2 are defined
 in [this doc](http://www.apache.org/legal/3party.html#category-a), where you can see that the licenses that are listed
-under ``Category A`` are automatically compatible with Apache 2, while the ones listed under ``Category B`` need
+under `Category A` are automatically compatible with Apache 2, while the ones listed under `Category B` need
 additional action:
 
 > Each license in this category requires some degree
@@ -220,8 +220,8 @@ Follow these guidelines when creating public commits and writing commit messages
 
 4. You can request review by a specific team member for your commit (depending on the degree of automation we reach, the
    list may change over time):
-    * ``Review by @gituser`` - if you want to notify someone on the team. The others can, and are encouraged to
-      participate.
+   - `Review by @gituser` - if you want to notify someone on the team. The others can, and are encouraged to
+     participate.
 
 Example:
 
@@ -239,5 +239,5 @@ Each project should be configured to use a continuous integration (CI) tool (i.e
 
 ## Related links
 
-* [Proto.Actor Contributor License Agreement](https://cla-assistant.io/asynkron/protoactor-go)
-* [Proto.Actor Issue Tracker](https://github.com/asynkron/protoactor-go/issues)
+- [Proto.Actor Contributor License Agreement](https://cla-assistant.io/keecon/protoactor-go)
+- [Proto.Actor Issue Tracker](https://github.com/keecon/protoactor-go/issues)

README.md

@@ -1,7 +1,7 @@
-[![Go Report Card](https://goreportcard.com/badge/github.com/asynkron/protoactor-go)](https://goreportcard.com/report/github.com/asynkron/protoactor-go)
-[![GoDoc](https://godoc.org/github.com/asynkron/protoactor-go?status.svg)](https://godoc.org/github.com/asynkron/protoactor-go)
-[![checks](https://github.com/asynkron/protoactor-go/actions/workflows/checks.yml/badge.svg)](https://github.com/asynkron/protoactor-go/actions/workflows/checks.yml)
-[![Sourcegraph](https://sourcegraph.com/github.com/asynkron/protoactor-go/-/badge.svg)](https://sourcegraph.com/github.com/asynkron/protoactor-go?badge)
+[![Go Report Card](https://goreportcard.com/badge/github.com/keecon/protoactor-go)](https://goreportcard.com/report/github.com/keecon/protoactor-go)
+[![GoDoc](https://godoc.org/github.com/keecon/protoactor-go?status.svg)](https://godoc.org/github.com/keecon/protoactor-go)
+[![checks](https://github.com/keecon/protoactor-go/actions/workflows/checks.yml/badge.svg)](https://github.com/keecon/protoactor-go/actions/workflows/checks.yml)
+[![Sourcegraph](https://sourcegraph.com/github.com/keecon/protoactor-go/-/badge.svg)](https://sourcegraph.com/github.com/keecon/protoactor-go?badge)
 
 ### [Join our Slack channel](https://join.slack.com/t/asynkron/shared_invite/zt-ko824601-yGN1d3GHF9jzZX2VtONodQ)
 
@@ -104,8 +104,8 @@ Next, install the [standard protocol buffer implementation](https://github.com/g
 commands to get all the necessary tooling:
 
 ```
-go get github.com/asynkron/protoactor-go/...
-cd $GOPATH/src/github.com/asynkron/protoactor-go
+go get github.com/keecon/protoactor-go/...
+cd $GOPATH/src/github.com/keecon/protoactor-go
 go get ./...
 make
 ```
@@ -122,6 +122,7 @@ those tests). We also skip directories that don't contain any tests.
 ```
 go test `go list ./... | grep -v "/_examples/" | grep -v "/persistence" | grep -v "/scheduler"`
 ```
+
 ## Hello world
 
 ```go
@@ -387,8 +388,8 @@ For more examples, see the example folder in this repository.
 
 ## Contributors
 
-<a href="https://github.com/asynkron/protoactor-go/graphs/contributors">
-  <img src="https://contributors-img.web.app/image?repo=asynkron/protoactor-go" />
+<a href="https://github.com/keecon/protoactor-go/graphs/contributors">
+  <img src="https://contributors-img.web.app/image?repo=keecon/protoactor-go" />
 </a>
 
-Made with [contributors-img](https://contributors-img.web.app). 
+Made with [contributors-img](https://contributors-img.web.app).

_examples/actor-autorespond/go.mod

@@ -2,8 +2,8 @@ module autorespond
 
 go 1.16
 
-replace github.com/asynkron/protoactor-go => ../..
+replace github.com/keecon/protoactor-go => ../..
 
 require (
-	github.com/asynkron/protoactor-go v0.0.0-00010101000000-000000000000
+	github.com/keecon/protoactor-go v0.0.0-00010101000000-000000000000
 )

_examples/actor-autorespond/main.go

@@ -4,7 +4,7 @@ import (
 	"fmt"
 	"time"
 
-	"github.com/asynkron/protoactor-go/actor"
+	"github.com/keecon/protoactor-go/actor"
 )
 
 // Auto Response in Proto.Actor is a special kind of message that can create its own response message

_examples/actor-backpressure/go.mod

@@ -2,9 +2,9 @@ module backpressure
 
 go 1.16
 
-replace github.com/asynkron/protoactor-go => ../..
+replace github.com/keecon/protoactor-go => ../..
 
 require (
 	github.com/asynkron/goconsole v0.0.0-20160504192649-bfa12eebf716
-	github.com/asynkron/protoactor-go v0.0.0-00010101000000-000000000000
+	github.com/keecon/protoactor-go v0.0.0-00010101000000-000000000000
 )

_examples/actor-backpressure/main.go

@@ -6,7 +6,7 @@ import (
 	"time"
 
 	console "github.com/asynkron/goconsole"
-	"github.com/asynkron/protoactor-go/actor"
+	"github.com/keecon/protoactor-go/actor"
 )
 
 // sent to producer to request more work

_examples/actor-deadletter/go.mod

@@ -2,10 +2,10 @@ module helloworld
 
 go 1.16
 
-replace github.com/asynkron/protoactor-go => ../..
+replace github.com/keecon/protoactor-go => ../..
 
 require (
 	github.com/asynkron/goconsole v0.0.0-20160504192649-bfa12eebf716
-	github.com/asynkron/protoactor-go v0.0.0-00010101000000-000000000000
+	github.com/keecon/protoactor-go v0.0.0-00010101000000-000000000000
 	golang.org/x/time v0.0.0-20210723032227-1f47c861a9ac
 )

_examples/actor-deadletter/main.go

@@ -8,7 +8,7 @@ import (
 	"time"
 
 	console "github.com/asynkron/goconsole"
-	"github.com/asynkron/protoactor-go/actor"
+	"github.com/keecon/protoactor-go/actor"
 	"golang.org/x/time/rate"
 )
 

_examples/actor-helloworld/go.mod

@@ -2,9 +2,9 @@ module helloworld
 
 go 1.16
 
-replace github.com/asynkron/protoactor-go => ../..
+replace github.com/keecon/protoactor-go => ../..
 
 require (
 	github.com/asynkron/goconsole v0.0.0-20160504192649-bfa12eebf716
-	github.com/asynkron/protoactor-go v0.0.0-00010101000000-000000000000
+	github.com/keecon/protoactor-go v0.0.0-00010101000000-000000000000
 )

_examples/actor-helloworld/main.go

@@ -4,7 +4,7 @@ import (
 	"fmt"
 
 	console "github.com/asynkron/goconsole"
-	"github.com/asynkron/protoactor-go/actor"
+	"github.com/keecon/protoactor-go/actor"
 )
 
 type (