Skip to content

Loading…

ppl sync command #10

Closed
mess110 opened this Issue · 3 comments

4 participants

@mess110

Regarding http://ppladdressbook.org/development/roadmap/ Synchronization UX. I worked with http://rubygems.org/gems/git in the past and it is great. Does a nice job.

Are you thinking of storing your contacts in a git repo? clone, add, commit and push can all be wrapped in some method sync as you called it. Would be a nice feature. What do you have in mind?

PS: When does the narwhal bacon?

@axelGschaider

I'm not completely sure what they mean by sync either (what is "Synchronization UX"?). But I myself would feel more comfortable with leaving management of external repos to good old plain git.
What I found rather confusing at first was that when "manually" changing or adding .vcf files, they first didn't show up in ppl. Then I figured out that ppl probably doesn't read the repository but the blobs in the .git folder. So you have to run

git add . && git commit -a -m 'some message'

in the local repo to make the changes visible in ppl.

I think wrapping those commands in a convenient sync command (as "sync manual changes") would fit better in the scope of a address book application while leaving the full complexity and possibilities of managing other repos with git.

my 2 cents

@storge-xx

well i'm with you fellas!

but seriously, i say that because i'm of two minds on this. on balance, i think i lean to the unix-like simplicity of doing it well.

...by the way, is posting a new issue the preferred way to discuss a desired feature creep? i have an idea that i think is hot-diggity but i don't want to be just opening issues. maybe a single issue "feature req" for people to pile on? part of this question is an ignorance of how git works overall, and then what you prefer in particular.

@hnrysmth
ppl member

...by the way, is posting a new issue the preferred way to discuss a desired feature creep? i have an idea that i think is hot-diggity but i don't want to be just opening issues. maybe a single issue "feature req" for people to pile on? part of this question is an ignorance of how git works overall, and then what you prefer in particular.

I know you've already opened that multiple email fields issue now, but I wanted to answer your question anyway. The answer is yes! Of course! Go nuts and open as many feature request issues as you want. And the same goes for anyone else reading this.

If opening too many feature request issues all the time ever became a problem I'm sure we could very easily discuss that and deal with it like sensible adults. But for now let's not risk missing any opportunities to improve or fix ppl.

An issue per request is better than one big issue for all because then it's easy to close individual requests and forget about them forever once they're implemented or rejected.

@hnrysmth hnrysmth was assigned
@hnrysmth hnrysmth closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.