-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve FHICT Git source #79
Comments
In GitLab by @StijnGroenen on Apr 16, 2020, 21:51 I just discussed this issue with Brend and Rens. We would like to propose another solution for implementing the Digital Excellence system. By creating one single structure for projects, improvements like the search algorithm, sorting, filtering and more only have to be developed for the single database and not for all the sources. Of course, this proposition needs to be discussed further. We will bring this up soon in a meeting. |
I've discussed this with the Digital Excellence team and I think I have enough feedback to be able to conclude that one uniform implementation for all sources, both internal and external, is more in favor than making one exception for the FHICT GitLab. In other words, create one flow for adding new projects to DeX and do not automatically include all FHICT GitLab projects in search results. |
That's great news, let's dedicate resources to this in the upcoming sprint (sprint 4). |
I updated the Setup Plan to incorporate these changes. |
This can be closed in favor of #127 , feel free to re-open if you disagree |
In GitLab by @Brend-Smits on Apr 15, 2020, 14:08
The flow for Gitlab is weird. When a user searches for a project, the platform will automatically search the Gitlab API for existing projects that we can show. However, what do we show the user for these projects in terms of Contributors, description or other information that is hard to automatically gather? And what if a user owns a project that is automatically shown via the API, but they want to make changes to for example the contributors or description? How do we handle this?
Why do we not make the flow uniform with other sources like Github:
Doing it this way we can easily add projects from different sources, the experience for adding Github, Gitlab, FHICT Git projects will be similar for every source. It also becomes easier to manage for DeX Platform and easier to implement.
A middle ground would be to do it as following:
However, users can claim the projects if the information is not correct, claiming the project will save it in our database (like we do with other projects that people add from for example "Manual add project").
The text was updated successfully, but these errors were encountered: