Pictopy

[abstract bear]

would just add faq

[young jasper]

looks great!!

[wraith creek]

Looks good, dark mode button will look good in navbar ig, rest everything's look good

[abstract bear]

arey it was just for testing purpose i added there

would move it up on the navbaar

navbaar look cools right?

[abstract bear]

thanks buddy

[wraith creek]

Yeah

[abstract bear]

and yes listen

when did i said i'll be taking any cristicism

🤣

just taking is there anything more that u feel can be improved ? @wraith creek

[wraith creek]

It looks good to me, honestly not the right person to comment much on UI/UX

[crude prism]

@wraith creek You are now level 16! :confetti_ball:

[abstract bear]

i'll deploy it would send u a link

then just go through if u feel something

test out rigrously

[wraith creek]

Yeah sure I would love to check it out

[worldly pulsar]

@abstract bear ,
Looks amazing.

You have put a lot of work into it.

Random images movement component is the best thing, in the entire UI.

[abstract bear]

thanx bri

[abstract bear]

i just thought that thing conveyed the message for what pictopy is image sorting libraray

[young jasper]

Hey, is the facetagging system working? how do I test it out?

[worldly pulsar]

It's doing the job nicely.

[young jasper]

I see the code, but can't see the option to use it in the app

[worldly pulsar]

Its working.

Did you run the backend?

[young jasper]

I did, I'm just wondering how do I test it out

like what does it do

[marsh idol]

On frontend, the APIs are not used yet

the backend part of face tagging is running

[worldly pulsar]

Your current images automatically get tagged when you go to face tagging page.

[marsh idol]

there is no face tagging page

[young jasper]

I see

So I was working on this issue #237
I guess I just need to put the APIs to use in the frontend with some minor changes

[marsh idol]

I think there are some PRs for this already, I don't know which. Please see the list of PRs and check if someone hasn't already done it.

[young jasper]

hmm, let me see

[young jasper]

I couldn't find any, there are some PRs on AI Tagging but not on face tagging

[worldly pulsar]

So, you can start working on it.

[young jasper]

@worldly pulsar @abstract bear @marsh idol Made some progress on this, I just had to create one extra api to link already existing ones and add some ui components
although the accuracy is pretty low...

next is to add camera support

[glass seal]

Hey guys! Any update about setting up locally? Was the issue fixed?

[young jasper]

Finished it!!

The latest SR No. I could find in the open PRs is 11, so I am to go with with 12?

[crude prism]

@young jasper You are now level 7! :confetti_ball:

[young jasper]

opened the pr here #375

[abstract bear]

amazing buddy

i started it but could'nt complet it as got busy with some other projects and exam

as if we saw face weere already getting cluster when image are uploading

[livid pond]

Hi everyone, I’m new to the community and eager to contribute to PictoPy. I'm trying to set up the project locally on Windows 11 with Ubuntu WSL, but I'm encountering errors in the Tauri frontend.

[abstract bear]

What is the python version you have installed

?

[livid pond]

3.12.3

[abstract bear]

Sorry you are facing problem in frontend setup

I did saw that

Could you be specific at what process you are facing issue

[livid pond]

after running npm run tauri dev

[abstract bear]

Try running the frontend in powershell

[livid pond]

okay

[wraith creek]

Try adding your wsl user to render group maybe, also for the white screen in frontend/src/Config/Backend.ts remove process.ev or import.meta just keep localhost:8000 url their

[young jasper]

@marsh idol Are you still working on this #345 ?
If not I would like to take this on, as #358 would also be best done after #345 is resolved.

[marsh idol]

Yes, been busy with exams will soon open a PR (2 days approx)

[young jasper]

alr, then I will leave #345 to you and work on #358 after you are done with yours.

[abstract bear]

hy @marsh idol i am done with the landing page i still thinking shall i add those links on the buttons what do you thinkk (might reply a little low have exam today ) ?

[worldly pulsar]

You should add the links.

[livid pond]

Thank you. it worked but with powershell😅 . still having same issue with wsl

[round laurel]

Hey @marsh idol ! Since you're busy with exams, is there anything I can help with? I’d really love to contribute.

Like Is there any issue that’s currently inactive or not being worked on that I can take up?

It would be great if you could let me know about any high-priority issues that are still pending.

[abstract bear]

https://picto-py-landing-page.vercel.app/ @marsh idol @mystic sigil @worldly pulsar @wraith creek hy guyz i i am done with [age iff freee have alook

except download buttons everything you see is working

go ahead and try rigrously

and let me know if any bugs you guyz find out

[worldly pulsar]

Page looks great.

Now, we need to have domain name for it.

[wraith creek]

In FAQs app name mentioned is PictoCopy
PictoyPy above Faqs is left aligned and download buttons are not working
Also on it would be great if download button at top is somehow able to identify our operating system and give us the download file accordingly
Also dark light mode button not working for me when my default system theme is dark
Also in phone view their is no need of hamburger menu ig

Hope this feedback helps

[worldly pulsar]

@radiant mauve , Should we have domain name for this page?

[wraith creek]

Rest animations and UI looks very smooth and good

[abstract bear]

bro when you default theme is dark majority of the web site won't work fine

[abstract bear]

and to optimize it always advised to ham burger menu

[abstract bear]

......

woh download kay liye we have to like rahul

[wraith creek]

their already exists one website
https://aossie-org.github.io/PictoPy/backend/backend_python/directory-structure/

maybe we can integrate this page here and improve UI/UX of rest of the pages too?
This page may also need an update after the changes we've made

[abstract bear]

i am thinking to add scroll down when click on download button when click on download button to the download section ??

[wraith creek]

no they work, though its not a big issue see if you can fix it, otherwise not much problem

[abstract bear]

umm i asked mentor he said to like make a page so i did

[wraith creek]

yes but that hamburger does not contain anything, that's not for optimisation that's just a replacement of navbar on mobile devices which generally have few options , in our case i dont think we need it

[wraith creek]

ohh ok sorry i missed that

[abstract bear]

koi na buddy

[abstract bear]

yup make sense i'll remove it

[wraith creek]

yess you can provide different version below and add other option Other downloads (along with Download in hero section) which will scroll to that and the main download button can detect OS and serve us the file accordingly? How this sounds?

[abstract bear]

hmm intresting scrolling thinking to add this scroll to the download secctionn but how would it will detect like oss??

i don't know this

[wraith creek]

maybe with this const { userAgent, platform } = window.navigator;?
and check the OS with .includes from multiple platforms which can be possible for eg:
const windowsPlatforms = ['Win32', 'Win64', 'Windows', 'WinCE']; these are all the possible platforms for windows
windowsPlatforms.includes(platform) then OS in windows
Simarly we can check MacOs as well as linux

https://medium.com/weekly-webtips/how-to-create-os-specific-download-buttons-bfe0d73c3d24
Maybe this can help too

[abstract bear]

wait i 'll check it and get back to you

[wraith creek]

I've created a PR would love some feedback on it, it makes setup smooth, user just needs to just run npm run setup and it will setup the whole project, also I've not tested it on MacOS, I dont have access to apple devices if anyone can test it on macos and give me some feedback it would be great:
https://github.com/AOSSIE-Org/PictoPy/pull/378

[abstract bear]

haan bhai bakwass hai band kar de

[abstract bear]

tested on mac band kar de aab

[wraith creek]

?? Can you point any particular thing here which you think is wrong or not upto the mark?

[abstract bear]

arey yrr mazak kar raha hoon

look great to me

[wraith creek]

no if something's wrong seriously tell, it can help me improve this

[abstract bear]

i don't have access to mac so i can test it on mac

[odd hinge]

i can do it

[young jasper]

This does not factor which distribution the user is using

Sure it will work for apt based systems, but not in case if the user is using fedora, openSUSE or arch

[wraith creek]

Thanks, if you face any issue do tell

[round laurel]

truee

[wraith creek]

Yes I know, packages may differ for different distributions that's why in case of other distributions I'm showing a message to download equivalent packages

If you have any idea for this do tell

One way is to detect their distribution somehow and add commands for all distributions

Ig maybe we can add for fedora apart from ubuntu/debian based systems

Other distribution users like those who use arch honestly don't need this setup script

[young jasper]

Typically such projects don't provide install scripts,
Just list all the dependencies for the more popular repositories, say 4-5
People who use distributions outside of these would be able to translate what packages they need to install on their own anyways

[marsh idol]

I have opened a PR for Tauri version upgrade. Although there no changes to actual code. You can change the docs with the existing code only.

Only cargo and package.json files have changed

[young jasper]

sure

[wraith creek]

Yeah, docker experience is not smooth and can't be fixed ig, so their's no harm in having an install script ig

[abstract bear]

Proposal bhe kyu daal raha hai message he daal de mentor

Ko bas

[radiant mauve]

i have merged till SR8

waiting for checks on SR. 9

@wraith creek there was a minor conflict in yours, i fixed it and merged

@wraith creek the backend tests are failing
can you check once

[crude prism]

@radiant mauve You are now level 15! :confetti_ball:

[marsh idol]

Those are fixed in one of my prs, I changed one API so tests were to be changed

[crude prism]

@marsh idol You are now level 14! :confetti_ball:

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/pull/364

fixed those tests in this one

[wraith creek]

thank you!

[radiant mauve]

okay
let's hope then nothing breaks in between in the backend for then

[radiant mauve]

bro, there's issue with your SR10
can you check and resolve conflicts

[wraith creek]

yess resolving them

[radiant mauve]

anyone else, who''s working
do take a fresh pull, there have been 5-6 merges recently

[wraith creek]

I'm sorry my laptop freezed for some reason, I'm pushing it give me few minutes

[wraith creek]

fixed them

[radiant mauve]

merged

[wraith creek]

after recent merges I found one more issue backend seems to crash
ImportError: cannot import name 'extract_metadata' from 'app.database.images' (/run/media/rishab/New Volume/Open Source/PictoPy/backend/app/database/images.py)

