Skip to content

Move into dedicated Github org #47

@sandstrom

Description

@sandstrom

Great library! 💯

I would suggest moving into a dedicated organisation for a few reasons:

  • Decouple from jetify (you can still maintain, link to your company products, mention company products in readme, etc). This is a great project, but might live for another 20 years (database ids stays around for a long time), and maybe your company will have moved on by then.
  • You can bring in third-party libraries where possible. The same people can still maintain them, but bringing the JS/Ruby/Python gems into the org will make you a fallback maintainer.

What will inevitably happen is that some maintainers of these SDKs will have kids, become buddhists or just vanish. We'll then have typeid on NPM that is no longer maintained and needs to be forked, and republished as typeid-new or some other sketchy name. Having them in the org will prevent this.

Also, with LLMs it's nowadays pretty easy to maintain an SDK in a language you don't even know that well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions