J'ajoute que presque toutes les « grandes » (en nombre d'articles) éditions de Wikipédia ont supprimé ce modèle. Les anglophones ont adopté la recommandation en:Wikipedia:No disclaimers in articles qui interdit ce type d'avertissement, de même que ceux pour contenu choquant, sensible etc. Je précise que sur Wikipédia en français, le Modèle:Sensible a été supprimé depuis longtemps : il serait cohérent de supprimer également le Modèle:Spoiler. Les hispanophones ne l'utilisent plus. Les italophones l'ont supprimé, les germanophones de même, les russophones de même, les catalanophones itou. Cette tendance lourde (à laquelle résistent également les lusophones et les néerlandophones) me semble frappée au coin du bon sens.
Friday, November 18, 2011
Suppression du modèle {{spoiler}} dans wikipedia
Intéressant débat multi-lingue sur la suppression du modèle {{spoiler}} dans wikipedia:
Thursday, November 10, 2011
Making a semantic property without linking
In Semantic mediawiki I wanted to add semantic functionality to a description in order to retrieve it in a semantic search but I dind't want a link on that description (far too long and meaningless as a title page).
To add a property to a page simply edit that page (for example the page "Property:Description") and enter "This property is a [[has type::text]]." It's magic, the links don't appear anymore!
- In making a property without linking (Alex Brown) said: "sure thing - add the property has type:String or has type:Number to the property page."
- I found on Help:Type String that "Values cannot be longer than 255 characters (if you use non-Latin characters, this number might be smaller). For longer strings, use datatype Text instead."
To add a property to a page simply edit that page (for example the page "Property:Description") and enter "This property is a [[has type::text]]." It's magic, the links don't appear anymore!
Firefox moved to a rapid release cycle
Since spring 2011 Firefox has moved to a rapid release cycle that's why we see so frequent releases.
More explanations at New development channels and repositories for rapid releases:
More explanations at New development channels and repositories for rapid releases:
[Firefox had 3 updates channel]
Because the updates we put on the Nightly channel aren’t tested before they are offered to users, we use a different icon and name (“Minefield”) to indicate they are risky and not the stable Firefox most users expect.
- Nightly – builds created out of the mozilla-central repository every night. These are not qualified by QA
- Beta – builds created out of the mozilla-central repository, qualified by QA as being of sufficient quality to release to beta users
- Release – builds created out of the mozilla-central repository, qualified by QA as being of sufficient quality to release to hundreds of millions of people
While this approach has treated us well we feel there are some issues inherent in the current structure:
- The quality expectation for updates on the Beta channel is vastly higher than the updates on the Nightly channel
- Users on the Beta channel may not even know they are running pre-release (but hopefully decent) versions of Firefox
- Due to #1 above, development on the mozilla-central repository is frozen while we stabilize for an update to the Beta channel. This causes a huge backlog of patches and adds additional risk for the next beta
- 3rd parties must track Firefox development closely to know when a milestone they care about (such as feature complete, API freeze, or string freeze) is reached
- For developers, the tree rules are constantly changing on mozilla-central depending on when we last shipped an update from it
[Firefox has moved to 4 updates channels]
Because of these issues we came up with a modified process:
- Nightly – builds created out of the mozilla-central repository every night. These are not qualified by QA
- Aurora – builds created out of the mozilla-aurora repository, which is synced from mozilla-central every 6 weeks1. There is a small amount of QA at the start of the 6 week1 period before the updates are offered
- Beta – builds created out of the mozilla-beta repository, qualified by QA as being of sufficient quality to release to beta users
- Release – builds created out of the mozilla-release repository, qualified by QA as being of sufficient quality to release to hundreds of millions of people
Subscribe to:
Posts (Atom)