I havent added any extract metadata so dont know about it, does anyone have any idea about this? I'll try to investigate it

[radiant mauve]

hey, I am skipping PR 11
there are conflicts in it, but the tradeoff is low

as it mostly includes of introduction of some new variables in the backend for analysis

[marsh idol]

can you mention the file?

[wraith creek]

images.py ig their is not defination of extract metadata present?

[marsh idol]

inside the routes folder or database folder?

[wraith creek]

database does not have extract metadata

[marsh idol]

the import is wrong in the file

extract metadata is present in utils

[radiant mauve]

@marsh idol i am finally on your PR(14)
can you resolve the conflicts

[marsh idol]

ok

[wraith creek]

yess

[wraith creek]

i think instead of creating a seperate PR for it you can change the import path in your current PR?

[marsh idol]

yes, fixing it in sr. no. 14

[radiant mauve]

do one thing
if you have some other PR's too
include all in the 14

[marsh idol]

ok, I have one more Pr (no. 15), will include it with this one.

[radiant mauve]

yeah, because high chances that conflict will propogate to all other PR's now

15th is the last in the series right?

[marsh idol]

yes

[wraith creek]

I have 3-4 more PRS havent added an SR no on them (will resolve conflicts and add SR nos they're quite old) one of them is to make setup easier having no conflicts maybe you can merge this by then:
https://github.com/AOSSIE-Org/PictoPy/pull/378/

[radiant mauve]

squash them into one
and label it 16th

[crude prism]

@radiant mauve You are now level 16! :confetti_ball:

[radiant mauve]

what a coincidence 🙂

[marsh idol]

lol 😂

[wraith creek]

yeah 😅

[wraith creek]

I'll squash them it may take some time those will have a lot conflicts combined as they're quite old by then you can merge the setup script it is not at all related to already exisiting files so it has no conflicts

[radiant mauve]

[NOTE] only for pictopy contributors in the server, apologies for the everyone ping

Hey @here
sorry, I have been off for a few weeks

So, in Pictopy there are lot of PR's that remain open

I merged few of them, but still there's a pile remaining, so what we are starting with is a merge series, currently starting with Sr. No. 17

I'll review only those PR's that have a Sr. No. mentioned in their title, we are adopting this method because of the scale, this project has reached to.

feel free to ping me for any queries

[radiant mauve]

yeah, I checked that out, didn't merge it
because Rahul was working
will do after his is merged

[marsh idol]

@wraith creek The precommit file is giving errors, I am not able to commit

[wraith creek]

what type of error?

[marsh idol]

line no. 6

[wraith creek]

I've added pre commit dependency in backend try isntalling pip install requirements again or just this specific package

[marsh idol]

ohh

[abstract bear]

@radiant mauve hi mentor i have made the pictopy landing page and added the links to download as well

please have a look and if u feel something is not kind of right i can work on it to improve

[marsh idol]

All done, now you only need to merge Sr. No. 14. It includes 15 as well

[abstract bear]

https://picto-py-landing-page.vercel.app/

[marsh idol]

Done

[radiant mauve]

great landing page bro ❤️

[dawn wedge]

NEGGER

THIS WACK

[dawn wedge]

@marsh wyvern

@marsh wyvern

@marsh wyvern

@marsh wyvern @marsh wyvern

@marsh wyvern

@marsh wyvern

@marsh wyvern

@marsh wyvern

[wraith creek]

@radiant mauve I've squashed 3 of my PRs in this:
https://github.com/AOSSIE-Org/PictoPy/pull/382

Their is one more PR left but I think it can be improved further so instead of opening seperate PRs for improvements I'll improve everything in that PR only so I've not added that for now

[deft talon]

hey @radiant mauve, I'm Tanush. I'm interested in contributing to the Pictopy project for GSoC 2025 and would appreciate any guidance on getting started.

[radiant mauve]

will review

[radiant mauve]

Hi, Tanush
ask your doubts, I am open for it

[wraith creek]

thank you!

[deft talon]

Hey @radiant mauve I’m skilled in JS/TS & MERN and want to contribute to Pictopy for GSoC 2025. How can I get started? Any beginner-friendly tasks or key areas to focus on?

[marsh idol]

The image compressor doesn't have a close button, you should do that too

[placid falcon]

Hey @radiant mauve I am a new contributor and have only solved one issue yet. I would like to work on more good issues. Can anyone please guide me on what more can i work on

[marsh idol]

That part is done by Dushyant in his PR

[wraith creek]

you search existing issues on which no one is working or try going through the codebase using the app and create issues anything you think needs improvement.

just checked someone already working on current good first issues

i think someone is working on it as you replied to someone above for that

[crude prism]

@wraith creek You are now level 17! :confetti_ball:

[wraith creek]

I wasn't working on it currently and its always good to have more and more classes to models, maybe you can work on this if you can't find any issues:
https://github.com/AOSSIE-Org/PictoPy/issues/246

no no, Vipul

its not a good first issue though I think

yeah

[placid falcon]

okay thankyouu so much

[calm meteor]

nice work @abstract bear

[round laurel]

Cool! Now got it. Now this theme is really matching with the name Pictopy

[calm meteor]

no problem bro

[round laurel]

When hovering over the cards, the icon changes according to the card's icon. That looks really good, man!

Would love to collaborate with you on the UI someday!

[radiant mauve]

Hey Guys, is there any MR to be reviewed?

Plz ping here

also, if someone wants their proposal to be reviewed, then DM me, then they can DM me their proposal draft

[wraith creek]

@mystic sigil after your merge I'm not able to generate thumbnails on my progressive branch for some reason, we are generating thumbnails automatically for added folders right?

[mystic sigil]

No we are genrating thumbnail in images/PictoPy.thumbnails

All in same folder

[wraith creek]

yup I saw that I meant we're not specifically calling any api from frontend now?

after merging changes Im getting this, is their anything I need to do to fix it?

[mystic sigil]

When you will nagivate to home page

1. it calls an API for generating thumbnails initially for the first time
2. for AI tagging during adding the folder for this api call (/images/add-folder) it creates an API call for generating thumbnails

[mystic sigil]

In the images/PictoPy.thumbnails is there any thumbnails ?

[wraith creek]

yeah I know about the 2nd, thanks for clarifying I'll look into this issue then

[wraith creek]

no

[mystic sigil]

Then may be some other issue , delete the db , and restart it may be find a solution because before final request I have tested it and also provide a demo video so it should work for me .

[wraith creek]

Ok then I'll further look into this, thanks!

[mystic sigil]

I just newly clone this repo , and updated rust after that facing this in previous version it was working fine

[crude prism]

@mystic sigil You are now level 9! :confetti_ball:

[mystic sigil]

@wraith creek I got the problem after resolving the conflicts during the final PR the PictoPy.thumbnails folder was empty that's way it was ignored

so please add 'PictoPy.thumbnails' folder in images folder

Everything will work fine

If still not work then do these and after that restart your frontend It will work

[worldly pulsar]

Really.
I must say.
It's so much better than initial UI.

[wraith creek]

yeah just noticed it, thanks but shouldn't backend create this folder automatically? I was assuming that

I'll put this logic in server start then in my latest PR if this folder doesnt exist then create it

yeah feels a lot smoother too compared to before

[mystic sigil]

Till now , manually .

[wraith creek]

yeah I've added the logic for that, now those folders will automataically get generated

[wraith creek]

I'm done with this MR, this is ready to be reviewed:
https://github.com/AOSSIE-Org/PictoPy/pull/369

But I think before me their is @mystic sigil's MR with SR No 18 in the queue so I'll wait for that to be reviewed.

[radiant mauve]

merged

great

[marsh idol]

I think you will be able to link AOSSIE's discord.

there is not an option to link to this discussion directly I guess

wait

it's there

https://discord.com/channels/1022871757289422898/1311271974630330388

Yes use this link: "https://discord.com/channels/1022871757289422898/1311271974630330388"

where is the website?

Also correct the typo "PictoCopy"

😅

yes I visited this link, the link is not there

for discord

oh, got it

The icon is a small

I didn't see it at first

Its' beside your name on the footer, I thought it was your discord id 😅

the download section could be centered

and you should change the icons, for mac, use apple's official logo, same for windows and for Linux, use debian's logo

nope, its not minimized

On my laptop's screen its fine but on my monitor's screen its not

In place of linux write Linux (.deb)

.deb package doesn't work on all types of linux

only on debian based distros

like ubuntu, linux mint

🫡

yes, Also, Aossie -> AOSSIE

[marsh idol]

@abstract bear the light mode and dark mode switch is not working

on the site

yess

Is this on the local machine or the hosted site?

[crude prism]

@marsh idol You are now level 15! :confetti_ball:

[marsh idol]

on hosted its not working

I tried different browser too

🤔

I tried firefox, edge and chrome, doesn't work 😦

on my phone is working

*it's

no wait

it doesn't work on the phone too

I checked again

You try on a different browser

maybe you will get the issue too

Looks nice

Also Linux -> Linux (.deb)

yes

PictoCopy corrected right?

👍

[worldly pulsar]

It was fun building this page.

[mystic sigil]

@radiant mauve I have completed my work on this MR:
https://github.com/AOSSIE-Org/PictoPy/pull/368

please review it

Thanks @abstract bear

Yes , it is looking Awesome

[hallow saffron]

Did the backend changed a lot? All my PRs that i made 3 weeks ago related to backend, all of them are failing the tests

[marsh idol]

Yes there were 2-3 major PRs

Can you tell which functions are failing the tests

?

[hallow saffron]

This is the PR https://github.com/AOSSIE-Org/PictoPy/pull/354/

---

Another one is this https://github.com/AOSSIE-Org/PictoPy/pull/353/

[viral cobalt]

anyone facing this error ?,

[wraith creek]

Have you pulled the latest changes? If not then pull and retry running backend server

Alternatively in backend folder you can create images folder and inside images PictoPy.thumbnails folder, I think you should be good to go then

[viral cobalt]

Okk, thanks for help @wraith creek

[hallow saffron]

I previously made this PR but the codebase was modified and this PR was failing all the tests. I updated it now.
https://github.com/AOSSIE-Org/PictoPy/pull/354

These are the performance stats:

[hallow saffron]

in my local system when i do pytest, 19 tests are passing.

[crude prism]

@hallow saffron You are now level 5! :confetti_ball:

[hallow saffron]

but in my PR it shows that it is failing

[hallow saffron]

can anyone help me with this please?

[wraith creek]

yeah sure, I'm a bit busy now but will definetely look into this by tomorrow and try to resolve it!

[wraith creek]

https://github.com/AOSSIE-Org/PictoPy/pull/353

For this PR their is no Facenet class in app.facenet.facenet

And for rusts their are also minor issues coming your tests like .lock does not exist can you point out any specific thing which you can't resolve and need help in?

and in other PR their is some syntactical issue in tauri config:
unable to parse JSON Tauri config file at /home/runner/work/PictoPy/PictoPy/frontend/src-tauri/tauri.conf.json because expected , or } at line 40 column 7

