FileSender is an open source project powered by Assembla

Assembla offers free public and private SVN/Git repositories and project hosting with bug/issue tracking and collaboration tools.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

things making the install less then optimal

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Set up automated test infrastructure using Selenium. The result should allow us to automatically test a FileSender version on a number of browsers. We want to make sure FileSender works for a set of specific browser - browser version - OS - OS version combinations: the supported browser matrix.

The supported browser matrix should list those environments typically encountered in the wild. The only way to scale up testing to the number of browsers is by automating. The goal is to prevent help desk calls to people running FileSender installs.

Automated testing enables us to test all versions at any time: nightly builds, betas, release candidates.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours
  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Stuff related to Assembla, sites etc. goes here.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Placeholder for new feature suggestions. Features go from "Suggested features" to "Planned features" if they are to be implemented.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

temporary placeholder for the stuff in the workplan for 2011. Once we have prioritised the stuff here and the "smaller" tickets that were already planned or suggested, all stuff we work on goes into "planned" and "under development" as appropriate

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours
  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Responsible user: Jan Meijer

Describe the goals for your next release

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Establish easy-to-use infrastructure to farm out language file maintenance. Likely tool to use is:
https://www.transifex.net/tour/features/translate/

Adopting this tool likely means an effort to go from one format to the other. Until we have resources to do that, we'll work with an extra Assembla space.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours
  • 0.0 Work remaining
  • |
  • 0.0 Worked hours
  • 0.0 Work remaining
  • |
  • 4.0 Worked hours

Bugs found in 1.5 (currently under development)

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Responsible user: Jan Meijer

Version 2.0 is the multi-file enabled release. It's a continuation of the work Vegard Polden and Jack Kittridge coded during summer 2013

1. new multi-upload.php and file upload UI, including drag & drop support
2. new download.php with "one-click to download all files as zip file" functionality
3. revised pause/resume that works with multi file
4. revised email flow
5. revised MyFiles based on the version 1.6 new MyFiles
6. fine-grained email receipt control

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Tickets filed under this milestone are features that are planned to be implemented

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Responsible user: vpolden

Module for standard usage statistics: how many uploads, downloads, users etc.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Responsible user: gijzelaerr

Implementation of planned feature number #7. Encryption technical design document can be found here:

https://docs.google.com/document/pub?id=1mvuBNseY9jbseM_DQKnJH9V-xIOXPCgncwaRQdZ-ooI

Gijs, please make sub-tickets under this milestone as needed.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Version 1.1 is essentially FileSender 1.0.1 with the Gears module replaced by HTML5 upload.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

New features to be released after 1.5. Exact version numbering to be decided on when tickets have been implemented. Quick wins package ought to be codeable in about 2 weeks and should contain 1 bugfix in addition to the new features.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours
  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

stuff kept around for historical purposes

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Bugs found in version 1.0(.x) and the various beta releases before the 1.0 release.

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Placeholder for bugs discovered in the 2.0 development

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Prototype (establish in playground) to figure out whether the UI would improve of a re-ordering of fields. The idea is that it's a different (possibly better) user experience if the file selection activity comes first and a user adds the "boring other bits" after that. It's the file(s) they're concerned about, those should go from A to B. So that's the most important thing and comes first. The rest is then a "oh, need to do that as well".

It could make for a cleaner way to display a list of selected files, needed for multifile-sending functionality. Iff done in the current UI such a list will likely look more messy. An additional advantage is it'll make it easier to make clear what the mandatory fields are: those are the ones coming first. The optional ones come afterwards.

A disadvantage is we're moving away from the "email like" interface.


-add dropzone for drag&drop (is it possible to make the entire screen a
dropzone?)
-create a good "list box" functionality where you can deselect files as well
before clicking send (you might already have this in the multifile upload
prototype?)
-change order of fields: file selection stuff first, followed by all mandatory
fields followed by optional fields
-clear indication of mandatory fields with some red dot behind it or something
-remove the 1-2-3-4 step on-page help

  • 0.0 Work remaining
  • |
  • 0.0 Worked hours

Due date: about 1 year ago (2013-03-29)

Responsible user: Jan Meijer

1.6 release