Change Details

This is the second task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Structure a SQLite database and create a django model for the //Bug// app. **Steps:** # Read the second part of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial02/ | Writing your first Django app ]] tutorial. # Create a Bug model with the following fields: "description", "bug_type", "report_date", "status", representing, respectivelly, the textual description of the bug, the type of the bug (e.g. error, new feature etc), the date in which the bug is being registered and the status of resolution of the bug (e.g. to do, in progress, done, etc). # Structure the database as described in the tutorial and create at least one //bug// through Django Admin. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.

IMPORTANT: Make sure to read the [Outreachy participant instructions](https://www.mediawiki.org/wiki/Outreachy/Participants) and [communication guidelines](https://www.mediawiki.org/wiki/New_Developers/Communication_tips) thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up Gerrit, etc. When in doubt, ask your question on [Zulip](https://www.mediawiki.org/wiki/Outreach_programs/Zulip) first! This is the second task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Structure a SQLite database and create a django model for the //Bug// app. **Steps:** # Read the second part of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial02/ | Writing your first Django app ]] tutorial. # Create a Bug model with the following fields: "description", "bug_type", "report_date", "status", representing, respectivelly, the textual description of the bug, the type of the bug (e.g. error, new feature etc), the date in which the bug is being registered and the status of resolution of the bug (e.g. to do, in progress, done, etc). # Structure the database as described in the tutorial and create at least one //bug// through Django Admin. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.

IMPORTANT: Make sure to read the [Outreachy participant instructions](https://www.mediawiki.org/wiki/Outreachy/Participants) and [communication guidelines](https://www.mediawiki.org/wiki/New_Developers/Communication_tips) thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up Gerrit, etc. When in doubt, ask your question on [Zulip](https://www.mediawiki.org/wiki/Outreach_programs/Zulip) first! This is the second task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Structure a SQLite database and create a django model for the //Bug// app. **Steps:** # Read the second part of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial02/ | Writing your first Django app ]] tutorial. # Create a Bug model with the following fields: "description", "bug_type", "report_date", "status", representing, respectivelly, the textual description of the bug, the type of the bug (e.g. error, new feature etc), the date in which the bug is being registered and the status of resolution of the bug (e.g. to do, in progress, done, etc). # Structure the database as described in the tutorial and create at least one //bug// through Django Admin. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.