@Udoka_Ugo We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@KemmieKemy We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@Js636f We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@Hulya We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@santana We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@Richa1496 We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@JukanaCodes We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@Dldisha We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@Akanksha_Bhattachan We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@BlessingDickson We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

@435643 We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 28 quality applications, and we could only accept 7 interns. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many interns who we did not accept in 2019 have become Wikimedia maintainers, contractors and even Outreachy interns and mentors this year!

I guess currently we are using ffmpeg -i input.mp4 -an output.mp4by adding -c copy parameters we can copy the frames instead of going through a decode->filter->encode process.

Preview of the above patch

@nandhinibalaji311 as you don't have any progress for sevaral months, Assigning this task to myself :-)
Please feel free to comment if you have any sugesstions :)

Results of the above patch-set

@Soda I couldn't get what you meant by the "horizontal state". Also I would suggest you to try out the current cropping functionality so you will get the idea on how it works. Here we are just trying to improve the user interface and user expierence of the same :-)

@Aklapper Thanks for the ping, Yes we can close this task and for any new requests, we can open the new ticket.

Hi @Hulya, By seeing your core location /Users/hulyakarakaya/Desktop/core I'm wondering why you placed core in desktop?
Generally, core should be placed in your default root folder of the web server for instance /Users/hulyakarakaya/var/www/html/core (if you are in linux system). and yes it depends on your operating system aswell.

Hello @Gechy, Thanks for taking up this task, Lemme know if you need any help, feel free to post your questions here :)

@Soda, Do you have any progress or struck some where else and seeking for help? Feel free to post your queries here if anything is still unclear :)

Hi @Soda, Thanks for taking up the ticket!
Currently, Video cropping and rotating can be selected individually before tapping on "Preview" button, So we are trying to achive performing croping by selecting "Crop layer" in rotated video player both actions together in same time and also adjust the CSS for the rotated player for the good user expierence, Hope you got the requirements of the ticket, Feel free to ask more questions if required, happy to provide more insights to help you :)

The code is changed a lot now, This patch need's to be rebased and minor tweeks has to be done.

We changed our infrastructure to support for the large files, By using 4cpu's and 8gb ram in a worker instance.

Updated https://video-cut-tool.toolforge.org/ for redirecting to https://videocuttool.wmflabs.org/

Ah we actually migrated the tool from toolforge to VPS instance, so the toolforge instance might not work now, Sorry I keep on forgetting redirecting to new tool link from toolforge instance. T250029

Hi @Soda, Thanks for creating the task.
As per here it is set to "https://videocuttool.wmflabs.org/video-cut-tool-back-end " right ?

Sorry for the delay, After a short workaround, I couldn't find a way to start the daemon service in the toolforge instance, So looking for the way to start the service, Would be happy to dicuss more at IRC (Nick: Gopa in #wikimedia-cloud) to make the tool live.

I guess https://wikicontrib.toolforge.org is the latest release of the tool now.
Source: https://github.com/wikimedia/WikiContrib/

Created a poster and published in the social media, Here are some links to the posts!

Hi @Tgr, I have reached you in telegram regarding the issue we face while deploying the tool, Did you find any insights?

I was searching around and found few insights, One possible way could be adding a class to the rev.getParsedComment() at line 510 and adding CSS properties hypens: auto / break-word: normal to the class should solve this bug I guess.

Okay, I tried to deply here: https://tools.wmflabs.org/wiki-irc/ Aah I'm missing something while deploying, Any toolforge folks around ?

I tried it locally, yes the installation is simple and easy, Also the flow and UI looks nice. I think we should definitely try this, I can try to set up a toolforge instance, @Tgr did you already create one?

I tried to reproduce this issue, I didn't face any issue/bugs and it's all working as expected. Tested in Browser firefox.

As you already made some good contributions to the tool so pinging @Crutishnyk, @IAmNetx if you are interested as a technical co-maintainer to the tool?

As @Jayprakash12345 is busy these days, We are looking for active co-maintainers for the tool's technical maintenance.

Hi @Fuzheado, The ? button (right down) in this figure actually links to the tools documentation.
Aah yeah, it may be not be in the right position to have a easy and quick look and lets try to change this info button to some where around soon in future.

In T252341#6122778, @Aklapper wrote:

@Gopavasanth: Ah, sorry! (Is there a separate task about cleaning that up? Would be worth it so I stop using the "wrong" instance.)

In T252341#6122751, @Aklapper wrote:

I assume the steps to reproduce should have been "Go to https://tools.wmflabs.org/video-cut-tool/ " instead?

Hello @Fuzheado You mean provide a link to basic documentation from tool ?

@Geertivp you are right, after digging little deeper I couldn't think of anything else now.