-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Add devsoc name and replace most csesoc references (#803)
* feat: Add devsoc logo and replace most csesoc references * update github source link * updated code owners and devsoc github links * updated links in onboarding and codeowners devsoc technical --------- Co-authored-by: Shaam <[email protected]>
- Loading branch information
Showing
7 changed files
with
46 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| auto_server/ @csesoc/notangles-leads | ||
| client/ @csesoc/notangles-leads | ||
| server/ @csesoc/notangles-leads | ||
| auto_server/ @devsoc-unsw/notangles-leads | ||
| client/ @devsoc-unsw/notangles-leads | ||
| server/ @devsoc-unsw/notangles-leads | ||
|
|
||
| .github/ @csesoc/technical | ||
| renovate.json @csesoc/technical | ||
| .github/ @devsoc-unsw/platform | ||
| renovate.json @devsoc-unsw/platform |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -22,7 +22,7 @@ Before you start, make sure that you have the following software installed. | |
|
|
||
| Clone the repository: | ||
|
|
||
| `git clone [email protected]:csesoc/notangles.git` | ||
| `git clone [email protected]:devsoc-unsw/notangles.git` | ||
|
|
||
| ### Running the front-end | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -46,7 +46,7 @@ const Footer: React.FC = () => { | |
| <div> | ||
| <h1 style={{ fontSize: '14px' }}>Notangles - UNSW Timetable Planner</h1> | ||
| <p> | ||
| Notangles is a UNSW timetable planner, brought to you by CSESoc Dev. It's an easy to use drag-and-drop tool | ||
| Notangles is a UNSW timetable planner, brought to you by DevSoc. It's an easy to use drag-and-drop tool | ||
| that allows you to plan your course classes and add to your calendar, even before term class registration | ||
| opens! We have many features including support for custom events, auto-timetabling, creation of multiple | ||
| timetables and sharing events with friends. | ||
|
|
@@ -58,7 +58,7 @@ const Footer: React.FC = () => { | |
| reliability. | ||
| </div> | ||
| <div> | ||
| Made by >_ CSESoc UNSW • | ||
| Made by Software Development Society (DevSoc) • | ||
| <Link target="_blank" href="mailto:[email protected]"> | ||
| </Link> | ||
|
|
@@ -67,7 +67,7 @@ const Footer: React.FC = () => { | |
| Feedback | ||
| </Link> | ||
| • | ||
| <Link target="_blank" href="https://github.com/csesoc/notangles"> | ||
| <Link target="_blank" href="https://github.com/devsoc-unsw/notangles"> | ||
| Source | ||
| </Link> | ||
| </div> | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| # Onboarding | ||
|
|
||
| Welcome to CSESoc Projects and the Notangles team! This page will come in handy when you’re running Notangles locally, and working on your own features. | ||
| Welcome to DevSoc and the Notangles team! This page will come in handy when you’re running Notangles locally, and working on your own features. | ||
|
|
||
| ## Your setup | ||
|
|
||
|
|
@@ -37,14 +37,13 @@ Before you start, make sure that you have the following software installed. | |
| - [Docker](https://www.docker.com/) (only needed if you are working on the back-end) | ||
| - [Instructions if you’re using WSL on Windows](https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-containers) | ||
|
|
||
|
|
||
| ## Getting the source code | ||
|
|
||
| We manage our source code with a version control system called [Git](https://git-scm.com/). Every time we *commit* new code, it gets added to a history of commits, so we can get old code back if needed. This code is then hosted on [GitHub](https://github.com/csesoc/notangles), so any code you *push* is backed up, and can be *pulled* by other team members. Git has other features like branches, which allow us to work on different versions of the same codebase at the same time, and merge them together later. | ||
| We manage our source code with a version control system called [Git](https://git-scm.com/). Every time we _commit_ new code, it gets added to a history of commits, so we can get old code back if needed. This code is then hosted on [GitHub](https://github.com/devsoc-unsw/notangles), so any code you _push_ is backed up, and can be _pulled_ by other team members. Git has other features like branches, which allow us to work on different versions of the same codebase at the same time, and merge them together later. | ||
|
|
||
| First of all, make sure that you have been added to the [Notangles repository](https://github.com/csesoc/notangles) on GitHub. While anyone can read our open-source codebase, you’ll need permissions to push changes. | ||
| First of all, make sure that you have been added to the [Notangles repository](https://github.com/devsoc-unsw/notangles) on GitHub. While anyone can read our open-source codebase, you’ll need permissions to push changes. | ||
|
|
||
| Once you’re in, summon a terminal and clone the repository by running `git clone [email protected]:csesoc/notangles.git`. (You can also use GitHub Desktop.) After that, navigate into the newly-cloned repository by running `cd notangles`. | ||
| Once you’re in, summon a terminal and clone the repository by running `git clone [email protected]:devsoc-unsw/notangles.git`. (You can also use GitHub Desktop.) After that, navigate into the newly-cloned repository by running `cd notangles`. | ||
|
|
||
| Then, run `cd client && npm install && cd ../server && npm install && cd ../scraper && npm install && cd ..`, which installs all the dependencies that the project needs. | ||
|
|
||
|
|
@@ -89,6 +88,6 @@ Then, push the branch to the Notangles repository by running `git push -u origin | |
|
|
||
| When you’re done with the issue, [create a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) on GitHub, then assign as reviewers the team lead, and members with experience in the area. | ||
|
|
||
| When your pull request has been approved and merged into the *dev* branch, you can archive the card on Trello. All archived cards can be referenced from “archived items”, under “more” in the Trello menu. | ||
| When your pull request has been approved and merged into the _dev_ branch, you can archive the card on Trello. All archived cards can be referenced from “archived items”, under “more” in the Trello menu. | ||
|
|
||
| As a side note, **make sure to always pull from *dev*** before you do any work! This is so you can get the latest code to work on, with all the new changes from other team members. | ||
| As a side note, **make sure to always pull from _dev_** before you do any work! This is so you can get the latest code to work on, with all the new changes from other team members. | ||