In T387744#10648737, @ChiomaVero wrote:

In T387744#10648723, @Reputation22 wrote:

refer here: https://phabricator.wikimedia.org/project/profile/4054/

Thank you so much.
I have one more question, if I want to solve other tasks, how do I locate their repository, is there a button that I am supposed to click?

hi @Adityakumar0545 i've raised some comments here https://gitlab.wikimedia.org/cloudvps-repos/videocuttool/VideoCutTool/-/merge_requests/32
lmk when you resolve them

refer here: https://phabricator.wikimedia.org/project/profile/4054/

hey @AyushShukla1807 lmk if you're stuck somewhere. This is actually a high priority ticket (BUG), and we're looking to close it asap.

hey @dipanjan_sengupta lmk if you're stuck somewhere in this ticket

hey @Soda @Gopavasanth @Punith.nyk let me know your thoughts on this. Lets initiate the discussion here on the ticket itself.

Have reviewed the PRs, please check on the comments

Thank you for tagging this task with good first task for Wikimedia newcomers!

feel free to refer to the patches previously raised by @AFZL210 (linked above)

also what is RoadToWiki ?

hey @Adityakumar0545 yes you're going in the right direction.
may i add a couple of check points for exit criteria here

• functionality: redirect to /
• check on both web and msite (mobile view)
• add a unit test mimicking the same functionality (you can refer to home.test.jsx for reference) [ probably something around fireEvent.click(); should work ]

https://gitlab.wikimedia.org/cloudvps-repos/videocuttool/VideoCutTool/-/merge_requests/31

Thank you for tagging this task with good first task for Wikimedia newcomers!

now the UI is changed. This bug is un-replicatable. Closing the ticket

hey @AyushShukla1807 feel free to ping us if you're stuck

also lets keep this in low priority. doesn't seem like fulfilling a lot of use cases here

hey @Punith.nyk removing you from the assignee here, since its open from long time.
also moving the ticket from in-progress to incoming.

this is done.
cc @Punith.nyk

this is done.. patch merged long time back
closing the ticket

hey @AFZL210 removing you from the assignee as no updates here. please raise a new mr on gitlab or post an update here if you're still working on this

Thank you for tagging this task with good first task for Wikimedia newcomers!

hey @satdeep_gill @Gopavasanth is this still happening?
should we priortize this?. please post an update here. else lets close the ticket

afaik this is fixed with the socket architecture revamp long back
please check and comment here @Gopavasanth

Thank you for tagging this task with good first task for Wikimedia newcomers!

I think this can also be marked as good-first-issue.
The resolution here is to change the name of the video when clicked on the Overwrite button.
Also remove the above mentioned fields from the wikitext on clicking Overwrite.

Hey @Soda lets try to reach for a resolution here. The fix was merged on master and is live on prod.
This ticket is in resolved state. Lets just try to close this 1 open pointer, before we mark it resolved.

lets try to reach a resolution for this asap

hey @Yamen any updates on this?
Is this still happening?

Thank you for tagging this task with good first task for Wikimedia newcomers!

