On Feb 16, the FamilySearch Integration PR was opened: FamilySearch Integration (#2176) master ← SourceAirbender:pr-2147-fs-login opened 12:19AM - 17 Feb 26 UTC (UTC) …

[image] dsblank: I know @Nick-Hall created GEPS 046: FamilySearch Integration - Gramps (and a feature request from 2009 0003377: Connect and synchronize Gramps with the FamilySearch API. - Gramps - Bugtracker – Free Genealogy Software ) but there is very little information there. We are workin…

I’ll start working on those two points.

I’ll make comments in github about some other items. Briefly: All imports should be at top of file We use relative imports You don’t need try/except around imports that are part of gramps The upgrade should be moved as per above (this is required) I’ve started an AGENTS.md that useful even if you…

[image] dsblank: The upgrade should be moved as per above (this is required) Sorry, can you clarify?

Currently, the upgrade code is in self._create_familysearch_sync_schema() But we need that extracted like the other upgrade paths into specific functions for version 22. Why? What happens if we want to change the FS schema further? We need another upgrade that will take a user from 22 to 23 (and bey…

@SourceAirbender @kmikkels noted (on the Gramps dansk brugergruppe Facebook group): wow! More than 300 translations needed. A lot regarding familysearch. Well, I have started. That’s a LOT of translation churning. Could that this string expansion be run through LLMs? … to see if there isn’t som…

[image] emyoulation: Could that this string expansion be run through LLMs? Weblate has an automatic suggestions feature. There are a number of AI tools listed.

I am not suggesting that an AI do the translations… at least, not as a first pass. I am requesting that the 300 terms/strings first be compared against themselves. And any closely matching strings can be harmonized to reduce the count. (This pass would give an idea of how internally consistent the …

I see what you mean. There are lots of strings because there’re lots of new interfaces and submenus. But you bring up a good point, it would be useful to reuse strings if and where applicable. I’ll do a pass sometime this week like you mentioned and see if there’s anything matching your criteria.

Just finished the translation. Not to much redundancy, but some. “Working” and “Working…” would be considered two different phrases. “this” and “this (that)” might have been possible to do otherwise. However what irritated me most was the number of times I had to type FamilySearch. I finally insta…

FamilySearch Integration PR

Development

Topic		Replies	Views
FamilySearch integration: architectural & govenernce discussion Development gramps-web , familysearch	20	339	June 18, 2026
FamilySearch Integration with Gramps Ideas familysearch	86	3615	July 26, 2026
Exporting data from FamilySearch Help familysearch	2	2771	July 20, 2021
User poll: what are you most interested in being developed? Development survey	25	631	April 16, 2026
FamilySearch Gramplet Help third-party-addon , familysearch	133	5520	February 8, 2025

FamilySearch Integration PR

Related topics