Make a mixin that displays an error page if a route has not match or a repository / account can't be accessed.

Depends on G-Node/gin-repo#33.

Requires to change form.is_public to form.public.

I wondered whether the Institute text field is in fact the institution? like LMU?

Provide all information required to create a grant request at gin-auth, when registering a new account.

Dependent on G-Node/gin-auth#107.

Required to refactor repository display and edit settings from mockup to real data.
Depends on G-Node/gin-repo#57.

Currently the list of collaborators at RepoSettings displays only the collaborators usernames,
since this list is delivered from gin-repo.

Full name and e-mail of the collaborators of a repository need to be fetched from gin-auth. Currently this would require an individual GET request for every collaborator. Ideally use a more performant solution.

Help and information text would be useful. The SSH key management page in particular, since it may not be immediately apparent what the keys are used for and if they're necessary. For example, users who don't care to set up SSH keys and use the CLI shouldn't worry about it.

Try to login using the session cookie issued during the authorization process of gin-auth

Auth pages don't specify a page title.

Add a bread crumb navigation in order to reduce the number of clicks necessary to navigate back:

Example:

Your Data > Shared Repositories > repo

Tokens are currently just removed from localStorage but not deleted on the server. Since this is currently not supported by gin-auth.

Once an account is activated, it would be convenient to link (or redirect) to the login page.

Find more information about migration here and here.

By integrating one of these options

• vue-markdown
• marked

Or something completely different.

e.g. reloading a repository main page results in
"Nothing here. Move along."

reloading the "files" page to check for updates as I push files ends with 404

If reloading is a problem, what about a refresh button?

Depends on G-Node/gin-core#1.

Refactor existing error handling to display the proper error messages.

• Add Terms of usage page
• Add link to page footer

After gin-auth pull request #69 e-mail is no longer updated via account update. Add update e-mail option within Personal settings. Address issue #24 in the process.

When viewing a repository on the web, it would be helpful to have a small tip showing how the data can be downloaded using the client.

For example

To download the data in this repository, use gin download <user>/<reponame>

The actual command may change depending on the final syntax of the download command.

Currently every keystroke within the Add collaborator input field triggers a request to gin-auth to return a filtered list of accounts. This is an overhead that should be reduced.

The firefox title is not set, i.e. when the GIN tab is open, firefox show "mozilla firefox" in the task bar and the frame title, something like G-Node GIN or similar would be nicer,

Firefox offered to remember the password upon account creation but is does not show the login as account name but the country, i.e. the last text field before the password. Is this under your control? Can this be changed to show the account name?

In the activation screen, the G-Node logo is a link but does not lead anywhere.

Same page, a link back to the sign-in page would be great

some help/information in the ssh key registration page would be good for the more naive user, why would I need it, why should I use it and how can I get an ssh key

• Add owner full name to each repository listing
• Remove line referring to current branch
• Remove "description:"
• Change "Public: bool" to "Public repository" or "Private repository"

When trying to create a new repository with the name of an existing repository, the current message towards the user is Conflict.

Come up with a more informative error message...

Add minimal footer including

• g-node logo + link to g-node
• copyright
• about
• contact

Figure out how to test js and vuejs.

• Vuejs testing.
• VueJS suggests using Karma for testing.
• Jasmin supposedly helps making Karma play nice with Travis.
• Reading this might also help when testing GUI stuff on Travis.
• Here an example of a project that actually uses Vuejs unit testing with Travis.

Currently errorEvent in src/js/App.vue is not functional.

Merge with alertEvent and refactor it's usage throughout the project.

• Move "Choose..." to a lower part of the features section.
• Add accordion changes from gnode-bootstrap; depends on G-Node/gnode-bootstrap-theme#4.
• Add versioning paragraph.

Integrate adding and removing the collaborators of a repository at the repository settings.

• Display existing collaborators.
• Add a new collaborator as its own action (not connected to updating a repositories' description or privacy setting).
• Remove an existing collaborator as its own action.

Depends on issue G-Node/gin-repo#42.

Manual page refresh (e.g. by pressing F5) at Repo and RepoSettings leads to an undefined repository.shared array, existing repository collaborators will not be displayed until RepoSettings is properly accessed via another link.

Repository browsing and permissions were previously based on pure mocked data. This data and leftover attached functions need to be identified and removed.

Implement and use a proper state value in requests to auth against CSRF as described in the OAuth2 RCF 6749.

A short description of the problem can be found here, here or here.

Integrate display and update of a repositories' description and privacy in the repository settings.

Updating a repositories privacy depends on issues G-Node/gin-repo#41 and G-Node/gin-repo#43.

Initiate export of a repository at its current state to a DOI service.

Details TBD.

Properly display the content of a repositories' readme file, e.g. as markdown.

Depends on #47.

at least in my case it does not lead to anything

• Change "can-pull" to "can-read" and "can-push" to "can-write"
• Add a Collaborator access level legend at the bottom of the settings page

updateTitle in src/js/App.vue currently does not properly update on non existing routes.

Add shell script for easy server side deployment of new versions.

Depends on issue G-Node/gin-repo#69.

Change RepoSettings.vue to support the following changes:

• Deal with the new collaborator JSON containing the repository permission levels when displaying existing collaborators.
• Change the default repository permission level from can-push to can-pull when adding a new collaborator to a repository.
• Display the repository permission level that a collaborator currently has (should currently be either can-pull or can-push).
• Add the option to either add or remove can-push to or from a collaborator.

Paginate

• Repository search results
• User search results
• Own repository list
• Shared repository list

Use gin-repo to handle repository data.

Changing the "make e-mail public" flag is not updated via the edit profile menu.

When a registration is initialized from gin-ui, redirect back to gin-ui after the registration at gin-auth is done.

The Country field in the sign up form is misidentified as the username by browsers (notably Firefox, #58) when saving credentials. Additionally, when navigating to the sign-up form with credentials are already stored in the browser, the browser offers to autofill the Country field with the stored username (tested in Chrome).

This needs more testing (and maybe some reading of autofill specs?) but it's possibly due to browsers using the last text field before the password as the username.