What should I work on in April? I expect I could get perhaps two of these features done in a month if I'm lucky. I have only 3 more funded months, and parts of one will be spent working on porting to Windows, so choose wisely! --Joey

[[!poll open=yes expandable=yes 4 "upload and download rate limiting" 15 "get webapp working on Android" 5 "deltas: speed up syncing modified versions of existing files" 8 "encrypted git remotes using git-remote-gcrypt" 0 "add support for more cloud storage remotes" 19 "don't work on features, work on making it easier to install and use" 2 "Handle duplicate files" 6 "direct mode (aka real files instead of symlinks) [already done --joey]" 3 "start windows port now"]]

References:

  • rate limiting
  • Android
  • deltas to speed up syncing modified files (at least for remotes using rsync)
  • encrypted git remotes
  • more cloud providers (OpenStack Swift, Owncloud, Google drive, Dropbox, Mediafire, nimbus.io, Mega, etc.)
  • old poll on "what is preventing me from using git-annex assistant" (many of the items on it should be fixed now, but I have plenty of bug reports to chew on still)
Posted Thu 17 Jul 2014 03:53:21 PM UTC

Help me choose a goal for the month of December. The last poll showed a lot of interest in using the git-annex assistant with phones, etc.

Background: git-annex uses symbolic links in its repositories. This makes it hard to use with filesystems, such as FAT, that do not support symbolic links. FAT filesystems are the main storage available on some Android devices that have a micro-SD card. Other, newer Android devices don't have a SD card and so avoid this problem.

I can either work on the idea described in desymlink, which could solve the symlink problem and also could lead to a nicer workflow to editing files that are stored in git-annex.

Or, I can work on Android porting, and try to get the assistant working on Android's built-in storage.

[[!poll open=no 81 "solve the symlink problem first" 17 "port to Android first" 1 "other"]]

Posted Thu 17 Jul 2014 03:53:21 PM UTC

The 2013 git-annex user survey is in progress here.

Posted Thu 17 Jul 2014 03:53:21 PM UTC

What directory should the Android webapp default to creating an annex in?

Same as the desktop webapp, users will be able to enter a directory they want the first time they run it, but to save typing on android, anything that gets enough votes will be included in a list of choices as well.

[[!poll open=yes expandable=yes 67 "/sdcard/annex" 6 "Whole /sdcard" 7 "DCIM directory (photos and videos only)" 2 "Same as for regular git-annex. ~/annex/"]]

Posted Thu 17 Jul 2014 03:53:21 PM UTC

Background: git-annex supports storing data in various special remotes. The git-annex assistant will make it easy to configure these, and easy configurators have already been built for a few: removable drives, rsync.net, locally paired systems, and remote servers with rsync.

Help me prioritize my work: What special remote would you most like to use with the git-annex assistant?

[[!poll open=yes 16 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 10 "Box.com (done)" 73 "My phone (or MP3 player)" 25 "Tahoe-LAFS" 13 "OpenStack SWIFT" 34 "Google Drive"]]

This poll is ordered with the options I consider easiest to build listed first. Mostly because git-annex already supports them and they only need an easy configurator. The ones at the bottom are likely to need significant work. See cloud for detailed discussion.

Have another idea? Absolutely need two or more? Post comments..

Posted Thu 17 Jul 2014 03:53:21 PM UTC