Locale bringup and barriers for entry

[Philippe Verdy via CLDR-Users]

My intent is to have those tags (that are internally numbered with a stable
id but may be renamed by proposing users, or by admins if tags are made
global and unprefixed) also usable in Survey discussions to attach a
comment to all CLDR data entries using that have been tagged with it by the
user (using a prefixed user tag) or by a global tag (created by the CLDR
tech admins).
I.e. reproduce what we can do easily in GutHub to track various related
bugs reports and RFEs or pending actions. Ideally there should also be a
graph of entries (these tags are working also like tasks in task lists,
they have a status coming from the posted comments, which can be closed
once solved)
May be some integration with GitHub and community development tools or bug
tracking tools would be useful, just like many opensource develomment
projects (of which CLDR is one). That integration comes with URNs/URLs
linked to CLDR data paths.
For now CLDR submission is too much hierarchic, and does not focus very
well on related groups of items that must be fixed together (in the same
locale, or across locales), so it is very difficult to isolate the
inconsistencies (and get reliable votes to fix them in the short time
allowed for submission and vetting (notably because the tool is much too
slow and uses really too much javascript/DOM resources in the browser, and
is very unresponsive to user events, creating many unexpected actions, or
ignored clicks).

Le sam. 22 sept. 2018 à 19:58, Marcel Schneider via CLDR-Users <
cldr-users at unicode.org> a écrit :

> On  22/09/18 17:23 Philippe Verdy via CLDR-Users wrote:
> [quote]
> > But the CLDR Survey does not allow us to participate directly by
> submitting LDML data
> > (as submitted but unvetted provisional data) and then merging them in
> our votes.
> > It would considerably speedup the data submission
>
> Steven R. Loomis hinted this in response to a demand I’d posted on Trac:
>
> https://unicode.org/cldr/trac/ticket/11255#comment:2
>
> > (I also think that such submissions should allow us to include some
> custom "hashtag",
> > that are usable in a search form in CLDR survey, so that we can group
> related items together:
> > we could have multiple hashtags, one for each property we want to track
> in alternative groups,
> > because these groups do not necessarily form a partition of the data
> space, they are not orthogonal).
>
> I don’t understand how SurveyTool would get these hashtags to work, but
> you may post this as a feature
> request. For newcomers, here is how to send feedback for processing by the
> CLDR Technical Committee:
>
> 1. Set your personal data in Preferences:
> https://unicode.org/cldr/trac/prefs
>
> 2. Submit any report, new data not having their locale ID in CLDR yet,
> feature requests:
> https://unicode.org/cldr/trac/newticket
>
> Don’t worry if you’re prompted to do some arithmetics. With your personal
> data in a cookie, that is less likely
> to happen. Make sure however not to exceed the maximum number of 5
> external links per post. Internal links
> are unlimited, using     ticket:123456     syntax or alternatives as shown
> in:
> https://unicode.org/cldr/trac/wiki/WikiFormatting
>
> What we can already do is to use XML comments in the files we’re working
> on, and there we may add hashtags.
> However SurveyTool won’t import them, only register our votes. Which is
> already a huge deal saving us much time.
>
> Regards,
>
> Marcel
>
> _______________________________________________
> CLDR-Users mailing list
> CLDR-Users at unicode.org
> http://unicode.org/mailman/listinfo/cldr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20180922/ee55fcde/attachment.html>