Skip to contents

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

Responsible user: etiennemeleard

Placeholder for tickets regarding new features (primarily the ones discussed with RENATER) as well as a couple of known cliend-side issues that need to be fixed. Don't start work on this milestone until the class refactoring has been done.

  • 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

Responsible user: Jan Meijer

General backlog placeholder for tickets we shouldn't forget but can't assign to any particular milestone right now

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

Responsible user: Jan Meijer

This milestone has the goal to take the 2.0 alpha code and apply the changes Etienne suggested to make the code easier to deal with lateron: more modular and using the PHP object model.

- format all code (php, javascript and html) according to the agreed upon coding conventions (PSR, see https://www.assembla.com/spaces/file_sender/wiki/Coding_conventions)
- agree on/document a class design
- agree on/document a future database design
- write down user stories underpinning class and database design
- think through the upgrade process from 1.6 -> 2.0 and make sure the design doesn't make upgrading impossible
- implement the class and database changes

The result of this milestone is 2.0 code that basically does what the current prototype from summer 2013 does. A different milestone is the place holder for feature expansion (as per the RENATER input)

  • 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. This milestone contains all tickets related to the work Vegard Polden and Jack Kittridge coded during summer 2013. I put all these tickets under a separate milestone to be able to give a clean start to the work of Etienne and Roman summer 2014 which will take 2.0 to the next level.

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: Xander Jansen

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

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

Due date: almost 2 years ago (2013-03-29)

Responsible user: Jan Meijer

1.6 release