This is an archive of past discussions with User:Greatedits1. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
By the way, the above list was generated using
this Petscan query. It can be easily modified by changing the date. The data page (under the Output tab) also has options for receiving the data in CSV or tabbed format, which some operating systems automatically load into a spreadsheet program for ease of use, such as copying and pasting the desired column (like page names).
Last issue, I mentioned there would be a flood, and so, here it is...
Portals status
We now have 4,620 portals.
And the race to pass 5,000 by year's end is on...
Can we make it?
The New Year, and the 5,001st portal, await.
( New portals are created with {{subst:Basic portal start page}} or
{{subst:bpsp}} )
Evad is back!
After disappearing in mid-thread, Evad37 has returned from a longer than expected wikibreak.
Be sure to welcome him back.
Improved cropping is coming to Portal image banner
User:FR30799386 is working on making {{Portal image banner}} even better by enabling it to chop the top off an image as well as the bottom.
Many pictures aren't suitable for banners because they are too tall. Therefor, User:FR30799386 added cropping to this template, so that an editor could specify part of a picture to be used rather than the whole thing.
Upgrade of flagship portals is underway
Work has begun on upgrading Wikipedia's flagship portals (those listed at the top of the Main page).
Work continues on the other five. Feel free to join in on the fun.
Spotting missing portals that are redirects
In place of many missing portals, there is a redirect that leads to "the next best topic", such as a parent topic.
Most of these were created before we had the tools to easily create portals (they used to take 6 hours or more to create, because it was all done manually). Rather than leave a portal link red, some editors thought it was best that those titles led somewhere.
The subjects that have sufficient coverage should have their own portals rather than a redirect to some other subject.
Unfortunately, being blue like all other live links, redirects are harder to spot than redlinks.
{{Portal image banner|File:American Falls from Canadian side in winter.jpg | [[Niagara falls]], from the Canadian side |maxheight=175px |overflow=Hidden|croptop=10}}
...there is plenty else to do in addition to building new portals:
The new portals need to be linked to from the encyclopedia.
On those portals about subjects that are not typically capitalized, the search parameters need to be refined/expanded, to maximize the chances of Did you know and In the news items being found and displayed.
A Recognized content section needs to be added to each portal that has a corresponding WikiProject.
Addition of a category on those portals that lack a subject category.
Implement the portal category system, adding the appropriate categories to each portal.
Upgrade, and complete (as per the tasks enumerated above), the old-style portals that are not regularly maintained, which have not been converted yet (about 1,100 of them).
Find and fix the remaining bugs in the underlying lua modules.
Build portal tools (scripts) to assist in the creation, development, and maintenance of portals.
Build a script to help build navbox footer templates, via the harvesting of categories, amongst other methods.
Update the portal building instructions.
Update the portal guideline.
Refine the programming of the portals to reduce their load time.
Design and develop the next generation of portals and portal components.
DannyS712 has created a user script prototype, User:DannyS712/Cat links, that can pull members from a category, a functionality we've been after since the project's revamp last Spring. Now, it's a matter of applying this technique to scripts that will place the items where needed, such as with a section starter script and/or portal builder script.
If you find any other portals that stand out, please send me the links so I can include them in the next issue. Thank you.
Conversion continues
There are about 1100 portals left in the old style, with subpages and static excerpts. As those are very labor intensive to maintain (because their maintenance is manual), all those except the ones with active maintainers (about 100) are slated for upgrade = approximately 1000. We started with 1500, and so over a quarter of them have been processed so far. That's good, but at this rate, conversion will take another 3 years. So, some automation (AWB?) is in order. We just need to keep at it, and push down on the gas pedal a bit harder.
You can find the old-style portals with an insource search of "box portal skeleton".
As you know, thousands of the new portals are orphans, that is, having no links to them from article space. For all practical purposes, that means they are not part of the encyclopedia yet, and readers will be unlikely to find them.
What is needed are links to these portals from the See also sections of the corresponding root articles.
Dreamy Jazz to the rescue...
Dreamy Jazz has created a bot to place the corresponding category link to the end of each portal (if it is missing), and place a link to each portal in the See also section of the corresponding root articles.
That bot, named User:Dreamy Jazz Bot, is currently in its trial period performing the above described edits!
Dreamy Jazz Bot has been approved and is now up and running.
What it does is places missing links to orphaned portals. It places a link in the See also section of the corresponding root article, and it puts one at the top of the corresponding category page.
We have thousands of new portals that have yet to be added to the encyclopedia proper, just waiting to go live.
When they do go live, over the coming days or weeks, due to Dreamy Jazz Bot, it will be like an explosion of new portals on the scene. We should expect an increase in awareness and interest in the portals project. Perhaps even new participants.
Get ready...
Get set...
Go!
Another sockpuppet infiltrator has been discovered
User:Emoteplump, a recent contributor to the portals project, was discovered to be a sockpuppet account of an indefinitely blocked user.
When that happens, admins endeavor to eradicate everything the editor contributed. This aftermath has left a wake of destruction throughout the portals department, again.
The following portals which have been speedy deleted, are in the process of being re-created. Please feel free to help to turn these blue again:
The Ref desks survived the proposal to shut them down
You might be familiar with the Ref desks, by their link on every new portal. They are a place you can go to ask volunteers almost any knowledge-related question, and have been a feature of Wikipedia since August of 2005 (or perhaps earlier). They were linked to from portals in an effort to improve their visibility, and to provide a bridge from the encyclopedia proper to project space (the Wikipedia community).
Well, somebody proposed that we get rid of them, and the community decided that that was not going to happen. Thank you for defending the Ref desks!
The cleanup after sockpuppet Emoteplump continues...
The wake of disruption left by Emoteplump and the admins who reverted many (but not all) of his/her edits is still undergoing cleanup. We could use all the help we can get on this task...
Almost all of the speedy deleted portals have been rebuilt from scratch.
Prior to 2018, for the previous 14 years, portal creation was at about 80 portals per year on average. We did over 3 times that in just the past 9 days. At this rate, we'll hit the 10,000 portal mark in 5 months. But, I'm sure we can do it sooner than that.
What's next for portal pages?
There are 5 drives for portal development:
Create new portals
Expand existing portals, such as with new sections like Recognized content
Convert or restart old-style portals into automated single-page portals
Link to new portals from the encyclopedia
Pageless portals
Let's take a closer look at these...
1: Creating new portals
Portal creation, for subjects that happen to have the necessary support structures already in place, is down to about a minute per portal. The creation part, which is automated, takes about 10 seconds. The other 50 seconds is taken up by manual activities, such as finding candidate subjects, inspecting generated portals, and selecting the portal creation template to be used according to the resources available. Tools are under development to automate these activities as much as possible, to pare portal creation time down even more. Ten seconds each is the goal.
Eventually, we are going to run out of navigation templates to base portals off of. Though there are still thousands to go. But, when they do run out, we'll need an easy way to create more. A nav footer creation script.
Meanwhile, other resources are being explored and developed, such as categories, and methods to harvest the links they contain.
2: Expanding existing portals
The portal collection is growing, not only by the addition of new portals, but by further developing the ones we already have, by...
Improving and/or adding search parameters to better power the Did you know and In the news sections.
Adding more selected content sections, like Selected biographies.
Adding and maintaining Recognized content sections, via JL-Bot.
Adding pictures to the image slideshow.
Adding panoramic pics.
Categorizing portals.
More features will be added as we dream them up and design them. So, don't be shy, make a wish.
3: Converting old portals
By far the hardest and most time-consuming task we have been working on is updating the old portals, the very reason we revamped this WikiProject in the first place.
There are two approaches here:
A) Restart a portal from scratch, using our automated tools. For basic no-frills portals, that works find. But, for more elaborate portals, as that tends to lose content and features, the following approach is being tried...
B) Upgrade a portal section by section, so little to nothing is lost in the process.
And a tool in the form of a script is under development for linking to portals at the time they are created, or shortly thereafter.
5...
See below...
New WikiProject for the post-saved-portal phase of operations...
Saved portals, are portals with a saved page.
What is the next stage in the evolutionary progression?
Quantum portals.
What are quantum portals?
Portals that come into existence when you click on the portal button, and which disappear when you leave the page.
Or, as Pbsouthwood put it:
...portals that exist only as a probability function (algorithm) until you collapse the wave form by observing through the portal button (run the script), and disappear again after use...
This was a spin-off from WikiProject Portals, for the purpose of developing zero-page portals (portals generated on-the-screen at the push of a button, with no stored pages).
Implementation of the new portal design has been culled back almost completely, and the cull is still ongoing. The cull has also affected portals that existed before the development of the automated design.
Some of the reasons for the purge are:
Portals receive insufficient traffic, making it a waste of editor resources to maintain them, especially for narrow-scope or "micro" portals
The default {{bpsp}} portals are redundant with the corresponding articles, being based primarily on the corresponding navigation footer displayed on each of those articles, and therefore not worth separate pages to do so
They were mass created
Most of the deletions have been made without prejudice to recreation of curated portals, so that approval does not need to be sought at Deletion Review in those cases.
In addition to new portals being deleted, most of the portals that were converted to an automated design have been reverted.
Which puts us back to portals with manually selected content, that need to be maintained by hand, for the most part, for the time being, and back facing some of the same problems we had when we were at this crossroads before:
Manually maintained portals are not scalable (they are labor intensive, and there aren't very many editors available to maintain them)
The builders/maintainers tend to eventually abandon them
Untended handcrafted portals go stale and fall into disrepair over time
These and other concepts require further discussion. See you at WT:POG.
However, after the purge/reversion is completed, some of the single-page portals might be left, due to having acceptable characteristics (their design varied some). If so, then those could possibly be used as a model to convert and/or build more, after the discussions on portal creation and design guidelines have reached a community consensus on what is and is not acceptable for a portal.
A major theme in the deletion discussions was the need for portals to be curated, that is, each one having a dedicated maintainer.
There are currently around 100 curated portals. Based on the predominant reasoning at MfD, it seems likely that all the other portals may be subject to deletion.
An observation and argument that arose again and again during the WP:ENDPORTALS RfC and the ongoing deletion drive of {{bpsp}} default portals, was that portals simply do not get much traffic. Typically, they get a tiny fraction of what the corresponding like-titled articles get.
And while this isn't generally considered a good rationale for creation or deletion of articles, portals are not articles, and portal critics insist that traffic is a key factor in the utility of portals.
The implication is that portals won't be seen much, so wouldn't it be better to develop pages that are?
And since such development isn't limited to editing, almost anything is possible. If we can't bring readers to portals, we could bring portal features, or even better features, to the readers (i.e., to articles)...
Some potential future directions of development
Quantum portals?
An approach that has received some brainstorming is "quantum portals", meaning portals generated on-the-fly and presented directly on the view screen without any saved portal pages. This could be done by script or as a MediaWiki program feature, but would initially be done by script. The main benefits of this is that it would be opt-in (only those who wanted it would install it), and the resultant generated pages wouldn't be saved, so that there wouldn't be anything to maintain except the script itself.
Non-portal integrated components
Another approach would be to focus on implementing specific features independently, and provide them somewhere highly visible in a non-portal presentation context (that is, on a page that wasn't a portal that has lots of traffic, i.e., articles). Such as inserted directly into an article's HTML, as a pop-up there, or as a temporary page. There are scripts that use these approaches (providing unrelated features), and so these approaches have been proven to be feasible.
What kind of features could this be done with?
The various components of the automated portal design are transcluded excerpts, news, did you know, image slideshows, excerpt slideshows, and so on.
Some of the features, such as navigation footers and links to sister projects are already included on article pages. And some already have interface counterparts (such as image slideshows). Some of the rest may be able to be integrated directly via script, but may need further development before they are perfected. Fortunately, scripts are used on an opt-in basis, and therefore wouldn't affect readers-in-general and editors-at-large during the development process (except for those who wanted to be beta testers and installed the scripts).
The development of such scripts falls under the scope of the Javascript-WikiProject/Userscript-department, and will likely be listed on Wikipedia:User scripts/List when completed enough for beta-testing. Be sure to watchlist that page.
Where would that leave curated portals?
Being curated. At least for the time being.
New encyclopedia program features will likely eventually render most portals obsolete. For example, the pop-up feature of MediaWiki provides much the same functionality as excerpts in portals already, and there is also a slideshow feature to view all the images on the current page (just click on any image, and that activates the slideshow). Future features could also overlap portal features, until there is nothing that portals provide that isn't provided elsewhere or as part of Wikipedia's interface.
But, that may be a ways off. Perhaps months or years. It depends on how rapidly programmers develop them.
Keep on keepin' on
The features of Wikipedia and its articles will continue to evolve, even if Portals go by the wayside. Most, if not all of portals' functionality, or functions very similar, will likely be made available in some form or other.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Google Code-In 2019 is coming - please mentor some documentation tasks!
Hello,
Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at the English Wikipedia.
I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!
From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.
If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.