[Soc-coordination] [Package Tracking System rewrite] Week 13 - September 13 - Status Report

[Marko Lalic]

Hello,

During the previous week the following user stories have been implemented:

- Source-to-source package dependency updates. The task which updates
information based on the repository Sources and Packages files is
extended to also resolve the source-to-source package dependencies
which arise either because a source package has a particular build
dependency or because one of its binaries depends on another source's
binary.

- An action item for packages that have a source dependency which
needs a new maintainer (as suggested by the WNPP data already being
retrieved by the PTS). For now, this is the only application of the
source-to-source dependency information.

- Create/delete/update a team. Teams let users define a group of
packages for which all the team members will receive news items. This
makes it easier to subscribe to a set of packages. The user that
creates a team is considered its owner and is the only one able to
modify its information or delete it. If a maintainer email is
provided, the team is automatically associated to any packages which
have the given email as a maintainer (or uploader). This association
is an ongoing process: any new packages which are detected by the PTS
are automatically added to the team if it contains the team's
maintainer.

- View/manage list of packages of a team. A team page is similar to a
package page, containing the list of the team's packages in a panel.
Any logged in user which is a member of the team is able to add a new
package to the team directly from the page itself -- an autocompleting
text box is provided in another panel.

- Join/leave a team. If a team is marked public by its owner, any
logged in user is able to join it by clicking a `Join` button in the
top of the page (similar to Subscribe for packages). On the other
hand, if a team is private, the page only includes a link to contact
the team's owner.

- Manage team members. A team's owner is able to manually add
arbitrary emails as members of the team. He is also able to remove any
of the team's already existing members.

- View a list of public teams. A list of all public teams is provided,
where apart from the team's name, the number of team members and
tracked packages is also displayed.

The final week of GSoC has the following planned user stories:

- Manage a team subscription. The user can mute/unmute a the whole
subscription (while staying a member of the team) or only some
packages. He can also set a list of keywords for each package of the
team so that he only receives emails tagged with those keywords.

- Receive updates for packages of the team. All members of the team
should receive package messages for packages that the team is
associated with. A user receives the message only if his personal
settings do not mute it in some way (team muted, package muted, his
subscription to the team does not have the message's keyword).

- View a list of teams the user is subscribed to. This is displayed in
the "subscriptions" profile page.

- Email control commands related to teams. The functionality of
joining a team, leaving a team, listing a team's packages, listing all
teams, and listing all teams a user is subscribed to will be exposed
via corresponding email control interface commands.

- Import the existing/old PTS package subscription info: a script to
prepare for migrating the service.

- Export PTS data to UDD: provide an alternative format to the output
of the management command that lists source packages and their
subscribers. This output format is adapted for what the UDD expects
from PTS.

- Reset password. Users can reset their password in case they forget
it. They are provided a URL in an email which lets them set a new
password for their account.

- Associate additional emails with an account. A user can request an
additional email to be added to his account, which takes effect once a
URL sent in an email message to the provided email address is
followed. The user is then able to log in to his account using any of
his associated accounts. When a user tries to associate an email
address which is already a part of a different account, the PTS offers
the user to merge the two accounts.

- Login via sso.debian.org. A Debian-specific addition to the
authorization/accounts management, allowing DDs to authenticate via
sso.debian.org. When a user is first logged in by this mechanism, a
new account is automatically created. The user's name is retrieved
from the Debian LDAP. For any user account which has a @debian.org
email address associated with it, the only log in option becomes
sso.debian.org -- any log in attempts are refused and the user is
instructed to authenticate on sso.d.o.

Thanks for reading.

Cheers,
-- 
Marko Lalić

email: marko.lalic at gmail.com