Plan to move our repository to an organization account

[dahlia]

We're planning to move our GitHub repository to an organization account for better project management. We've requested GitHub support to help us acquire the inactive @fedify username for this purpose. Here's our formal request to GitHub support:

Dear GitHub Support,

I am writing to request the takeover of the inactive GitHub username “@fedify”. This username is currently held by an account that shows no activity since its creation—no repositories, contributions, or any other engagement.

I am the maintainer of the Fedify project (https://github.com/dahlia/fedify), which is an open source ActivityPub server framework. We would like to use this username as an organization account to host our project and related repositories.

The reasons for this request are:

1. The current “@fedify” account has been completely inactive with no public contributions or repositories
2. The name directly relates to our project's name and purpose
3. We need an organization account to better manage our growing open source project
4. The username would help us maintain consistent branding across different platforms (@fedify on npm, JSR, etc.)

If possible, we would greatly appreciate if you could help us acquire this username. We believe this would benefit the GitHub community by putting the inactive username to active use for an open source project.

Please let me know if you need any additional information to process this request.

Thank you for your time and consideration.

Best regards,
Hong Minhee (@dahlia)

If we successfully acquire @fedify, that will be our new organization name. If not, we'll choose an alternative name. We'll keep you updated on the progress!

In any case, we'll ensure a smooth transition with proper redirects from the current repository. Stay tuned for updates!

[dahlia]

Here's a quick update on our GitHub organization plans: GitHub support has informed us they no longer process inactive username requests. We'll try reaching out to the current owner of @fedify account to see if we can work something out.

We'll keep you posted on how this goes! 🤞

[ThisIsMissEm]

Three perhaps alternate names:

• fedify-js
• fedify-sdk
• fedify-framework

obviously not as good as just fedify though

[dahlia]

How about fedify-dev, which is consistent with the domain name fedify.dev?

[ThisIsMissEm]

Ha! I didn't even think of that one! I think I'd go with that then even though -org is leading in the polls

[dahlia]

Here's the poll!

https://hollo.social/@fedify/0194a0e3-a022-7671-8f80-c95ab42e0d50

[dahlia]

We've just moved the Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

• @dahlia/fedify → @fedify-dev/fedify
• @dahlia/botkit → @fedify-dev/botkit
• @dahlia/hollo → @fedify-dev/hollo
• @dahlia/fedify-amqp → @fedify-dev/amqp
• @dahlia/fedify-h3 → @fedify-dev/h3
• @dahlia/fedify-express → @fedify-dev/express
• @dahlia/fedify-postgres → @fedify-dev/postgres
• @dahlia/fedify-redis → @fedify-dev/redis
• @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
• @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
• @dahlia/fedichatbot → @fedify-dev/fedichatbot
• @dahlia/microblog → @fedify-dev/microblog

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!