[Building Sakai] Suggestion for improvement of i18n and L10n handling in JIRA
Beth Kirschner
bkirschn at umich.edu
Wed Feb 8 08:55:58 PST 2012
Hi Shoji,
No problem -- I jumped the gun and have reverted the JIRA component to read "Internationalization".
- Beth
On Feb 6, 2012, at 3:44 AM, Shoji Kajita wrote:
> Hi Beth,
>
> I found that "x-internationalization" you are proposing has been
> already available on Jira.
>
> I think it is not a good solution because:
>
> 1. it is NOT matching for "internationalization" (Jira tells me "No
> Matches" when I'm typing in Component/s field in creating a Jira
> issue so that almost nobody can use),
>
> 2. we haven't reached the conclusion.
>
> Please continue our discussion to find a better solution.
>
> Best regards,
> Shoji
>
> At Thu, 2 Feb 2012 10:43:10 -0500,
> Beth Kirschner wrote:
>>
>> How about we try for a low-tech hack of changing the I18N component to sort alphabetically to the end -- ("x-Internationalization"). This will make sure the primary component owners get assigned?
>>
>> - Beth
>>
>> On Feb 2, 2012, at 7:11 AM, Jean-Francois Leveque wrote:
>>
>>> All the CLE internationalization component issues are currently
>>> automagically assigned to Beth Kirschner (Lead for this component in
>>> JIRA) if the real component name is after Internationalization in
>>> alphabetical order. She then assigns most of the issues to the real
>>> component owner. I don't think this is really convenient.
>>>
>>> Internationalization and translation issues are currently mixed in the
>>> internationalization component. There is no way to know the ones are
>>> internationalization from the ones that are translation.
>>>
>>> A better solution for both issues is welcome if my suggestion is not
>>> good enough.
>>>
>>> J-F
>>>
>>> On 31/01/2012 17:35, Aaron Zeckoski wrote:
>>>> That doesn't really sound easier to me and there are getting to be an
>>>> awful lot of checkboxes there. The current filters should do exactly
>>>> what you want without a lot of work to make this change in JIRA.
>>>> -AZ
>>>>
>>>>
>>>> On Tue, Jan 31, 2012 at 11:01 AM, Jean-Francois Leveque
>>>> <jean-francois.leveque at upmc.fr> wrote:
>>>>> Hi
>>>>>
>>>>> Currently, SAK issues can have internationalization in the list of
>>>>> components.
>>>>>
>>>>> AFAICT, the only real internationalization component has been in kernel
>>>>> since the creation of kernel with Sakai 2.6.0.
>>>>>
>>>>> Currently the JIRA internationalization component is used both for L10n
>>>>> and i18n issues.
>>>>>
>>>>> I suggest we stop using this component and add 2 new check-boxes (like
>>>>> the Maintenance Team Issue one):
>>>>> Internationalization Issue
>>>>> Localization Issue
>>>>>
>>>>> It seems to me this way will be easier to check which languages have
>>>>> been updated or to look for internationalization issues.
>>>>>
>>>>> What do you think ?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> J-F
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>
>>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
More information about the sakai-dev
mailing list