Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Kotlin] A delivery section in Spanish in the Kotlin README: clone, open, run the demo

Open Beginner friendly
#161 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
android, kotlin
Domain
documentation

Research direction

Read the Kotlin README and inspect the demo variant and seven-screen navigation in app/frontend/mobile/kotlin. Write the Spanish “Entrega” section with the stated setup, run, profile, troubleshooting, and ZIP steps; include the exact git archive command after confirming the repository paths. Done when a fresh-clone reader can follow the guide and run the app in under 15 minutes.

Written by the indexing model from the issue text.

Description

area/kotlin

Part of the first delivery (parent issue above, due 2026-10-23).

What to write

A "Entrega" section in Spanish at the top of the Kotlin README, written for a classmate who has never opened the project:

  1. Requirements: Android Studio version (2026.1.4 or newer), JDK, and an emulator with API 37.
  2. Clone, open app/frontend/mobile/kotlin, pick the demo variant and press Run.
  3. How to switch profile (estudiante, profesor, administrativo).
  4. Where to find each of the 7 screens.
  5. Common problems: Gradle sync, the emulator, the Nearby devices permission on Android 17.
  6. How to build the ZIP: git archive of the Kotlin directory, with the exact command.

Done when

  • Someone who has not seen the project follows it from a fresh clone to the app running in under 15 minutes.
  • Merged into develop by 2026-10-21.
Dominant language
Java
Stars
1
Forks
0
Avg merge
1d 8h
Merged PRs (30d)
80

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from K-Forge/KApp

All issues in K-Forge/KApp

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.