-------- Message transféré --------
Sujet : [retrocomputing devroom] FOSDEM 2019 - Retrocomputing DevRoom CfP
Date : Sun, 28 Oct 2018 23:12:58 +0100
De : Pau Garcia Quiles <pgquiles(a)elpauer.org>
Pour : FOSDEM visitors <fosdem(a)lists.fosdem.org>
Copie à : retrocomputing-devroom(a)lists.fosdem.org
FOSDEM 2019 - Retrocomputing DevRoom Call for Participation
FOSDEM is a free software event that offers open source communities a
place to meet, share ideas and collaborate. It is renown for being
highly developer-oriented and brings together 8000+ participants from
all over the world. It is held in the city of Brussels (Belgium).
FOSDEM 2019 will take place during the weekend of February 2nd-3rd
2019. More details about the event can be found at
CALL FOR PARTICIPATION
After last year's success, the Retrocomputing DevRoom will be back in
2019, with talks about use of older computing hardware and software in
Presentation topics could include but are not limited to:
- Emulation of old systems to run videogames, legacy software, etc
- New software, hardware or related to be used with classic systems
- Open source software emulation/simulation
- Open hardware
- Operating systems/executives for retrocomputers/retrosystems
- Uses of retrocomputing today
- Other retrosystems topics
- Opportunities in retrocomputing
You are not limited to slide presentations, of course. Be creative.
However, FOSDEM is an open source conference, therefore we ask you to
stay clear of marketing presentations. We are not afraid of technical
stuff: devrooms are a place for development teams to meet, discuss,
hack and publicly present their project’s latest improvements and
If you will have special needs for your talk (e. g. because you will
need to plug some sort of a system), please note that clearly in your
proposal so that we can provide it.
You can use the Wikipedia definition of retrocomputing as a reference
definition to see if you talk qualifies, although it is not exclusive:
- 30 November 2018: submission deadline for talk proposals
- 16 December 2018: announcement of the final schedule
- 2 February 2019: Retrocomputing DevRoom
Use the FOSDEM Pentabarf tool to submit your proposal:
- If necessary, create a Pentabarf account and activate it. Please
reuse your account from previous years if you have already created it.
- In the "Person" section, provide First name, Last name (in the
"General" tab), Email (in the "Contact" tab) and Bio ("Abstract" field
in the "Description" tab).
- Submit a proposal by clicking on "Create event".
- Important! Select the "Retrocomputing DevRoom" track (on the
"General" tab). If you do not select a track, then nobody, from any
track, will look at your submission!
- Provide the title of your talk ("Event title" in the "General" tab).
- Provide a description of the subject of the talk and the intended
audience (in the "Abstract" field of the "Description" tab)
- Provide a rough outline of the talk or goals of the session (a short
list of bullet points covering topics that will be discussed) in the
"Full description" field in the "Description" tab
- Provide an expected length of your talk in the "Duration" field,
including discussion. The default duration is 30 minutes.
Please note neither FOSDEM nor the Retrocomputing DevRoom will
reimburse any expenses you incur
RECORDING OF TALKS
The FOSDEM organizers plan to have live streaming and recording fully
working, both for remote/later viewing of talks, and so that people
can watch streams in the hallways when rooms are full. This requires
speakers to consent to being recorded and streamed.
If you plan to be a speaker, please understand that by doing so you
implicitly give consent for your talk to be recorded and streamed. The
recordings will be published under the same license as all FOSDEM
Hope to hear from you soon! And please forward this announcement.
The Retrocomputing DevRoom is managed by Pau Garcia Quiles
(retrocomputing-devroom-manager at fosdem.org).
A mailing list of speakers, audience and the curious is available,
please subscribe at:
Pau Garcia Quiles
retrocomputing-devroom mailing list
how much netsurf willing to handle and support to be used for privacy
i tried it with I2P , and i found it working good with 3.6 installed
from debian repo.
but wonder if the browser leaky by default or not. if so, any willing to
make to happen for secure,private browsing?
Im trying to build netsurf in debian using these instructions:
but when i reach this step:
$ cd netsurf
To build the native front end (the GTK front end on Linux, BSDs, etc)
you could do:
it gives me this message:
M.CONFIG: JPEG (libjpeg) enabled (NETSURF_USE_JPEG := YES)
M.CONFIG: PDF export (haru) disabled (NETSURF_USE_HARU_PDF := NO)
M.CONFIG: glibc internal iconv enabled (NETSURF_USE_LIBICONV_PLUG
PKG.CNFG: CSS (libcss) failed
Makefile:521: *** Unable to find library for: CSS (libcss). Stop.
i tried to download the source code and done the same steps , i got the
I just noticed when testing a beta website in NS that doing
with foo.svg having only a viewPort but no width and height attributes
seems to render as 1x1 image. Shouldn't it fallback to the viewport boungs?
On Debian Sid here with gcc-8 being the default, I have this error with
expr: syntax error: expecting ')' instead of '6'
expr: syntax error: expecting ')' instead of '1'
This is because gcc -dumpversion returns only "8".
It seems this is expected output, cf.
So it should use -dumpfullversion -dumpversion
(both, as older gcc don't know about the first option.)
Just to let everyone know, I am porting some stuff to Windows from Linux. I
use the MSYS2 enviornment to make mingw-w64 packages and there is quite a
lot of software ported. I have done some work on some netsurf libraries to
this. This includes making .DLL's or shared libraries for Windows.
To do this, I've been using Cmake and I've had some success that I want to
share with everyone here This is stuff I willing contribute in to this
project in order to help get netsurf stuff available for Windows, Win32, and
possibly something like CygWin or even MSYS2.
The Cmake build system should also work on OS/X which I don't have as well
as some other things. It might even be possible to use Cmake to cross
compile to things like Android.
To start off with, here is an updated version of the CMakeLists.txt file I
wrote for LibParseUtils. An older version is available at (
https://bugs.netsurf-browser.org/mantis/view.php?id=2621 ) You would place
this in the root directory.
Hopefully, the CMakeLists.txt file in this message is received.
Some notes about this version. This one does change the pkg-config file
generated to require iconv in some cases where it's not part of the system.
Test .EXE's are build ONLY if testing is enabled.
I do want to encourage you to include this CMakeLists.txt in your
distribution. I am pleased to report that The tests complete at 100%
including the iconv and non-iconv versions. IN addition, I also was able to
make a fallback for earlier cmake versions to use iconv.
IIconv is rather a special dependency because in Linux, the iconv functions
are located in the RTL. In windows, this is not the case but there are
implementations of it so when building such such acases, the pkg-config file
has to list. As a requirement.