How does this compare to the AWS Labs alpha version?

[pimhakkert]

Hi team,
I see you’ve added a significant backend and frontend on top of https://github.com/awslabs/aws-js-s3-explorer/tree/v2-alpha, which looks like a great addition. Ideally, this project should have been created by properly forking the original repo from the start, that’s the best way to keep clear history and credit. At minimum, proper attribution should be added now to respect the open source community and help users track updates. Thanks for understanding!

[wparad]

That's not a bad idea, we might just do that. Although at this point besides some of the styling here, there isn't really anything left that represents that original repo. So I'm not sure that makes as much sense. I'm a bit torn.

How about this, if there are enough people that give a 👍 on this issue, we'll at some link to the obsoleted AWS labs managed version.

[pimhakkert]

I agree that most of the project has changed, and I understand where you're coming from.

That said, since this project originated from that repository, it feels right to acknowledge the original work. Even if attribution may not be strictly required under the Apache License 2.0 in this case, it’s still the respectful and ethical thing to do.

As an alternative, you could refer to that repository as the original frontend-only implementation of the S3 explorer, which this project has expanded upon.

[wparad]

I don't think that makes sense either, as this is also a front end only solution which is basically a complete rewrite of that. And actually for what it's worth, this didn't actually originate from that one, while same things were taken, most of what we have here was inspired by a number of things, not only all open source.

If there is a large chunk of code left that we missed applying the appropriate license, please let me know so that we can get this updated.

[pimhakkert]

Ah I'm sorry for that, I was referring to your addition of Cognito/Authress. Appreciate the clarification. If this was more of a rewrite inspired by various sources rather than a direct fork, then that changes things. I originally got that impression because the structure and functionality felt closely aligned with the AWS Labs project.

If the code is indeed mostly/all new, then linking as inspiration rather than attribution might be more appropriate, in which case I think your original suggestion is more than enough. Thanks for being open to updating things if anything was reused directly.