the Cockpit 0.21 release is going to be in Fedora 21 Alpha and will be
the one used for the Cockpit Test Day.
Most/all of what's cooking right now should be fair game for Fedora 21,
I'd say, so we just keep working on master as usual and make releases
from it that will then go to Fedora 21.
when you make the next release, please make sure that it is coordinated
I am afraid that the risk is high that our change to 9090 might break
Cockpit completely in Fedora 21 unless we coordinate carefully with the
If coordination is too difficult, let's just revert our change and go
back to port 1001.
In any case, there is nothing dramatically bad about going in to the
test day with Cockpit 0.20, so we can also decide to not make a release
for Fedora 21 Alpha at all.
Can you take care of this, Patrick?
Lets do another shot at the weekly IRC meeting today.
Here is a agenda. Please reply if there is anything else you want see added.
* Fedora 21 status
* Pull requests that need review or help
* Important issues that need attending
* Navigation redesign
* Atomic features
* Open floor
Time is 15:00 UTC and the place is #cockpit on freenode.
There's been lots of discussion (on IRC and elsewhere) about choice of
our default port, currently 1001. That's an unregistered port, but it's
very unlikely we could register it (doing so requires an IETF RFC).
Fedora is the first distro we're packaged in "for real" ... and the
Fedora Server WG has asked us to try and use a port that has less of a
chance of conflicting with something else in the future.
On the Cockpit side it's very important that we use a memorable port. In
fact it's one of the few ports admins will be typing repeatedly over and
The one that looks appropriate is 9090, which is for "Web System
Manager". It's pretty easy to remember and hopefully will be consistent
with some other web based consoles for other OS's.
I have just merged #1025, which puts the 'shell' module into private
scopes. (Thanks, Stef!)
Quite a bit of code has moved and much has been renamed, so you need to
carefully rebase your pull requests on the new master now.
I'll do that next for the journalctl-direct branch.
Lets have a IRC meeting next Monday 18th in #cockpit on freenode.net
I propose the time 15:00 UTC.
There is a nifty little CLI command you can run to get the corresponding
time in your own timezone:
date -d "15:00 UTC"
See you there!