You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: client/index.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@
14
14
/>
15
15
<meta
16
16
name="description"
17
-
content="An interactive drag-and-drop timetable planner to help UNSW students plan and organise their course classes every trimester. Created by CSESoc Dev, we have many features including support for your own custom events, auto-timetabling, creation of multiple timetables and sharing events with friends. Organise your studies, find ideal class times with friends and take control of your academic life. Start planning now!"
17
+
content="An interactive drag-and-drop timetable planner to help UNSW students plan and organise their course classes every trimester. Created by DevSoc, we have many features including support for your own custom events, auto-timetabling, creation of multiple timetables and sharing events with friends. Organise your studies, find ideal class times with friends and take control of your academic life. Start planning now!"
18
18
/>
19
19
<meta
20
20
name="keywords"
21
-
content="notangles, crossangles, bojangles, UNSW, timetable, timetabler, planner, plan, calendar, trimester, trimesters, semester, term, social timetabling, schedule, csesoc, myUNSW, student, academic, organise, organize, courses, classes, auto-timetabler, University of New South Wales, tool, study, app, manage, personalise, customise"
21
+
content="notangles, crossangles, bojangles, UNSW, timetable, timetabler, planner, plan, calendar, trimester, trimesters, semester, term, social timetabling, schedule, csesoc, devsoc, myUNSW, student, academic, organise, organize, courses, classes, auto-timetabler, University of New South Wales, tool, study, app, manage, personalise, customise"
Copy file name to clipboardExpand all lines: onboarding.md
+6-7Lines changed: 6 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Onboarding
2
2
3
-
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.
3
+
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.
4
4
5
5
## Your setup
6
6
@@ -37,14 +37,13 @@ Before you start, make sure that you have the following software installed.
37
37
-[Docker](https://www.docker.com/) (only needed if you are working on the back-end)
38
38
-[Instructions if you’re using WSL on Windows](https://docs.microsoft.com/en-us/windows/wsl/tutorials/wsl-containers)
39
39
40
-
41
40
## Getting the source code
42
41
43
-
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.
42
+
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.
44
43
45
-
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.
44
+
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.
46
45
47
-
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`.
46
+
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`.
48
47
49
48
Then, run `cd client && npm install && cd ../server && npm install && cd ../scraper && npm install && cd ..`, which installs all the dependencies that the project needs.
50
49
@@ -89,6 +88,6 @@ Then, push the branch to the Notangles repository by running `git push -u origin
89
88
90
89
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.
91
90
92
-
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.
91
+
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.
93
92
94
-
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.
93
+
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.
0 commit comments