Page MenuHomePhabricator

CampWiz Nxt Redesign: Root Path
Closed, ResolvedPublic

Description

Environment Setup:
Follow this to setup your environment.

Instructions

  • Create a new branch in Target Repository for each of the migration with the following naming convention: <your username>_<component/page name with space replaced with hyphen>.
  • The codebase must be working without any breaking changes after your edit.
  • Each branch must have gone through Pull Request before being merged into our production build.
  • Folder structure would be
    • For Pages: pages/<entity>/<Entity><Action>.tsx
    • For shared components: components/<group>/<component Name>.tsx. Here, <group> is optional
  • Please do not use AI. You have to write your own commit message properly with all the relevant changes. In the past we experimented with AI and it was messy.

Micro Tasks
Migrate the following pages/components into target place(s): (For example, app/user/login/page.tsx to src/pages/user/Login/index.tsx)

  • app/components/campaign/CampaignEditForm.tsx to src/pages/campaign/CampaignEdit.tsx

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@Tiven2240 @Nokib_Sarkar
Hi, I am Harshal. I was curious about contributing in this but I was having the same doubt as @Sam978. Could you please clarify on it like which files more we have to change. From what i can see is that mostly we have to migrate almost all the files as now we are doing revamp of the CampWiz NxT.
Thank you so much for your help and time.

@Nokib_Sarkar
Hi, I'm Pavan YDG and I'm interested in contributing to this project idea. I've gone through the project and have gotten a nice understanding of it. Can I proceed with the micro task.

Thank you.

@Nokib_Sarkar Fews day try run this project but stuck this number got error

stuck.PNG (870×254 px, 13 KB)

Please paste text (such as full error messages) as plain text. Text in screenshots cannot be searched for and cannot be copied. Thanks.

i just follow the step-up process in repo description:-

