Sorry about the digest response. Footnotes at bottom of msg. > Message: 1 > Date: Thu, 31 Aug 2017 13:50:29 -0400 > From: James Mason <j...@slashmail.org> > To: "Discussion about the Wikimedia genealogy project." > <wikimedia-genealogy@lists.wikimedia.org> > > Several different systems have been put forward as candidates to be > "the" Wikimedia genealogy project. Of those, several have been in > existence for a number of years and are in regular use. Yet I have seen > very little on the question of why any of those may or may not have been > chosen as a starting point.
... In the WMF-sphere there is a strong opposition to NMH/NFH (Not Made Here/Not From Here) solutions, even standing the middle of a wheel graveyard. Witness Flow when there are literally hundreds of drop-in forum/communication systems which can be implemented modularly such as PHPBB. My personal choice of using WebTrees[1] was specifically to allow an unlimited number of contributors to work on a single GED, and allow an unlimited number of GEDs to be hosted/displayed. It is not a wiki. It has some wiki-like characteristics. It could become a wiki. I doubt it is currently ready to scale. On the other hand, it would work extremely well as an interim, and is able to import/export standard and non-standard GED. > Message: 2 > Date: Fri, 01 Sep 2017 08:15:04 +0800 > From: Sam Wilson <s...@samwilson.id.au> > To: wikimedia-genealogy@lists.wikimedia.org > Subject: Re: [Wikimedia-genealogy] Is the delivery of software > fundamental to this project? > > ... > WeRelate > ... > Wikidata as a central > repository > ... > My personal approach these days is ... To painfully refactor: WeRelate has content and community, and other good/bad things. Wikidata, if possible, requires creating a new genealogy data standard [mandatory reference to https://xkcd.com/927/]. Federation seems a good approach. I am less-keen on thinking about forking a community, although forking their content has some interesting possibilities. Wikidata has been pretty much useless or a disaster for sister projects other than interwiki links - and even that has semantic issues. (imo: this is due a lack of interest/resources in supporting non-wikipedia efforts, not that Wikidata cannot do a stellar job.) So, much against my philosophy, I can agree there is a need for software development: a decentralized federation for node searching/sharing/indexing, self-healing? Preferably with a platform agnostic api, so multiple GUI and engines can be built. But I would rather work with the very large pile of genealogy wheels than start something entirely new. Amgine [1] On Github: https://github.com/fisharebest/webtrees Official: https://www.webtrees.net/ Wiki: https://wiki.webtrees.net/
_______________________________________________ Wikimedia-genealogy mailing list Wikimedia-genealogy@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-genealogy
