Make basm-rs great again
Opened this issue · 9 comments
MBGA
TODOs
- Put some cute logo to README (something like https://github.com/SAWARATSUKI/KawaiiLogos/blob/main/Go%20Lang/Golang.png)
- Host a rustdoc website (hopefully docs.rs)
- Buy basm.rs domain
- Create a branding website (대충 https://bun.sh/ 이런느낌으로)
- else?
로고를 만들었습니다. #101
Make basm-rs Great Again!
Made a new github org https://github.com/boj-rs, and invited @kiwiyou and @byeongkeunahn as owners
Whoa, I needed to setup 2FA on my phone for the first time to accept the invitation ;-)
Do you have some kind of plans on what to do?
I've also invited @Bubbler-4, who is creater of cargo-boj and gaboja. I am trying to gather Rust projects related to Baekjoon, such as basm and gaboja, in one place so that they can promote each other and create synergy. If everyone agrees to move the basm, gaboja, and cargo-boj projects under the boj.rs organization on GitHub, I plan to purchase the domain https://boj.rs and run a project introduction page.
Since migration is completed, we need to fix the URL in the templates to point to the new repo.
@byeongkeunahn The codespace link in README has been fixed. 136c164
@kiwiyou Nice. Could you also update the templates in scripts/templates?
It seems like the codespaces prebuild isn't working after the transfer.
For repositories owned by organizations, repository-level settings for GitHub Codespaces are available for organizations on GitHub Team and GitHub Enterprise plans. To access the settings, the organization or its parent enterprise must have added a payment method and set a spending limit for GitHub Codespaces.
I believe this can be a blocker for maintaining basm-rs repo under this organization account. How should we deal with this?
I've implemented a workaround. The link to Codespaces is changed to my repo (fork), where prebuild runs normally without billing. The downside is that it must be kept sync with the main repo. Tell me if it goes stale.