Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move issues from SourceForge tracker to Github #8

Closed
lkoe opened this issue Jan 10, 2018 · 5 comments
Closed

Move issues from SourceForge tracker to Github #8

lkoe opened this issue Jan 10, 2018 · 5 comments
Labels
help wanted

Comments

@lkoe
Copy link
Member

lkoe commented Jan 10, 2018

Part of the activities to migrate the project from SF is to move issues (bugs, feature requests).
If possible conversations in the old tickets should be replicated.
@Bananeweizen
Copy link
Collaborator

The most recent automated tool I found is https://github.com/cmungall/gosf2github. However, I never used that myself, so I'm not sure how well the original conversion and authors are still readable. Generally, all of the new tickets will have yourself as the author.

Bananeweizen added a commit that referenced this issue Jan 20, 2018
@Bananeweizen
fix #8: modifier order quickfix not working
7f40b05 
The offset reposition calculation didn't include the indentation of the
Javadoc, there the offset was wrong by (indentation)*(javadoc lines)
bytes.

To avoid knowing the indentation, the quickfix now calculates the
modifier positions of the AST node instead, since the marker position
must be between the first and last modifier node position.
@lkoe lkoe closed this as completed in 38eae77 Jan 20, 2018
@Bananeweizen
Copy link
Collaborator

I referenced the wrong issue in my commit, therefore re-opening.

@Bananeweizen Bananeweizen reopened this Jan 21, 2018
@lkoe
Copy link
Member Author

lkoe commented Feb 22, 2018

I've come to the conclusion that I don't want to do this by myself.
Although people took the time to originally report the problem, which is appreciated, I value my own time as well.
Thus I will be closing all tickets over at SF with an appropriate comment to open a new bug/rfe here, if so desired.
Disagreement or offers to volunteer are still welcome, until the deed is done.

@Bananeweizen
Copy link
Collaborator

Seems reasonable, even if it puts additional effort on the original reporters. The benefit of this approach is a very healthy cleaning of no more reproducable or nor more important issues...

@rtack
Copy link

rtack commented May 17, 2018

could be closed as a decision has been made to not put more effort into it.

@Bananeweizen Bananeweizen closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rtack @Bananeweizen @lkoe