Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
suhrj 7659134b75 added new event 2 years ago
..
2004 tagging update 5 years ago
2005 tagging update 5 years ago
2006 tagging update 5 years ago
2007 tagging update 5 years ago
2008 updated e-mail address 2 years ago
2009 tagging update 5 years ago
2010 changed full qualified links to relative links for fsfeurope.org (redirecting to fsfe.org) and fsfe.org 2 years ago
2011 changed hyperlink from members.*.html to team.html 2 years ago
2012 changed hyperlink from members.*.html to team.html 2 years ago
2013 changed hyperlink from members.*.html to team.html 2 years ago
2014 removed translation of front-page 2 years ago
2015 fix various faulty pages 3 years ago
2016 Dutch translation of event 2 years ago
2017 added new event 2 years ago
clt removed the CLT hotel form (left a explanatory message rather than deleteing the page) 7 years ago
Makefile restructured premake 2 years ago
README added info on tagging. 7 years ago
SFD-2010.el.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 8 years ago
SFD-2010.en.xhtml adding Bonn's summary 9 years ago
divide-and-reconquer.png svn path=/trunk/; revision=16272 9 years ago
events.ca.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.da.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.de.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.el.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.en.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.es.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.fi.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.fr.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.hr.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.hu.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.ics.xsl DTEND not needed for full day events. 2 years ago
events.it.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.nb.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.nl.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.pl.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.pt.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.ro.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.rss.xsl - repair rss+ics generation for events 6 years ago
events.ru.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.sources use of wiki event fetcher 2 years ago
events.sq.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.sr.xhtml bugfix: do not add nested <body> structure by accident 3 years ago
events.xsl bugfix: do not add nested <body> structure by accident 3 years ago
fscons-2010.el.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 8 years ago
fscons-2010.en.xhtml svn path=/trunk/; revision=17057 9 years ago
fscons-2010.png svn path=/trunk/; revision=16272 9 years ago
fscons-2010.pt.xhtml merged all updated data from trunk into design, at revision 18962. build works on my machine 8 years ago
sfd-2010.png material for event page SFD 9 years ago

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