https://github.com/AOSSIE-Org/PictoPy/pull/360

Do let me know any specific part in which you need help

[hallow saffron]

alright ill fix these 2 PRs

whats wrong with this one?
https://github.com/AOSSIE-Org/PictoPy/pull/354

its passing pytest in my local system

[marsh idol]

Yes, I saw that workflow error. Some album function is not passing the test right?

[hallow saffron]

yes

[marsh idol]

you have not even changed any album function, then why the error is coming up 🤔

[hallow saffron]

TwT

[wraith creek]

I tested locally changing the patch to this app.routes.albums.edit_album_description

so that it binds with namespace of routes makes it work

it works but still not sure why this happened in the first place with the database patch

but for now you can change this patch and complete your PR

[modest pollen]

Hi everyone, I'm working on #355 I made necessary changes to the project, but I'm facing an issue while pushing them

I'm getting error This is my first time contributing, so I'd really appreciate any guidance on resolving this.

[wraith creek]

113 mbs getting pushed weird, have you added the images or other big files too while staging and committing? If yes then please reset your commit and only add andcommit the files which are changed

[modest pollen]

Okay @wraith creek I will just check into it

Thank you @wraith creek

[hallow saffron]

I've been working on this PR: https://github.com/AOSSIE-Org/PictoPy/pull/354/ and could really use some help. The feedback has been positive about this PR on discord.
The other PRs are being merged ahead of it. I'm spending a lot of time resolving conflicts and updating tests daily. Would it be possible to get a review or decision on this PR? This would help maintain the momentum of development and reduce redundant work. Thank you

[wraith creek]

I think you should add SR No in title to get it reviewed

[hallow saffron]

added

[wraith creek]

@radiant mauve we need to revert this PR as it does not introduce any change to the codebase and the code is AI generated totally, functions are not implemented at all:
https://github.com/AOSSIE-Org/PictoPy/pull/410/files

@hallow saffron Can you revert these changes in your existing PR or should I create a new one reverting this?

[crude prism]

@wraith creek You are now level 18! :confetti_ball:

[hallow saffron]

oh i accidentally deleted a msg

[crude prism]

@hallow saffron You are now level 6! :confetti_ball:

[hallow saffron]

i sent this code ss

[wraith creek]

yeah I saw that

[wraith creek]

Thanks for telling about this

[hallow saffron]

can i make a new PR about reverting this?

or should i do it in the existing one only

[wraith creek]

you can do it in the existing one

[hallow saffron]

Done

[hallow saffron]

I’ve been trying to fix some errors in my PR https://github.com/AOSSIE-Org/PictoPy/pull/353, but I keep running into new ones. Thinking of closing this PR, deleting the branch, and starting fresh with a new branch and PR. Would that be okay?

[wraith creek]

yess you can do that if it has already consumed a lot of time

[hallow saffron]

So im working on this https://github.com/AOSSIE-Org/PictoPy/issues/351

I did some changes, should i include the documentation in the same files or should i make a new file?

[hallow saffron]

can do i do this in cargo.toml

[wraith creek]

If its a big change you can include in seperate file

[wraith creek]

yess

[hallow saffron]

I made this PR alternative to the previous one:
https://github.com/AOSSIE-Org/PictoPy/pull/416

I did nothing related to python, it is failing linting in github actions 🙁

[wraith creek]

Ohh these are changes from that PR which needs to be reverted that are causing this linting issue, it will be fixed automatically once your PR where you've reverted this is merged or in meantime you can delete those files here too in this branch if you want

[hallow saffron]

oh okayy, got it

what do you think about the PR tho

[wraith creek]

you've added caching and overall optimised editing of image in rust right?

Your PR is very well structured kudos for that!
the benchmark_runner.rs was not needed in PR i feel

Seeing the current scale and scope of the app it can be a good to have, no harm in having it! Looks great overall

[hallow saffron]

the core folder which is filled with the ai generated code is causing this problem, i deleted that folder and now it is passing the linting tests

[wraith creek]

yeah that's what I told either you can delete it here or wait for your PR where you've deleted to get merged either way it is fine.

[hallow saffron]

yes

[crude prism]

@hallow saffron You are now level 7! :confetti_ball:

[marsh idol]

Yes, you should delete it

anyways those files are baseless

[hallow saffron]

Thank you!
I added the benchmark file to verify if there is actually a difference in performance or no

[wraith creek]

yess I know, A screenshot of it would be fine on PR description for showing the performance difference, rest if you want you can delete this file from the PR

[hallow saffron]

I'd also like to get some feedback on this PR if possible:
https://github.com/AOSSIE-Org/PictoPy/pull/354

For a while i accidentally forgot my actual problem and did somethin else instead 😭

[wraith creek]

Batch processing is good and was needed I think especially for those who would like to process large amount of images

I really liked that you have added all the type hints as well as comments under the functions

Honestly again perfomance monitoring utilities were not needed

Overall it too looks structured and great!

[marsh idol]

@hallow saffron Now there are some rust-related issues in your PR

linting

[hallow saffron]

yea i fixed that rn

the issue was

there was 1 empty blank line :D

[marsh idol]

ohh

[hallow saffron]

i have been told by my seniors that if u do some work, always quantify the results, show numbers , etc

so thats why i kinda implemented performance metrics at the end to show the imrovement results

[wraith creek]

yess that's good I meant it was not needed in the PR itself, you can show the performance improvements in a screenshot in description which you did already

[hallow saffron]

oh so i should make a performance script
run it, put the ss in PR
and then delete the script

[wraith creek]

Adding monitoring systems and script is overall a good practice and is done in large projects but considering that this project is an offline gallery app with not such a large scale it is not necessary here

[wraith creek]

yeah you can do that

[marsh idol]

@hallow saffron There are some more errors again in linting, I can suggest that you run this command once before the commit:

cd frontend/src-tauri/
cargo fmt -- --check

with this you will be able to resolve all
the errors locally

[wraith creek]

strange cargo's formatter runs automatically on mine locally

[marsh idol]

it is part of the pre-commit right?

if yes, then there is no way we cannot detect the errors except the case when someone uses --no-verify with git commit

[hallow saffron]

cargo fmt -- --check
cargo clippy --fix --lib -p picto_py --allow-dirty
cargo fmt

pre-commit run --all-files
ruff check .
black .
pre-commit run --all-files

all of this, i shall do now

finally

[marsh idol]

finally 😄

[wraith creek]

yess its their in the script

[marsh idol]

@hallow saffron were you running git commit with --no-verify flag?

[hallow saffron]

no

oh wait

i used the vs code source control

i think it does use no verify flag

[marsh idol]

Yes it doesn't

[hallow saffron]

what should be the mid term evaluation date in proposal?

[crude prism]

@hallow saffron You are now level 8! :confetti_ball:

[hallow saffron]

who pinged

[wraith creek]

July 18 is the final date of submission

[hallow saffron]

isnt gsoc supposed to run till aug?

[wraith creek]

I meant final submission date for mid eval

[hallow saffron]

OH

so any date before 18 july?

i see

whats ur github btw

[wraith creek]

Rishab87

[wraith creek]

refer to this:
https://developers.google.com/open-source/gsoc/timeline

July 14 we can begin submission for mid evals

[heavy jasper]

sorry to bandwagon this convo, however concerning GSOC, have you already submitted proposals? I've been looking to submit for a project, however I'm a bit confused as to how many other individuals are also applying for the same thing/progrect/proposed project.

[wraith creek]

yess, I will make few changes though after getting feedback from the mentors. I think its not possible to know the exact number of how many people will apply in this project.

[hallow saffron]

Picto will come under medium sized project right?

[marsh idol]

Yep

[dusky coral]

Hi everyone! I’m Mrunal, a third-year B.Tech student exploring Pictopy for GSoC. While setting up the project, I ran npm run tauri dev but got warnings related to Vite and Tauri. It says the folder isn’t recognized as a Tauri project, and I don’t see a src-tauri directory in my cloned repo. Also when i tried to run npm run dev, it worked but then i am unable to add any folder when i am clicking on Add folder. Any help would be appreciated! Thanks.

[marsh idol]

did you install all the dependencies first, like Rust, Visual studio build tools? If yes, then are you running the npm run tauri dev command in /frontend/ folder?

[dusky coral]

yeah i have installed all the dependencies and yes i am running it in frontend folder

[crude prism]

@dusky coral You are now level 2! :confetti_ball:

[dusky coral]

i also tried to run it in script folder as mentioned in README file. but its not working

[marsh idol]

If you are not able to see the src-tauri folder

