Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

Weekly Report

In T386128#10812158, @Carita_Ndibe wrote:

Congratulations @Nayohmeee
All the Best.

In T386128#10811904, @Ezinneanne wrote:

In T386128#10809414, @Nayohmeee wrote:

In T386128#10809276, @Gopavasanth wrote:

Congratulations @Nayohmeee on being selected for Outreachy! 🎉
Wishing you a great journey ahead—happy coding and best of luck with the program!

As you move through the community bonding period, feel free to refine your project timeline and finalize the steps leading up to the coding phase. If you have any questions, don’t hesitate to reach out—whether on Zulip, via email, or directly on this ticket.

Thanks you so much! I'm really glad to be here and have an opportunity to contribute. I'll revisit the project timeline and ask for clarification as the need arises😊

Congratulations @Nayohmeee well deserved. All the best in your outreachy journey

In T386128#10809740, @Lebogang wrote:

In T386128#10809414, @Nayohmeee wrote:

In T386128#10809276, @Gopavasanth wrote:

Congratulations @Nayohmeee on being selected for Outreachy! 🎉
Wishing you a great journey ahead—happy coding and best of luck with the program!

As you move through the community bonding period, feel free to refine your project timeline and finalize the steps leading up to the coding phase. If you have any questions, don’t hesitate to reach out—whether on Zulip, via email, or directly on this ticket.

Thanks you so much! I'm really glad to be here and have an opportunity to contribute. I'll revisit the project timeline and ask for clarification as the need arises😊

Congratulations @Nayohmeee on your selection! It was a pleasure contributing alongside you. All the best as you begin this exciting journey 🌟

In T386128#10809276, @Gopavasanth wrote:

Congratulations @Nayohmeee on being selected for Outreachy! 🎉
Wishing you a great journey ahead—happy coding and best of luck with the program!

As you move through the community bonding period, feel free to refine your project timeline and finalize the steps leading up to the coding phase. If you have any questions, don’t hesitate to reach out—whether on Zulip, via email, or directly on this ticket.

Hello, the instructions on the Outreachy final application page says "Please work with your mentor to provide a timeline of the work you plan to accomplish on the project and what tasks you will finish at each step". Is there a specific work outline the Wikipedia organization would like us interns to work with and edit into the timeline we are to submit? Or are we expected to be creative and write up our own estimated timeline according to our understanding of the project?
I am asking so I'd know how best to proceed and also so I don't waste valuable time working on the wrong thing.
i'd appreciate some clarity on this please

In T386128#10684896, @Bimbo wrote:

Hallo @Ederporto!

I'm Bola, am new here.
I just completed T389647: Addressing the new Lusophone technological wishlist proposals - Task 1 and already sent it to your mail but just discovered you've pinged some persons to the task. Want to know if i should move on to task 2.

In T386128#10663315, @Ederporto wrote:

Hello, everyone!
Sorry for the huge delay!

At the Tasks section of this proposal, you are able to find the two subtasks you need to follow in order to be evaluated.
Please, do not share your tasks answers with other participants, but you are encouraged to help each other if you want!

Pinging: @Nishachandila, @Umekibe, @Jacob-Ojumu, @Nayohmeee, @Preciousdesk10, @Ezinneanne, @Lebogang, @Snowy04, @Carita_Ndibe, @Addobentil, @GloryEdem and @Gutopro911

Hello, I am Naomi an Outreachy contributor for the June 2025 season. After writing up a development plan, how are we expected to submit it please?

In T376127#10232368, @Victoriamusasizi wrote:

In T376127#10223720, @Nayohmeee wrote:

In T376127#10220455, @Mankav wrote:

In T376127#10220285, @Nayohmeee wrote:

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hello @Nayohmeee, could you please provide a screenshot of the error you are encountering? This will help me understand the issue better.

Additionally, did you run the command sudo chmod 777 src/? This command ensures that the src directory has the necessary permissions for reading, writing, and executing.

Hi thanks for replying, there is no error message. The src file is not copied on to the src folder on docker , yes it exists but there is nothing inside the folder. I wonder if i should manually copy the files myself , and yes I have tried the sudo chmod command severally too

what is your output of this:

ls -la $(pwd)/src

on my local machine all the src/ files/folders have rwx permissions, but on docker/wsl2 they dont have those permissions

Note that using chmod is good, but you need to ensure both the Docker daemon and the running container have access to the folder

try:

sudo chmod -R 755 $(pwd)/src
sudo chown -R $USER:$USER $(pwd)/src

I have tried this and other commands and still i get the permission denied error

In T376127#10224541, @Okay-michael wrote:

In T376127#10224381, @Nayohmeee wrote:

In T376127#10220470, @Okay-michael wrote:

In T376127#10220285, @Nayohmeee wrote:

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hi Nayohmeee, sorry about the issue you're having getting things to work fine. I suspect the problem is with the way you're managing your development environment, so I'm going to recommend you install Windows Subsystem for Linux 2 (WSL2) and run Docker using it as the backend if you’re running on Windows 10 and above. This way you may not need to manually copy any file or directory into the docker/shell environment as docker directly uses it for it's backend. WSL2 provides a more Linux-like environment with better performance and compatibility, making it ideal for developing with tools like make.
Here's how to get started,

