Difference between revisions of "User:BACbKA"
(→My GRAMPS-related scratchpad) |
(→My GRAMPS-related scratchpad) |
||
Line 6: | Line 6: | ||
* reports & export should have more in common -- in filtering/selecting source set and output data | * reports & export should have more in common -- in filtering/selecting source set and output data | ||
** new action - filter, expose for cli? | ** new action - filter, expose for cli? | ||
+ | ** see also bug [http://www.gramps-project.org/bugs/view.php?id=1600 #1600] | ||
* what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases: | * what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases: | ||
# two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming. | # two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming. |
Revision as of 21:38, 23 February 2011
- merge familylines and relgraph good stuff into a common report
- auto-translation of names, places, etc. - for reports and exports
- reports & export should have more in common -- in filtering/selecting source set and output data
- new action - filter, expose for cli?
- see also bug #1600
- what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases:
- two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming.
- make life easy for people taking periodic exports from gramps
This is a known hot issue, see How_you_can_help#Web_2.0 - can we send out only the stuff that changed? (yet another multisync sub-problem)