Osaka) • Member, LibreOffice Japanese Team (2011-) • Member, Membership Committee of The Document Foundation • Activities: organizing events, building communities, occasional Q&A, QA work, and translation
all over the world must support many languages and cultures • This is very important for software like LibreOffice that has features for languages and cultures • In open source, local users can help improve the software by themselves • Including issues like vertical writing, ruby text, encoding, UI, and cultural customs
cannot fully understand all language and culture needs • To improve quality with small resources, we need feedback from local users • Local community helps connect users and developers and find problems
about how our community works to improve software quality, even with small resources and many problems • These examples come from working with the Japanese LibreOffice community • I think some ideas can help other open-source projects too
feedback loop • Focus on continuous integration(CI) and automated testing (out of scope for this talk) • Self-managed, distributed structure for global contributors
build • Open patch acceptance process • Bug report and bug triage from users • Feedback from user forums • Help and documentation to clarify specifications
Direct problem reports from users or testers • Importance: Foundation for quality improvement • Example tools: Bugzilla, GitHub Issues • Notes: • LibreOffice customizes Bugzilla by adding fields • GitHub Issues usually provide templates to help users submit clear reports..
data loss) are given high priority • Confirm bug reproducibility and clarify the problem • Add reproduction steps and environment details • Use Bibisect tool to identify the commit that caused the problem
find which code change caused a bug • It works by testing versions between a known good and a bad one • This helps pinpoint the exact commit that introduced the problem
Automatically collected crash data and usage info • Importance: Helps detect issues even without user reports • Considerations: Privacy and setup complexity • Example: LibreOffice also has the option to send crash reports
Collecting user opinions through questionnaires or interviews • Importance: • Provides direct feedback on user satisfaction and needs • Considerations: • Can be time-consuming and costly • Less common in FLOSS but useful for targeted insights
for identifying usability and UX issues • Involves observing users performing real tasks • LibreOffice does not do this now • Social media • Sometimes useful, but requires much effort • Information is often incomplete, and communication can be difficult
file bugs based on questions posted on ASK • Often add details to existing bug reports • ASK more efficient than Mailing List or Telegram • Only consistent working process now • Recently active members: Saburo-san, Sudo-san, Ironami- san, and others also appreciated • More details in the next talk by Sudo-san
translations • Review required by reviewers (review shortage is a challenge) • Previously held translation-focused online hackfests (mob- work style) • These hackfests are currently paused due to no lead person • Active contributors: Sabro-san, AAAA-san, and others (thank you!)
Korean communities on bug identification and triage • Bugs reproducible only in specific language environments can be found • We track issues via a CJK meta-bug • CJK Telegram channel exists for communication • One TDF team member focuses on multilingual support and investigates/fixes CJK bugs • We want to increase such collaborations
a booth at about 7–8 open source events in Japan every year • We get direct feedback from users and participants • Through these exchanges, we identify issues and gather improvement ideas • We also communicate actively with community members and other FLOSS communities
Japanese team meetings for task review and urgent work • Weekly online hackfests • LibreOffice Kaigi (annual conference) • Organized remotely • New contributor recruitment at online and offline events • Incentives such as gifts for event speakers • Moderation and review of announcements by mailing list moderators
with steady effort • Diverse roles—translation, review, bug reporting—are all important • Community size matters; growth is essential to sustain feedback quality
even without many experts • Multilingual and multicultural support is vital for FLOSS quality worldwide • Local communities play a key role in addressing language- and culture-specific issues • These lessons apply to many open-source projects
held on December 13–14, 2025, at the IIJ office in Tokyo. • We are currently accepting CfP submissions. • Through this event, we aim to foster community interaction and discover new people interested in our activities. • Joint event : GNOME Asia Summit
enoki
ijin
ahus1
techniczna
r3_yamauchi
kakehashi
hisashiwatanabe
cubicdaiya
keisuketakiguchi
nullpo_head
endohizumi
senseofunity129
tak0x00
yeseniaperezcruz
bermonpainter
zakiyama
honnibal
maltzj
brad_frost
skipperchong
jonyablonski
hatefulcrawdad
vanstee
mraible
dougneiner
![45 Thank you • Shinji Enoki • Email: [email protected]](https://files.speakerdeck.com/presentations/3454f2f675394c75a112f839799d7059/slide_44.jpg){kind=link}