Regarding the docs: should we add an explicit text banner to mention / clear up differences to the existing jwt-auth?

[mfn]

Now that https://laravel-jwt-auth.readthedocs.io/ is up, it might be confusing what this is related to https://jwt-auth.readthedocs.io/

Would it make sense to add an paragraph right on the first page to describe the difference? Maybe this would be a good place to also link to https://github.com/PHP-Open-Source-Saver/jwt-auth#migrating-from-tymondesignsjwt-auth (FWIW, I prefer having the migration part in the readme, because this makes it super quick available on github and also on the composer page)

[leon0399]

Yeah, looks great! I think adding this information (about relations to original package) to the homepage of documentation too is the way. Anyway, it looks very empty now 😄

What about migrating, worth keeping it in both places, IMO

[Messhias]

Yes, we should keep this section in the documentation because most of the users (to not say 100% hahahahha) came from the old package, so let's keep it.

[leon0399]

Shouldn't we move it to discussions?

[Messhias]

Yes, but what we talking about is:

• Keep the Tymon credit for the initial package and creation.
• Do our banner with our credits.

But to be honest the banner it's more a visual thing than a necessity, so for me to avoid all the copyrights and those stuff in the presentation we should just remove the banner and keep it as it is in the documentation.

[mfn]

KISS sounds good to me; can always be changed later

[Messhias]

KISS sounds good to me; can always be changed later

We can move those discussions to discord? I remember someone told to us to have a server to keep discussions alive in real-time.

[mfn]

I'm out with slack/discord or similar chats. They give a "walled garden" feeling where's on github it's all transparent in one place.

[Messhias]

I'm out with slack/discord or similar chats. They give a "walled garden" feeling where's on github it's all transparent in one place.

Makes sense, so let's keep it here :)