Communication of rules / policies and changes

[hrdl-github]

We received complaint that we don't communicate our policies clearly (e.g. the maximum number of concurrent jobs, which I haven't even heard about). Should we improve our current process and if so, how? Here are a few ideas:

• Additional section / page on GitHub pages, if public visibility is not an issue
  • Current policy / important information
  • Changelog archiving all announcements of the mailing list

[orting]

This is one complaint after one instance of not communicating policies? We had to make temporary restrictions due to increased load from corona lockdown. After a while we got more machines online and did not explicitly revoke the temporary policy. The current policy is as stated in the welcome mail, which is basically "play nice". We should be careful about how we spend our resources. Cluster work is my lowest priority and phd duty hours should be tracked so they will not exceed the budget (mine was 50 in total and I spent much more). Dont know what Oswins deal is, but I guess other things are also more important. If people want better communication they can hire someone to do it or do it themselves. Silas tir, 30 06 2020 kl. 06:27 -0700, skrev lennonhill:

…

We received complaint that we don't communicate our policies clearly (e.g. the maximum number of concurrent jobs, which I haven't even heard about). Should we improve our current process and if so, how? Here are a few ideas: Additional section / page on GitHub pages, if public visibility is not an issue Current policy / important information Changelog archiving all announcements of the mailing list — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.