#113 Planning i18n hackfest during flock 2019
Closed: Fixed 10 months ago by pravins. Opened a year ago by pravins.

Hi All,
As we did workshop in flock 2018, lets plan workshp for flock 2019 as well. This ticket is created for gathering idea's for task we can complete during workshop

Idea 1: After implementing CI for few packages, now need to think. How can we do it for all packages? and How to increase test coverage?

high level agenda could be:

  • latest i18n developments
    • fonts / rendering / glibc / unicode
    • input methods / typing boosters
    • langpacks
  • test cases and CI
  • planned activities/objectives
    • future goals (or in pipeline)

Idea: Also we can contribute to openQA tests for Fedora Distribution to increase test coverage and locale support.

Test Case clean up, improvements, curation, new tests and link to CI.

We may consider test suite improvement for fonts CI (in liberation-fonts and lohit-fonts).
- https://src.fedoraproject.org/rpms/liberation-fonts
- https://src.fedoraproject.org/rpms/lohit-devanagari-fonts

I would like to participate in this activity for Test Case clean up as well as contributing in increasing the efficient test coverage for CI.

Thanks all for the input, i will submit proposal to flock. Also having this hackfest also help to connect with other teams/contributors present at flock.

I would like to attend this hackfest and work on extending the existing CI test cases for fonts packages. We do have dictionary packages also to work on writing CI test cases. Then we have packages like harfbuzz, fonttools, fontforge where also we need good test case coverage.

I would like to attend this hackfest as well and work on adding or improving CI to packages.

Thanks all, i have submitted proposal for flock https://pagure.io/flock/issue/138

I proposed a talk on the future of langpacks also.

I proposed a talk about how new features in ibus-typing-booster can help language learning: https://pagure.io/flock/issue/197

I will create Wiki page with schedule for Hackfest and other information.

Metadata Update from @pravins:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

10 months ago

Login to comment on this ticket.