Closed himorin closed 3 years ago
xfq
commented
3 years ago
- do we have tracker like for arabic? (I assume no)
Looking at https://www.w3.org/2011/04/dbwg/group-services?gid=109193 it indeed seems that we don't have one set up (or that it was removed by the systeam, perhaps).
xfq
commented
3 years ago It looks like we removed the public-i18n-cjk mailing list. Are we going to abandon it, @r12a?
r12a
commented
3 years ago It looks like we removed the public-i18n-cjk mailing list. Are we going to abandon it, @r12a?
As i remember it, the jlreq group created the public-i18n-japanese list because they didn't want to use the public-i18n-cjk list. As far as the jlreq group is concerned, i think the public-i18n-cjk list is now irrelevant.
However, since that time i have been thinking that we should also consider value of having the cjk list when most japanese folks will not be following it, or will be getting duplicate daily notifications if they do. That cjk list was originally set up to allow cross-fertilization of ideas that are common to all groups, such as aspects of vertical text or ruby, but the discussions it actually hosts are, i think, in fact language-specific most of the time, and therefore too distracting to korean people who are not interested in chinese-specific or chinese people not interested in korean-specific topics. There are other ways we can produce the cross-fertilization, as in fact we currently have to anyway for mongolian, which also has related vertical text and ruby interests.
It seems to me that, because the jlreq and clreq groups are very active, it would probably be better to create public-i18n-chinese, and public-i18n-korean lists and no longer use the public-i18n-cjk list.
That said, the charters of each group should probably mention that the public-i18n-cjk archive contains some historical discussions that may be of interest, while clearly indicating that it is not currently used.
r12a
commented
3 years ago -i18n-japanese is for discussions (mainly in Japanese), but I think we discussed to set this list public but not welcome subscribe for just watching?
The public must have a way to interact with the group, but actually this should be by raising GitHub issues (which are then notified to the public-i18n-japanese list). I wouldn't make a meal of describing the use of the japanese list – just mention that it's there.
r12a
commented
3 years ago Oh, and i would strongly recommend keeping the admin list for its intended admin use, such as arranging meetings or other administravia, and keeping those out of the public-i18n-japanese list.
r12a
commented
3 years ago we don't have concrete plan of meetings (usually picking from Tue 10am JST), nor no meeting information page. Do we want to have a link of "Meeting Information"?
I think you should have a meeting information page (in member-only date space) that you can point to in the agenda or meeting announcement as well as on the home page. I recommend using the i18n wg page as a template, since that received some thought and experience-based redesign. It doesn't matter if the jlreq group doesn't have a regular date for meetings.
xfq
commented
3 years ago It seems to me that, because the jlreq and clreq groups are very active, it would probably be better to create public-i18n-chinese, and public-i18n-korean lists and no longer use the public-i18n-cjk list.
Not sure about the klreq group, but it looks like the current participants of the clreq group are comfortable using GitHub, and I don't think there is need for a separate list. We can send the meeting agenda/minutes to the admin list and discuss on GitHub.
r12a
commented
3 years ago Ok for the group members, but the public needs to be able to subscribe to a mailing list to receive notifications of GH changes. That is currently public-i18n-cjk, but would be the new publc-i18n-chinese list.
himorin
commented
3 years ago we don't have concrete plan of meetings (usually picking from Tue 10am JST), nor no meeting information page. Do we want to have a link of "Meeting Information"?
I think you should have a meeting information page (in member-only date space) that you can point to in the agenda or meeting announcement as well as on the home page. I recommend using the i18n wg page as a template, since that received some thought and experience-based redesign. It doesn't matter if the jlreq group doesn't have a regular date for meetings.
I've thought about having one in member only space while ago, but I've noticed that most of JL-TF participants do not have member access (or say no IE status) and gave up. But at this moment, I've noticed that I can configure permissions to include task force group, so let me add a page (like one for arabic, in /2021/04/ or something), and set permissions as member + JL-TF.
r12a
commented
3 years ago Thanks for setting up the page. You did the right thing wrt access permissions. Small nit: you need to change "members of the Arabic Layout Task Force" -> "members of the Japanese Layout Task Force"
r12a
commented
3 years ago How are we doing wrt converting the README page to the new content and providing a translation? (Once it's done, i'll change the links from various pages to point to home.md.)
himorin
commented
3 years ago pointed out during discussion w/Kida-san: seems no link/mention to CEPC?
kidayasuo
commented
3 years ago I am fine without mentioning the CEPC in the "To just follow the work" section. I would like to keep the document as simple as possible.
himorin
commented
3 years ago @r12a @xfq requesting review on the latest version.
himorin
commented
3 years ago Really thank you for review! I'll merge PRs related to this.
@kidayasuo we have a new format of our home, which will also be listed in w3.org/International/ site, currently placed as home.md in this repository. It seems there are several items need to be discussed, and I'm raising this PR (rather than updating #256).
note: #256 will be merged after this PR landed.