Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix packaging info in prep for influx of packaging maintainers #158

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kaosine
Copy link
Member

@kaosine kaosine commented Dec 25, 2022

Starting pr to update this info and link it here, this'll probably be a start in a move towards hopefully updating to a more advanced and proper site(especially getting around the warts of vuepress that we've noticed over time). But this info is necessary imo asap for package maintainers esp in a notice here depending on what we do going forward.

This is a draft PR and should be treated as such, it is open for edits and suggestions like all draft prs we create here. Suggestions are welcomed and in fact needed.

Starting pr to update this info and link it here, this'll probably be a start in a move towards hopefully updating to a more advanced and proper site(especially getting around the warts of vuepress that we've noticed over time). But this info is necessary imo asap for package maintainers esp in a notice here depending on what we do going forward.
@kaosine kaosine changed the title Update index.md Fix packaging info in prep for influx of packaging maintainers Dec 25, 2022
@Daeraxa
Copy link
Member

Daeraxa commented Dec 27, 2022

I'm not sure I understand what this PR is adding or designed to add when fleshed out?

@kaosine
Copy link
Member Author

kaosine commented Dec 28, 2022

@confused-Techie can probably fill you in more, but the general idea is to add notices on that Community Packages page, and have it give links to the packaging instructions. Then beyond there, making sure with #14 to fix the order of the docs into a more user-friendly format. Which #14 may be what this one is dependent on....not sure. Unless we don't change many of the links that is....

@kaosine
Copy link
Member Author

kaosine commented Dec 28, 2022

Err not #14 but #60 my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants