changed the description 2 times within 3 minutes

@golinux looks like some of this message is for @nylen but you didn't ping him. ;)

I know on Github, when you @ping someone in an issue, they get notified by email by default.

or maybe @nylen did get notified.. I see now @golinux opened this on the @nylen fork, not the main repo...

@andy5995 Exactly. :) He was just a bit slow in responding. I will repeat here that it's a good idea and will reduce confusion to discuss changes in a git issue or #devuan-www or pm etc. before making commits.

Thanks for the follow-up. The email notifications for this issue got sent to my spam box, it looks like you may need to configure DKIM or other related arcana.

In the future I will open an issue first. However I am fine with using a merge request as a way to explore a change, knowing that it may need revision or it may not be exactly what you want. To me this is a more definitive contribution than opening an issue and it is easier for me than setting up an IRC client. Once a merge request is already open it should also be easier for you to use the GitLab review tools to suggest any needed changes.

Let's move the discussion over to https://git.devuan.org/devuan-editors/devuan-www/merge_requests/101 which is still open, and I will make another commit there to address the changes suggested here.

closed

The email notifications for this issue got sent to my spam box

I just looked again and confirmed there was no notification sent when this issue was created, only when Andy pinged me directly.

I assumed it would be since you are the main participant here. Have no idea why that didn't happen. I have been receiving all notifications.

I assumed it would be since you are the main participant here. Have no idea why that didn't happen. I have been receiving all notifications.

I think, @golinux it's because you opened the issue on his fork, instead of commenting directly on his merge request. (Though really if someone opens an issue on someone's fork, the fork owner should get notified. Maybe a Gitlab bug...)

I will repeat here that it's a good idea and will reduce confusion to discuss changes in a git issue or #devuan-www or pm etc. before making commits

Ok, if that's what you wish. But should I assume when you say "commits" that you mean "merge requests"? Because only admins can actually make commits.

I think it can sometimes be more convenient for potential contributors to make merge requests before discussion happens, because otherwise to open the discussion, someone has to mention a page and then quote some block of text. Whereas otherwise if someone submits a merge request, the affected changes can be seen and discussion can take place on the merge request itself, and it becomes easier to reference a particular line. Or if the change isn't wanted at all, the reviewer (admin) can simply close the merge request without committing it to the repo.

Some projects choose to point out something in contributor docs something like

"If you thing something should be changed, open an issue or discuss it first. If you submit a merge request, you may find that it's not wanted and it will be closed"

Which basically just gives the contributor fair warning their merge request may get closed without merging.

It's more for the case when a contributor sees something very obvious that should be changed and is confident that their merge request will not be closed without discussion.

In the 4+ years I've been maintaining the website, I have never seen a discussion on a merge request so it never occurred to me to do so. Content/changes were discussed refined elsewhere and then I put them on the site. So this is a new workflow for me and it's going to take some time for me to adapt. I am easily overwhelmed and it's been a little stressful dealing with new contributors who are used to doing things differently . . .

I can relate to getting overwhelmed and stressed.. ;) I've joined the www chat room and I'll use that, or open a git issue, if I notice anything. If there's anything I can do to help things be smooth and non-overwhelming, let me know. :)

Yes. That's much better than all those emails coming in all the time. Thanks. You'll understand better when you get to 77. :)

@nylen You might like https://www.irccloud.com/ if you don't want to bother with IRC clients.