then try recloning the repo and then run npm install inside frontend folder

[dusky coral]

okay

and then npm run dev?

[marsh idol]

npm run tauri dev

[dusky coral]

okay. i will try and inform . thanks for the help

[marsh idol]

I should make a setup video for PictoPy. What do you guys think?

I can make it for windows and ubuntu both

someone can help with Mac

[dusky coral]

Yeah thats a great idea. it will really help if you will make a setup video

[wraith creek]

I think someone was already working on it

[mystic sigil]

Yes, @marsh idol if working , please update the README as well. It's not well-structured, and a lot of things are clashing like in Automatic Setup "npm run setup" should be after"cd Pictopy" and also a lot things need to format .

[marsh idol]

Sure

[marsh idol]

Yes Karn was working on it but I asked him and said I can do it.

[wraith creek]

Ohh ok, do tell if I can help in any way, in editing the video or creating a certain part

[marsh idol]

Sure 👍

[viral cobalt]

is this project setput video?

[devout owl]

Hi can someone help me out, during the initial setup, in frontend, after running 'npm run tauri dev', it takes a lot of time and starts the application while giving several warnings,
and for running the backend i installed the requirements multiple times but 'fastapi dev' is still not runnning, i have installed it explicitly as well

i have done this process multiple times, so i have lost track of what is installed and running correctly nd what is creating the issue, can someone plz tell how to proceed

on running npm run tauri dev

[mystic sigil]

You are using ubuntu

Run these commands first

sudo apt update
sudo apt install -y libglib2.0-dev libgl1-mesa-glx

After that

npm run tauri dev

[coarse sparrow]

Can anyone help me in which format I have to send proposals for review

[marsh idol]

https://docs.google.com/document/d/1xtG6kixBtAs8ueuwc8VCduk6Tf-xrelBJZajbrkOWy0/edit?tab=t.0#heading=h.na7bvdbop7g5

[crude prism]

@marsh idol You are now level 16! :confetti_ball:

[coarse sparrow]

After that whom I have to send it for review

[marsh idol]

To @radiant mauve sir

he is mentoring for PictoPy

[wraith creek]

Can we mention issues too in proposal as in template just pull requests are mentioned, do we need to strictly follow the template?

[wraith creek]

@marsh idol in video you can mention one more point which I just added in README in my recent PR

If someone is committing from a terminal in which venv is not activated then they need to install ruff black mypy and pre-commit globally otherwise if venv is activated and they have ran pip install -r requirements.txt once then there is no problem.

[marsh idol]

Okay

[marsh idol]

What if we add the commands to install these globally in the setup script itself?

[wraith creek]

Yes I've added them in my recent PR
But still it will be good to mention it in the video for those who are installing it manually

[marsh idol]

ok

[dusky coral]

Hello..I commented on a few issues but haven’t received a response yet. I noticed #406 (Sidebar UI Improvements) is still open..should I start working on it, or is someone else assigned? Let me know. Thanks!
Also, a big thanks to @marsh idol for suggesting to reclone the repo..everything is working fine now! 😊

[marsh idol]

