Betafunksjoner

This page is a translated version of the page Beta Features and the translation is 20% complete.
For utvidelsen, se: Extension:BetaFeatures.

Betafunksjoner er en måte du kan prøve ut nye funksjoner og verktøy på Wikipedia og andre Wikimedia-sider før de er gitt til alle. Se dine innstillinger for å skru på betafunksjoner for deg selv; husk at funksjoner må aktiveres på hver side du ønsker å bruke dem på.

Fortell oss hva du synes om dette programmet på denne diskusjonssiden.

Formål

Hovedformålet med betafunksjoner er å gi Wikimedias designere og ingeniører (fra både Wikimedia Foundation og fellesskapet) muligheten til å prøve ut tekniske forbedringer i et miljø hvor mange brukere kan prøve ut, gi tilbakemeldinger og benytte seg av disse funksjonene i faktiske bruksområder. Betafunksjoner gir også en hjelpsom vei for gode tilleggsfunksjoner og andre programmeringer fra felleskapet til å bli integrert inn i kjernen av sidene gjennom undersøkelse, utprøving og gjennomgang av Wikimedia Design and Engineering.

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

Right now, users can:

  • 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 “Lagre”, 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 .

Current Beta Features

Here are the current beta features which we are testing with this system:

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.


Creating your own

Do you want to create your own Beta Feature? Great! James is happy to help guide you.

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 “Betafunksjoner” 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 “Betafunksjoner” preferences tab:

 
Screenshot of the “Betafunksjoner” preferences screen in Vector (2010).

Kjente problemer

  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.

Eksterne lenker