List view

• Release 2.3

  This milestone includes all the features and bugs to be fixed before we release Portus 2.3. ## Code freeze!! All features have already been implemented (or they are in PRs). From now until we release 2.3, only bug fixes and documentation changes are accepted.

  Due by November 29, 2017

  •61/61 issues closed
  100% complete0 open61 closed

• Documentation for 2.1

  1. Documentation is still a bit behind, we should work more on that and improve UX. 2. We've added lots of stuff for 2.1, we should make sure that everything is properly documented (what the feature consists in, paths to upgrade, etc.). 3. We've added a blog section in http://port.us.org. We should write more often.

  Due by August 26, 2016

  •8/8 issues closed
  100% complete0 open8 closed

• Tentative: Better Release procedure

  Due by July 28, 2016
  0% complete0 open0 closed

• Tentative features for the 2nd stable release of Portus

  That is, features that don't have a high priority for the 2nd stable release of Portus.

  No due date

  •23/23 issues closed
  100% complete0 open23 closed

• 2nd stable release of Portus

  No due date

  •38/38 issues closed
  100% complete0 open38 closed

• 1st stable release of Portus

  No due date

  •39/39 issues closed
  100% complete0 open39 closed

• UI improvements

  As we now have a better idea regarding which kind of data we'll display, the UI should be adapted accordingly. This milestone is a general collector of all the improvements we'll need to look at.

  No due date

  •5/5 issues closed
  100% complete0 open5 closed

• Teams & Roles

  Portus needs to implement the concept of Teams and Roles. A Team is defined as a cherry picked subset of users, to which one or more namespaces will belong to. The type of access granted to those namespaces will be defined by the Role assigned to each Team member, and will be consistent across all namespaces owned by the Team. Each user must be able to have one or multiple roles, defined as such: *Owner* This is the default and unchangeable role for the the own namespace. This Role will also be inherited by the Team creator on the Team namespace(s), and can be granted to other Team members. - Has RW rights on the namespace - Has access to the Team management: - Who's part of the team - Which Role each team member has within the team While a user must keep his Owner Role for the private namespace, the ownership of a team and its namespace can be dropped, as long as another Owner for the same Team exists. As you can't have a Team without an Owner, the Owner of a team can either delegate the Ownership to other Team members or delete the Team. *Contributor* - Has RW rights on the namespace *Viewer* - Has RO access to the namespace. Separated from those roles, there must be a possibility of marking non personal namespaces as public. This will be presented to the Owner of the namespace in form of a checkbox, deactivated by default. By marking the checkbox, anyone registered as a Portus user, but not part of the Team will have RO access to the namespace, maintaining the validity of the previously defined Roles within the team. The checkbox can be deselected by the Owner at anytime.

  No due date

  •4/4 issues closed
  100% complete0 open4 closed