Event - Historique des versions

Xtof : /* Comment accepter les RSVPs */

2018-04-24T05:12:07Z

Comment accepter les RSVPs

Xtof : /* Comment fournir une UI RSVP */

2018-04-24T05:10:45Z

Comment fournir une UI RSVP

Xtof : /* Comment baliser */

2018-04-24T04:29:20Z

Comment baliser

Xtof le 24 avril 2018 à 04:26

2018-04-24T04:26:20Z

Xtof le 24 avril 2018 à 04:18

2018-04-24T04:18:41Z

Xtof le 24 avril 2018 à 04:10

2018-04-24T04:10:58Z

Voir les modifications

Xtof le 24 avril 2018 à 04:09

2018-04-24T04:09:08Z

Xtof : Page créée avec « {{:iwc:event-fr}} {{:iwc:event}} »

2017-02-24T06:32:19Z

Page créée avec « {{:iwc:event-fr}} {{:iwc:event}} »

Nouvelle page

@@ Ligne 44 : / Ligne 44 : @@
 === Comment accepter les RSVPs ===
-A site publishing event posts '''should''' <span id="Accepting_RSVPs">accept</span> [[rsvp]] [[webmentions]] and update the event's attendance information accordingly.
+Un site publiant des posts événements '''devrait''' <span id="Accepter les_RSVPs">accepter</span> les [[webmentions]] [[rsvp]] et mettre à jour l'information de participation à l'événement.
-See: http://microformats.org/wiki/rsvp
+Voir : http://microformats.org/wiki/rsvp
 === Comment accepter les invitations ===

@@ Ligne 37 : / Ligne 37 : @@
 === Comment fournir une UI RSVP ===