I think changing the heading from h2 to paragraph for the line Setting the callback url does the work here.
The context is same as above (Create an application with the following grants) [within it we're asked to fill up the callback url]

As of now we're displaying the time as received from the server end itself. Implement a basic utility function on client end, to format the time and call it while displaying it to ProgressBar

Thank you for tagging this task with good first task for Wikimedia newcomers!

MR -> https://gitlab.wikimedia.org/cloudvps-repos/videocuttool/VideoCutTool/-/merge_requests/30

Thanks @Aklapper
Will keep that in mind.

In T338465#10554690, @dipanjan_sengupta wrote:

In T338465#10554660, @Reputation22 wrote:

Hi @dipanjan_sengupta I would strongly advise you to pick one ticket at a time. Lets not hoard on the tickets. Lets give everyone a chance to pick up the tasks.
Removing you from assignee here

i picked 1 bug and 1 feature , i can handle it @Reputation22
mistakenly had changes the status of the task , have now fixed the status . if needed u can still assign this to me

Hey @KunalKatara12 removing you from the assignee of this ticket. Since there were no updates here.
Feel free to reclaim the task.

Hi @dipanjan_sengupta I would strongly advise you to pick one ticket at a time. Lets not hoard on the tickets. Lets give everyone a chance to pick up the tasks.
Removing you from assignee here

Duplicate T338465
@Aklapper should we close this?

Was this never picked up @Soda @Punith.nyk ?

This is an open ticket regarding MetaMask clearing up your localstorage and stuff not reflecting from your client to server.
But now i believe since we've migrated to cookies (in case for login especially) maybe we can close this.
Wdys @Soda

please do ping us if you're stuck anywhere

hey @Ashwinpraveengo any updates on this?

whats the status here @Soda?
afair this was done. can you please post an update here? if not lets priortize it. wdys?

Whats the status here @Gopavasanth ?
Is it still happening? should we priortize this? afair this is resolved. can you please check and report back here?

Whats the status here @Gopavasanth ?
Is it still happening? Should we priortize this?

Whats the status here @Gopavasanth @Soda ?

Can we make this as feature req/enhancement
Also lets give it a priority
cc @Punith.nyk

This is done. We've migrated to cookies instead of localstorage.
cc @Soda

Should we close this @Soda ?

Hey @Claytonsalem the callback url is for Wikimedia OAuth 2.0 (enabled in VCT). Sure feel free to raise a PR for updating the readme.

Hey @dipanjan_sengupta sure. do ping me here if you're stuck anywhere

Sure. We can have a progress bar for downloading as well. Lets create a new ticket for it (feature request / enhancement), and lets discuss over the approach you'll be going forward with over there. @dipanjan_sengupta

Closing for now.

You have to provide the extension (.webm) in the end

In T368816#10220531, @Tacsipacsi wrote:

In T368816#10219466, @bd808 wrote:

In T368816#10201603, @Gopavasanth wrote:

The idea is to automatically send a reminder to the tool's maintainers at the address tools.<TOOL_NAME>@toolforge.org

The plan to send the notifications to the given tool's Toolforge email address would automatically email all registered maintainers of the tool. The backend logic for handling that address uses information from the LDAP directory that is the canonical data store for Toolforge tool maintainer information. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Email#Mail_to_a_Tool

I see. I seem to have skipped through that comment (even though I tried to read all comments, not only the description, before replying).

In T368816#10220476, @Reputation22 wrote:

Hi @MahimaSinghal lets not jump into this

I think it actually makes much more sense than the Author column, and therefore I’d do this independently of the emailing feature: this tool is about reporting unhealthy tool, and fixing that is the job of the maintainers, not that of the authors (who may have long left the project).

and besides if we add another column saying Send Email, anyone can click on it and send the email to the maintainers (essentially spamming them)

Sorry, but this is just a slippery slope. Adding a Maintainers column doesn’t mean we have to add a Send Email column as well.

In T368816#10219107, @MahimaSinghal wrote:

In T368816#10210400, @Tacsipacsi wrote:

Who will receive the notification emails? The Author column contains the first (why only the first?) author of the tool – which may not be the same as the maintainer (for example, Átíró, of which I’m the only maintainer, lists Chery, who has never had Toolforge access), and in fact may not even be an existing SUL user name. If you send emails, you should send them to the maintainers, not the authors. (I don’t know how they can be queried programmatically, but https://toolsadmin.wikimedia.org/tools/id/atiro clearly lists me as the sole maintainer, so the data is available somewhere.)

If the mails go to the right people, I’d be happy receive notifications about tools I maintain being down ASAP (i.e. at the next check). I think there should be a management interface where I can

• Set planned downtime, so that I don’t get emails if I manually and intentionally stopped the service.
• Mark the tool fixed, so that if it’s down at the next check, it’s regarded as a new downtime. However, if I don’t mark it as fixed, the next successful check should also mark it fixed. (Not manually marking it as fixed risks that if I believe to have fixed it, but it goes down by the next time it’s checked, I’m not alerted.)
• Maybe also acknowledge the alert without fixing it – this would allow sending repeated mails, in case I missed the previous ones, without bothering me about something I very well know.

In that case one more column could be created which lists maintainers of the tools, and then the mail could be sent to maintainers.

@Gopavasanth If this looks fine to you, i can create a pull request for this feature.
Basically just added one more column which lists maintainers of the tool.

done @KCVelaga
cc @Gopavasanth @Soda

Hi @Jdlrobson Currently there are multiple copies of the same repo!
Should we merge them all in one (i,e your personal Github), so that we maintain only one source of truth.

This is done
cc @Soda @Gopavasanth

done

we won't be deleting videocuttool-bookworm, we will be upgrading its resources
and would be deleting videocuttool instance altogether

@Yamen if possible can you share the link of the video over here as well please
Thanks

Whats the status here @Punith.nyk

Same as T345110
Closing it

Wait what do you mean by converting it to mpg
The videos are usually converted to webm, or ogv

but we need the logs @Soda

@Punith.nyk whats the status here?

this can be picked up for #indic-mediawiki-developers mini hackathon guwahati 24