https://x.com/fluentd hasn't been updated since Oct 2022
- Dominant language
- Ruby
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 20
Description
### Describe the bug
`@fluentd` account on x.com (https://x.com/fluentd) hasn't been updated since Oct 2022.
And nobody of the currently active committers (@ashie @cosmo0920 @daipom @kenhys) have access to it.
In addition we don't know who has access to the account and how it's managed.
Although we have several important notices about Fluentd (such as Fluentd LTS), we aren't able to notify users them by it.
### To Reproduce
Please see https://x.com/fluentd
You'll find that https://x.com/fluentd/status/1582196334743863296 is the last post of this account.
### Expected behavior
The account https://x.com/fluentd should be managed appropriately.
At least the currently active committers should have access to the account.
In addition we should determine a rule for safely sharing this account among maintainers.
### Your Environment
```markdown
- Fluentd version:
- Package version:
- Operating system:
- Kernel version:
```
### Your Configuration
```apache
N/A
```
### Your Error Log
```shell
N/A
```
### Additional context
@edsiper @agup006 @repeatedly @tagomoris @toru-takahashi Does anyone have access to this account?
Contributor guide
Research direction
Start by reviewing the @fluentd account, its last post, and the access question directed to the listed maintainers. Done means establishing who can access the account and agreeing on a safe sharing and maintenance rule for future Fluentd notices.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100