-Event posts should have [[webaction]] buttons for RSVP actions and inviting others. E.g. some subset of:
+Les posts d'événements devraient avoir des boutons de [[webaction]] pour les actions RSVP et inviter d'autres. Par ex. quelques sous-ensembles de :
-<code>[ Going ][ Maybe ][ Interested ][ Can't Go ][ Ignore ][ Invite ]</code> perhaps based on private vs. public events, if you've already RSVPd, or relationship with the person.
+<code>[ Going ][ Maybe ][ Interested ][ Can't Go ][ Ignore ][ Invite ]</code> peuvent être basés sur des événements public vs privé, si vous avez déjà répondu RSVP, ou en relation avec la personne.
-See [[Facebook]]'s RSVP UI:
+Voir l'UI RSVP de [[Facebook]] :
 * http://microformats.org/wiki/rsvp-examples#Facebook

@@ Ligne 16 : / Ligne 16 : @@
 == Comment faire ==
 === Comment baliser ===
-Event posts must be <span id="Marking up">marked up</span> with [[h-event]].
+Les posts d'événements doivent être <span id="Marking up">marqués</span> avec [[h-event-fr|h-event]].
-Example of an h-event with an embedded [[h-card]] for the [[p-location]]:
+Exemple d'un h-event avec une [[h-card-fr|h-card]] embarquée pour le [[p-location-fr|p-location]] :
 <pre style="line-height: 1.4em; padding: 1em; border: 1px solid #ddd; color: black; background-color: #f9f9f9; white-space: pre-wrap;">
 &lt;div class="h-event"&gt;
@@ Ligne 35 : / Ligne 35 : @@
 &lt;/div&gt;
 </pre>
 === Comment fournir une UI RSVP ===

@@ Ligne 4 : / Ligne 4 : @@
 Un '''<dfn>événement</dfn>''' est un type de [[post-fr|post]] qui en plus d'un nom de post (titre de l'événement) a une datetime de démarrage (probablement une datetime de fin) et un lieu.
-''Pour de l'information sur les [[events-fr|événements] IndieWebCamp, voir :''
+''Pour de l'information sur les [[events-fr|événements]] IndieWebCamp, voir :''
 * [[events-fr|événements]]
 == Pourquoi ==
 === Pourquoi publier des événements indie ===
-You should post events on your own site to own your events and so your friends with indieweb sites can directly [[RSVP]] to you (as well as post [[invitation]]s to others) without depending on a [[silo]] to mediate your event related interactions.
+Vous devriez poster des événements sur votre propre site pour posséder vos propres événements et par conséquent vos amis avec des sites indieweb peuvent directement vous [[RSVP-fr|RSVP]] (tout comme poster des [[invitation]]s à d'autres) sans dépendre d'un  [[silo-fr|silo]] pour une intermédiation de vos interactions en rapport avec l'événement.
-=== Why POSSE events ===
+=== Pourquoi POSSEr les événements ===
 You should [[POSSE]] copies of your events to the [[silos]] where your friends without their own indieweb sites keep track of their events and/or calendar.
 __TOC__
@@ Ligne 66 : / Ligne 66 : @@
 == Exemples IndieWeb ==
-In implementation order:
+Par ordre d'implémentation :
 === Ben Werdmuller ===
 {{benwerd}} uses [[idno]] on werd.io to post events since [http://werd.io/event/51c94deebed7de5c2386a1b4/unofficial-portland-post-indiewebcamp-meetup 2013-06-25] (right after IndieWebCamp [[2013]]!), which automatically accept RSVPs from other sites using [[RSVP]] webmentions. Events may also be [[comments|replied]] to in the same manner as notes and articles. E.g.
@@ Ligne 197 : / Ligne 197 : @@
 He's been posting [http://boffosocko.com/kind/RSVP/ RSVPs to his WordPress site] for some time as well, originally doing so manually, but later moving to using Post Kinds functionality when that became a simpler option.
-=== IndieWeb Itches ===
+=== Démangeaisons IndieWeb ===
 The following people either strongly want to implement events on their site, or are in the process of doing so, you may find some implementation clues in their notes
@@ Ligne 210 : / Ligne 210 : @@
 # POSSE (perhaps by sending a webmention) to opentechcalendar and have it create a public event copy
-== Consuming Tools And Services ==
+== Outils et Services de Consommation ==
 === Quill ===
 [[Quill]] (site/service, open source) parses for h-event in particular to:
@@ Ligne 220 : / Ligne 220 : @@
 * How? Why? Which Properties?
-=== This Week ===
+=== Cette Semaine ===
-* The [[this-week]] newsletter (service, open source) generation code consumes h-event differently, specifically for:
+* La génération du code de la newsletter [[this-week|this-week]] (service, open source) consomme différemment le h-event, spécifiquement pour :
 * start/end date info (for determining recent and upcoming events)
 * name/location - for display as such for an event
@@ Ligne 229 : / Ligne 229 : @@
 [[mf2util]] (open source python library) parses specifically for h-event vs h-entry to determine post type, and provides cleaned data to applications using it (timestamps get converted to Python types, locations are normalized, ...). An application using this is the IRC bot by {{sknebel}} that announces new Indieweb livestreams on #indieweb, which parses /events to determine on which days IWCs happen.
-=== mf2 to iCalendar ===
+=== mf2 vers iCalendar ===
 [https://github.com/gRegorLove/mf2-to-iCalendar mf2-to-iCalendar] is a PHP library that converts [[h-event]] markup to [[iCalendar]].
@@ Ligne 249 : / Ligne 249 : @@
 '''Screenshots needed'''
-=== Map image ===
+=== Image Carte ===
 Some [[silos]] event posts (e.g. [[Facebook]], [[Plancast]]) automatically generate a horizontal rectangle map view of the event location.
@@ Ligne 273 : / Ligne 273 : @@
 Time order presentation usually include some text about the RSVP, e.g. "is going", "is attending"
-==== Silo Attendees ====
+==== Participants Silo  ====
 Every event silo by default shows who else is has [[RSVP]]ed that yes they're going, and more so, often first display who <em>you know</em> that's going to the event. Quickly seeing "who else is going" or might go or is invited is a huge sense of context/comfort as well, especially with little face icons.
@@ Ligne 310 : / Ligne 310 : @@
 Event-aware destinations to consider:
-==== POSSE to Eventbrite ====
+==== POSSE vers Eventbrite ====
 [[Eventbrite]] - has best API for creating events, getting updates, perhaps backfeeding attendees etc.
 * [https://github.com/snarfed/bridgy/issues/275 Bridgy feature request: publish Eventbrite events]
@@ Ligne 348 : / Ligne 348 : @@
 * [https://github.com/snarfed/bridgy/issues/274 Bridgy feature request: publish Facebook events]
-==== POSSE to Lanyrd ====
+==== POSSE vers Lanyrd ====
 [[Lanyrd]] - has an API for creating events, getting updates, backfeeding RSVPs
 * [https://github.com/snarfed/bridgy/issues/390 Bridgy Publish feature request: POSSE to Lanyrd]
 * [https://github.com/snarfed/bridgy/issues/391 Bridgy backfeed from Lanyrd feature request]
-==== POSSE to Plancast ====
+==== POSSE vers Plancast ====
 [[Plancast]] - event-specific silo
@@ Ligne 382 : / Ligne 382 : @@
 IndieWeb Examples - real world IndieWeb experiments with POSSEing events to Twitter:
-===== Tantek POSSE to Twitter =====
+===== Tantek POSSE vers Twitter =====
 {{t}} automatically POSSEing event posts to Twitter
 * since [https://twitter.com/t/status/881540257631674369 2017-07-02] with explicit RSVP call to action (since RSVPs were in development, [http://tantek.com/2017/189/t1/rsvps-display-on-indie-events implemented just 4 days later]!) tweet text format:
@@ Ligne 510 : / Ligne 510 : @@
 # ... more?
-==== Before 2014-02-07 ====
+==== Avant le 2014-02-07 ====
 This was perhaps the pinnacle of Facebook's event page design.

@@ Ligne 1 : / Ligne 1 : @@
 [[Category:PostType]]
 {{stub-fr}}
 <span style="float:right;height:128px;font-size:128px;margin-bottom:-64px">📅</span>
-Un '''<dfn>événement</dfn>''' est un type de [[post]] that in addition to a post name (event title) has a start datetime (likely end datetime), and a location.
+Un '''<dfn>événement</dfn>''' est un type de [[post-fr|post]] qui en plus d'un nom de post (titre de l'événement) a une datetime de démarrage (probablement une datetime de fin) et un lieu.
-''For information on IndieWebCamp [[events]] themselves, see:''
+''Pour de l'information sur les [[events-fr|événements] IndieWebCamp, voir :''
-* [[events]]
+* [[events-fr|événements]]
-== Why ==
+== Pourquoi ==
-=== Why publish indie events ===
+=== Pourquoi publier des événements indie ===
 You should post events on your own site to own your events and so your friends with indieweb sites can directly [[RSVP]] to you (as well as post [[invitation]]s to others) without depending on a [[silo]] to mediate your event related interactions.
 === Why POSSE events ===
@@ Ligne 16 : / Ligne 14 : @@
 __TOC__
-== How to ==
+== Comment faire ==
-=== How to markup ===
+=== Comment baliser ===
 Event posts must be <span id="Marking up">marked up</span> with [[h-event]].
@@ Ligne 39 : / Ligne 37 : @@
-=== How to provide an RSVP UI ===
+=== Comment fournir une UI RSVP ===
 Event posts should have [[webaction]] buttons for RSVP actions and inviting others. E.g. some subset of:
 <code>[ Going ][ Maybe ][ Interested ][ Can't Go ][ Ignore ][ Invite ]</code> perhaps based on private vs. public events, if you've already RSVPd, or relationship with the person.
@@ Ligne 46 : / Ligne 44 : @@
 * http://microformats.org/wiki/rsvp-examples#Facebook
-=== How to accept RSVPs ===
+=== Comment accepter les RSVPs ===
 A site publishing event posts '''should''' <span id="Accepting_RSVPs">accept</span> [[rsvp]] [[webmentions]] and update the event's attendance information accordingly.
 See: http://microformats.org/wiki/rsvp
-=== How to accept invitations ===
+=== Comment accepter les invitations ===
 A site publishing event posts '''should''' <span id="Accepting_Invitations">accept</span> [[invitation]] [[webmentions]] and update the event's "invited" information accordingly.
 <!-- See: http://microformats.org/wiki/invitation -->
-=== How to limit capacity ===
+=== Comment limiter la capacité ===
 Some events have limited capacity and want to offer "tickets," ie only accept the first N RSVPs.
@@ Ligne 67 : / Ligne 65 : @@
 [http://indiewebcamp.com/irc/2015-11-29#t1448841891092 IRC discussion of whether/how this fits into the webmention spec.]
-== IndieWeb Examples ==
+== Exemples IndieWeb ==
 In implementation order:
 === Ben Werdmuller ===
@@ Ligne 264 : / Ligne 262 : @@
 [[File:event-map-horizontal.jpg]]
-=== Attendees ===
+=== Participants ===
 Event posts should display attendees, [[RSVP]]s in general, and [[invitation]]s.
@@ Ligne 452 : / Ligne 450 : @@
 * [https://martymcgui.re/2017/07/13/123031/ Example post]. [https://martymcgui.re/2017/07/13/123031/calendar.ics ICS File].
-== Silo Examples ==
+== Exemples de Silo ==
 === Attending ===
 {{main|Attending}}
@@ Ligne 542 : / Ligne 540 : @@
 * ...
-== See also ==
+== Voir aussi ==
 * [[events list]]
 * [[datetime]]

← Version précédente		Version du 24 avril 2018 à 04:09
Ligne 1 :		Ligne 1 :
	{{:iwc:event-fr}}		{{:iwc:event-fr}}
−
−	~~{{:iwc:event}}~~