TODOs

[sgoudham]

List of stuff we need to do before moving it to the catppuccin organisation.

• Update every port's ...user.css files to reflect the new location of files
  • I believe it's just the fields @namespace, @updateUrl
• Create and agree on structure of README
  • Create CONTRIBUTING.md
• Disregard unnecessary information in each port's README. (e.g stars badge is no longer relevant)
  • (I believe @nekowinston is interested in defining a build system to auto-generate these which ties into the above)
• Create issue labels for each port (I really hope there isn't a label limit 😅)
• Check that CODEOWNERS file is accurate

[nekowinston]

I think this list covers most of the TODOs. 👍

Disregard unnecessary information in each port's README

I'm not even sure that we need a README for each stylesheet, some of them are literally only "press stylus install" and you're done. Whats worth mentioning for some ports, like GitHub, is enabling CSP Patching in Stylus.

I really hope there isn't a label limit

nixpkgs currently has 166 labels so I don't think that will be an issue.

[sgoudham]

I was thinking a README for each port would be good because:

1. We're Catppuccin:tm: and our aesthetics are usually quite nice, the logo, main heading, catwalk image etc
2. Each port has its own LICENSE file and it's not always guaranteed to be MIT since there are user styles that are derivatives. Would be nice having that README footer with the license.
3. As you mentioned, some ports do have some special instructions and ideally I feel like it's the README's job to point that out.

I get it though, not particularly wanting to die on this hill and happy with any alternative solutions proposed

[spookyintheam]

I was looking into the automation stuff for the READMEs and trying to understand our automation goal.

• Do we want to only automate the main README so that any new userstyle we add gets added automatically to the list and keep the content of the userstyle README upto the userstyle maintainer? This would mean that we need to create a template for userstyles.
• Or do we also want to automate the userstyle READMEs since most of them are going to be the same except the display images. Of course, we can add additional checks for some specific userstyles like GitHub which need additional steps to use. This might be counterproductive. winston already mentioned that we can have additional steps for some userstyles mentioned in the main README itself.
  Would appreciate some light on this.

[rubyowo]

I can do the first TODO, however i need clarification.
Should the new uri point to the rfc, or the normal org?

[sgoudham]

Closing in favour of a project board.