Heads up...
- AnyOldName3
- Posts: 2677
- Joined: 26 Nov 2015, 03:25
Re: Heads up...
In the first post of each report there's a thing at the bottom saying who originally posted it, but this isn't the case for comments on issues. I thought this was something that was being worked on. It's really hard to follow a comment chain when you can't tell who posted what.
Re: Heads up...
Apparently a lot has happened since the power to my apartment went out! People need to stop crashing their cars into power lines.
A news post would be greatly appreciated! Thanks for all this hard work to help keep people contributing to the project.
Just to be clear, if we don't have a preference one way or the other, is there one that you all would prefer that we use?
A news post would be greatly appreciated! Thanks for all this hard work to help keep people contributing to the project.
Just to be clear, if we don't have a preference one way or the other, is there one that you all would prefer that we use?
- Thunderforge
- Posts: 503
- Joined: 06 Jun 2017, 05:57
Re: Heads up...
Both GitHub and GitLab can accept code contributions equally. GitLab has the additional convenience of having the issue tracker there. But in terms of the project itself, the goal was to have both be acceptable means of contribution. Use the one you prefer.
Re: Heads up...
Can you add an ability to edit bugreports for developers?
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Heads up...
Sorry, that's just the way things are for now. It might be possible I can write a tool to automate that, but that is going to take time that I don't actually have. Full time work, four kids... etc.AnyOldName3 wrote: ↑18 Jun 2018, 01:24 In the first post of each report there's a thing at the bottom saying who originally posted it, but this isn't the case for comments on issues. I thought this was something that was being worked on. It's really hard to follow a comment chain when you can't tell who posted what.
Not that anyone else's time is more or less valuable than my own, I just have very little to give the project and the last 2 weeks, I've given lot to pick up the slack and get shit done.
This is also why I have little tolerance these days and have no problems deleting posts and banning people to help keep things technical here. There are a lot things taken care of by moderators so that developers don't have to deal with the day to day bullshit.
Re: Heads up...
This.
Also, I really agree that it's hard to follow conversations with peoples' names removed. However, do y'all expect psi29a to go through every single comment thread on Redmine and edit all those comments to include who said it? That's a little crazy, so I think it's going to have to be okay with people.
Edit: Also, tremendous work psi29a, this is awesome
Re: Heads up...
psi29a is definitely in beast mode! But, please, give him the chance to attend to his family again after this monumental migration task is done.
Regarding the comment author issue: For the time being, you can always return to the old bug tracker and read the discussions there. Future issues won't have that flaw, so the problem will eventually die out. - Of course, many of the affected issues will stay open for quite some time, so some kind of solution (e.g., putting in the name of the author) would be nice. Definitely not a task for the devs or our new admin though.
Regarding the comment author issue: For the time being, you can always return to the old bug tracker and read the discussions there. Future issues won't have that flaw, so the problem will eventually die out. - Of course, many of the affected issues will stay open for quite some time, so some kind of solution (e.g., putting in the name of the author) would be nice. Definitely not a task for the devs or our new admin though.
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Heads up...
For those wanting to get work done on the new issue tracker: https://gitlab.com/OpenMW/openmw/issues
Guests (people on GL but not a member of the project) have the ability to create issues and add comments.
For those that want to edit issues, including updating them, assigning them and eventually closing them need ask permission to join the project which can be done here: https://gitlab.com/OpenMW/openmw
One of the developers can add you as a 'Reporter'. Those wishing to have the role 'Reporter' should have either offered an MR (or PR on github) (previous contributor) or currently working on a MR (or PR).
Guests (people on GL but not a member of the project) have the ability to create issues and add comments.
For those that want to edit issues, including updating them, assigning them and eventually closing them need ask permission to join the project which can be done here: https://gitlab.com/OpenMW/openmw
One of the developers can add you as a 'Reporter'. Those wishing to have the role 'Reporter' should have either offered an MR (or PR on github) (previous contributor) or currently working on a MR (or PR).
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: Heads up...
BTW... if anyone is looking for a job where they can work from home (like I am looking):
https://about.gitlab.com/jobs/
https://about.gitlab.com/jobs/
Re: Heads up...
I have a question. With GitHub/Redmine, I would get emails for PR activity (opened/closed messages, responses, etc) even if I didn't participate in it, while for bugs I'd only get messages if I created the issue or was assigned to it. Is there some way to set up GitLab's notifications similarly? It would be nice too if I could get a notification for any specific issue message that mentions me. GitLab's Custom notification setting doesn't seem to have options for things that involve me directly (which is odd since the Participate option sets notifications only for things I've directly participated in; though that applies to everything, not just issues, so isn't adequate).