Why is this project still on Sourceforge? The biggeset benefit I see is the ability to easily view commit history and code structure directly on the web page. So much easier to navigate than however SourceForge does it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've read the developer's preference, however, having the ability to easily watch commits as they happen is a handy feature. I've submitted little patches to a few projects just by noticing hiccups as I use the program. I can't contribute back in a casual manner with code that's behind a wall.
Sometimes it's obvious code cleanup that someone just hadn't got around to yet but are greatful for the little reorganization. Besides, it isn't like they have to accept a pull request.
Like, literally, I've just done a drive-by code cleanup on a file and said "hey, you want this?" "Sure, that's easier on the eyes." SF was nice 20 years ago but cumbersome nowadays.
I guess I can follow github forks of this code but then it doesn't make it easy to discern reasons for code changes. Just makes for less headaches all around if someone does want to contribute suggestions.
Last edit: Jordan 2015-10-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't contribute back in a casual manner with code that's behind a wall.... Just makes for less headaches all around if someone does want to contribute suggestions.
I am sure the developer is aware of the pros and cons of the various code repositories and help forums and has made a choice that suits. If another service offers advantages unavailable on Sourceforge that the developer values sufficiently, then the project might move. However, the choice of repository and help forum remains a developer prerogative.
Last edit: wellread1 2015-10-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why is this project still on Sourceforge? The biggeset benefit I see is the ability to easily view commit history and code structure directly on the web page. So much easier to navigate than however SourceForge does it.
Because it suits the developer.
I've read the developer's preference, however, having the ability to easily watch commits as they happen is a handy feature. I've submitted little patches to a few projects just by noticing hiccups as I use the program. I can't contribute back in a casual manner with code that's behind a wall.
Sometimes it's obvious code cleanup that someone just hadn't got around to yet but are greatful for the little reorganization. Besides, it isn't like they have to accept a pull request.
Like, literally, I've just done a drive-by code cleanup on a file and said "hey, you want this?" "Sure, that's easier on the eyes." SF was nice 20 years ago but cumbersome nowadays.
I guess I can follow github forks of this code but then it doesn't make it easy to discern reasons for code changes. Just makes for less headaches all around if someone does want to contribute suggestions.
Last edit: Jordan 2015-10-12
The developer's code contribution policy is casual differently.
Feature requests can be made at https://sourceforge.net/p/keepass/feature-requests/. Bug reports can be made at https://sourceforge.net/p/keepass/bugs/. Patches can be submitted at https://sourceforge.net/p/keepass/patches/
I am sure the developer is aware of the pros and cons of the various code repositories and help forums and has made a choice that suits. If another service offers advantages unavailable on Sourceforge that the developer values sufficiently, then the project might move. However, the choice of repository and help forum remains a developer prerogative.
Last edit: wellread1 2015-10-12
+1 for moving to Github since it’s faster, looks better and easier on eyes.
I think it is time to change it, we are in 2021, soon in 2022.
With this, there will be a better development.
I have opened a ticket here: https://sourceforge.net/p/keepass/bugs/2123/
And 2 tickets on GitHub:
- https://github.com/dlech/KeeAgent/issues/330
- https://github.com/dlech/Keebuntu/issues/72
Thanks in advance.
Opening tickets will not convince Dominik to move to GitHub. His reasons in the post referenced above, are clear.
If you want a code repository, see this thread.
https://sourceforge.net/p/keepass/discussion/329220/thread/02383c83/?limit=25&page=1#5904
cheers, Paul