- Added namespace

[AlexBacich]

No description provided.

[theshivamlko]

@alexrintt can u approve this , required in my project. I have done this locally

[alexrintt]

@theshivamlko is your project an app? If so, add a git dependency to AlexBacich's fork:

dependencies:
  shared_storage:
    git:
      url: https://github.com/AlexBacich/shared-storage
      ref: master

If your project is another package I don't recommend depending on shared_storage because I'll archive it soon.

[AlexBacich]

@alexrintt , are you going to abandon this one? It's quite useful and I think I'm not the only one using it. Unless there are better alternates.
If you don't mind can you please add me to its owners so I could keep maintaining.

[alexrintt]

are you going to abandon this one?

Yes, I'm not actively working on this package anymore.

It's quite useful and I think I'm not the only one using it. Unless there are better alternates.

There are, maybe. I'm not aware of any yet but SAF is a common use-case.

If you don't mind can you please add me to its owners so I could keep maintaining.

Actually I prefer you to use your own repository because you will be the one maintaining it, it's easier to manage this way (CI/CD, permissions, secrets, etc.).

You can also replace the package name with a name of your choice and publish to pub.dev.

If you agree with that, I will add a deprecation notice and a link redirecting to your repository.

What do you think?

[AlexBacich]

@alexrintt , I think that's better option than simply abandoning.

However, the most optimal one feels to me to keep just one project. You can add me in Package Ownership in
https://pub.dev/packages/shared_storage/admin

And similar thing in the GitHub repository.

This way we may maintain consistency in issues, commits history, etc. And no need to migrate from one package to another.

[theshivamlko]

@AlexBacich Fork it, publish your own, else I am doing it, there are so many duplicate packages already on pub.dev

[AlexBacich]

@theshivamlko , go for it.