• Install WSL2 from Microsoft store.
• Configure Docker to use WSL2 by following the instructions on this link https://docs.docker.com/desktop/install/windows-install/
• Clone the remote repo once again into a directory on your WSL2, it comes with make pre-installed.
• cd into the cloned local repo, create a virtual environment using "python3 -m venv env" and activate the virtual environment using "source env/bin/activate"
• run "pip install -r requirements.py" to install all the dependencies in the virtual environments.
• Now follow along with the instructions provided above on the task description and remember to "run sudo chmod 777 src/" If you're having troubles with file/folder/database permissions

Using this setup has a streamlined workflow and access to a wide range of Linux tools and utilities like make. You can try this and don’t forget hit me back if you’re having difficulty getting this setup running, I'll be glad to assist.

so far i have been able to work with wsl but granting permissions on windows for the src/ does not seem to apply on the docker environment, I have tried granting permissions but somehow it refuses to reflect on docker. Has anyone had this isue

If you have been able to install WSL2 successfully and connected docker to use it for backend then all you need to do is issue the change permission command directly on WSL2 terminal. Just cd into the project directory and run sudo chmod 777 src/ inside the WS2 terminal . As long as you have docker desktop running, issue the command make run will start the app assuming you followed all the instructions provided in the project description religiously. You can do all these right inside WSL2 but you must remember to have Docker desktop running. If you're still not getting it then we can consider scheduling a video call on Zulip.

In T376127#10220470, @Okay-michael wrote:

In T376127#10220285, @Nayohmeee wrote:

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hi Nayohmeee, sorry about the issue you're having getting things to work fine. I suspect the problem is with the way you're managing your development environment, so I'm going to recommend you install Windows Subsystem for Linux 2 (WSL2) and run Docker using it as the backend if you’re running on Windows 10 and above. This way you may not need to manually copy any file or directory into the docker/shell environment as docker directly uses it for it's backend. WSL2 provides a more Linux-like environment with better performance and compatibility, making it ideal for developing with tools like make.
Here's how to get started,

• Install WSL2 from Microsoft store.
• Configure Docker to use WSL2 by following the instructions on this link https://docs.docker.com/desktop/install/windows-install/
• Clone the remote repo once again into a directory on your WSL2, it comes with make pre-installed.
• cd into the cloned local repo, create a virtual environment using "python3 -m venv env" and activate the virtual environment using "source env/bin/activate"
• run "pip install -r requirements.py" to install all the dependencies in the virtual environments.
• Now follow along with the instructions provided above on the task description and remember to "run sudo chmod 777 src/" If you're having troubles with file/folder/database permissions

Using this setup has a streamlined workflow and access to a wide range of Linux tools and utilities like make. You can try this and don’t forget hit me back if you’re having difficulty getting this setup running, I'll be glad to assist.

In T376127#10220470, @Okay-michael wrote:

In T376127#10220285, @Nayohmeee wrote:

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hi Nayohmeee, sorry about the issue you're having getting things to work fine. I suspect the problem is with the way you're managing your development environment, so I'm going to recommend you install Windows Subsystem for Linux 2 (WSL2) and run Docker using it as the backend if you’re running on Windows 10 and above. This way you may not need to manually copy any file or directory into the docker/shell environment as docker directly uses it for it's backend. WSL2 provides a more Linux-like environment with better performance and compatibility, making it ideal for developing with tools like make.
Here's how to get started,

• Install WSL2 from Microsoft store.
• Configure Docker to use WSL2 by following the instructions on this link https://docs.docker.com/desktop/install/windows-install/
• Clone the remote repo once again into a directory on your WSL2, it comes with make pre-installed.
• cd into the cloned local repo, create a virtual environment using "python3 -m venv env" and activate the virtual environment using "source env/bin/activate"
• run "pip install -r requirements.py" to install all the dependencies in the virtual environments.
• Now follow along with the instructions provided above on the task description and remember to "run sudo chmod 777 src/" If you're having troubles with file/folder/database permissions

Using this setup has a streamlined workflow and access to a wide range of Linux tools and utilities like make. You can try this and don’t forget hit me back if you’re having difficulty getting this setup running, I'll be glad to assist.

In T376127#10220455, @Mankav wrote:

In T376127#10220285, @Nayohmeee wrote:

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hello @Nayohmeee, could you please provide a screenshot of the error you are encountering? This will help me understand the issue better.

Additionally, did you run the command sudo chmod 777 src/? This command ensures that the src directory has the necessary permissions for reading, writing, and executing.

PLEASE HELP, I am stuck at bullet point 8 because my src file refuses to be copied into my docker/shell environment. Both cmd.sh and requirements.txt are copied but not src and I have tried everything I know, including tweaking the dockerfile to enable the file to be copied, does anyone know how i can fix this please?

Hello, Naomi here, I am an Outreachy applicant and I am keenly interested to intern at Wikimedia. I am a software engineer with specialization in backend web development using Python (Flask and Django) and i have experience working with both Git and GitHub.