digitalexcellence / dex-epics Goto Github PK

In GitLab by @Brend-Smits on Mar 4, 2020, 20:36

• What architecture should be used for the backend? dex-backend#15
• Should we make use of microservices, if so, how? dex-backend#15
• Will there be containerization? dex-backend#16
• How do we make sure that future additions to the platforms can be easily added and maintained? (Add a new platform like Github as a source for DeX to get data from)

In GitLab by @Brend-Smits on Mar 9, 2020, 13:23

• How are we going to tackle this? Research is required to define sub-issues
• Are there going to be categories?
• Tags? Auto-tagging?
• Filter on: Source, Collaborators
• Sort on: Date

Issues:

• Filter projects: https://git.fhict.nl/dex/dex-backend/-/issues/55
• Research: How can we tag and categorize projects?: https://git.fhict.nl/dex/dex-backend/-/issues/56
• Sort projects: https://git.fhict.nl/dex/dex-backend/-/issues/57

The original issue

Id: 4
Title: SURFContext OAuth

could not be created.
This is a dummy issue, replacing the original one. It contains everything but the original issue description. In case the gitlab repository is still existing, visit the following link to show the original issue:

TODO

In GitLab by @Brend-Smits on Mar 4, 2020, 20:36

• Investigate what governance is required to get this project off the ground
• What data can we legally gather and use from our own platforms?
• What data can we legally gather and use from external platforms like Github?
• What methods of gathering data are okay to use? Web scraping, API's, etc.

In GitLab by @Brend-Smits on Mar 4, 2020, 20:36

• What hosting should be used? dex-backend#16
• How can we assure that it's easily maintainable for future groups?
• How can we assure that governance can easily 'sell' the platform to internal IT from Fontys?
• How can we easily scale the platform? dex-backend#25
• Set up a pipeline and release every sprint dex-backend#18

In GitLab by @Brend-Smits on Mar 9, 2020, 13:20

• Brainstorm and setup requirements
• Notified if a person that I follow does something
• Notified for 'hot/trending/ item
• Research, how should we notify the user? Email, in dashboard
• Notification feed
• Research, should users get an email with weekly hot items for example?

User Story: As a user, I want to receive weekly notifications about hot/trending projects so that I’m reminded about the platform and do not miss trending projects
Criteria:

1. A weekly notification should be sent to platform users that are interested in trending projects. Trending topics can be defined by visitor count, likes or shares.
2. Notifications should be configurable on the user settings page. Users can configure if they would like to receive them via email or on the platform itself. They can also configure the frequency of the notifications.

In GitLab by @Brend-Smits on Mar 24, 2020, 14:38

Implementation of external Github source

User Story: As a student, I want to be able to use external sources like Github so that I can add projects to the platform via Github more easily
Criteria:

1. Assuming the student is on the ‘add project’ page, the user can click on the Github source card. This will ask the user to authenticate with the source and ask for permission for the required scopes. The student will now select which projects they want to import to the platform.
2. When the importing is done, it is possible that certain information is missing or could not be imported. The user should be given a notification about this and should be asked ‘Check and verify that the information that is imported is correct”
3. If the import(s) is unsuccessful, the user should be notified with an error message. This should be notified to the automated error-monitoring system as well.
4. If the import(s) is successful, the user should be notified and shown a list view of the imported projects, with their representative URLs to the detailed pages.

In GitLab by @RensNooren on Mar 24, 2020, 21:45

A first working version of the frontend with atleast the first 4 pages, as seen in the wireframes, implemented and designed with the styleguide.

In GitLab by @Brend-Smits on Mar 24, 2020, 14:39

Style guide
Branding defined
Logo

In GitLab by @Brend-Smits on Mar 9, 2020, 13:04

• Highlight projects on frontpage
• Search feature
• Search recommendation
• Research: What ways are applicable to show interesting projects from the community on top of the search results or recommendations (page views, likes, forks, contributions as an example) (Priority)
• Research: How can we design an algorithm for search and recommendation while keeping the algorithm easy to maintain and extendible in the future? (Priority)

Issues:

