Skip to content

Instantly share code, notes, and snippets.

@tamaina

tamaina/misskey dev.md

Forked from syuilo/misskey dev.md
Last active March 1, 2021 04:21
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tamaina/0311717a780b72a7c4381271bf522ecb to your computer and use it in GitHub Desktop.
Save tamaina/0311717a780b72a7c4381271bf522ecb to your computer and use it in GitHub Desktop.
Download ZIP
Thoughts on the current state of Misskey development [by syuilo]
Raw
misskey dev.md

Translated by DeepL and aqz/tamaina @aqz@c2.a9z.dev.
Source (Japanese): https://gist.github.com/syuilo/1a8cc608b2ab7451151e409029a943bb

Recently, I've been feeling the limitations of developing Misskey as an individual.
The reason for this is, in a nutshell, that I can no longer take time for development and maintenance due to my job.
The only time I can develop Misskey and its surrounding projects is during my days off, which makes it difficult for me to do the following things, and I feel the limit of my personal development.
If you say it's a matter of motivation, that's all right, but I'm often devastated mental at work, and I can't make as much progress as I'd like.

  • It's hard to review PRs you have made.
    • It takes a while to catch up before you actually see the code.
      • Understanding the background and context
  • Difficult to ensure code quality
    • Other collaborators are volunteers, just like me, so sometimes they can't take the time, and sometimes they don't get to review codes.
      • However, if I feel unsure about changes I made, I ask for a review as much as possible and will continue to do so.
    • Maintaining CI is something we need to get serious about, but again, I don't have the time.
      • Tend to be lower priority than other tasks
      • I want to write an e2e test.
  • The documentation is not ready in time.
    • But again, I don't have the time.
    • If we don't have the right documents, we won't have enough contributors.
    • As for the translation, the volunteers are doing it very fast, so we are grateful for that.
      • It's just, "How do I translate this?" or "What is the purpose of this?" I'm the only one who can respond to them, so it creates a waiting state.
  • Unable to handle and sort out/groom issues
    • Collaborators are doing a rather good job here.:pray:
    • Sometimes I'll take a gander down on Saturday or Sunday, but my reaction will be delayed.
  • It's time consuming and painful for me to get direct inquiries to me like DMs.
    • Unlike an Issue, you have to answer right away.
    • A lot of English, so it's hard to understand the text.
    • If you have any problems, it is better for everyone to use issues or discussions rather than talking to me directly.
      • It would be better if we could provide such a place without relying on GitHub, but again, I don't have the time.

Almost all of the problems listed above would certainly be solved, or at least improved upon, if I had more time to work on them.
The only way to increase my hours would be to quit my job, but I don't have enough savings or donations to live on Misskey development alone, so that will be difficult at this point.

I have a blueprint, assuming I have the time.

  1. For some reason, I can find the time to develop Misskey.
  2. Documentation could be maintained.
  3. More contributors would be becoming.
  4. It would take some of the burden off of me so I could get on with more valuable tasks.
  5. CI could be maintained.
  6. Stability would increase.
  7. More users would be becoming.
  8. ✌

Thank you to everyone who supports Misskey (collaborators, contributors, patrons, and users):pray:
I would like to continue to develop it step by step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment