Archived
15
23
Fork
You've already forked meta
6

Social media handle #21

Closed
opened 2022年11月07日 17:44:21 +01:00 by Ghost · 15 comments
- [x] pick a mastodon instance - [x] create a mastodon account - [x] archive the credentials in the https://codeberg.org/codename/secrets repository
Ghost added this to the Launch milestone 2022年11月07日 17:44:21 +01:00

@codename/Owners anyone willing to take care of this one?

@codename/Owners anyone willing to take care of this one?

Happy to take care of the social media handle, once a name is picked. In the meantime I will look for several instances that is in-line with codename's ideals.

Happy to take care of the social media handle, once a name is picked. In the meantime I will look for several instances that is in-line with codename's ideals.
Contributor
Copy link

It says 'mastodon' account. Prefer always referring to them as 'fediverse' account. And different apps, e.g. GoToSocial can be considered (programmed in Golang in a great project culture). GtS is light-weight, much more than Mastodon. Self-hosting can be considered.

A further option is that The Forgers Guild starts an instance under the domain of smithy.town (which given my last notes on naming remains unused.. and having it available under the guild has my preference). This instance is then only available to members of the guild for account creation.

It says 'mastodon' account. Prefer always referring to them as 'fediverse' account. And different apps, e.g. GoToSocial can be considered (programmed in Golang in a great project culture). GtS is light-weight, much more than Mastodon. Self-hosting can be considered. A further option is that The Forgers Guild starts an instance under the domain of `smithy.town` (which given my last notes on naming remains unused.. and having it available under the guild has my preference). This instance is then only available to members of the guild for account creation.
Member
Copy link

Alternatively it could be under forg.es?

That way related projects like ForgeFed could have accounts without appearing to be tied to Smithy (if that name is chosen for Codename)

Alternatively it could be under `forg.es`? That way related projects like ForgeFed could have accounts without appearing to be tied to Smithy (if that name is chosen for Codename)
Member
Copy link

For the record, a conversation about this took place on Matrix a couple of days ago.

Self-hosting was discussed, and was strongly discouraged by @dachary and @fnetX on account of the mantenance overhead, and a consensus appeared to emerge that using an existing trustworthy instance is probably preferable, at least at first.

However an instance was not chosen.

For the record, [a conversation about this took place on Matrix](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$yGyA2Ldu9ndRBdVYWlbUP4DaJgLDMFVJ5uHFDz4tDok) a couple of days ago. Self-hosting was discussed, and was strongly discouraged by @dachary and @fnetX on account of the mantenance overhead, and a consensus appeared to emerge that using an existing trustworthy instance is probably preferable, at least at first. However an instance was not chosen.
Member
Copy link

In my opinion Fosstodon would be an appropriate instance. It appears to be well managed and is used by many popular FLOSS projects such as LibreOffice, Home Assistant, QGis, Owncast, HedgeDoc, etc.

I'm sure there are other good options too though.

In my opinion [Fosstodon](https://hub.fosstodon.org/about/) would be an appropriate instance. It appears to be well managed and is used by many popular FLOSS projects such as LibreOffice, Home Assistant, QGis, Owncast, HedgeDoc, etc. I'm sure there are other good options too though.

I put my 2 cents for https://floss.social/ where ForgeFed is already hosted.

I put my 2 cents for https://floss.social/ where ForgeFed is already hosted.

I think FLOSS social would be better suited.

I think FLOSS social would be better suited.
Owner
Copy link

https://rage.love/@noyovo/109123918096643685 during the Codeberg Mastodon migration, there was this voice recommending against Fosstodon (just dropping this for the record). I moved to floss.social with another project, it's also great. https://mstdn.social/ is also likely a good choice.

I don't have a preference.

https://rage.love/@noyovo/109123918096643685 during the Codeberg Mastodon migration, there was this voice recommending against Fosstodon (just dropping this for the record). I moved to floss.social with another project, it's also great. https://mstdn.social/ is also likely a good choice. I don't have a preference.
Member
Copy link

I haven't noticed right wing racists on Fosstodon, but I'd also be fine with floss.social since that's three recommendations for that now.

I haven't noticed right wing racists on Fosstodon, but I'd also be fine with floss.social since that's three recommendations for that now.
Member
Copy link

I went ahead and registered @forgejo@floss.social.

It is pending approval; one it's approved I'll share the credentials in the secrets repo.

I went ahead and registered `@forgejo@floss.social`. It is pending approval; one it's approved I'll share the credentials in the secrets repo.

@caesar It should have been confirmed, but nothing on https://floss.social/@forgejo yet.

@caesar It should have been confirmed, but nothing on https://floss.social/@forgejo yet.
Member
Copy link

The account is now active and credentials are shared in the secrets repo.

The account is now active and credentials are shared in the secrets repo.

Apologies for writing in a closed issue. The "bio" of the account is

\ˈfor.d͡ʒe.jo\ – a libre code forge (a soft fork of Gitea)

I really like the IPA bits. I think the following sentence should mention "community" in some way, e.g. community run soft fork of Gitea. Obviously when a final tagline is ready, that will take precedence.

Apologies for writing in a closed issue. The "bio" of the account is > \ˈfor.d͡ʒe.jo\ – a libre code forge (a soft fork of Gitea) I really like the IPA bits. I think the following sentence should mention "community" in some way, e.g. *community run soft fork of Gitea*. Obviously [when a final tagline is ready](https://codeberg.org/forgejo/meta/issues/42), that will take precedence.
Member
Copy link

Apologies for writing in a closed issue.

Not a problem at all!

I really like the IPA bits. I think the following sentence should mention "community" in some way, e.g. community run soft fork of Gitea. Obviously when a final tagline is ready, that will take precedence.

Yes, I agree, mentioning community would be good. I didn't want us to be defined by being a fork of Gitea, but on the other hand, at first, it will help people understand what we are. I'll update it to match your suggestion for now.

> Apologies for writing in a closed issue. Not a problem at all! > I really like the IPA bits. I think the following sentence should mention "community" in some way, e.g. *community run soft fork of Gitea*. Obviously [when a final tagline is ready](https://codeberg.org/forgejo/meta/issues/42), that will take precedence. Yes, I agree, mentioning community would be good. I didn't want us to be defined by being a fork of Gitea, but on the other hand, at first, it will help people understand what we are. I'll update it to match your suggestion for now.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
7 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#1 Pick a name
forgejo/meta
Reference
forgejo/meta#21
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?