Weekly meeting
by Marius Vollmer
=================
#cockpit: meeting
=================
Meeting started by mvollmer at 13:01:38 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2017-08-28/meeting.2017-08-28-1...
.
Meeting summary
---------------
* Agenda (mvollmer, 13:01:43)
* Applications (mvollmer, 13:04:31)
* any other business (mvollmer, 13:15:10)
Meeting ended at 13:20:23 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mvollmer (26)
* dperpeet (6)
* zodbot (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 1 month
Workshop in Berlin
by Lars Karlitski
Hi!
We're organizing a Cockpit workshop in the two days preceding All
Systems Go! conference [1] in Berlin — on the 19th and 20th of October.
The idea is to bring the Cockpit community together to help each other
out in various areas relating to Cockpit. For example, getting started
writing a module, tackling beginner tasks, or understanding Cockpit's
general architecture.
If you're interested, please let us know (either on this list or to me
directly) that you're planning on coming and which topics you'd like to
learn or teach about. This will help us to plan accordingly.
Also, spread the word if you like the idea!
Cheers
Lars
[1] All Systems Go! is the more broad successor to last year's
systemd.conf:
https://all-systems-go.io/
6 years, 2 months
Cockpit's javascript debuginfo map files
by Stef Walter
ignatenkobrain asked on #cockpit to describe our requirements around
javascript debuginfo so those can be taken into account in efforts such as:
https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo
Here they are:
* Cockpit is written mostly in javascript.
* This javascript runs in the browser. The browser may not be
a Linux system. This means Cockpit code as installed in Fedora
Debian or Ubuntu is actually running on a Mac, Windows, or Linux.
* Browsers load .map files that live next to the javascript .js
files which are loaded. They make an HTTP request for this data.
* Cockpit assets loadable by the browser are placed in
/usr/share/cockpit/<package>/ directories
This is documented here:
http://cockpit-project.org/guide/latest/packages.html
* The map files should be available for loading into the web browser
when cockpit-debuginfo is installed in order to provide assistance in
debugging Cockpit.
* The map files are not architecture specific, but are tightly bound
to the Cockpit javascript that is installed.
* The map files are produced by a myriad of technologies. In Cockpit's
case these are 'webpack', 'uglify-js' and 'less'. These technologies
change rapidly over time, as does much about javascript :S
* There are also map files for stylesheets and other loadable
assets on the page. These non-javascript debuginfo should be
handled in the same way.
More info:
https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
File format:
https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
Hope that helps,
Stef
6 years, 2 months