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: Google-Summer-of-Code-2023.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ A: Oppia Android won't be able to participate in GSoC this year. Note that this
75
75
76
76
**Q: What technical skills do I need to work on Oppia?**
77
77
78
-
A: For Oppia Web, Angular 2+, Python 3.9 and Google App Engine are useful and recommended for most Oppia work; in addition, UI design skills are useful for frontend, user-facing work. Please see the individual project ideas to determine whether these skills are recommended for the project in question. Note that, although GSoC is aimed at beginner contributors to open source and at students, "beginner to open source" is not the same as "beginner to coding" -- the projects assume some proficiency with coding. This [[page of learning resources|Learning-Resources]] might be helpful for learning the technologies needed to contribute to Oppia.
78
+
A: For Oppia Web, Angular 2+, Python 3.10 and Google App Engine are useful and recommended for most Oppia work; in addition, UI design skills are useful for frontend, user-facing work. Please see the individual project ideas to determine whether these skills are recommended for the project in question. Note that, although GSoC is aimed at beginner contributors to open source and at students, "beginner to open source" is not the same as "beginner to coding" -- the projects assume some proficiency with coding. This [[page of learning resources|Learning-Resources]] might be helpful for learning the technologies needed to contribute to Oppia.
79
79
80
80
**Q: How can I increase my chances of getting selected?**
Copy file name to clipboardExpand all lines: Google-Summer-of-Code-2024.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Welcome! If you're interested in applying to work with Oppia for GSoC, please fo
75
75
76
76
**Q: What technical skills do I need to work on Oppia?**
77
77
78
-
A: For Oppia Web, Angular 2+, Python 3.9, Google App Engine and Apache Beam are useful and recommended for most Oppia work; in addition, UI design skills are helpful for frontend user-facing work, and experience with Docker and GitHub Actions is useful for developer workflow projects. Also, it is important to be able to write tests for the code you submit (using Karma, Webdriverio and unittest). Please see the individual project ideas to determine which skills are recommended for the project in question. Note that, although GSoC is aimed at beginner contributors to open source and at students, "beginner to open source" is **not** the same as "beginner to coding" -- the projects assume that you have proficiency with coding. For Oppia Web, you might find this [[page of learning resources|Learning-Resources]] helpful, as well as other pages on our [wiki](https://github.com/oppia/oppia/wiki) that provide guidance on Apache Beam, testing frameworks, etc.
78
+
A: For Oppia Web, Angular 2+, Python 3.10, Google App Engine and Apache Beam are useful and recommended for most Oppia work; in addition, UI design skills are helpful for frontend user-facing work, and experience with Docker and GitHub Actions is useful for developer workflow projects. Also, it is important to be able to write tests for the code you submit (using Karma, Webdriverio and unittest). Please see the individual project ideas to determine which skills are recommended for the project in question. Note that, although GSoC is aimed at beginner contributors to open source and at students, "beginner to open source" is **not** the same as "beginner to coding" -- the projects assume that you have proficiency with coding. For Oppia Web, you might find this [[page of learning resources|Learning-Resources]] helpful, as well as other pages on our [wiki](https://github.com/oppia/oppia/wiki) that provide guidance on Apache Beam, testing frameworks, etc.
79
79
80
80
**Q: How can I increase my chances of getting selected?**
Copy file name to clipboardExpand all lines: Google-Summer-of-Code-2025.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Good luck!
81
81
82
82
A: Please see the individual project ideas to determine which skills are recommended for the project in question. Also, in general:
83
83
84
-
- For Oppia Web, Angular 2+, Python 3.9, Google App Engine and Apache Beam are useful and recommended, and experience with Docker and GitHub Actions is useful for developer workflow projects. Also, it is important to be able to write tests for the code you submit (using Karma, Webdriverio and unittest). You might also find this [[page of learning resources|Learning-Resources]] helpful, as well as other pages on our [wiki](https://github.com/oppia/oppia/wiki) that provide guidance on Apache Beam, testing frameworks, etc.
84
+
- For Oppia Web, Angular 2+, Python 3.10, Google App Engine and Apache Beam are useful and recommended, and experience with Docker and GitHub Actions is useful for developer workflow projects. Also, it is important to be able to write tests for the code you submit (using Karma, Webdriverio and unittest). You might also find this [[page of learning resources|Learning-Resources]] helpful, as well as other pages on our [wiki](https://github.com/oppia/oppia/wiki) that provide guidance on Apache Beam, testing frameworks, etc.
85
85
86
86
- For Oppia Android, you will need to know how to program in Kotlin, and have experience with Android development. Knowledge of Bazel may also be helpful for some projects.
Copy file name to clipboardExpand all lines: Installing-Oppia-(Linux;-Python-3).md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,12 +137,12 @@ For your virtual environment, we recommend you use [pyenv](https://github.com/py
137
137
```bash
138
138
exec"$SHELL"
139
139
```
140
-
4. Now you can install Python 3.9.20 and the associated pip like this:
140
+
4. Now you can install Python 3.10.16 and the associated pip like this:
141
141
142
142
```console
143
-
$ pyenv install 3.9.20
144
-
installing python-3.9.20...
145
-
installed python-3.9.20 to /home/user/.pyenv/versions/3.9.20
143
+
$ pyenv install 3.10.16
144
+
installing python-3.10.16...
145
+
installed python-3.10.16 to /home/user/.pyenv/versions/3.10.16
146
146
```
147
147
148
148
5. Install direnv
@@ -151,7 +151,7 @@ exec "$SHELL"
151
151
sudo apt install direnv
152
152
```
153
153
154
-
6. Setup direnv into your shell.
154
+
6. Setup direnv into your shell.
155
155
If you are using bash:
156
156
157
157
```bash
@@ -161,7 +161,7 @@ exec "$SHELL"
161
161
162
162
```bash
163
163
eval"$(direnv hook zsh)">>~/.zshrc
164
-
```
164
+
```
165
165
> [!WARNING]
166
166
> Be careful with using graphical editors like Notepad in Windows. These can add carriage returns (`\r`) that confuse our Linux-based development tools. Instead, we recommend using editors designed for programming or command-line text editors.
167
167
@@ -186,7 +186,7 @@ exec "$SHELL"
186
186
with this content:
187
187
188
188
```console
189
-
use python 3.9.20
189
+
use python 3.10.16
190
190
```
191
191
192
192
Then run this command in the same folder:
@@ -406,21 +406,21 @@ On Arch Linux, you should follow these instructions to set up your virtual envir
406
406
407
407
3. Reload your shell or open a new terminal window to load your updated `.bashrc`, `.zshrc`, or `config.fish`
408
408
409
-
4. Now you can install Python 3.9.20 and the associated pip like this:
409
+
4. Now you can install Python 3.10.16 and the associated pip like this:
Installed Python-3.9.20 to /Users/user/.pyenv/versions/3.9.20
197
+
Installed Python-3.10.16 to /Users/user/.pyenv/versions/3.10.16
198
198
```
199
199
200
200
4. Make Python 3 available globally on your system:
201
201
202
202
```console
203
-
pyenv global 3.9.20
203
+
pyenv global 3.10.16
204
204
```
205
205
206
-
Note that you can use a different version of Python 3 if you prefer--we'll specify Python 3.9.20 as our version for Oppia development later.
206
+
Note that you can use a different version of Python 3 if you prefer--we'll specify Python 3.10.16 as our version for Oppia development later.
207
207
208
208
5. Create a virtual environment for oppia by making a file `.envrc` in the `opensource/` directory with the following contents:
209
209
210
210
```text
211
-
use python 3.9.20
211
+
use python 3.10.16
212
212
```
213
213
214
214
Then run `direnv allow` in the `opensource/` directory to allow `direnv` to run there. Whenever you are within the `opensource/` directory (or any of its subdirectories, or any of their subdirectories, etc.) the virtual environment will be active. You can confirm this by running:
215
215
216
216
```console
217
217
$ which python
218
-
.../opensource/.direnv/python-3.9.20/bin/python
218
+
.../opensource/.direnv/python-3.10.16/bin/python
219
219
```
220
220
221
221
## Running Oppia on a development server
@@ -297,9 +297,9 @@ For your vitual environment, we recommend you use [pyenv](https://github.com/pye
297
297
298
298
299
299
Traceback (most recent call last):
300
-
File "/Users/user/.pyenv/versions/3.9.20/lib/python3.8/runpy.py", line 174, in _run_module_as_main
300
+
File "/Users/user/.pyenv/versions/3.10.16/lib/python3.10/runpy.py", line 174, in _run_module_as_main
301
301
"__main__", fname, loader, pkg_name)
302
-
File "/Users/user/.pyenv/versions/3.9.20/lib/python3.8/runpy.py", line 72, in _run_code
302
+
File "/Users/user/.pyenv/versions/3.10.16/lib/python3.10/runpy.py", line 72, in _run_code
303
303
exec code in run_globals
304
304
File "/opensource/oppia/scripts/start.py", line 205, in <module>
0 commit comments