Listen to and share the music in the Atmosphere.
musicsky.up.railway.app/
nextjs
atproto
music
typescript
react
docs: add community health files and update README
+222
-22
+85
CODE_OF_CONDUCT.md
+85
CODE_OF_CONDUCT.md
···
1
+
# Musicsky Code of Conduct
2
+
3
+
## Our Pledge
4
+
5
+
We pledge to make our community welcoming, safe, and equitable for all.
6
+
7
+
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
8
+
9
+
## Encouraged Behaviors
10
+
11
+
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
12
+
13
+
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
14
+
15
+
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
16
+
2. Engaging **kindly and honestly** with others.
17
+
3. Respecting **different viewpoints** and experiences.
18
+
4. **Taking responsibility** for our actions and contributions.
19
+
5. Gracefully giving and accepting **constructive feedback**.
20
+
6. Committing to **repairing harm** when it occurs.
21
+
7. Behaving in other ways that promote and sustain the **well-being of our community**.
22
+
23
+
## Restricted Behaviors
24
+
25
+
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
26
+
27
+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
28
+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
29
+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
30
+
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
31
+
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
32
+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
33
+
7. Behaving in other ways that **threaten the well-being** of our community.
34
+
35
+
### Other Restrictions
36
+
37
+
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
38
+
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
39
+
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
40
+
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
41
+
42
+
## Reporting an Issue
43
+
44
+
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
45
+
46
+
When an incident does occur, it is important to report it promptly. To report a possible violation, **please write an email to mejsiejdev@gmail.com.**
47
+
48
+
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
49
+
50
+
## Addressing and Repairing Harm
51
+
52
+
---
53
+
54
+
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
55
+
56
+
1. Warning
57
+
1. Event: A violation involving a single incident or series of incidents.
58
+
2. Consequence: A private, written warning from the Community Moderators.
59
+
3. Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
60
+
2. Temporarily Limited Activities
61
+
1. Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
62
+
2. Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
63
+
3. Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
64
+
3. Temporary Suspension
65
+
1. Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
66
+
2. Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
67
+
3. Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
68
+
4. Permanent Ban
69
+
1. Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
70
+
2. Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
71
+
3. Repair: There is no possible repair in cases of this severity.
72
+
73
+
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
74
+
75
+
## Scope
76
+
77
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
78
+
79
+
## Attribution
80
+
81
+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
82
+
83
+
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
84
+
85
+
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+77
CONTRIBUTING.md
+77
CONTRIBUTING.md
···
1
+
# Contributing to MusicSky
2
+
3
+
Thank you for your interest in contributing! This guide covers everything you need to get started.
4
+
5
+
## Prerequisites
6
+
7
+
- [Node.js](https://nodejs.org/)
8
+
9
+
## Local Setup
10
+
11
+
```bash
12
+
# 1. Fork and clone the repository
13
+
git clone https://tangled.org/mejsiejdev.bsky.social/musicsky.git
14
+
cd musicsky
15
+
16
+
# 2. Install dependencies
17
+
npm install
18
+
19
+
# 3. Start the development server
20
+
npm run dev
21
+
```
22
+
23
+
Open [http://localhost:3000](http://localhost:3000) in your browser.
24
+
25
+
## Branch Naming
26
+
27
+
| Prefix | When to use |
28
+
| -------- | ------------------------------------ |
29
+
| `feat/` | New features |
30
+
| `fix/` | Bug fixes |
31
+
| `chore/` | Maintenance, tooling, or config work |
32
+
33
+
Example: `git checkout -b feat/share-track`
34
+
35
+
## Commit Style
36
+
37
+
This project follows [Conventional Commits](https://www.conventionalcommits.org/).
38
+
39
+
```
40
+
<type>(<optional scope>): <short description>
41
+
42
+
[optional body]
43
+
```
44
+
45
+
Common types: `feat`, `fix`, `chore`, `docs`, `refactor`, `style`, `test`.
46
+
47
+
Examples:
48
+
49
+
```
50
+
feat(player): add repeat mode toggle
51
+
fix(auth): handle expired OAuth token gracefully
52
+
chore: upgrade Next.js to 16.3
53
+
```
54
+
55
+
## Pull Request Checklist
56
+
57
+
Before opening a PR, make sure the following pass locally:
58
+
59
+
```bash
60
+
npm run typecheck # TypeScript type checking
61
+
npm run lint # ESLint + Prettier formatting check
62
+
```
63
+
64
+
A good PR:
65
+
66
+
- Has a clear title following the commit style above
67
+
- Describes _what_ changed and _why_ in the PR body
68
+
- Keeps changes focused - one concern per PR
69
+
- Links to a relevant issue if one exists
70
+
71
+
## Reporting Bugs
72
+
73
+
Please open a [issue](https://tangled.org/mejsiejdev.bsky.social/musicsky/issues) and include:
74
+
75
+
- Steps to reproduce
76
+
- Expected vs. actual behaviour
77
+
- Browser / OS / Node.js version if relevant
+21
LICENSE.md
+21
LICENSE.md
···
1
+
MIT License
2
+
3
+
Copyright (c) 2026 Maciej Malinowski and contributors.
4
+
5
+
Permission is hereby granted, free of charge, to any person obtaining a copy
6
+
of this software and associated documentation files (the "Software"), to deal
7
+
in the Software without restriction, including without limitation the rights
8
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+
copies of the Software, and to permit persons to whom the Software is
10
+
furnished to do so, subject to the following conditions:
11
+
12
+
The above copyright notice and this permission notice shall be included in all
13
+
copies or substantial portions of the Software.
14
+
15
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+
SOFTWARE.
+39
-22
README.md
+39
-22
README.md
···
1
-
This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
1
+
# MusicSky
2
+
3
+
> Listen and share music in the Atmosphere
4
+
5
+
MusicSky is a social music platform built on the [AT Protocol](https://atproto.com/). Sign in with any ATProto-compatible server (Bluesky, self-hosted PDS, etc.) and share what you're listening to.
6
+
7
+
## Tech Stack
8
+
9
+
| Layer | Technology |
10
+
| --------- | ------------------------------------------------ |
11
+
| Framework | Next.js 16, React 19 |
12
+
| Auth | AT Protocol OAuth (`@atproto/oauth-client-node`) |
13
+
| Database | SQLite + Kysely |
14
+
| Styling | Tailwind CSS v4, shadcn/ui |
15
+
| State | Zustand |
2
16
3
17
## Getting Started
4
18
5
-
First, run the development server:
6
-
7
19
```bash
20
+
# Install dependencies
21
+
npm install
22
+
23
+
# Start the dev server
8
24
npm run dev
9
-
# or
10
-
yarn dev
11
-
# or
12
-
pnpm dev
13
-
# or
14
-
bun dev
15
25
```
16
26
17
-
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
27
+
Open [http://localhost:3000](http://localhost:3000) in your browser.
18
28
19
-
You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
29
+
## Scripts
20
30
21
-
This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.
22
-
23
-
## Learn More
24
-
25
-
To learn more about Next.js, take a look at the following resources:
31
+
| Script | Description |
32
+
| ------------------- | ------------------------------------------------- |
33
+
| `npm run dev` | Run migrations and start the development server |
34
+
| `npm run build` | Build for production |
35
+
| `npm run start` | Run migrations and start the production server |
36
+
| `npm run migrate` | Run database migrations |
37
+
| `npm run gen-key` | Generate a private key for production deployments |
38
+
| `npm run typecheck` | Type-check with TypeScript |
39
+
| `npm run lint` | Lint with ESLint |
40
+
| `npm run format` | Format with Prettier |
26
41
27
-
- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
28
-
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
42
+
## Contributing
29
43
30
-
You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!
44
+
Contributions are welcome. Please open an issue or pull request.
31
45
32
-
## Deploy on Vercel
46
+
1. Fork the repository
47
+
2. Create a feature branch (`git checkout -b feat/your-feature`)
48
+
3. Commit your changes
49
+
4. Open a pull request against `main`
33
50
34
-
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
51
+
## License
35
52
36
-
Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.
53
+
[MIT](LICENSE.md)