yarn install
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[######################################################################################] 1416/1417

got stuck this got error like :-

info There appears to be trouble with your network connection. Retrying...

but my nextwork connection i fine

now try to yarn cache clean

try reinstall

yarn install
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error Error: https://registry.yarnpkg.com/@mui/icons-material/-/icons-material-6.5.0.tgz: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (C:\Users\DELL\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:142037:19)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:919:9)
    at Object.onceWrapper (node:events:633:28)
    at TLSSocket.emit (node:events:531:35)
    at Socket._onTimeout (node:net:604:8)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
info There appears to be trouble with your network connection. Retrying...
[###########---------------------------------------------------------------------------------------------------------------] 131/1417

@Nokib_Sarkar The backend is down i guess even i am getting 404 error while setting up the frontend locally

@Nokib_Sarkar @Tiven2240 Just to confirm in regards to the CampaignEditForm component, this module is supposed to be migrated into /pages and not /components? In other words, it's supposed to be a route-level component?

If it is supposed to become a route-level page it'll also need to manage its own state - right now I can see it accepts props such as dispatch, loading, etc..

Hi @Nokib_Sarkar and @Tiven2240 can you assign it to me i would like to work on it .Thanks

Hello @Nokib_Sarkar and @Tiven2240
I am trying to start working on T415408 (CampWiz NxT Redesign: Root Path).
However, I am unable to access the target repository campwiz-nxt-frontend2 — it shows 404 (project not found).
Could you please grant me access to the repository so I can begin the migration task?
Thank you.

Hi @Nokib_Sarkar and @Tiven2240,

I have completed the migration of CampaignEditForm as part of the microtask and opened a PR:

PR Link: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/4

The project builds successfully (npm run build) and no functional changes were introduced.

Please review and let me know if any modifications are required.

Thank you.

Hi @Nokib_Sarkar and @Tiven2240 . I've tried to run the next.js project, but it returns Error : HTTP error! status: 403, message: in the home and login page and "i18next::translator: missingKey en translation setting.translatewiki" in the console. Is this expected ?

also, the CampaignEdit.tsx file has been migrated. So are there any other pages that need work which can be assigned as a MICROTASK ?

Hi there! I heard that the contribution period began a couple of days ago - I went ahead and submitted my first PR (https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/8) related to migrating the CampaignEditForm component.

@Nokib_Sarkar I also saw you created a detailed roadmap markdown of the migration plan - I'll be adjusting my proposal based off of that. Much thanks for including that in the repo

Hi all

I'm Remy, a freshman at the American University of Beirut, I really want to contribute to this project and participate to GSoC 2026. I have been going through the code, the migration tasks, and the discussion threads to understand the code and the project.

For all of you who want to see the backend data when running the frontend locally, I have managed to find a small workaround from the source repository.

In the source repository, you have a .env.example file. You can copy the three uncommented lines and paste them into your new frontend repository cloned repo.

Alternatively, you could simply change the following line in your .env file:

VITE_BACKEND_API_PATH=http://localhost:5173/api/v2

to

VITE_BACKEND_API_PATH=https://campwiz-backend-dev.toolforge.org/api/v2

This would enable the frontend to work with the dev backend.

As @Nokib_Sarkar mentioned earlier, the backend isn’t actually necessary for the task. Even if you attempt to log in with your Wikimedia account, the flow would attempt to fetch a URL from the API and redirect you to the production version of the CampWiz app anyway.

The backend would mainly be useful for previewing some data (e.g., campaign lists) during development.

For the migration task, you don’t actually need the backend, and you can move along with the task without it.

Hello @Nokib_Sarkar @Tiven2240,

I’ve just submitted a pull request for the migration of the Submission section from Next.js to Vite/React:

Migrated pages: SubmissionListPage, EvaluationListPage, EvaluationPreviewPage and all associated components

Added routes for these pages and a types/ folder for shared types

I would appreciate your review of the pull request, and if everything looks good, for it to be merged into the codebase.

Hi, just wanted to update those of concern; I've been digging more into the codebase and made a bugfix + implemented the custom session context hook it looks like was planning to be added as a part of the migration.

Here's the PR: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/13

Feel free to provide your feedback on this.

Excited to continue learning and looking forward to the application period opening soon!

@Nokib_Sarkar and @Tiven2240
I just need to ask about something about this project
Next.js project need to be converted pure react.js to avoid dedicated Node.js server so, this website have feature ssg site right ?
but react use SPA how they react use SSG(static site generation)? think of using library (like vite-react-ssg ),using build file in vite depoly in hosting provider or using astro build framework ?

Hi @Nokib_Sarkar and @Tiven2240,

I had previously completed the CampaignEditForm microtask. Since I did not see any additional specific microtasks listed and noticed that several components still require migration, I proceeded with migrating the SingleCampaignChip component as a similar task.

I have opened a PR for this migration:
PR Link: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/18

Please let me know if any changes are required.

Hi @Nokib_Sarkar and @Tiven2240,

Following my previous migrations of CampaignEditForm and SingleCampaignChip, I have migrated another campaign component i.e LoadMoreCampaignChip to the React (Vite) SPA structure and opened a new PR.

PR Link: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/29

Please let me know if any changes or improvements are required. I’d be happy to update it.

Actually, we are getting a lot of pull requests from a lot of candidates, so we are not accepting/commenting on any pull request now. Most of them are AI generated pull requests which might not as constructive as a human. As a result, we decided to interview the candidates to ensure proper qualifications and skills. Please send an email to tools+gsoc26@wikilovesfolklore.org. please include whether you are a Wikimedian, first time GSoC contributor, full time professional and your outlook toward Open Source contribution besides your other relavant contributions. We might give you slots for interview if your email gives us enough merit. Remember to include [GSoC 2026] in your subject line.

@Nokib_Sarkar that means I need submit proposal in email?

Not exactly proposal, but a short bio and past open source contributions so that we can determine a short interview slot based on our availability. Do not forget to mention your availability too. Always remember, we want the email to be short, and not be AI generated at all.

Johannnes89 removed • WMFOfflce as the assignee of this task.
Johannnes89 added a subscriber: • WMFOfflce.
Johannnes89 removed a subscriber: • WMFOfflce.

@Nokib_Sarkar Tomorrow going open gsoc application
that interview going in march or april?
In email I need add microtask pr and open souce experience

Sorry, can you rephrase the question?

@Nokib_Sarkar
my question is GSOC open the proposal submit tomorrow 16 march to 31 march
if I emailed you right now that interview going in march or april?
In email I need add microtask pr and open souce experience right?

Johannnes89 removed • WMFOfffce as the assignee of this task.
Johannnes89 added a subscriber: • WMFOfffce.
Johannnes89 removed a subscriber: • WMFOfffce.

@Nokib_Sarkar
I am also try to participate in outreachy and tomorrow show project list of outreachy
that will ok ?
I participate both GSOC and outreachy?

The interview would be as soon as possible in March. Also, yes, you need experience with microtask.

@Nokib_Sarkar
I am also try to participate in outreachy and tomorrow show project list of outreachy
that will ok ?
I participate both GSOC and outreachy?

@Nokib_Sarkar
that will ok to participate both GSOC and outreachy?

As per my understanding, we would not restrict your participation in both GSoC and Outreachy if rules allow provided that you commit your assigned hours in this project (if selected).

Hi @Nokib_Sarkar,

I tried sending the email to tools+gsoc26@wikilovesfolklore.org as mentioned, but received a delivery failure message. Could you please confirm the correct email address to send my details for the interview?

Hi @arya55, we can confirm the email tools+gsoc26@wikilovesfolklore.org works correctly. Please try again.

@Nokib_Sarkar I try send email but
got error email:-

We're writing to let you know that the group you tried to contact (tools) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post:

  • You might have spelled or formatted the group name incorrectly.
  • The owner of the group may have removed this group.
  • You may need to join the group before receiving permission to post.
  • This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help Center at https://support.google.com/a/wikilovesfolklore.org/bin/topic.py?topic=25838.

Thanks,

wikilovesfolklore.org admins

  • Original message -----

X-Received: by 2002:a17:906:f58d:b0:b97:9fae:66a9 with SMTP id a640c23a62f3a-b979fae8009mr181347266b.46.1773577756660;

Sun, 15 Mar 2026 05:29:16 -0700 (PDT)

ARC-Seal: i=2; a=rsa-sha256; t=1773577756; cv=pass;

d=google.com; s=arc-20240605;
b=gFV4YHZk0AxZvWOYq4K0AQFk/MUIDKi0Akm9ErOvB5nFm+kajX1CFFfWYCLrf1S9jN
 rxz9OkLa71UHPhxBOJxX8LhU22FnZQeONrVO5DRHUc1sDyqSbWEaISDNAFROW9wvoXRM
 46cfPW6wjTL2QDK7tMmE4Uo9anGIOr+sKpyyMzfBrtrjPEYCT5SadRaXwuihnZojOugV
 OCFgagLPCH0DkL9TGWPrvwwkNAQI9hYStoUbBCmcGPQ1W1Xh/DCgWL1jm0iLsb8038dT
 xBAb/PMPIgN7kNT7MLombrLYgccL46cv09JSYVq9hvYM0EEWdrdYhpKZpQyTJRYezsZe
 0pjw==

ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;

h=to:subject:message-id:date:from:mime-version:dkim-signature;
bh=M5+NYJ+2kI2s96nMRff099Fo+Q8G1hhlaNIVxBV/RWM=;
fh=Sl9jQ1hs1G+F7W7wLYmuIJEJhbqrqXAHEQukptzzNTo=;
b=GzKI/TI9KSxTo5EN23HonPuiqVyrpdDAjE14SxpD+C087C6zqXeAySpLv1LQ1sK1NN
 cM086CPmNPEAX67ENaw+FHzgSyuIcxhIB+noHcQC1lap0yCavc0TEMhzs23jlfgK3yOH
 lgq1paJbGNcm6b+sE+763mwJYWTOW8RzaBAe2L8igUSAKZi6KfDcI+pOBQKWdzsOxzmv
 8rOYWRRXiO6Krt8ORiwuf05lpb42bGWUYS/cnSDecsDHtSs90kwL4RKGbpPNTu4tK1Vq
 PdXQfW282nyylSQrx1C8a+88BrrUowZy38F56PaWggffO8+uWJ8COlVjHO9ICe7xvzxI
 2Ogw==;
dara=google.com

ARC-Authentication-Results: i=2; mx.google.com;

dkim=pass header.i=@gmail.com header.s=20230601 header.b=XIINfFzP;
arc=pass (i=1);
spf=pass (google.com: domain of dipanshuvishwakarma616@gmail.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=dipanshuvishwakarma616@gmail.com;
dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
dara=neutral header.i=@wikilovesfolklore.org

Return-Path: <dipanshuvishwakarma616@gmail.com>
Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41])

by mx.google.com with SMTPS id a640c23a62f3a-b9742f53c37sor231066566b.25.2026.03.15.05.29.16
for <tools+gsoc26@wikilovesfolklore.org>
(Google Transport Security);
Sun, 15 Mar 2026 05:29:16 -0700 (PDT)

Received-SPF: pass (google.com: domain of dipanshuvishwakarma616@gmail.com designates 209.85.220.41 as permitted sender) client-ip=209.85.220.41;
Authentication-Results: mx.google.com;

dkim=pass header.i=@gmail.com header.s=20230601 header.b=XIINfFzP;
arc=pass (i=1);
spf=pass (google.com: domain of dipanshuvishwakarma616@gmail.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=dipanshuvishwakarma616@gmail.com;
dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
dara=neutral header.i=@wikilovesfolklore.org

ARC-Seal: i=1; a=rsa-sha256; t=1773577756; cv=none;

d=google.com; s=arc-20240605;
b=OOtvH3Z4/WERub80M33RvvHoU+onZRwKiPvNEW+MyqNIYvizFaOl46NsxljAwJttO0
 ATD3LkMyvM52dJq7/Yv/8FnzLJOKgWz5Yj03M3fjtS/ry6ob2ztYS+HFBkO5bKsKUOz3
 4lywfbf44nD7lbbDPOw+yeYiulgJnJTrARXFzjdw0RwQMvcRIr+wnqjpNfusPB+qIGqC
 mK0Sjt0XmSkZ6GqXtCViFpIPeB4Z6rwPWUmYH3AC8RGSxMsw4ijhp8qU3Ojj4i6Rone9
 TsCc0jCvnwcdvgLsK4L4S3A5wkXf+EMhX0VMUsW7LXekJcIqIINolTJ8YD8NkhMtiE0w
 7yfw==

ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;

h=to:subject:message-id:date:from:mime-version:dkim-signature;
bh=M5+NYJ+2kI2s96nMRff099Fo+Q8G1hhlaNIVxBV/RWM=;
fh=Sl9jQ1hs1G+F7W7wLYmuIJEJhbqrqXAHEQukptzzNTo=;
b=cCeIpuOdVbt3CRmY7heL60g0sfQv/Kh+JISUk8RZxIDVLukRHMnH5j2dU+1w9AWFHU
 ZnLTeFCiw3mG3RQC8DWAksYj30r6iruvUOWmYyvMz4/2Y6ELBMCRlaMYUdII9p/jnwB7
 hyvNw/v37NtiTAP2ZZnOP3STr7tARnkktzIccFtYni59AtNoEnA7vE0aRJtWs9vddZC0
 I3Z1LFvfbVT7BPgrJzvgJoS4+zgXcCy/2Zg7Fkk9x1KrFm3t5o3Hfd7azCzvAIE5oMdJ
 9KCv7S6ruZv9RzMDiXjt1EnOZgwHi6rlue1laj1rdCCB27XWJEJB5sGt6JauBtHDFAci
 ug7g==;
darn=wikilovesfolklore.org

ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

d=gmail.com; s=20230601; t=1773577756; x=1774182556; darn=wikilovesfolklore.org;
h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
 :date:message-id:reply-to;
bh=M5+NYJ+2kI2s96nMRff099Fo+Q8G1hhlaNIVxBV/RWM=;
b=XIINfFzPekX5j/AAX4ukVhlamqp9Ay0zVsMoHlCOz8c7uDmRYV+LzBGG5fbjwWrBar
 DZGpMyd9pv9jmGWw1h9cLWhrAq08wH94FHJjqA6IC80FrmuG9zzTzZSY+SLd855FfIDN
 lz3TwcU2T9F8pklzV+nxSRLEVJ3lNEkFt1h8yYtApejQJ4esqZeC6BgTWBA8R4TBhfmg
 w4/IMQjA/GfYySjXoJ2N5iZpoLwy2L1hyVmcpnqkinLXHcknKtsSemIwvjwwoX+r/mca
 ZOhxt+QrRMU8XSIQWX0LU/iMnV4dK+KQbKqdN74nz4yRNcNN1foMgYCY0s3/lcwKNeJ6
 gchw==

X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

d=1e100.net; s=20251104; t=1773577756; x=1774182556;
h=to:subject:message-id:date:from:mime-version:x-gm-gg
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=M5+NYJ+2kI2s96nMRff099Fo+Q8G1hhlaNIVxBV/RWM=;
b=L8vJekMY6qgN1aYr8/YfkN0RGB2i48nFx2Tm2D7Hiij7rRujQS8wXvjAdrtnZUR2fm
 G1Xs4czVkjvNFR/3I92vBGlgIXCdEr2B7rSaHX4L5Gi10+hSnw3eXsIGpFekLSRccb4I
 Y1ImomI8SV3Tk+v3bL8ZkuZptZvSt4Rv8StPLTX9Q9uPffoDOAOqqgzzbxbt3+ezexrY
 RN12lUhdlJ20JFWM2r0wStxTF/3J4NRNS9Yb148TG5IB9O4CDSWSuEgI7b8z9CcXlPWB
 EhjseELHmS9RZcnFGCbGc/8hiDYpA7mDmQJe3anpxMY51ofEvQwqbSoY4YZyb6EOj+wm
 QmdQ==

X-Gm-Message-State: AOJu0YxD6E8/sii4GU2y0rLZgFmo80Bm/5+pYukZroHLANZjNoF2RfH8

LPl2uHeM0fz7ZuyKs8jaBFfAY87GmhzSuDg14Nb72wpKml5a2cVLoUmt6XkTMFKJHxV9ynDRe0H
9Ky6eQ914rhDCfd86h/mAd6T8KS7hBMM9BJ7lqxA=

X-Gm-Gg: ATEYQzwaMzxCzAfEMOE+AlkEUnTe2yP24boeoRBd1pArJxthMsp8ZcKCEhTki2llPnM

XOziXZydRoJISkqKMNBhJg0GdB32BgYljQvYBOaDLdi/KPBI7RcyUeTIHhR5prfpFRNN8UWH8IT
Zm9979BLFbMLtmNlWG6m8BaJa7RrdAvBhKNXVfAKDSFGYAUG2SQLkNifyc2oYf6k9KrGiNt2sQf
2tn9SffbKR2ruOR4HAWr2bUYy3YVdetcl1oafdr47OkbljXePGGciIDyCnFCeoaywUi7LfxnPBD
1RoVKJU=

X-Received: by 2002:a17:907:cd01:b0:b93:8995:8f3a with SMTP id
a640c23a62f3a-b976500f8d5mr471925666b.3.1773577755684; Sun, 15 Mar 2026
05:29:15 -0700 (PDT)
MIME-Version: 1.0
From: Dipanshu Vishwakarma <dipanshuvishwakarma616@gmail.com>
Date: Sun, 15 Mar 2026 17:59:25 +0530
X-Gm-Features: AaiRm5369JKHzDEbvGmiK1W7fGlLV2TRCODCEPoU-vhcciHgNEf2e11dMwO3yl0
Message-ID: <CAHdxOGVc_7wnbs5LCqpAH7oki=J_n_zbPs+awD1CBzHB1w1cvA@mail.gmail.com>
Subject: =?UTF-8?Q?=5BGSoC_2026=5D_Candidate_Introduction_=E2=80=93_Dipanshu_Vish?=

=?UTF-8?Q?awakarma?=

To: tools+gsoc26@wikilovesfolklore.org
Content-Type: multipart/alternative; boundary="0000000000001bf2fc064d0f40a3"

Hi @Nokib_Sarkar,
I also received a delivery failure when trying to email tools+gsoc26@wikilovesfolklore.org. Could you please confirm if there’s an alternative way to send our interview details?

Can you please use support+gsoc26@wikilovesfolklore.org?

Thank you, @Nokib_Sarkar! I was able to send my details successfully

Thank you for the heads up - sent over my email! Looking forward to a potential opportunity to chat.

I've sent over an email to support+gsoc26@wikilovesfolklore.org, looking forward to further steps!

Hi @Nokib_Sarkar and @Tiven2240 I have completed the microtask of migrating the CampaignEditForm component to the new structure

PR Link : https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/31

The component was migrated to:
src/pages/campaign/CampaignEdit.tsx

I have also sent the requested email(support+gsoc26@wikilovesfolklore.org) with my short introduction and open source contributions for the interview process.

if any changes are required please let me know.
Thank you for your time and guidance.

Hi @Nokib_Sarkar , I’ve completed the CampaignEditForm and CampaignEdit migration.

  • Migrated component to React structure
  • Removed Next.js-specific code
  • Fixed TypeScript compatibility issues (enums, types, imports)
  • Verified app runs successfully locally

PR: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/36

Please let me know if any changes are required.

@Nokib_Sarkar I’d like to continue contributing. Could you suggest the next microtask I should work on?

Hi,

I have completed the Root Path microtask by converting the Next.js-based dashboard into a pure React implementation.

GitHub Repository:
https://github.com/mokshith1222/campwiz-react

Looking forward to your feedback.

Hi, I have started working on the CampWiz NxT Redesign microtask.

I have successfully migrated the CampaignEditForm component from Next.js to pure React.

Changes done:

  • Removed Next.js dependencies and ensured compatibility with Vite
  • Fixed Autocomplete null handling to maintain type safety
  • Replaced native div with MUI Box to correctly support the sx prop
  • Improved component structure and ensured proper UI behavior

PR link: https://github.com/atharv1345/campwiz-nxt-frontend2.git

Looking forward to your feedback. Thanks!

Hi, I have completed the CampaignEdit migration microtask.

The component has been successfully migrated and TypeScript issues resolved.

PR: https://github.com/Open-Knowledge-Impact-Foundation/campwiz-nxt-frontend2/pull/41

Looking forward to your feedback.

@Nokib_Sarkar
I have completed this microtask and submitted a PR. I would like to work on another microtask.

Hi @Nokib_Sarkar , I wanted to clarify...for candidates who haven’t received a response regarding an interview, does that mean they are no longer being considered for GSoC 2026? because i have sent mine 2 weeks ago but haven't received an email

"Hi! I am Yogesh U G, GSoC 2026 applicant for CampWiz NxT Redesign. I have set up the project locally, studied the codebase, and analysed all 15+ pages. The root path app/page.tsx uses async server component, fetchSession() and uTranslation() which will be replaced with useSession() hook and useTranslation() from react-i18next in pure React. Screenshots attached."

Screenshot (102).png (1,366×625 px, 495 KB)

Screenshot (101).png (1,366×626 px, 48 KB)

Nokib_Sarkar claimed this task.

Hi @Nokib_Sarkar,

My name is Mohammad Alawneh, and I am a Computer Science student from Palestine.

I am interested in contributing to the CampWiz NxT Redesign project for GSoC 2026.

I have created my Developer account and would like to start working on the microtask. However, I cannot access the target repository.

Could you please grant me access to the repository so I can begin working on the microtask?

Thank you!

Hi @MohammadAlawneh thank you for your interest, however GSoC 2026 is ending soon, so no new microtasks will be accepted for this project. You are welcome to check out the projects in progress if you are interested in contributing to GSoC next year.

Hi ,

Thank you very much for your kind reply and for taking the time to answer
my question.

I really appreciate the helpful resources you shared. I understand that the
GSoC 2026 application period has ended.

I will continue improving my skills and contributing to open source
projects, and I look forward to applying for GSoC next year.

Thank you again for your support. I hope to contribute to the Wikimedia
community soon.

Best regards,
Mohammad Maher

‫في الخميس، 6 أغسطس 2026 في 6:07 م تمت كتابة ما يلي بواسطة ‪LGoto‬‏ <‪
no-reply@phabricator.wikimedia.org‬‏>:‬

LGoto added a comment. View Task
https://phabricator.wikimedia.org/T415408

Hi @MohammadAlawneh https://phabricator.wikimedia.org/p/MohammadAlawneh/
thank you for your interest, however GSoC 2026 is ending soon, so no new
microtasks will be accepted for this project. You are welcome to check out
the projects in progress if you are interested in contributing to GSoC next
year.

*TASK DETAIL*
https://phabricator.wikimedia.org/T415408

*EMAIL PREFERENCES*
https://phabricator.wikimedia.org/settings/panel/emailpreferences/