Petrb

Previous page history was archived for backup purposes at User talk:Petrb/LQT Archive 1 on 2015-07-10.

Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, interface administrator, etc.) was adopted by community consensus in 2013. According to this policy, the stewards are reviewing activity on wikis with no inactivity policy.

You meet the inactivity criteria (no edits and no logged actions for 2 years) on this wiki. Since this wiki, to the best of our knowledge, does not have its own rights review process, the global one applies.

If you want to keep your advanced permissions, you should inform the community of the wiki about the fact that the stewards have sent you this information about your inactivity. A community notice about this process has been also posted on the local Village Pump of this wiki. If the community has a discussion about it and then wants you to keep your rights, please contact the stewards at the m:Stewards' noticeboard, and link to the discussion of the local community, where they express their wish to continue to maintain the rights.

If you wish to resign your rights, please request removal of your rights on Meta.

If there is no response at all after one month, stewards will proceed to remove your administrator and/or bureaucrat rights. In ambiguous cases, stewards will evaluate the responses and will refer a decision back to the local community for their comment and review. If you have any questions, please contact the stewards.

Yours faithfully.

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:17, 4 January 2022 (UTC)

Hello Peter,

I want to contribute to this project but have some queries how do I start...?

Hello Peter,

I want to contribute to this project but have some queries how do I start also are good first task are good, can you provide your email.

Hello, Great to hear it! We are in need for active developers like never before. First step is definitely to get yourself more familiar with Huggle itself. That means install it and use it. Maybe you figure out it's not as cool project as you anticipated. Here is the landing page for users: https://en.wikipedia.org/wiki/Wikipedia:Huggle . Once you are familiar with Huggle, then here is the phabricator list of open tasks https://phabricator.wikimedia.org/maniphest/query/qCXs.CiDoJGl/ and here is the repository with code itself: https://github.com/huggle/huggle3-qt-lx before you start working on coding, you will need to setup your developer environment so that you are actually able to compile Huggle. Our developer wiki is your friend:

• https://github.com/huggle/huggle3-qt-lx/wiki/Developer-guide
• https://github.com/huggle/huggle3-qt-lx/wiki/Portable-development-environment

Let me know if you have any other questions! I am also on IRC #huggle on freenode but, I am only randomly online.

Okay no problem. I am in the way to clone the repo and work on it currently working on the requirements, if I am not landed on wrong page then here it is: https://github.com/huggle/huggle3-qt-lx/wiki/Building-on-Windows

Very happy to hear that I am at my place of interest now. I will let you know when I am ready with my ideas.

Thank you

OK, keep in mind that Windows is most "hostile" environment out here for this developer environment setup, so it may be a bit of struggle to get it to compile there. You will need Visual Studio (community edition is enough), CMake, and Qt5 with WebEngine installed. Getting it to compile on Windows requires advanced knowledge of C++ and MSVC compiler suite. If you don't have that I would recommend to work in Linux VirtualBox instead, as that's much easier to setup.

I have worked on visual studio, CMake and Qt5. Okay I'll try to compile it on windows if failed then will switch to Linux VirtualBox.

I'm contacting you, as your project is featured on the New Developers page! :) Would you be interested in mentoring a project in the Outreachy Round 15? If so, here is what you might be interested in learning about:

1. Get an overview of the selection process, and your responsibilities before, during, and after the program

1. Create a task, or modify an existing one on Phabricator. Make sure it includes: Project title, description (summary in 8-10 lines), skills required (Phabricator tags are welcome), mentors (required two), micro tasks (link to Phabricator task that must be completed to become a strong candidate).*

1. Tag the task with #Outreach-Programs-Projects and    #Outreachy-Round-15 on Phabricator.

Learn more about the accepted projects from previous round.

Hi Petr!

The Extension:MultiUpload page says that you've taken over maintenance of that extension from Tderouin, who has abandoned it. I'm very unclear how this process works, and I'm confused. I applied a while back to maintain this extension, and successfully had a git repo created for that, so I thought I was the maintainer, though I haven't made time to work on it yet.

My intention was to check in a completely new piece of code in place of the existing extension, since I've written a new MultiUpload interface as part of a different project. Here's a demo video: https://www.youtube.com/watch?v=4d90Tt5EGAc

Do you want to do something different with MultiUpload? Would it be better for me to create a new, separate extension and leave MultiUpload to you?

Thanks!

This post was posted by Lee Worden, but signed as Wonder.

Sorry, I didn't see this message, you can do whatever you want with that extension, you can even become the maintainer if you wish.

Your recent page move from API:Recentchanges to API:RecentChanges breaks the convention of other pages. We're not using the internal name, as far as I know, we're using the command. Take, for example, API:Usercontribs, which is not only lower-case, but if we were using the internal name, would actually just be "Contributions" once you strip off the "ApiQuery". Or were you referring to a different internal name that I'm not thinking of?

i want to change my username. could you proceed it?

This post was posted by Francis McLloyd, but signed as Україна.

Why do you make a disconnect form SUL and why didnt you change my username globaly?

He can't. You must do this on all wikis, sorry :'(. Extension:CentralAuth does not support global renames.

The question I have is here, and I though you might be able to help with it.

This post was posted by Lieutenant S. Reznov, but signed as Inquisitor Ehrenstein.

I just replied to you at Project:Requests.

This post was posted by Lieutenant S. Reznov, but signed as Inquisitor Ehrenstein.