Codeberg/Contributing
26
57
Fork
You've already forked Contributing
9

[Project] Translate (Weblate) #23

Open
opened 2023年08月22日 00:48:41 +02:00 by fnetX · 4 comments
Owner
Copy link

About the project

Maintaining Codeberg Translate, a Hosted Weblate instance for Codeberg projects.

State

Running - Looking for co-maintainers

List the people who joined the team.

Tasks

Which references are already available for the project?

Looking for ...

  • Teamleads / Maintainers (taking responsibility)
  • Co-Maintainers (sharing responsibility)
  • Software developers
  • System administrators
  • Writers
  • Designers
  • Public Relation / Communication experts
  • Input and suggestions
  • Testing and Feedback

Details

No response

Issue thread meta

  • ... discuss the project idea and give general input
  • ... discuss technical details about the project
  • ... commit yourself to be part of the project (becoming a maintainer etc)
  • ... suggest approaches to the project (e.g. creating a repository, chat etc)
### About the project Maintaining Codeberg Translate, a Hosted Weblate instance for Codeberg projects. ### State Running - Looking for co-maintainers ### List the people who joined the team. - @bubu ### Tasks - [ ] Maintain and Update the Weblate installation in an LXC container, including database - [ ] Provide support to users in the [Community Issue Tracker ](https://codeberg.org/Codeberg/Community/issues/) - [ ] Triage bugs and [collaborate with upstream developers](https://github.com/WeblateOrg/weblate/issues/) - [ ] Develop the software (features, bugfixes etc) - [ ] Write and maintain the end-user documentation ### Which references are already available for the project? - Production: https://translate.codeberg.org/ - Repos: - https://codeberg.org/Codeberg-Infrastructure/weblate-docker-compose - https://codeberg.org/Codeberg-Infrastructure/weblate-docker - https://codeberg.org/Codeberg-Infrastructure/weblate - Upstream: https://github.com/WeblateOrg/weblate - Matrix-Channel: https://matrix.to/#/#codeberg-translate:bubu1.eu - User-Documentation: https://docs.codeberg.org/codeberg-translate/ - Issues related to Weblate on Codeberg: https://codeberg.org/Codeberg/Community/issues?q=&type=all&state=open&labels=73496&milestone=0&assignee=0&poster=0 ### Looking for ... - [ ] Teamleads / Maintainers (taking responsibility) - [x] Co-Maintainers (sharing responsibility) - [x] Software developers - [x] System administrators - [ ] Writers - [ ] Designers - [ ] Public Relation / Communication experts - [x] Input and suggestions - [x] Testing and Feedback ### Details _No response_ ### Issue thread meta - [ ] ... discuss the project idea and give general input - [ ] ... discuss technical details about the project - [x] ... commit yourself to be part of the project (becoming a maintainer etc) - [x] ... suggest approaches to the project (e.g. creating a repository, chat etc)

Not sure if that is the best place to discuss (I can move it to matrix if wanted), but depending on what is needed, I could help with the end-user documentation work.

Not sure if that is the best place to discuss (I can move it to matrix if wanted), but depending on what is needed, I could help with the end-user documentation work.
Author
Owner
Copy link

The codeberg documentation is really barebones and sometimes not even accurate it seems. The weblate documentation is more complete, but sometimes difficult to grasp.

I'd recommend to try and be efficient by working on the Weblate docs and only writing a short codeberg onboarding section. Improving the Weblate docs, and especially finding information quickly is a todo.

Other than Documentation, it would be cool to have some Python / django / frontend developers who are able to tackle some issues with Weblate and upstream them.

The codeberg documentation is really barebones and sometimes not even accurate it seems. The weblate documentation is more complete, but sometimes difficult to grasp. I'd recommend to try and be efficient by working on the Weblate docs and only writing a short codeberg onboarding section. Improving the Weblate docs, and especially finding information quickly is a todo. Other than Documentation, it would be cool to have some Python / django / frontend developers who are able to tackle some issues with Weblate and upstream them.

I work with Python and Django a bit. Maybe I could help out there or with documentation.

I work with Python and Django a bit. Maybe I could help out there or with documentation.
Author
Owner
Copy link

@jaerrib this would be great. Potential things that would be great:

  • when users log in to Codeberg and visit Weblate, they are not automatically logged in. It would be cool if there could be a background check that tries to complete the sign in flow (see Codeberg/Community#1415)
    • alternatively, it would be great if Weblate allowed a customizable (e.g. markdown) welcome popup on first visit for guests, so that we can present them with something like "Hi, your Codeberg account is not automatically detected. Please click here to sign in"
  • another big problem is that the colour customization breaks our themes, see Codeberg/Community#1409
  • a more recent suggestion of mine is to have a look at the notification settings, IMHO they are hard to understand. I'll happily help with user research to find more about this. A low-hanging fruit would be to display the actual value next to fields with "Default settings", because I don't know what the defaults are ...
@jaerrib this would be great. Potential things that would be great: - when users log in to Codeberg and visit Weblate, they are not automatically logged in. It would be cool if there could be a background check that tries to complete the sign in flow (see https://codeberg.org/Codeberg/Community/issues/1415) - alternatively, it would be great if Weblate allowed a customizable (e.g. markdown) welcome popup on first visit for guests, so that we can present them with something like "Hi, your Codeberg account is not automatically detected. Please click here to sign in" - another big problem is that the colour customization breaks our themes, see https://codeberg.org/Codeberg/Community/issues/1409 - a more recent suggestion of mine is to have a look at the notification settings, IMHO they are hard to understand. I'll happily help with user research to find more about this. A low-hanging fruit would be to display the actual value next to fields with "Default settings", because I don't know what the defaults are ...
Sign in to join this conversation.
No Branch/Tag specified
wiki-notice
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Contributing#23
Reference in a new issue
Codeberg/Contributing
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?