• Research: Data gathering for top search results or recommendations (page views, likes, forks, etc): https://git.fhict.nl/dex/dex-backend/-/issues/59
• Research: How can we design an algorithm for search and recommendation while keeping the algorithm easy to maintain and extendable in the future?: https://git.fhict.nl/dex/dex-backend/-/issues/60
• Implement recommendation algorithm: https://git.fhict.nl/dex/dex-backend/-/issues/61
• Identify and Implement improved search algorithm: https://git.fhict.nl/dex/dex-backend/-/issues/62

In GitLab by @Brend-Smits on Mar 4, 2020, 20:36

• How can we gather data from Gitlab?
• What data can we gather from Gitlab?
• Implement a user interface that is easily expandable and that is easy to use
• Implement a backend that follows SOLID principles where applicable
• Comply with legal entities / GDPR

Wilrik comments:
Loose,Wilrik W.R. De @wilrikdeloose · 2 weeks ago
Maintainer
We'll start with hosting GitLab and manually added projects on the platform. The design of the platform however should be setup in such a way that it is easy to add different data sources (internship reports, graduation portfolios, etc).

Loose,Wilrik W.R. De @wilrikdeloose · 2 weeks ago
Maintainer
It would be nice to have a feature that allows the user to take their internal GitLab project(s) and make it publicly available so that the portfolio is available outside of FHICT, for instance when graduated.

In GitLab by @Brend-Smits on Mar 29, 2020, 20:15

Any issues that are not directly related to an epic but are still due in a sprint are called "Overhead".

Sprint 2:

• Setup unit test: https://git.fhict.nl/dex/dex-backend/-/issues/63
• Postman API Integration tests: https://git.fhict.nl/dex/dex-backend/-/issues/38
• Investigate saving the database with EF Core: https://git.fhict.nl/dex/dex-backend/-/issues/51
• Research: Query Language: https://git.fhict.nl/dex/dex-backend/-/issues/48
• Research: Database technology: https://git.fhict.nl/dex/dex-backend/-/issues/45
• Define coding guidelines: https://git.fhict.nl/dex/dex-backend/-/issues/50
• Wiki: How to setup local development: https://git.fhict.nl/dex/dex-backend/-/issues/46
• Research: Backend tech stack: https://git.fhict.nl/dex/dex-backend/-/issues/7
• IdentityServer - Single sign on with Fontys: https://git.fhict.nl/dex/dex-backend/-/issues/64
• Update existing technical documentation: https://git.fhict.nl/dex/dex-backend/-/issues/65
• Create issue templates: https://git.fhict.nl/dex/dex-backend/-/issues/9
• Add linting to the pipeline: https://git.fhict.nl/dex/dex-backend/-/issues/68
• Certificates: https://git.fhict.nl/dex/dex-backend/-/issues/66
• Editor config file: https://git.fhict.nl/dex/dex-backend/-/issues/67

In GitLab by @Brend-Smits on Mar 9, 2020, 13:08

• Personal projects
• Platform wide projects
• Follow user/projects
• Implement with notification
• How should we implement this?

Issues:

• Endpoint to retrieve only highlighted projects: https://git.fhict.nl/dex/dex-backend/-/issues/53
• Add role for people that are allowed to add/remove highlighted projects: https://git.fhict.nl/dex/dex-backend/-/issues/52
• Projects should have an embed button that generates an iframe: https://git.fhict.nl/dex/dex-backend/-/issues/54

In GitLab by @Brend-Smits on Mar 24, 2020, 14:41

User Story: As a user, I want to be able to share my user profile with others so that I can share my projects and have it act as a portfolio
Criteria:
Assuming that I’m on my own profile page, I can configure if I want the profile to be publically accessible or not. I will also be able to copy the URL easily to share it.

1. The profile page of a user should show the projects the user has contributed to.
2. The profile page of a user should show the roles of the contributions
3. The profile page contains a highlighted section where the user can highlight projects
4. The profile page contains general information like a photo, bio, and interests
5. The profile page allows editing of the general information

In GitLab by @Brend-Smits on Apr 14, 2020, 11:27

Based on the protocols:

• @wilrikdeloose will add these requirements

Example: Student starts with some hobby project, the project evolves over time and more students are starting to use it. It now becomes a level X project (this is a system defined by school). The project leader can then request a project validation, this validation requires the student to meet the requirements defined above. A team from Digital Excellence will then validate the project by hand. After validation, the project will show a 'validated' status.