fsfe-website/events
Besnik Bleta 06fad62663
the build was successful Details
Adding new items in events section
2018-04-16 22:48:20 +03:00
..
2004 tagging update 2014-08-20 12:11:13 +00:00
2005 tagging update 2014-08-20 12:21:38 +00:00
2006 tagging update 2014-08-20 12:21:38 +00:00
2007 tagging update 2014-08-20 12:21:38 +00:00
2008 updated e-mail address 2017-03-12 09:57:58 +00:00
2009 tagging update 2014-08-20 12:26:08 +00:00
2010 changed full qualified links to relative links for fsfeurope.org (redirecting to fsfe.org) and fsfe.org 2017-06-16 12:33:35 +00:00
2011 changed hyperlink from members.*.html to team.html 2017-06-16 12:23:34 +00:00
2012 changed hyperlink from members.*.html to team.html 2017-06-16 12:23:34 +00:00
2013 Adding the recent changes to the right branch 2018-01-23 21:20:41 +02:00
2014 removed translation of front-page 2017-06-02 15:49:10 +00:00
2015 Lower-casing the names of days and months; typo fixing; cosmetic changes; consistency changes 2018-01-03 16:04:31 +02:00
2016 Lower-casing the names of days and months; typo fixing; cosmetic changes; consistency changes 2018-01-03 16:04:31 +02:00
2017 Merge PR #108 2018-01-24 09:05:38 +01:00
2018 Adding new items in events section 2018-04-16 22:48:20 +03:00
clt removed the CLT hotel form (left a explanatory message rather than deleteing the page) 2012-03-11 17:30:57 +00:00
README added info on tagging. 2012-02-25 00:13:35 +00:00
SFD-2010.el.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 2010-12-22 13:58:53 +00:00
SFD-2010.en.xhtml adding Bonn's summary 2010-09-21 15:39:51 +00:00
divide-and-reconquer.png svn path=/trunk/; revision=16272 2010-08-06 10:27:19 +00:00
events.ca.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.da.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.de.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.el.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.en.xhtml implementing coc 2018-03-12 16:09:03 +01:00
events.es.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.fi.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.fr.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.hr.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.hu.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.ics.xsl DTEND not needed for full day events. 2016-12-05 08:08:24 +00:00
events.it.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.nb.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.nl.xhtml adding dutch translations 2018-04-09 15:48:54 +02:00
events.pl.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.pt.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.ro.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.rss.xsl - repair rss+ics generation for events 2013-01-18 00:45:24 +00:00
events.ru.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.sources Remove feature to feed event entries from the wiki 2018-03-12 12:57:18 +01:00
events.sq.xhtml updating them withCoC reference 2018-04-05 11:36:39 +02:00
events.sr.xhtml bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
events.xsl bugfix: do not add nested <body> structure by accident 2016-05-28 10:53:41 +00:00
fscons-2010.el.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 2010-12-22 13:58:53 +00:00
fscons-2010.en.xhtml svn path=/trunk/; revision=17057 2010-09-24 10:09:12 +00:00
fscons-2010.png svn path=/trunk/; revision=16272 2010-08-06 10:27:19 +00:00
fscons-2010.pt.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 2010-12-22 13:58:53 +00:00
sfd-2010.png material for event page SFD 2010-09-03 13:29:42 +00:00

README

EVENTS GUIDELINES: How to write a good event entry?
---------------------------------------------------

Event entries appear on our website start page if they are tagged with
"front-page" [1]. It is important to make sure that they are well designed and
give visitors sufficient information to decide if if they want to go there.

The events are maintained over the SVN from our website. The events are stored
under events/YYYY/. More information on how to get access to the website can be
found on our webmaster website
<http://www.fsfe.org/contribute/web/web.en.html>.

== The event entry ==

An event entry is a file with the name "event-YYYYMMDD-01.en.xml". Where 
- YYYY is the year
- MM is the month
- DD is the day
- 01 is the number of the event on that day. The second event will have 02, ...
- en is the language code

In case of a multi day event, take the start date to determine the file name.

== Content of the file ==

The content of this files look like that:

<?xml version="1.0" encoding="utf-8"?>
 
<eventset>
  <event start="YYYY-MM-DD" end="YYYY-MM-DD">
    <title>Name of the Event, City, Country</title>
    <body>
      Information in one paragraph.
    </body>
    <page>http://www.luga.de/Aktionen/LIT-2009/</page> 
  </event>
</eventset>

== General information ==

=== What should be highlighted? ===

When we write an event entry, we should make sure that -- besides the date --
it describes 1) why FSFE is promoting this event, 2) WHERE _exactly_ is this event taking
place, WHAT do you have to pay to get it, WHEN will be the speech. 

1) Why are we promoting this event: Events entries appear on the start page. We
should take care of them. Sometimes, the only reason we are promoting an event
is because someone from FSFE is participating (giving a speech, a
conference...) then the event entry should say who, what his position is and
what the talk will be about.

2) Where this event takes place: In the title, make sure that the place where
the event is taking place is mentioned. For instance, "FSCONS 2009, Göteborg,
Sweden". More details should be brought in the description. Please also enter
street name and number so people find the event without having to look for that
information somewhere else.

Is this event open to public? Do you have to pay an admission fee? This
question should be answered in the description.

 - Speaker(s) (mandatory, maybe as link)
 - Title/Summary of speech/conference (mandatory)
 - Language of speech/conference (mandatory)
 - Start and end time of speech/conference (mandatory)
 - Expected audience (optional)
 - Possible link to preparatory/additional information (optional)

== Terminology ==

Whenever an event uses a terminology we do not encourage, like Open Source,
intellectual property or Linux instead of GNU/Linux; the event entry should
avoid this terms. And if necessary, e.g. when it is in the title it should be
quoted to avoid confusion.

=== Example ===

Open Source Day, Göteborg, Sweden [2009-11-13]

Adriaan de Groot and Karsten Gerloff will speak at [[this event dedicated to
how open source can increase profitability | link to the event]] by cost
reduction for small and medium-sized businesses. The seminar is organized by
Resource Point AB, a consulting firm focused on open source, in collaboration
with Informator and FSCONS, which is a meeting place for the propagation of
Free Software.

-------
Should be replaced with
-------

"Open Source Day," Göteborg, Sweden [2009-11-13]

Adriaan de Groot and Karsten Gerloff will speak about business case studies and
Free Software licenses at this event preceding FSCONS. The event takes place in
Göteburg at the World Culture Museum, Södra vägen 54, Gothenburg from 12.00 to
17.30. Attendance fee is 995 SEK (you get 30% rebate at FSCONS).

== Difference betweeen <page> and <link>

For links to external event pages we use <page> as for links to FSFE's websites
we use e.g. <link>http://wiki.fsfe.org/groups/Berlin</link>. The difference is
that the links with <page> do not appear on the start page but only on
http://www.fsfe.org/events, and are thus less strongly advertised, while the
links with <link> also appear on the start page.

[1] http://fsfe.org/contribute/web/tagging.en.html