For holding translated content, the FSF hosts translations for its licenses
as "Unofficial translations"[1].

The reason can be that it's somehow legal terms so it's at risk if
different versions imply different meanings. But for the "policy" where we
generally have the understanding "Whether those constitute "policy" or just
best practice is left as an exercise for the reader.", if there are ASF
members maintain the content, I agree that we can mark the translated
content as official.

Best,
tison.

[1] https://www.gnu.org/licenses/translations.en.html


tison <wander4...@gmail.com> 于2023年10月27日周五 11:46写道:

> FWIW, I ever wrote a (Chinese) blog about communication tools for an OSS
> community[1], that has a section to talk about mailing list.
>
> I enter the OSS world with the Perl 6 (a.k.a. Raku) community so it's
> native to me for working with mailing list and even IRC. But it's quite
> unfamiliar for especially new contributors even from a worldwide
> perspective.
>
> > What if we had a global storage for everything that happens in a
> project?
>
> Convey/Forwarding to the mailing list is the current solution. I'm
> prototyping a community tool to archive activities and will be glad to
> collaborate. As Orbit or CommonRoom does, saving all the activities from
> different channels so that we can be both (1) archive (2) searchable, and
> (3) even _analyzable_.
>
>
>
> Best,
> tison.
>
> [1] https://zhuanlan.zhihu.com/p/395057453
>
>
> <rbo...@rcbowen.com> 于2023年10月26日周四 22:20写道:
>
>> On Thu, 2023-10-26 at 07:42 +0000, Christofer Dutz wrote:
>> > We have this rule: If it didn’t happen on the list, it didn’t happen
>> > (Don’t even know if it’s really written down somewhere or if it’s
>> > just a common mantra).
>>
>> It's written here:
>>
>> https://community.apache.org/newbiefaq#NewbieFAQ-IsthereaCodeofConductforApacheprojects
>> ?
>>
>> And here: https://incubator.apache.org/guides/committer.html
>>
>> Whether those constitute "policy" or just best practice is left as an
>> exercise for the reader.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

Reply via email to