NEW REPO! DO NOT OPEN ISSUES HERE

[haarts]

This is the new home of this library:

https://github.com/SourceHorizon/logger

[josh-burton]

Is it? Why not archive this repo?

Is this fork published on pub.dev? Is flutter_logger forked and published too?

As someone looking to start using logger, its quite confusing where to start, and what is or isn't maintained.

[haarts]

This is because I took over the maintenance of this repo some time ago. But I wasn't assigned admin rights (I also forgot to ask).

I want to step back from this project and have found several very capable new maintainers. But because I do not have admin rights, I cannot add new maintainers. Nor can I archive this repo. I've tried contacting the original author several times via several routes but he is unresponsive.

That is why the repo is now forked. That fork is now the canonical repo.

I did have admin rights on pub.dev, so nothing changes there. The new maintainers will push new versions there.

I never took any ownership of flutter_logger, so I can't comment there.

[Bungeefan]

Hi, I am one of the new maintainers of this project, alongside with @Oliinyk-Volodymyr.

Unfortunately, as Harm mentioned, we cannot use the original repository, but we are able to upload and maintain the pub.dev package.

We've already talked about flutter_logger package and whether we should provide a fork for that as well.

At the moment there is no definite answer to this, however my opinion is that if there is enough demand for it, we can certainly try to fork it and publish it as a new package on pub.dev (since none of us has access to the original).
On the other hand, there are already some maintained forks with their respective packages on pub.dev, so you could probably use one of those without any problems.

See simc/logger_flutter#24 (comment)

[haarts]

See also https://pub.dev/packages/logger_flutter_plus

[holocronweaver]

@Bungeefan @haarts Please create/reuse a Github org for the forked package, similar to say hivedb, rather than moving it under another single user. That way changing maintainers will not involve changing repos, avoiding confusing situations like this which also lose issues / analytics / stars / etc. Using orgs also makes it clearer who has permissions for the org for newcomers and thus who to contact when permissions are needed.

I also suggest adding at least two people with admin rights to the org, ideally 3+, to avoid one person leaving the project resulting in the need to fork. The non-primary admins need not be currently active in the project, just reasonably active on Github so they can act as a backup point of contact.

Aside: please keep using the flutter_logger package - this isn't a 'true' fork afaict, just maintenance changing hands due to an absentee admin, so no need to change the name.

[Bungeefan]

@holocronweaver
Sorry for the long delay for a proper response, I would certainly welcome an organization for the logger repository, however we need a proper name for it that doesn't need to be changed it in a year or so.
We are not really affiliated with anything, nor was there a brand name (or similar) before, and we cannot name it "logger".

So if anyone has got a good unused name that we can use, I am ready to create an org and move logger under it.

[Bungeefan]

@holocronweaver Your wish has come true! 🎉

I am happy to announce that the logger repository is now under a new organization with both me and @haarts as owners!