Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

"OpenDocument Reader - view ODT" is too generic

Abierto
  • ¿Algo no está bien?
#430 5 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
android, kotlin
Área
content

Línea de trabajo

The store title comes from fastlane/metadata/android/en-US/title.txt, and the short and full descriptions sit beside it in the same folder. The issue is a naming decision rather than a code change, and the thread has been quiet for about 300 days with no agreed name, so confirm with the maintainers before editing. Done means a new title is agreed and applied consistently across F-Droid and Google Play metadata.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

low

"OpenDocument Reader - view ODT" is to generic.

  1. Visit the app on F-Droid
  2. Observe the title: "LibreOffice & OpenOffice document reader | ODF" (will be changed to "OpenDocument Reader - view ODT") -- responsible file: https://github.com/opendocument-app/OpenDocument.droid/blob/main/fastlane/metadata/android/en-US/title.txt
  3. Visit the same app on Google Play
  4. Observe the title: "OpenDocument Reader - view ODT"

Suggestion

If I may, I'd like to offer some suggestions that might help with the project's branding:

  • Avoid including the descriptor "- view ODT" in the software title, as it complicates listing the software cleanly in software directories. Use a concise, single-term name for the software.

  • If retaining any reference to the OpenDocument format in the title or description, it should ideally use the broader term "ODF" (Open Document Format) rather than just "ODT," since the app supports multiple OpenDocument file types—including text documents (.odt), spreadsheets (.ods), presentations (.odp), and more. For example, "OpenDocument Reader" or "OpenDocument Suite" with a description mentioning support for viewing and editing ODF files would improve accuracy and discoverability.

  • The term "Reader" is insufficient and potentially misleading, as the application offers editing capabilities, not just document viewing. The title should reflect the app's full functionality, using terms like "Editor," "Suite," or "App" to avoid user confusion.

  • The current project name is overly generic and could benefit from a distinctive, unique name that stands out while still referencing its role as an OpenDocument-format suite or editor. Consider deriving inspiration from existing office suite names, which often combine descriptors with unique branding elements (e.g., LibreOffice, Collabora). A unique name helps with branding, discoverability, and user recall.

Lenguaje dominante
Kotlin
Estrellas
473
Forks
44
Merge medio
4 h 7 min
PR fusionados (30 d)
54

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opendocument-app/OpenDocument.droid

Todos los issues de opendocument-app/OpenDocument.droid

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.