Yes, you can start the work, mention Pranav sir (this project's mentor) in your PR when you are done

@wraith creek @mystic sigil Can you guys give feedback on my latest PR? Major changes have been made in the setup process and I have made the videos for setup.

PR: https://github.com/AOSSIE-Org/PictoPy/pull/421

New README.md file: https://github.com/AOSSIE-Org/PictoPy/blob/0aa4772541c6b3e5fa7c64b0938dcefc1c7da47e/README.md

[wraith creek]

It looks great, main readme file now looks more minimal. Video is also great! I've no issues with this.

[marsh idol]

Thanks ❤️

[mystic sigil]

All fine @marsh idol 👍

[dusky coral]

hey guys had a doubt, is folder selection is only available in the pictopy app and not in the web browser?

[wraith creek]

yess

[dusky coral]

somebody mentioned this issue in the repo. so i added the warning, when you will click on the add folder in web, it will show a pop-up.

should i create a PR for this? so that issue will be resolved

[marsh idol]

Actually, all the features of the app can run only in desktop app

any component which imports Tauri's dependency will not work

in the browser

[dusky coral]

Yes, its just that somebody raised this issue so i thought it will help. nevermind.

[crude prism]

@dusky coral You are now level 3! :confetti_ball:

[dusky coral]

I’ve fixed the sidebar issue. Before I commit and push, can you confirm which branch I should use for the pull request? Should I push it to main, or is there a specific branch for contributions?

[marsh idol]

main

[dusky coral]

okay thank you

[radiant mauve]

Hey everyone, what are your views on using C# for frontend?

[mystic sigil]

Sir C# offers some compelling advantages, especially regarding .NET integration and cross-platform potential via MAUI, the rewrite effort and the existing functionality provided by our current tauri/react solution means that switching would need to solve a very specific problem that we currently have. I believe that if the current system is working, then we should continue to use it, unless a specific need arises that can only be solved by C#.

[marsh idol]

I also have similar things in my mind, the main advantage of using ReactJS and Tauri is that there is a huge community support for ReactJS and there are many useful libraries written for ReactJS. I completely agree that C# based apps can perform better than Tauri but here are few considerations:

1. The learning curve for new contributors would become much steeper if we switch to C#. Also they need to set up a full Visual Studio environment to contribute.
2. The components which we are able to create so easily using React and TailwindCSS, it may not be that easy to create them in cross platform frameworks like Avalonia and .NET MAUI
3. .NET MAUI doesn't have support for Linux, so we can only develop apps for Windows and Mac. Plus this framework is relatively new.
4. Avalonia can be explored but the community support is less and we may struggle with solving our issues.

[wraith creek]

I honestly think the current setup is better than C# specially when our main objective of the GSoC project is to invite new contributors:

1. Agreeing with @marsh idol , C# has a higher learning curve compared to React + most of the current contributors are also much familiar with React.

2. React and tauri has a higher community support, issues , libraries are easier to find online. So transitioning to C# means not just changing a language, but also adopting a whole new ecosystem.

3. Also its cross platform support is limited too like .NET MAUI’s Linux support is still not their.

So overall C# offers high performance which can be good for end users but if we want to invite new contributors we need to make the code beginner friendly so that user can productively contribute to the code.

If end users are the main goal then we still might consider C# but still that's debatable

So I think we should stick with the current setup (or the electron.js setup for frontend which we'll add in GSoC) seeing the current goals of the org.

[marsh idol]

I believe that even Tauri is better than electron, Electron is just too heavy

[wraith creek]

yeah tauri is a sweet spot between simplicity and performance

[mystic sigil]

Agree with @marsh idol , Tauri is very much better than Electron

[wraith creek]

@radiant mauve @marsh idol tauri implementation is best I think but if we still wanna switch I found something:
https://pywebview.flowrl.com/
We can consider PyWebView too and packagethe app with PyApp, its easier to setup, we can use the same react code and I think packaged application will be smaller too and performance is also decent.

What do you say?

The code will be beginner friendly too with even lesser learning curve, as rust will be removed.
Though I'm not completely sure about it as I was just going through it as I'm writing this and haven't tested it locally but would appreciate on views on this

[marsh idol]

I think in this we can't access local files from the frontend like we are able to do it in Tauri

like in tauri we are using convertFileSrc() provided by Tauri's asset API

to render images and videos in the gallery. In pywebview, there is no such functionality

[wraith creek]

Yup you are right, just went through its docs

but their can be some way for this?

[mystic sigil]

@wraith creek if really want to switch then should go with C# , otherwise Tauri is the best

[marsh idol]

I guess there isn't 😅

[wraith creek]

No I dont want to switch Im myself in favour of tauri I think its best as I mentioned above, C# is not a good option for the reasons I gave above, I was just trying to find an alternative if still AOSSIE wants to switch it to some other framework. And I found this and its size footprint was comparable to tauri that's why I presented it.

Will check if any other alternatives exist, but I too think we should not change tuari

[wraith creek]

PyWebView can serve local static files through its inbuilt HTTP server but yes I dont think its as efficient as tauri

[marsh idol]

then those files would have to be present the the http server's folder?

if its serving static images

[wraith creek]

Dont know checking

Yes it needs to be present there, +1 for tauri again

[marsh idol]

there is something called Tkinter also right? but its only for basic apps written in python

[wraith creek]

Yeah I made my 12 th python project with it but haven't used it afterwards let me check

Nope its for small apps only not good for our case

[marsh idol]

yup

[wraith creek]

Then their's a no better alternative for this case then I think I've searched a lot of alternatives till now (NW.js, Neutrilino.js, PyWebView etc), haven't found any better alternative till now

[wraith creek]

@radiant mauve , I also had one PR pending, can you please review it?
https://github.com/AOSSIE-Org/PictoPy/pull/408

[dusky coral]

hii guys,
I was looking through the issues and found #300 interesting, Landing page for pictopy. Since it’s not assigned to anyone, I wanted to check if I can work on it...
I have experience with React, Next.js, and CSS, so I can design a clean and engaging landing page that explains PictoPy and includes the download links for macOS and Windows.

[mystic sigil]

@dusky coral #300 is already done in https://github.com/AOSSIE-Org/PictoPy/pull/404

I think @karnx forgot to reference the issue

[dusky coral]

oh okay thank you @mystic sigil

[radiant mauve]

Hey guys, if anyone is still confused regarding whether the project is Medium duration or Large
the project is Large duration, so please make the changes accordingly in your proposals, and GSOC proposal submission page

[dusky coral]

hello guys, can anybody help me, i am getting "something went wrong" again and again

[coarse sparrow]

Maybe you have added more tech stack or project category. Try to make it less

[dusky coral]

yes that was the issue. Thank You so much @coarse sparrow

[dusky coral]

Hi everyone! Just staying in touch during the waiting period. I’m still interested in contributing, let me know if there’s anything helpful I can pick up meanwhile.

[marsh idol]

Thank you so much @radiant mauve and @marsh wyvern for giving me the opportunity as a GSoC Contributor for 2025 ✨ ❤️ .

I assure you that I will be able to achieve what I have proposed for Pictopy. I will continue to contribute to this project along with all the other members 🙏

[mystic sigil]

Congratulations @marsh idol all the best 👍

[crude prism]

@mystic sigil You are now level 10! :confetti_ball:

[marsh idol]

Thank you 😃

[odd hinge]

only one got selected for pictopy ?

[odd hinge]

congrats @marsh idol

[marsh idol]

Thank you 😄

[marsh idol]

yes, this year, there is mostly one person per project in AOSSIE

[odd hinge]

ooh !

[radiant mauve]

Congrats Rahul
looking forward to your contributions

[marsh idol]

Hey guys, in case anyone didn't see the update I posted in the https://discord.com/channels/1022871757289422898/1235551640594022480 channel, here it is:

Hello Everyone!
I am Rahul, contributing to the project ⁠Pictopy. My mentor @radiant mauve and I held a meeting to decide the goals for the project. We have decided on weekly syncs to keep track of the progress (Also, additional meetings for discussion and review of important feature designs ). We discussed the possible goals for our project this year. After the exact outcomes are decided, we will update them here.

We discussed about packaging the PictoPy desktop application and came to the conclusion that the Tauri framework is the best option for us to serve the desktop app to end-users.

I will be opening a PR that will add an auto-update feature to the app. This would facilitate users to update the app without manually going to the GitHub Releases page for each update.

We discussed that the backend is quite stable, and it's the frontend that needs work. Although we would still be adding new features to the backend.

From now, I would post the updates here also.

[real gale]

Hi guys!
I’m Rohan, and I’ve just recently successfully set up the project.
I’d love to contribute, ||ideally take up a task that aligns with the frontend revamp to begin with.|| Any suggestions for a good starting issue or bug to work on?

[marsh idol]

Hi Rohan, welcome to the community!

You can first start by setting up the project locally. After that I will suggest some issues to work

[real gale]

Thank you Rahul!

Yes, I've sucessfully set up the project locally.

[marsh idol]

Cool. I think your local repository is not up to date with the latest commits

First sync that. Also, as a feedback, did you face any issues in setting up the repository and which way did you use to set it up?

with the npm script or manual way?

To being with I am assigning this issue to you: https://github.com/AOSSIE-Org/PictoPy/issues/215

Please tell you github username

[real gale]

rohan-pandeyy

[marsh idol]

Comment under the issue.

As a suggestion, I would recommend turning on discord notifications for this channel, to not miss any important updates @real gale

[real gale]

Okay

[marsh idol]

Please tell about this too @real gale

[real gale]

I used the npm script for setting up the repository, and I didn't run into any issues at all.

Everything went smoothly.

[marsh idol]

Great!

Also, first pull the latest changes from the repos main branch into your local

then start the work

[real gale]

I just double checked and my local main branch seems to be up to date with the remote.

I pulled the latest changes when I started, and there hasn't been any new commits since then according to my git log

[crude prism]

@real gale You are now level 2! :confetti_ball:

[marsh idol]

Okay. Can you share the screenshot of the settings page in the app?

[real gale]

Here you go Rahul

[marsh idol]

hmm, something is definitely off. Because the settings page you sent is outdated

can you show me the version history screenshot from VS code?

like this one

[real gale]

Here it is

[marsh idol]

can you close the app and run npm install

then again open the app by npm run tauri dev

Wait

You clicked on the download and install updates option?

when you first opened the app?

[crude prism]

@marsh idol You are now level 18! :confetti_ball:

[real gale]

yes, i did update it

[marsh idol]

okay. You first go to windows settings and uninstall pictopy. Or you can right click the icon on desktop to open its file location and uninstall it from there

We were just testing the update feature and the update you downloaded was not latest one. So next time you run npm run tauri dev, click on "Later"

[real gale]

Alright

I'll follow the steps you've mentioned

[marsh idol]

after you are done, send me the screenshot of the settings page

[real gale]

Okay

Ahh

I see the difference

[marsh idol]

Yes 😄

Now you can go ahead with the issue fix

Do tell if you have any doubts

[real gale]

Okay

[real gale]

Hey Rahul, quick question
Is there a minimum height already specified by the mentors or within the design guidelines?

Or should I let it minimize as much as possible, as long as the layout doesn't start breaking?

[real gale]

(for height and width both?)

[marsh idol]

See the tauriconf.json file

[marsh idol]

Inside src/src-tauri

[real gale]

Yes, I was updating there only,

[crude prism]

@real gale You are now level 3! :confetti_ball:

[real gale]

"width": 800,
"height": 600,

so minWidth also to be 800 and same with minHeight? (600)

[marsh idol]

Yea

[real gale]

The navbar starts breaking after 920 though

turns into a scrollable navbar

[marsh idol]

https://tauri.app/reference/config/#minwidth

[marsh idol]

Okay make it 1000

[real gale]

Yes boss

[marsh idol]

Refer this to set

The dimensions

[real gale]

Yes, thank you

[marsh idol]

For any Tauri related doubts you should not rely on LLMs, they have very outdated info

Always refer official docs

[real gale]

Okay noted

I'll be sticking to the minHeight being 600px only, so that it doesn't interfere with the project's

"height": 600,

Okay, I've implemented the changes regarding the issue. Here is the what the maximum allowed minimized window width and height looks like. Please let me know if you have any feedback

||The navbar does turn into a scrollable one on minimum height but it also doesn't interfere with the project's specified height: 600||

Except if you don't like how the navbar has that scrollbar beside it and prefer min height 1000 like you mentioned above. I'll do so

[crude prism]

@real gale You are now level 4! :confetti_ball:

[real gale]

Let me know if the changes are fine and you want me to create the pull request or change the min height to 1000 :)

[marsh idol]

Can you share the screen recording of trying to reduce the screen width, I want to see how far it is going

[real gale]

okay

Here you go

[marsh idol]

What are the parameters you have set?

[real gale]

        "minWidth": 500,
        "minHeight": 600,

[marsh idol]

Make it 1280 and 720. And then share the video again.

Even if the navbar works, our whole app might not be fully responsive

[real gale]

respectively?

[marsh idol]

So minimum width and height should be restricted

[marsh idol]

Yes

[real gale]

okay

[crude prism]

@real gale You are now level 5! :confetti_ball:

[real gale]

for ```css
"minWidth": 1280,
"minHeight": 720,

[marsh idol]

Nice

Open a PR, I will review tonight

[real gale]

Okayy

[marsh idol]

Make sure you open PR from a new branch for your issue

Don't make pr directly from your main branch

It's nothing of concern but it is a good practice

[real gale]

Okay

Is there any specific template to follow for PR?

[marsh idol]

No, for now raise according to your choice

[real gale]

Okay

[real gale]

Thanks for your time and help Rahul! :)

[real gale]

Hello Rahul, could you please suggest another/some more issues, that would help me familiarise myself with the codebase? I'm keen to keep contributing

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/442

comment under this issue

[real gale]

Done 👍

[marsh idol]

assigned

[real gale]

Thanks :)

[real gale]

Pictopy doesn't have a user account system right? Is that why this issue aims to remove the User Avatar for now?

[tawny cloak]

Hello @marsh idol ,
I'm Shreya Saxena, and I'm excited to contribute to PictoPy as part of my open-source journey. I’ve just completed my first issue on PictoPy , which involved improving the documentation — specifically working on the CONTRIBUTING.md, README.md, and other relevant docs to make onboarding easier for new contributors.

This was a great learning experience, and I'm looking forward to contributing more. If there are any other "good first issues" or beginner-friendly tasks available, please feel free to tag me or suggest some — I’d be happy to help.

Thanks to the maintainers for creating such a welcoming project.

[marsh idol]

Hi, Shreya

thank you for the PR

I will review it.

Do you know Redux toolkit and React?

[tawny cloak]

I’ve completed JavaScript and TypeScript, and I’m currently learning the basics of React. I haven’t worked with Redux Toolkit yet, but I’m open to learning it if required. I’m excited to contribute and would be happy to take on any beginner-friendly issues that align with my current skill level.

[marsh idol]

okay, great. Right now, I cannot find any relevant issues for you. When some basic issue comes up, I will ask you about it.

[tawny cloak]

okay thank you

[real gale]

Hey Rahul,
Just to confirm, this issue is specifically about removing these three features right? (refer attached image please)

Also, regarding the implementation, should I just comment out the related tsx, functions, and CSS, or should I completely delete them from the codebase?

[crude prism]

@real gale You are now level 6! :confetti_ball:

[marsh idol]

Yes, you can delete the code.

[real gale]

Okay

[real gale]

Hey Rahul,
I've completed the issue#442 ||or at least what I understood what the issue asked for, ||please let know if ||it's incorrect or ||anything needs changing
I've **deleted ** the three features from the entire codebase.

[marsh idol]

Will review tomorrow.

[crude prism]

@marsh idol You are now level 19! :confetti_ball:

[real gale]

Okay

[real gale]

Good morning yall 😋

[real gale]

Hi Rahul, any updates for this issue 442? I'm happy to create a PR if everything looks good, or make any tweaks you suggest.

[marsh idol]

yes, create it

[real gale]

Hey guys could any one you help me out please?
So the coderabbitai bot has suggested this change on my recent pull request.
Since this is one of my first times contributing to open source, I'm a bit unsure, how do I apply these changes to my existing PR? Do I need to create a new PR, or is there a way to update the current one with new commits?

Any guidance would be super helpful! Thanks!

[real gale]

Just figured this out, and if in case someone else didn't know as well like me...
Turns out you don't need to create a new PR.
You just make the changes on your local branch, commit them, and push those commits to the same branch your PR is based on and github automatically updates your existing PR with the new commits.

[marsh idol]

Yes this is how we do it

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/446

This is a very basic issue. If you want, I can assign.

[tawny cloak]

@marsh idol Okay you can assign this issue to me I will go through it

thanks

[marsh idol]

Comment under the issue

[tawny cloak]

ok

[real gale]

Hey Rahul, I've successfully submitted the PR with all checks passing.

Any more issue suggestions?

[real gale]

Hi Rahul,
I was exploring the open issues and came across one about this backend API documentation issue: https://github.com/AOSSIE-Org/PictoPy/issues/357
I think working on this issue would jump start me into understanding the API connections and endpoints used in the project, which would help for future contributions

[crude prism]

@real gale You are now level 7! :confetti_ball:

[real gale]

Would it be okay if I take on this issue?

[marsh idol]

It already has a PR, the author forgot to link it

[real gale]

OHH

alright

[real gale]

I thought the PR wasn't gonna get merged so I'd try for myself

[real gale]

Hello, can someone help me out and tell me why's this PR Check failing?

[marsh idol]

There is some macos specific issue. I am looking into that since past few days

ignore it for now

[real gale]

Ahhh

Okayy

[marsh idol]

Sometimes, it randomly goes away

It's strange

[real gale]

Yeah, it didn't occur yesterday in my last PR

something regarding error running bundle_dmg.sh

[marsh idol]

yes

[real gale]

my brain just unlocked the concept of GitHub Actions
this is INCREDIBLE STUFF!!

[marsh idol]

It is incredible 🙂
Also one of the most important features of GitHub

[real gale]

Hey guys,

I've noticed some open issues that seem to be minor or potentially unnecessary (probably raised by someone like me who's just trying to start out). And I was wondering, when looking to contribute, how do you typically identify issues that genuinely matter? I understand it involves exploring the project, but sometimes it's tough to distinguish between a minor preference from a real problem. Any tip would possibly keep me away from creating multiple spam and unnecessary issues

[marsh idol]

Focusing on the core functionality of app is the key thing. Most of the times, we don't need new features, we want to improve the existing ones.

Mostly all the bugs, be it UI or backend related are always welcomed.

New features are debatable

[real gale]

Ohhh. Okay noted! Thanks for the tip :)

[real gale]

There seems to be a bug related to Refreshing Cache. I was investigating into it and it's... gotten me quite puzzled. Could I please connect with someone who understands PictoPy's backend over VC?

[crude prism]

@real gale You are now level 8! :confetti_ball:

[marsh idol]

That functionality is going to be removed soon. In the backend update

There will not be a need of cache. Our SQLite database will store the image paths, so we will access directly from there

[real gale]

Is there any global toast system already in place in PictoPy?

If not, then is there any other method of handling alerts or messages like banner or dialog?

[marsh idol]

Dialog one has a PR

There is no error dialog

Refer to the PR made by ravi-coder.

You can make a similar error dialog.

If you want to work on it

[real gale]

Oh yess! That is exactly what I need

Will this PR be merged soon?

[real gale]

A Global Error Dialog? Would it be okay to create?

[marsh idol]

Yes, you can create an issue for it, I will assign

https://github.com/AOSSIE-Org/PictoPy/issues/443

similar to this one

[marsh idol]

yes

[real gale]

Hello Rahul,
I just created a **GlobalErrorDialog **and it is controlled by Redux States.

Do you like this functionality? Or have any feedbacks?

[marsh idol]

In the global dialog component made by ravi, I saw a variant variable

I did not see it until today

Can you see if we really need an error dialog

[real gale]

The codebase did have a specific "ErrorDialog" prior to this, but it wasn't global, it seems like it was only created for Duplicate Paths

[marsh idol]

Or we can just set variant to error in the dialog and be okay?

[real gale]

Hmm that is true, adding variant: 'destructive' would also convert the infoDialog into an error dialog

[marsh idol]

Okay, can you show a scree. Recording for it?

And also, sorry for this, you made a new component and it may have wasted your time 🥲

[real gale]

Of what exactly, could you please clarify?

[real gale]

No no man its no issue

Always a learning

I got the chance to go through Ravi's code in depth because of this

[marsh idol]

The error dialog of the folder but with the component made by ravi

[real gale]

Alright

This is what Duplicate Path error looks like with the component made by ravi

[marsh idol]

Okay, I need some changes made by ravi in his code

After his PR is merged

You can start the work on yours

Once it is merged

[real gale]

I have a small point that I'd like to lay out on the table regarding this Dialog box

[crude prism]

@real gale You are now level 9! :confetti_ball:

[marsh idol]

Sure

[real gale]

I personally think the "Info" in GlobalInfoDialog could possibly cause confusion for incoming contributors

If we use this Dialog for lets say all the future popups like success, failure, error or warning,

Renaming it to GlobalDialog would sound more appropriate..? As it captures a broader feild of usage for it

[marsh idol]

Right, I will comment it under the PR

[real gale]

Should I close this issue then? https://github.com/AOSSIE-Org/PictoPy/issues/454

[marsh idol]

Yes

[crude prism]

@marsh idol You are now level 20! :confetti_ball:

[real gale]

Hey Rahul,
Just wanted to follow up on the Remove User Avatar, Image Compression, Theme Selection PR I submitted day before yesterday.
I haven’t seen any reviews or comments yet, so I was wondering if there’s anything that’s blocking it..

or if there’s anything you’d like me to change or clarify?

[real gale]

Hey Rahul,
I'm keen to keep contributing to the UI/frontend, so if there are any upcoming issues there, I'd love to have a go at it.

On another note, I had also spent some time diving into the backend API documentation, how album's create, delete, view all etc. calls happen, same with images and face-tagging (while trying to work on this issue, ||until you made me realize it already has an open PR😅||). So if there happens to be a good first issue related to backend, I'd be interested in giving it a try as well.

[marsh idol]

Sure! I will inform when there is one.

[real gale]

Thank you! :)

[marsh idol]

Keep up the good work, guys 🫡 . We have to make this project big.

@real gale I have a probable task for you. If you are interested, I can assign

When we release our app using the https://github.com/AOSSIE-Org/PictoPy/blob/main/.github/workflows/build-and-release.yml workflow, we are not providing changelog inside the release body. This makes it difficult for user to see what's changed and who contributed those changes.

So you have to modify the workflow to include a changelog. Refer this: https://github.blog/news-insights/product-news/beta-github-releases-improving-release-experience/

[real gale]

Of course Rahul, 100%

I've just recently been going through github's CI/CDs

[marsh idol]

Can you open an issue for this?

[real gale]

Alright, please give me a couple of minutes, caught up with some work right now sorryy

[real gale]

"Modify the workflow to automatically generate a changelog during the release process" is the goal right?

[marsh idol]

Yew

*yes

[real gale]

https://github.com/AOSSIE-Org/PictoPy/issues/455
I've opened the issue :)

[marsh idol]

Assigned

[real gale]

Hey Rahul, I did some research work and have found two options to go about with the issue:

1. GitHub has this native built in release notes generator: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
2. This third party GitHub action: Release Drafter: https://github.com/marketplace/actions/release-drafter

Both are very similar, but seem to have just a slight difference:
The native generator will only generate the changelog at the time of release, and doesn’t keep any ongoing draft. The release-drafter will continuously draft a changelog for release after every PR merge (as in, will maintain a live draft release all the time)
Other than this, native generator will follow the basic GitHub template, ||eg: <PR Title> <PR number> by @<contributor>||
while release drafter's template is customizable

Which one would you suggest?

[marsh idol]

We will go with release-drafter. As this bot automatically updates a draft-release, we just need to upload the artifacts from tauri action to this existing release.

See : https://github.com/tauri-apps/tauri-action#:~:text=This GitHub Action has three main usages%3A test the build pipeline of your Tauri app%2C uploading Tauri artifacts to an existing release%2C and creating a new release with the Tauri artifacts.

So you will make some modification in the build-and-release.yml file too

Also @real gale , make sure to categorize the changelog: bugfixes, Features, documentation

To test this thing, you will first have to test on your fork, you will not be able to test on the main repo. So open a test PR in your fork and merge it. This will help properly test the bot

[real gale]

Yess, I was just planning out the testing strategy. Thanks for this

[crude prism]

@real gale You are now level 10! :confetti_ball:

[real gale]

Please correct me if I'm wrong, but a release would only have 2 things right?

1. Bug Fixes
2. Features added

Should I or should I not, add Documentation as a part of a release draft, Rahul?

[marsh idol]

No, let's have docs also, we need separate section for it

[real gale]

Alrighttt

Could you please confirm the labels for these categories

categories:
  - title: 'Features'
    labels:
      - 'UI'
      - 'enhancement'

  - title: 'Bug Fixes'
    labels:
      - 'bug'

  - title: 'Documentation'
    labels:
      - 'documentation'

  - title: 'Others'
    labels: []

[marsh idol]

We need "others" category too, to not miss out any PR

This will have any PR which doesn't have the tags given above

If possible, have a section for first time contributors

[real gale]

Hey Rahul, I was going through the list of available template variables, it doesn't look like there's anything for listing all the New Contributors from previous commit...

[marsh idol]

fine, just list contributors

[real gale]

Okay

[real gale]

Here's what the drafts will look like,
The PR under "Features" was labeled enhancement or UI
Similarly for "Bug Fixes" & "Documentation"; label was "bug" and "documentation" respectively.
All the PRs under "Others" had none of the above mentioned labels.

Then we have the list of all contributors to this release

[real gale]

These are all test PRs but the convention goes like
<PR name> <PR number along with link> by @<contributor>

[marsh idol]

Looks great!

Is it possible to include only the contributors for this release?

we do not want to tag all the contributors

only those who have contributed since the last release

[real gale]

Yes sir, the $CONTRIBUTORS template variable only includes the contributors involved in one specific release, not all the contributors from the past

It doesn't include all historical contributors.

[marsh idol]

Okay

[real gale]

PR?

[marsh idol]

yes

[real gale]

Ready :)

[marsh idol]

will review tomorrow

[real gale]

Good night!

[marsh idol]

Good night!

[real gale]

Hey Rahul, I just wanted to quickly ping you, regarding Release Drafter's functionality,
for a PR to be categorized by the Release Drafter, the PR needs to be containing the label, not the issue it is linked to...

[real gale]

Hi Rahul,
I’ve tested the entire release pipeline ||Release Drafter + Tauri artifact upload|| both are working well when I push a tag like v0.1.0

I have this question though, for this latest PictoPy release v0.1.0 how did you push tags? Did you push the tags using git tag v0.1.0 or was it automated by a bot/tool

[marsh idol]

It was automated by the tauri action

[real gale]

Oh

[crude prism]

@real gale You are now level 11! :confetti_ball:

[real gale]

https://tenor.com/view/cat-wtf-cat-neko-wtf-wait-what-what-did-i-just-read-gif-3919016042940980163

I'm confused with a question
I can't even seem to frame

[real gale]

By "automated by tauri" you mean, the build + artifact upload was automated by tauri action, right? after you pushed the tag??

[marsh idol]

No, according to current implementation, we do not need to push the tag.

For your PR, the tauri action shoul upload the artifacts to the tag created by release-draft

So tag creation will now be handled by release drafter

[real gale]

I think it's finally working 😭

I created a release in my forked repo first
Then created a new release (to test for historical contributors, or only the ones who contributed to this release)

One more thinggg

sorry

but, now that this is set

Okay, so now.. I think only the versioning of the release is left.
By default, Release Drafter seems to only increment the patch version 👇

regardless of whether the PR was a bug, enhancement, or feature

It does have this version-resolver: though, which gives us the power to config "which type of labels can change what decimal of the version"

Now, I haven't exactly tested how this "version-resolver" block works, but it looks like it can automatically change the tags according to semantic versioning, as in "what type of label can change what decimal"

By "decimals" I mean the different levels of versioning 😂 ||major minor and patch||

[dapper atlas]

Hi myself Purnasai V , An undergraduate student ,just entering 1st year , exploring new ways to learn new things , hope this gives me positive start.....Thankyou every one...i would like to take advises and grow together with you people..by contributing to this org...

can u plz help me with how to start contribution..

[real gale]

Welcome Purnasai!
You can start by referring to CONTRIBUTING.md and setting up the project in your local machine. :)

[marsh idol]

right now, leave it. We can edit the version before publishing the release, I can manually do it.

[crude prism]

@marsh idol You are now level 21! :confetti_ball:

[marsh idol]

@real gale Did you figure out how the app's executables will get uploaded to the release?

[real gale]

The files under "Assets" right?

[marsh idol]

yes

[real gale]

Yess.
The current system is going like:
Draft keeps updating
if you click on the "Publish release" button,
the tags will get assigned, build-and-release will trigger tauri and will upload the exes to this new release

[real gale]

In this screenshot, the mac, windows and linux releases had failed because of incorrect tauri sign key (iirc) since the repo was forked onto my account

I'm currently traveling so I don't have an access to my computer right now

[marsh idol]

how does publishing the release trigger the build and release workflow?

okay, got it

in the workflow file make these changes:
change tagName to "v__VERSION__"
remove releaseBody

make these changes and push it in the PR

[real gale]

I did, I made this change, I removed releasename, releasebody, changed tagName as well there was one more change I had made

releaseDraft was changed to false

yess

[marsh idol]

keep release draft as trye

*true

and keep releasename

[real gale]

no but this is the tauri workflow right?

[marsh idol]

yes

[real gale]

turning releaseDraft to true will create a new draft and discard Release Drafter's draft

[crude prism]

@real gale You are now level 12! :confetti_ball:

[marsh idol]

ok

[real gale]

Yess, I had made the necessary changes in Release Drafter's config file to keep the Release title as "PictoPy vX.Y.Z"

[real gale]

This entire release was made by the two actions solely

[marsh idol]

make sure that tagname matches in both actions

in tauri there uis "app-v"

prefix

[real gale]

OHHH rightt

[marsh idol]

while in the second draft there is just "v"

[real gale]

I'll look into this as soon as I reach home

[real gale]

Hey Rahul,
Addressing your query
I've changed the draft tag from being v0.1.0to app-v0.1.0
Which one do you prefer? v0.1.0 or app-v0.1.0
||I personally prefer the first one 😅 ||

[marsh idol]

First one

[real gale]

Alright, this is what it looks like after all the changes
To put it altogether, the tag template follows this naming convention: vMAJOR.MINOR.PATCH
The name of the Release will be: PictoPy vMAJOR.MINOR.PATCH
The Tauri Action will automatically be trigger when Publish Release is pressed.
The artifacts will be attached to the current draft (made by Release Drafter)

The overall thing is: PR merged > Draft updated > Manual Publish of the release > Auto build-and-release upload

The only doubt I have is about the Mac,Windows,Linux signed builds which are failing because of secret key Error failed to decode secret key: incorrect updater private key password

[marsh idol]

Great bro, nice work

[marsh idol]

don't worry about that you are getting that error because your repo doesn't have those secrets setup

[real gale]

YESSS

alright

commit?

[marsh idol]

Yup

[real gale]

Hey Rahul,
I had committed the latest changes and a few more, suggested changes by the CodeRabbit bot. I'm happy to have had this opportunity to contribute, please do let me know if there's any other probable task for me to work on. Thank you :)

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/458

This issue is up for grabs @here

[marsh idol]

@real gale

https://github.com/AOSSIE-Org/PictoPy/actions/runs/16221800960/job/45803894720

can you look into this, there is some error in the workflow

[real gale]

https://tenor.com/view/sweating-nervous-wreck-gif-251389163301299969

[real gale]

Hey, sorry I was not at home back then.. I found this blog post about something which I think is related to the issue:

https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/

[marsh idol]

no worries, take your time

[real gale]

I'll start working on this

[real gale]

Hey Rahul, I've opened a PR fixing the error.
https://github.com/AOSSIE-Org/PictoPy/pull/460

[marsh idol]

@real gale https://github.com/AOSSIE-Org/PictoPy/releases/tag/v0.1.1

It works 😄

the installers are also uploaded

[real gale]

WOOOP

[marsh idol]

I have a task. Anyone who is interested, open the issue and tell me to assign it:

https://aossie-org.github.io/PictoPy/

The docs website needs to be updated:

1. https://aossie-org.github.io/PictoPy/setup/ in this page, we have to now directly link CONTRIBUTING.md file instead of readme. Also, some links in quick links portion are not valid, replace them with valid links to the contributing.md part
2. On the home page, some of these links are not valid, remove those

Also this overview page needs proper formatting

and change this from react hooks to Redux Toolkit

[real gale]

Interestedd 🙋

[marsh idol]

You can open the issue

[marsh idol]

basically, make this table same as the one in readme file

[real gale]

Opened :) #461

[real gale]

I had a small question, why'd the project change from Radix to ShadCN?

Better components?

[marsh idol]

Yes

And shadcn is based on radix and on top of that its default components are good

[real gale]

Ouu

Good to knoww

[unreal quartz]

Is this is still available?
i would like to work on that

[marsh idol]

It is solved.

[unreal quartz]

ohh
if there is something else . please let me know

[marsh idol]

Hello everyone, I am glad that many of you are interested in this project. Right now, I am implementing the backend part of my GSoC proposal. We will we starting the new UI work from 18th. Hopefully at that time, I will be able to open both backend and frontend issues 😄

Till then check out my GSoC updates journal and the backend work I am working on:
Journal: https://docs.google.com/document/d/1w2nTQ5nLkWb824FT27L6YKCgT6dThwRLa1gt33h7UfM/edit?usp=sharing

Backend work: https://docs.google.com/document/d/1CRnPiuXxg-xtmtSdWu91Ltoc4VwgZoC_iKp0utrGSfg/edit?usp=sharing

I will update these docs to include latest info by today

[unreal quartz]

Hey!
Thanks for sharing the updates — I just checked out your journal and the backend docs, and it’s super exciting to see the progress you're making! 🔥

Really looking forward to tomorrow — can’t wait to start working on the new UI with everyone! It’s going to be a great phase for the project.

[marsh idol]

just a little heads up, I will open a PR for backend today , by 6PM. After that I will open the issues.

@unreal quartz @real gale @tawny cloak

[real gale]

Ready!! :)

[unreal quartz]

That's Crazy , excited for that

[real gale]

I can see A LOT

of changes

omg

[marsh idol]

The PR is opened, I am wrting issues now 😄

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/472

Guys I have opened 1 issue, check it out. I am opening more.

[crude prism]

@marsh idol You are now level 22! :confetti_ball:

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/473

First UI issue is created. Note that solving this issue requires knowledge of redux toolkit.

[marsh idol]

https://github.com/AOSSIE-Org/PictoPy/issues/474

I have opened one more issue related to creation of backend unit tests for the new backend.

[real gale]

Hey Rahul, you mentioned in the issue:

Remember, we need to have hidden albums too, even if we show the hidden albums,** the user will require password to open a hidden album**.
So I was wondering if is there an existing util inside the codebase for handling passwords...

[marsh idol]

Just use bcrypt library

For hashing passwords

[real gale]

Okay

[marsh idol]

This issue is still available for anyone to take, if you are not having any other issues assigned in this project you can take it up.

[real gale]

Evening sirr,
I was starting to build the Postman API calls to the collection you shared to me... But I haven't really **contributed **to a Postman collection before, ||I do use Postman extensively for personal testing|| so I wanted to ask you, do you want me to create a PR for Postman as well?

[marsh idol]

Give me your email, I will give you edit access

[real gale]

Sent in DM

[marsh idol]

Are you able to edit in the main collection now?

not the fork

[real gale]

I tried to save a change, but Postman is still prompting me to fork the collection.

[crude prism]

@real gale You are now level 14! :confetti_ball:

[real gale]

I did accept the invitation to join the workspace.

[marsh idol]

can you try loggin in and out and check again

ok wait

now you will be able to do it

check

[real gale]

Great

[real gale]

Yess

It's working now thank you!!

[real gale]

WOW! The frontend design looks so good! 😭 very nice

[real gale]

Good morning sir,
I wanted to share a quick progress update regarding the issue#472
I've got the first five album operation routes implemented successfully in my local machine...and also set up the corresponding requests in the shared pictopy postman collection

[marsh idol]

Great

[real gale]

I was wondering if you could please take a quick look at the collection when you have the time to?

So that I can ensure that the API design aligns perfectly with your expectations and the project's conventions...

[marsh idol]

Sure

[real gale]

Thankyou!!

[marsh idol]

Yes, the routes are appropriate

[real gale]

Thank you for the clarification sir :)

[real gale]

Good evening boss,
I was working on the albums/images routes. And have noticed a difference in names in the codebase and the dbdiagram.io schema...

Would you want me to change these image_classes and class_id to match with the names in dbdiagram

[marsh idol]

No image classes has a different purpose

See the full diagram

You hav to create new table

[real gale]

OHH

One more doubt, I'm not supposed to touch the routes/images.py right?
I should define all the routes asked for in the issue, inside routes/albums.py file only, right?

[marsh idol]

Yes

[real gale]

Okay thanks

[real gale]

Hi Rahul sir,
I've set the up the final four route requests in the PictoPy Postman collection... I would really appreciate it if you could give them a quick check and let me know if anything needs adjusting

And if everything is fine, should I open a PR to your backend-revamp branch?

[real gale]

Good afternoon @marsh idol sir, hope you're doing fine, should I open a PR to your backend-revamp branch if everything is alright?

[marsh idol]

Hi, I was occupied in some work, I will review today, you open the PR

[real gale]

Okay sir

[real gale]

I've opened a PR to your backend-revamp branch

[real gale]

Hello @marsh idol sir, I was starting work on the backend-tests and have a small doubt... I might have to make changes in the app.database.albums or app.routes.albums file... Wouldn't making changes in these files, without them having merged into your PictoPy's fork's master branch, create merge conflicts for you?

[marsh idol]

No

You can push the changes for the tests into the same PR that you created for albums

I will close two issues together then

[real gale]

Okay

[real gale]

Hello sir, could you please confirm if this way of writing the tests is acceptable?

[marsh idol]

yess

[marsh idol]

Also one more thing, all of you can address me by my first name😄. Please don't address me by sir 🫠

[vital hinge]

Hey everyone!
I’m Rohith, an open source enthusiast with a few contributions under AOSSIE.
It’s a new week, and I’m looking to kick things off by diving into a new project, I hope I will be able to be part to build this project to the next level.

[tame tendon]

Hey Everyone!
I'm Aryan , a begginer in open source but would like to work on this project,I think I'll be helpful in taking this project to new heights.

[ornate jungle]

Hey @marsh idol

Is this issue open to work on ..

I was thinking on working on it

https://github.com/AOSSIE-Org/PictoPy/issues/241

[marsh idol]

That is an old issue, we are working on building a new frontend, keep checking this project for any new frontend related tasks that are up for grabs.

[ornate jungle]

Got it, thanks for the update!

[ornate jungle]

Hey @marsh idol Just to clarify — since the new frontend is still under development, does that mean there aren’t any current tasks open for contribution until the new frontend is fully implemented? I just want to make sure I’m not missing any opportunities to contribute in the meantime.

Looking forward to contributing once things are ready!

[marsh idol]

No no, I will open tasks/issues for the new frontend work, everyone will get to build new frontend

[real gale]

Hello @marsh idol, It's been a while since my last activity here.. how are you doing? :)

I have managed to update the album backend according to the changes you proposed in the PR's comment section...

[marsh idol]

I am doing great

[marsh idol]

Nice, I will review

Give me 3-4 days, I am preparing to go back to college so busy with other things

[real gale]

AYY samee

alright no issues take ur timee

[tawny cloak]

Hey @marsh idol ,
I’ve been going through the repo to fully understand how the onboarding page is structured ,

Umm.. I’ll be sharing the updated plan soon like how will I be approaching it, along with a couple of small doubts. Also, just a heads-up — my college is starting from 4th August too, so same situation 😅

Will keep you posted!

[marsh idol]

Sure, take your time.

[real gale]

Hello Rahul,
Should I add these validation checks in the database..?

for all functions?

[vital hinge]

Hi Rahul,
I hope you're doing well!

I was going through the issues on the PictoPy project and came across this one link. I believe it’s a good fit for my first contribution.

I wanted to check if the issue is still relevant and whether anyone is already working on it. If it's available, I’d love to take it up.

[crude prism]

@vital hinge You are now level 2! :confetti_ball:

[marsh idol]

Validation is not needed

Because we are already defining foreing key constraint on the DB table.

If the image id doesn't exist, the DB won't allow to insert.

[marsh idol]

Hi,
Right now, the issue is not being taken up because the new frontend is not ready.

Once it will be ready, I will see what older issues are relevant and open them up for assignment.

[real gale]

Yes, that’s what I thought as well, confirmed for just in case. Thanks!

[real gale]

Hi Rahul,
Thanks for your review on my PR

One quick question:
After going through the folders routes, I saw your schemas/folders.py file, it already defines:

class ErrorResponse(BaseModel):
    success: bool = False
    message: str
    error: str

Can I import and reuse this same class in routes/albums using

from app.schemas.folders import ErrorResponse

Since this will help keep consistency and take out duplicate class definition
or should I redefine ||& duplicate|| ErrorResponse into schemas/albums.py so each module stays isolated?

[marsh idol]

Yes right now, make a separate one. We will open up issues in future for code refactoring.

[real gale]

Okayy

[real gale]

Hi Rahul, I have pushed the requested changes to the PR.

[crude prism]

@real gale You are now level 15! :confetti_ball:

[real gale]

I can see a branch conflict suddenly now, was there a change in the backend/main.py since yesterday?

[marsh idol]

Yes

[jaunty mountain]

hi there,
i would like to contribute to this project but dont know where to start can someone help @marsh idol @real gale @vital hinge @tawny cloak @ornate jungle

[marsh idol]

Hi @jaunty mountain

You can start by setting up the project locally.

[jaunty mountain]

the thing is i am totally new to this org , i was trying to find someone with the role of contributor or mentor as server guideline mention take help from but as a begineer i have a questions what are the skills required if i dont have can i still contribute

[marsh idol]

For PictoPy, we have mentioned our tech stack in the README.md of our project

[crude prism]

@marsh idol You are now level 23! :confetti_ball:

[marsh idol]

You can refer that

[jaunty mountain]

ok

the only skill i have is react and a bit of pytho from the list of readme so whats next

[marsh idol]

great, you can contribute to the frontend

right now, we do not have any issues available to take up. When we will list those issues, you can work on them.

[jaunty mountain]

should i learn something new to contribute to backend or else

[marsh idol]

FastAPI

[jaunty mountain]

should learn basics will that be enough like a 2 hour one shot type

[marsh idol]

yes

[jaunty mountain]

@marsh idol do i need to learn mongo db for fast api

[marsh idol]

No, we use SQLite

[jaunty mountain]

can you share any resourse that may help and the requirements for fast api

[crude prism]

@jaunty mountain You are now level 2! :confetti_ball:

[marsh idol]

This might help:
https://youtu.be/tiBeLLv5GJo?si=R502Sugb8pahqlDc

[jaunty mountain]

its beginner level right

[marsh idol]

yes

only if you know about writing backend APIs with some other languages like NodeJS, Java

[jaunty mountain]

hmm i am learning though right now with node js

[analog spoke]

I am a beginner here and want to contribute ,but not getting from where to start?

[real gale]

Welcome to AOSSIE's PictoPy @analog spoke

To begin contributing, you should start by setting up the project on your local machine

A brief guide can be found here

[carmine pilot]

Hey everyone myself rakshit and i am contributing consistently from last 2 months now i am looking to contribute in Pictopy if any issue @real gale @marsh idol please assign it to me.
https://devrakshit.me
https://github.com/rakshitjain23
it's my portfolio i have experience in working with next.js and in backend fastapi i am learning so..

[marsh idol]

Hi everyone

We are working on the PictoPy frontend and I wanted someone to work on a sub task

The task is to create a scroll bar like this for the images returned from the API

Notice that the more the number of imges, in a year, the more the the size of that year. in the scroll bar

If anyone is willing to work on this, they can start working and explain me the approach after 24hrs.

[real gale]

Interested 🙋

[marsh idol]

Please go ahead and come up with an approach

[real gale]

Okay thank you

[marsh idol]

Look Google Photos for yourself to see how the scroll bar works

[real gale]

Hello @marsh idol, ||extremely sorry for the overshoot of deadline||
I wanted to share my approach for the timeline scrollbar.

So currently, the GET All Images in an Album route's response body only gives us the image id:

{
  "success": true,
  "image_ids": [
    "3e77a466-d261-4878-9600-9695e3ace73e"
  ]
}

and since we need a year based scrollbar, similar to Google Photos... we’ll also need metadata regarding the date_created or year of these image_ids (your opinions please)

Then we group by year, aggregating and normalizing counts of images per year into proportions for scrollbar segments.

I saw the changes in Pictopy’s Postman Collection, and saw the Sync Microservice can continuously add or remove images from different years. So whenever sync adds or removes photos, We’ll have to update those year counts and re-render ||(???)|| the scrollbar so that each year’s segment expands or shrinks proportionally