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.
Total votes: 90
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
Total votes: 62
- rate limiting
- 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)
My goal for this month is to get more people using the git-annex assistant, and fix issues that might be blocking you from using it. To do this, I'd like to get an idea about whether you're already using it, or what's keeping you from using it.
If you use
git-annex at the command line and have no reason to use the
assistant, please instead fill in this poll on behalf of less technically
adept friends or family -- what's preventing you from introducing them to
I'm using the assistant! (3%)
I need a Windows port (12%)
I need an Android port (13%)
I need an IPhone port (not holding my breath) (1%)
Well, it's still in beta... (0%)
I want to, but have not had the time to try it (4%)
Just inertia. I've got this dropbox/whatever that already works.. (2%)
It's too hard to install (please say why in comments) (1%)
Perceived recent increase of bug reports and thus sitting it out. (0%)
Initially the lack of direct-mode. Now concerns about the safety of direct mode. Perhaps after the next release. (11%)
I haven't always well understood the differences between commandline operation & the assistant, so the differences would confuse me, and I found the command line more understandable & less scary. Now trying to learn to like & trust the assistant. (4%)
An Ubuntu PPA would be supercool! Thanks for your great work!! (9%)
Not yet in Debian sid amd64 (8%)
Waiting for Fedora/CentOS rpm repository. (2%)
throttling transfers, it upsets people when I saturate the connection (0%)
partial content (0%)
Not yet available in macports (0%)
No build yet for Nokia N9 (1%)
Using only git-annex webapp to config does not seem to work: Create walkthough? (1%)
No build for OSX 10.6 (2%)
Needs more focus on the UI. (2%)
Just inertia. I don't have a Dropbox/whatever. (0%)
Replaces files with a symlink mess. (1%)
configurable option to only annex files meeting certian size or filename criteria (0%)
I'm really confused about how to make it sync with a remote NON-bare repository. I'm even afraid to try `git remote add`, since there is no clear method to completely forget a git-annex remote... (1%)
A build for te raspberry pi would be supercol! (2%)
Would be nice to exclude subfolders from the gui or through a config file (0%)
I wish I had transparently encrypted git repos in the cloud available, like jgit. (0%)
too many inodes used in direct mode. maybe it's possible to keep more info as git objects instead? (0%)
I need to be able to restrict in which repo dirs changes get auto-committed (0%)
Provide .deb package (0%)
Better documentation/walkthroughs on using git-annex within an existing git repo. AKA mixed use (0%)
Union mounts to have a single view of file collection on the network (0%)
Ubuntu PPA does not build with webapp (0%)
I set it up, but am confused about what I set up! It would be great to be able to start from scratch. (0%)
I need to be able to restrict in which repo dirs changes get auto-committed using a syntax similar to gitignore (0%)
Total votes: 221
Feel free to write in your own reasons, or add a comment to give me more info.
Note: Poll is now closed. Nearly all these issues have been dealt with. Please file bug reports if any of these issues still affect you.
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.
solve the symlink problem first (81%)
port to Android first (17%)
Total votes: 99
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?
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..
Started work on the interface displayed when the webapp is started with no existing git-annex repository. All this needs to do is walk the user through setting up a repository, as simply as possible.
A tricky part of this is that most of git-annex runs in the Annex monad, which requires a git-annex repository. Luckily, much of the webapp does not run in Annex, and it was pretty easy to work around the parts that do. Dodged a bullet there.
There will, however, be a tricky transition from this first run webapp, to a normally fully running git-annex assistant and webapp. I think the first webapp will have to start up all the normal threads once it makes the repository, and then redirect the user's web browser to the full webapp.
Anyway, the UI I've made is very simple: A single prompt, for the directory where the repository should go. With, eventually, tab completion, sanity checking (putting the repository in "/" is not good, and making it all of "$HOME" is probably unwise).
Ideally most users will accept the default, which will be something
/home/username/Desktop/Annex, and be through this step in seconds.
Suggestions for a good default directory name appreciated.. Putting it on a folder that will appear on the desktop seems like a good idea, when there's a Desktop directory. I'm unsure if I should name it something specific like "GitAnnex", or something generic like "Synced".
Time for the first of probably many polls!
What should the default directory name used by the git-annex assistant be?
something lowercase! (20%)
Total votes: 50
(Note: This is a wiki. You can edit this page to add your own poll options!)