Page MenuHomePhabricator

Create project tag for EImage
Closed, ResolvedPublic

Description

EImage

Type of project:
Component

Description (read the best practices and include a sentence understandable to the public and without "This project is for tracking work related to..." noise, plus a link to further information!):
EImage is extension, which allows users to display images from external image hosts as if they were stored locally. External images may be thumbnailed/resized/framed just like local images and the syntax used is very similar to MediaWiki's Images syntax, but must feature is that, than EImage can also overlay text on top of images.

Canonical code repository URL of the project (if this project has a code base):
EImage

View policy of the project itself:
Public (default)

Event Timeline

Its project based on orphaned Extension:EImage, which I use on my wiki with combination ImageSizeInfoFunctions extension. I have repaired code for use with MW 1.39 LTS, and my plan is merge both.

Aklapper changed the task status from Open to Stalled.Mar 2 2023, 9:00 AM

Hi @Want, thanks for taking the time to report this! https://www.mediawiki.org/wiki/Extension:EImage currently says it's archived. https://www.mediawiki.org/w/index.php?oldid=4058612 points to https://github.com/Robpol86/EImage/ being read-only. Where to find the current code URL? :)

git clone https://www.thewoodcraft.org/pub/wiki/eimage.git

I have not final repository for now. Change for MW version 1.35 was only cosmetic and for MW 1.39 too. Now I do more changes, because original version use original form registration yet and in MW 1.35 was deprecated $wgAllowImageTag which is very important for my wiki, because used by extension ImageSizeInfoFunctions too.

For example using EImage you can visit page

https://www.thewoodcraft.org/wiki/index.php/Thewoodcraft.org:Registrace

and with ImageSizeInfoFunctions worked my template Images (documentation has example using)

https://www.thewoodcraft.org/wiki/index.php/Template:Image

Percentage size is a key feature for my wiki. I use my own crop.php page to prepare the images. My plan is: to combine features from both extensions into one and add custom features that can then be available for other wikis. And the EImage extension is a good base for this, as it is already very complex on its own.

By my experience is very important if is git repository maintained by Gerrit or not. As a casual developer, I don't have time to keep track of all the changes, and if it weren't for the fact that I actively use the wiki for my other projects, I probably wouldn't. Just like Robert Pooley, the original author of EImage.

My AccessControl extension has been continuously supported since 2008, and in all that time none of my wikis where I use it have had a security incident. However, many people are unaware of its use because it is intended for MediaWiki, where public content is combined with private content, and these usually have the Special:Version page disabled to prevent bots from applying exploits to a particular version of the database or PHP.

I was at Hackathon 2019 in Prague. Because I live in Prague ;-) and it was there, in collaboration with Nicolas, that the current version was created, which I have now, after 3 years of testing, integrated into the main development branch. If it wasn't for the fact that the development is in Gerrit from the very beginning, it probably would never have happened.

Hi @Want, thanks for taking the time to report this! https://www.mediawiki.org/wiki/Extension:EImage currently says it's archived. https://www.mediawiki.org/w/index.php?oldid=4058612 points to https://github.com/Robpol86/EImage/ being read-only. Where to find the current code URL? :)

I didn't want to restore the archived page until there was a repository for it.

I have not final repository for now.

Do you plan to host it in Wikimedia Gerrit or host it in Wikimedia GitLab? I think I'd first prefer a place where others could contribute to its code (though that's not a hard requirement so if you have realistic plans to move the canonical code repo location to a more public place that should be fine).

and it was there, in collaboration with Nicolas, that the current version was created, which I have now, after 3 years of testing, integrated into the main development branch

Uh, congratulations, and thanks for your patience!

Gerrit. AccessControl (maintained by me) has repo in Gerrit too. At least I will work with it more often and reduce the likelihood of forgetting how to do what again. ;-) For it my request, create new project EImage, because it's condition for repository request ( https://www.mediawiki.org/wiki/Gerrit/New_repositories/Requests )

Aklapper moved this task from Incoming to Projects to create on the Project-Admins board.

Oh, that sounds all great! Thanks! Requested public project EImage has been created: https://phabricator.wikimedia.org/project/view/6421/

(In case you need to edit the project or project workboard itself at some point and lack permissions, please see Trusted-Contributors.)

Interested people are welcome to join the project as members, and to watch the project in order to receive notifications on task updates.

If tasks are created under this new project which are about a specific codebase, please make sure to also add these codebase project tags to the tasks in addition.

Recommended practices for project and workboard management in Phabricator are available.

Feel free to bring up any questions you might have about Phabricator or about best ways to manage projects in Phabricator.

Enjoy!