אפשרויות בטא

This page is a translated version of the page Beta Features and the translation is 30% complete.
לthe extension, ראו Extension:BetaFeatures.

יכולות הבטא הן דרכים בהן אתה יכול לנסות יכולות חדשות בוויקיפדיה ובאתרים אחרים של קרן ויקימדיה לפני שמוצגות לכולם. עבור להעדפות שלך כדי להפעיל אפשרויות בטא עבור עצמך; זכור שיש להפעיל את האפשרויות הללו בכל אתר בנפרד.

בבקשה אפשר לנו לדעת מה אתה חושב על התוכנית הזו בדף השיחה הזה.

מטרה

המטרה המרכזית של אפשרויות בטא היא לאפשר למפתחי ומהנדסי ויקימדיה (חברי הקהילה ואנשי קרן ויקימדיה) להשיק שיפורים טכניים בממשק שבו יוכלו משתשים רבים לנסות, לתת משוב ולהשתמש באפשרויות אלו במערכת המשמשת אותם לעריכה ביום-יום.

The code to provide features like this is in an extension, BetaFeatures . Beta Features' preferences are available in a Preferences tab, accessible via the personal bar at the top of the page for all logged-in users.

Functionality

נכון להיום, משתמשים יכולים:

  • manually opt-in to individual features
  • automatically enroll in all additional features as they are subsequently released[issue 1]

To use either function, users should select the appropriate checkbox, then click “שמירה”, which will save their Beta Features preferences (like with other preferences). Every now and then new features are made available to users, as outlined at Beta Features/Roadmap .

אפשרויות בטא נוכחיות

הנה אפשרויות הבטא הנוכחיות שאנו בוחנים עם מערכת זו:

These features are only available on some wikis:

These features are beta features on some wikis while enabled for everyone on all others:

We invite Wikimedia product teams and community volunteers who want to test out new features, or significant changes to existing features, to do so through this project.


Deployed features

Other features

This list may document extensions or features that are obsolete or dormant, or are still in planning. Do not rely on the information here being up-to-date.


ליצור בעצמך

האם ברצונך ליצור בעצמך אפשרות בטא? יופי! ג'יימס ישמח להדריך אותך.

First, you should check that your code meets the following basic requirements:

  • Not significantly degrade site performance;
  • Not noticeably degrade perceived performance of the site, or the user's system;
  • Not crash the user's browser;
  • Not cause data loss, or corruption;
  • Pass basic interoperability with other Beta Features features; and[issue 2]
  • Contribute positively to the user's experience of the site, and be additive in nature. E.g. Beta Features cannot be used to remove site features or functionality without adding features meant to replace what was removed.
  • You should expect to test your new feature on the WMF pre-deploy beta server for at least one week before deploying to production. This testing period is intended to catch any serious bugs before jeopardizing users on production.

If you're happy your code meets these requirements, you should write-up your proposal on the New Features proposal page. As part of creating the Beta Feature, you will be asked for some text copy and an image to represent your feature in the user interface; the Design and Product teams can help you with this.

Appearance

The appearance of the “אפשרויות בטא” tab in Preferences is purposefully different, to both inspire interest and propose a departure from the standard layout and complexity of the existing user preferences.

Here is a screenshot of the “אפשרויות בטא” preferences tab:

 
Screenshot of the “אפשרויות בטא” preferences screen in וקטור ישן (2010).

תקלות ידועות

  1. Note that this currently doesn't enroll users until they visit the Preferences page. (phab:T64815)
  2. This is not to say that interoperability is a blocker. Interoperability issues need to be surfaced, and blocker-ness will be determined on a case-by-case basis.

קישורים חיצוניים