Skip to content

Commit 96e8975

Browse files
valens200valens200
authored
Merge branch 'main' into docs
Signed-off-by: valens niyonsenga <95166477+valens200@users.noreply.github.com>
2 parents d0fbeeb + f72a153 commit 96e8975

File tree

5 files changed

+201
-0
lines changed

5 files changed

+201
-0
lines changed

‎docs/2024/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,3 +63,4 @@ More info to come here.
6363
Photos to come soon.
6464

6565
Thanks for being part of the community. 💚
66+

‎docs/2024/rest/index.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,7 @@ This project involves the following tasks:
4141

4242
2. **Upgrading Existing Endpoints to Version 2:**
4343

44+
4445
- Develop a REST API guideline which will provide a solid set of rules to follow.
4546
- Upgrade existing endpoints to V2 based on the guideline, also ensuring backward compatibility.
4647
- Update documentation to reflect the changes and versioning.
@@ -49,4 +50,13 @@ This project involves the following tasks:
4950
- Study each endpoint and its functionality to identify potential edge cases.
5051
- Write unit tests for all existing and new endpoints.
5152

53+
More specific details about each task can be found in the [Task Details Table](https://docs.google.com/document/d/158BZBZ5owLtI-SqD1MIduMy4bR3XLuwm4aDLynoFZAA/edit?usp=sharing).
54+
- Develop a REST API guideline which will provide a solid set of rules to follow.
55+
- Upgrade existing endpoints to V2 based on the guideline, also ensuring backward compatibility.
56+
- Update documentation to reflect the changes and versioning.
57+
58+
3. **Increasing Test Coverage:**
59+
- Study each endpoint and its functionality to identify potential edge cases.
60+
- Write unit tests for all existing and new endpoints.
61+
5262
More specific details about each task can be found in the [Task Details Table](https://docs.google.com/document/d/158BZBZ5owLtI-SqD1MIduMy4bR3XLuwm4aDLynoFZAA/edit?usp=sharing).

‎docs/2024/rest/updates/2024-05-07.md

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: Community bonding
3+
author: Divij Sharma
4+
---
5+
<!--
6+
SPDX-License-Identifier: CC-BY-SA-4.0
7+
8+
SPDX-FileCopyright Text: 2024 Divij Sharma <divijs75@gmail.com>
9+
-->
10+
11+
# Community Bonding
12+
13+
## Introduction meeting
14+
15+
*(May 7,2024)*
16+
17+
This was the first meeting of the community bonding period for GSoC '24. Mentors and contributors introduced themselves, and the general meeting time and platform were decided.
18+
19+
## Meeting 1
20+
21+
*(May 9,2024)*
22+
23+
This was the first general meeting after the introduction meeting. Mentors discussed the importance of communication and the need for regular updates. The contributors were free to ask any questions they had.
24+
25+
## During community bonding week 1
26+
27+
*(May 9,2024- May 15,2024)*
28+
29+
### Activities
30+
31+
* I created an unofficial communication group with fellow contributors to get to know each other better.
32+
* I discussed the project and the tasks that need to be completed during the coding period with the mentors.
33+
* I clarified some of my doubts regarding the project timeline.
34+
35+
### Work done
36+
37+
* I was already familiar with the code-base because of my previous contributions to FOSSology. I started working on upgrading the REST APIs to version 2.
38+
* I fixed some minor bugs in the following of my uplink PRs related to the upgradation:
39+
- [feat(api): Upgrade User & Group APIs to Version 2 ](https://github.com/fossology/fossology/pull/2711)
40+
- [feat(api): Upgrade Folder, License & Obligation APIs to Version 2](https://github.com/fossology/fossology/pull/2712)
41+
42+
## Meeting 2
43+
44+
*(May 16,2024)*
45+
46+
We discussed the progress made during the first week of community bonding. Mentors asked if contributors were able to set up their development environments and if they faced any issues. Everyone gave a brief overview of the tasks they were working on.
47+
48+
## During community bonding week 2
49+
50+
*(May 16,2024- May 22,2024)*
51+
52+
### Activities
53+
54+
* I had calls with fellow contributors to help them set up their development environments.
55+
* I had a discussion with my colleague [Valens](https://github.com/valens200) about how we shall manage our tasks.
56+
57+
### Work done
58+
59+
* I continued working on upgrading the REST APIs to version 2.
60+
61+
* I finalized the work on a new endpoint to retrieve user copyright findings and also upgraded Jobs and Report APIs to version 2.
62+
- [feat(api): New endpoint to retrieve user copyright findings ](https://github.com/fossology/fossology/pull/2717)
63+
- [feat(api): Upgrade Jobs and Report APIs to Version 2 ](https://github.com/fossology/fossology/pull/2736)
64+
65+
66+
## Meeting 3
67+
68+
*(May 23,2024)*
69+
70+
We discussed the progress made during the second week of the community bonding period. Mentors asked if contributors faced any issues while installing the project and encouraged us to make small contributions. We also decided on the time for project-specific weekly meetings.
71+
72+
## During community bonding week 3
73+
74+
*(May 23,2024- May 29,2024)*
75+
76+
### Activities
77+
78+
* I helped few of my colleagues in setting up their development environments.
79+
80+
### Work done
81+
82+
* I continued working on upgrading the REST APIs to version 2.
83+
84+
* I upgraded the Search, Copyright & Admin APIs to Version 2.
85+
- [feat(api): Upgrade Search, Copyright & Admin APIs to Version 2 ](https://github.com/fossology/fossology/pull/2744)
86+
87+
## Meeting 4
88+
89+
*(May 30,2024)*
90+
91+
We discussed the progress made during the third week of the community bonding period. Mentors gave general updates followed by weekly updates by contributors. We had a session on how are we supposed to present and maintain our work during the coding period through the documentation.
92+

‎docs/2024/rest/updates/2024-05-30.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: Week 1
3+
author: Divij Sharma
4+
tags: [gsoc24, rest]
5+
---
6+
<!--
7+
SPDX-License-Identifier: CC-BY-SA-4.0
8+
9+
SPDX-FileCopyrightText: 2024 Divij Sharma <divijs75@gmail.com>
10+
-->
11+
12+
# Week 1 meeting and activities
13+
14+
*(May 30,2024)*
15+
16+
## Attendees:
17+
18+
- [Divij Sharma](https://github.com/dvjsharma)
19+
- [Gaurav Mishra](https://github.com/GMishx)
20+
- [Samuel Dushimimana](https://github.com/dushimsam)
21+
- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
22+
- [Soham Banerjee](https://github.com/soham4abc)
23+
- [Valens Niyonsenga](https://github.com/valens200)
24+
25+
## Discussion:
26+
27+
- **Who should be doing what?**
28+
- Discussed project responsibilities with my colleague [Valens](https://github.com/valens200) and mentors.
29+
- We decided that currently I will focus on the REST API Version 2 upgrade and OAuth 2.0 implementation, while Valens would work on adding test cases for the current REST API implementation.
30+
31+
- **REST API Version 2 updates**
32+
- I mentioned that the work on the REST API Version 2 upgrade is almost complete and suggested we can start looking for any further improvements.
33+
- Mentors suggested I should review the code and look for any possible improvements based on my proposed guidelines. [(REST API Guidelines)](../API-guidelines.md).
34+
35+
- **OAuth 2.0 architecture discussion and needs**
36+
- [Gaurav](https://github.com/GMishx) explained the various modes of authentication we aim to have in the FOSSology project. These are:
37+
- Token based authentication
38+
- Authorization Code Grant (Web Application)
39+
- Client Credentials Grant (Machine to Machine)
40+
- I cleared my doubts regarding the OAuth 2.0 implementation and its significance in the project. I also got a rough vision of what needs to be implemented and what is already implemented. [(Reference Material)](https://github.com/fossology/fossology/wiki/OpenID-Connect-authentication-configuration)
41+
42+
## Activities:
43+
44+
- Tested the REST API Version 2 on a local instance and noted down the improvements that can be made.
45+
- Researched on OAuth 2.0 and how it can be implemented in the project.
46+
- Did minor improvements in the following PR:
47+
- [feat(api): Upgrade User & Group APIs to Version 2 ](https://github.com/fossology/fossology/pull/2711)

‎docs/2024/rest/updates/2024-06-06.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
title: Week 2
3+
author: Divij Sharma
4+
tags: [gsoc24, rest]
5+
---
6+
<!--
7+
SPDX-License-Identifier: CC-BY-SA-4.0
8+
9+
SPDX-FileCopyrightText: 2024 Divij Sharma <divijs75@gmail.com>
10+
-->
11+
12+
# Week 2 meeting and activities
13+
14+
*(June 6,2024)*
15+
16+
## Attendees:
17+
18+
- [Divij Sharma](https://github.com/dvjsharma)
19+
- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
20+
- [Valens Niyonsenga](https://github.com/valens200)
21+
22+
## Discussion:
23+
24+
- No major updates since the last meeting.
25+
- Discussed the improvements that can be made in the REST API Version 2.
26+
- Discussed the implementation of OAuth 2.0 in the project.
27+
28+
## Activities:
29+
30+
- **OAuth 2.0**
31+
- Researched OAuth 2.0 and its application on production servers. Found the [Auth0 article](https://auth0.com/intro-to-iam/what-is-oauth-2) particularly helpful. Studied various architectural patterns for different flows to determine the best fit for our project.
32+
- Prepared a draft outlining the implementation details, focusing on two scenarios:
33+
34+
- **For the API**:
35+
- Create an endpoint to add new clients, accepting `name`, `clientId`, and `scope`.
36+
- Another endpoint to configure FOSSology, accepting `appName`, `clientId`, `clientSecret`, `clientClaim`, `redirectUri`, and `discoveryUri`. The `discoveryUri` will be used to fetch other required endpoints.
37+
- Once these steps are completed, FOSSology will be configured to use OAuth 2.0. Users can obtain a token from their authorization server to access the FOSSology API.
38+
39+
- **For the Web Application**:
40+
- Implement the Authorization Code Grant flow for the frontend. This requires a login page where users can log in and receive a code, which can be exchanged for a token to access the FOSSology API.
41+
- Researched libraries to implement this flow on the frontend.
42+
- On the server side, implement a mechanism to verify user credentials received from the server and issue a token to the user.
43+
44+
- **REST API Version 2**
45+
- Reviewed the code and identified areas for improvement.
46+
- Found the following things which we can look into:
47+
- Status Codes: Particularly 204 (no content)
48+
- Adding pagination to all necessary endpoints
49+
- Using model classes for all major/minor responses
50+
- Test coverage
51+
- Authentication workflow

0 commit comments

Comments
 (0)