[Fedocal] Reminder meeting : Bodhi stakeholders' meeting
Dear all, You are kindly invited to the meeting: Bodhi stakeholders' meeting on 2018-12-18 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.freenode.net The meeting will be about: We will meet to talk about what has been going on in Bodhi development and what is currently planned for the future. There will be an open floor at the end for the airing of grievances, but only after someone pins me before the Festivus tree. The agenda is in the bodhi-stakeholders document in the Infrastructure gobby repository. Source: https://apps.fedoraproject.org/calendar/meeting/9429/ ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: interesting article on commit messages
On Sun, 2018-12-16 at 15:43 -0800, Kevin Fenzi wrote: > Saw a nice article on commit messages: > > https://juffalow.com/other/write-good-git-commit-message > > The one big easy thing I liked from it was: > > "A properly formed Git commit subject line should always be able to > complete the following sentence: if applied, this commit will subject line here>" > > I think this might be a good rule of thumb to apply to our commits, at > least in ansible repo. I'm as guilty as the next person on useless > commits, but I'm gonna try and do better. ;) if your commit message is shorter than 500 words and doesn't explain: 1) the entire history of the problem 2) the detailed nature of the fix 3) every other possible approach you considered 4) brexit you're just not trying hard enough. ...or...that might just be my philosophy. :P but yes, isolating a change of interest down to a single commit and then finding that commit message gives you absolutely no useful information at all about the *reason* for the change is one of the most annoying things I can think of. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
[Fedocal] Reminder meeting : Infra Office Hours
Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-12-18 from 18:00:00 to 19:00:00 UTC At fedora-ad...@irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/ ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Short Outage 2018-12-18
Planned Outage - Fix Raid - 2018-12-18 18:00 UTC There will be an outage starting at 2018-12-18 18:00 UTC, which will last approximately 1 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-012-18 18:00UTC' Reason for outage: Servers need to be rebooted for megacli to clear cache on replaced disk drives. Affected Services: virthost03.phx2.fedoraproject.org download03.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org db-datanommer02.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org db01.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org elections02.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org fas03.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org fedocal02.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org mm-frontend-checkin01.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org os-control01.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org os-master01.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org os-node01.phx2.fedoraproject.org virthost06.phx2.fedoraproject.org proxy101.phx2.fedoraproject.org virthost18.phx2.fedoraproject.org koschei-web02.phx2.fedoraproject.org virthost18.phx2.fedoraproject.org log01.phx2.fedoraproject.org virthost18.phx2.fedoraproject.org mailman02.phx2.fedoraproject.org virthost18.phx2.fedoraproject.org memcached02.phx2.fedoraproject.org virthost18.phx2.fedoraproject.org noc01.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7445 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: interesting article on commit messages
On 12/16/18 5:25 PM, Todd Zullinger wrote: ...snip... > One of the things I think makes sense for the ansible repo > is using the concept of the "area: " prefix for commits. > That makes it immediately clear what part of the code is > being addressed when perusing the history. > > For ansible, that's often the name of the role, so commits > working on roles/cgit would naturally start with "cgit: ..." > It makes reading the git log --oneline output very pleasant. Yeah, thats a really good idea. ;) kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: interesting article on commit messages
On Sun, 16 Dec 2018 at 18:43, Kevin Fenzi wrote: > > Saw a nice article on commit messages: > > https://juffalow.com/other/write-good-git-commit-message > > The one big easy thing I liked from it was: > > "A properly formed Git commit subject line should always be able to > complete the following sentence: if applied, this commit will subject line here>" > > I think this might be a good rule of thumb to apply to our commits, at > least in ansible repo. I'm as guilty as the next person on useless > commits, but I'm gonna try and do better. ;) Now you can all say you are guilty.. but are you Smooge-level guilty? > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: interesting article on commit messages
On Sun, 2018-12-16 at 15:43 -0800, Kevin Fenzi wrote: > I think this might be a good rule of thumb to apply to our commits, > at > least in ansible repo. I'm as guilty as the next person on useless > commits, but I'm gonna try and do better. ;) I will say that I find the whimsical nature of some of the Ansible commit messages to be entertaining. I do try to employ meaningful commit messages in Bodhi's git log, and sometimes even write a couple paragraphs detailing the reasoning behind it when appropriate. signature.asc Description: This is a digitally signed message part ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Re: interesting article on commit messages
On 17/12/18 02:25, Todd Zullinger wrote: Kevin Fenzi wrote: Saw a nice article on commit messages: https://juffalow.com/other/write-good-git-commit-message The one big easy thing I liked from it was: "A properly formed Git commit subject line should always be able to complete the following sentence: if applied, this commit will " I think this might be a good rule of thumb to apply to our commits, at least in ansible repo. I'm as guilty as the next person on useless commits, but I'm gonna try and do better. ;) Nice. It's always good to read more on making the most of git. In the hope that it's useful, there's also some good reading in the git documentation as well. Some of it is targeted specifically at the git project, but most of it is generally good advice. In particular: https://git-scm.com/docs/SubmittingPatches.html#describe-changes https://git-scm.com/docs/git-commit#_discussion are both fine guidelines. One of the things I think makes sense for the ansible repo is using the concept of the "area: " prefix for commits. That makes it immediately clear what part of the code is being addressed when perusing the history. For ansible, that's often the name of the role, so commits working on roles/cgit would naturally start with "cgit: ..." It makes reading the git log --oneline output very pleasant. I totally agree with this. Thanks for sharing the article. With luck, all the infra folks will have a light few weeks with fewer commits than normal and more time spent enjoying the day away from the screen. :) ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
