MOTD

[lukego]

Define a simple workflow for writing and maintaining notes about how a given lab machine is being used.

For example have a file /etc/motd that is automatically displayed when users login and which can be edited locally by users of a given machine.

Example contents could be:

2016-02-20: Luke is running heavy benchmarks on this machine during this week.
            This may cause the lab lock to be held for hours at a time.

[domenkozar]

It would be easier to have motd file versioned in snabblab-nixos, do you think that would work? I can implement it in 2 minutes :)

[lukego]

How will people update it? This has to be optimized for convenience so that people will use the file to announce/deannounce their activites.

[lukego]

(Giving everybody commit access to snabblab-nixos and making everybody comfortable with deploying changes is probably a good idea, on reflection. Having to push the motd update to github is a little less convenient than editing it locally but could be a more maintainable workflow.)

[domenkozar]

Sooner or later most of changes will go to snabblab-nixos and I believe it's better to get everyone used to that from the beginning. There will be a motd file in the repository, so by clicking the edit button github will fork and propose to submit a PR.

If you think that's too controversial to start with, we can also start with /etc/motd :)

[lukego]

Sounds reasonable.

How do we make the repo write-accessible to everybody? Just add all known contributors to a new access group with write access to snabblab-nixos repo? If so I think you should be able to do this: you have admin rights.

[domenkozar]

@lukego deployed motd, could we maybe move snabblab back to snabco organization? If I understand correctly permissions were an issue with Slack, but that was fixed by Github if I remember correctly?