I am starting to think about activating github issue tracking. It would probably be better that users report their issues there instead of in the forum.
If we can move all the trac issues to github and close trac then I guess that would be nice. not sure if there is some critical trac feature that we need, that github does not have yet.
otherwise.. is it ok to run trac and github in parallell? most new issues will likely be reported in github then..
what problems does that generate? a problem I envision is that in a commit we often want to say which issue it fixes and if we have two issue trackers then a simple number is not enough.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If we can move all the trac issues to github and close trac then I guess that would be nice. not sure if there is some critical trac feature that we need, that github does not have yet.
I have been trying to migrate the trac issues to a temporary repo.. no success yet but I have the feeling it can be done. I have installed the xmlrpc plugin in Trac so feel free to try it out..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there are some trac-to-github scripts.. I am testing those. It seems they are not well maintained though and require python 2.x. I have installed xmlrpc plugin in our trac so you can test it also if you like.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running trac-to-github right now .. unfortunately I have not been able to achieve more than 60 github api requests / hour so it takes a while.. I think it will take a couple weeks.. when it is done I plan to share the results and we can look at the repo..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah that's what I had noticed the one sent you was based off of an older tool, but was updated in 2019. I wouldn't mind helping. I'm would just hate to screw something up out of my lack of understanding of how track works and what your expectations of how things should look in github. I do have a raspberry pi 4 that is sitting idle. I was thinking of running cppcheck donate cpu program on it, but if there is a better use for it let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am starting to think about activating github issue tracking. It would probably be better that users report their issues there instead of in the forum.
If we can move all the trac issues to github and close trac then I guess that would be nice. not sure if there is some critical trac feature that we need, that github does not have yet.
otherwise.. is it ok to run trac and github in parallell? most new issues will likely be reported in github then..
what problems does that generate? a problem I envision is that in a commit we often want to say which issue it fixes and if we have two issue trackers then a simple number is not enough.
I have been trying to migrate the trac issues to a temporary repo.. no success yet but I have the feeling it can be done. I have installed the xmlrpc plugin in Trac so feel free to try it out..
I'm not sure if you have tried this https://github.com/svigerske/trac-to-github
there are some trac-to-github scripts.. I am testing those. It seems they are not well maintained though and require python 2.x. I have installed xmlrpc plugin in our trac so you can test it also if you like.
I am running trac-to-github right now .. unfortunately I have not been able to achieve more than 60 github api requests / hour so it takes a while.. I think it will take a couple weeks.. when it is done I plan to share the results and we can look at the repo..
Yeah that's what I had noticed the one sent you was based off of an older tool, but was updated in 2019. I wouldn't mind helping. I'm would just hate to screw something up out of my lack of understanding of how track works and what your expectations of how things should look in github. I do have a raspberry pi 4 that is sitting idle. I was thinking of running cppcheck donate cpu program on it, but if there is a better use for it let me know.