Translations of README.md #3436
Replies: 8 comments 14 replies
-
That sounds like a good idea, perhaps with an explanatory |
Beta Was this translation helpful? Give feedback.
-
Yeah, this makes sense. Although, I wonder if instead of deleting the files and unlinking them, we could add a line to the top of each README that says "Last updated on (date), for (release)". Then you wouldn't necessarily need to delete anything if it wasn't maintained, because people would see the last time it was updated. This could save you some work. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I can order astronaut ice cream and reproduce compilation errors in Martian, but point taken. Localized READMEs are a little bit like obscure platforms: without someone actively maintaining them, they can be worse than no support, because they offer the illusion of support without the accountability of accuracy. |
Beta Was this translation helpful? Give feedback.
-
Can I propose something a little different and more organised and accessible IMHO? Like we are doing here: and you can se it running on Github Pages here: it uses a workflow to use MDBOOK and so we can have a compreensive easy to understand readme, multilanguage, searchable
we could create a branch exclusively for the documentation on CORE, example docs-master and docs-1.14.7-dev ... to not confuse with CORE code, and anyone contributing would be also more easy to translate all other documentation that is available only in english like in https://github.com/dogecoin/dogecoin/tree/master/doc
|
Beta Was this translation helpful? Give feedback.
-
I'm proposing the creation of a new branch here on CORE called "1.14.7-dev-docs" were as a community we can organize all documentations that later on we could push to a new branch called "main-docs" and use Google Pages to push as a static webpage https://github.com/dogecoin/dogecoin/tree/3fba0e8b5d7c6cf304593efe66068bcabeb06666 What should be done in your opinion to accomplish this? |
Beta Was this translation helpful? Give feedback.
-
Agree. Paulo, core is trying to stay focused on executing 1.14.7 release. I
thought it was good of Patrick to accommodate your request for pt_PT in a
creative way to address added pressure on maintainers with explosion in
translations. There is already scope creep in 1.14.7 and these other items
would only add to that for the time being. IMO
…On Thu, Feb 22, 2024 at 12:34 PM Old Dip Tracker ***@***.***> wrote:
I disagree with that proposal because branches inherit maintainers and
this would automatically either increase the workload for maintainers, or
permission people with rights on code that are extremely risky.
Separate concerns. If you want to make a website, make your website. There
is no need to do it here.
—
Reply to this email directly, view it on GitHub
<#3436 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZSY44XY4SOVW53B7OPILTYU6TVZAVCNFSM6AAAAABDR3W2UOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKNRRGQZDS>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Why not a new Repository inside CORE? to separate things and at the same time organise things that are directly related to CORE? |
Beta Was this translation helpful? Give feedback.
-
Currently, I observe 3 problems with README translations:
Although I completely understand that everyone wants their language to be there, for whatever reason, an unmanageable process is no good for maintenance on this repository.
Therefore I want to propose, preferably for the next development branch we create when #3407 is finished because this is a process change, to change the way we do these and other documentation translation a little.
doc/intl
. Although this means that the original intent of these translated README files is no longer the sole scope, this becomes manageable.doc/intl/README.md
, and the rootREADME.md
anddoc/README.md
are only linking to this file, rather than to each individual translation. This solves having to maintain endless README edits.This leads to a situation that if someone wants to translate any documentation, this is easy. Just need reviews, and don't need to worry about any other documentation, other than the source. It also means maintainers get a much better grip on the state of documentation and can prevent distributing outdated information.
Open to suggestions.
Beta Was this translation helpful? Give feedback.
All reactions