> new translations should only come from platform by bot

Cool that makes sense. I think that is an okay limitation for
something that is way easier to contribute with, but thats me as a
naive outsider saying that :)

I don't think it would be an easy change to make to jenkins, but
probably would be straight forward.

A demo at future docs office hours (Which alex volunteered to do)
would be a great start, they get recorded and published to
community.jenkins.io, and then we can know more and see who might want
to champion any changes needed to core/build process.

On Sat, Mar 5, 2022 at 1:04 AM Kevin Chiu <[email protected]> wrote:
>
> > Are you thinking this would just be for core or plugins as well?
>
> I think plugins maintainers can choose to join or not.
>
> > is this because it should be pulling down data as an automated step?
>
> Yes, after start using translating platform,
> new translations should only come from platform by bot
> Except edit English string
> For example: Gitea
> https://github.com/go-gitea/gitea/tree/main/options/locale
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/eccec27d-6793-40aa-a93a-ece97a130c90n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duu3aejSFToYAdUxRkxSKWqfW1MGCT54o03fB2ohj2YcrA%40mail.gmail.com.

Reply via email to