Open clanmills opened 3 years ago
@nehaljwani: While looking for something in Exiv2's Redmine website, I noticed a couple of small things.
If I try to search on https://dev.exiv2.org/ then I get a GitHub 404 error.
Also, if I search in https://dev.exiv2.org/projects/exiv2 then I don't get any results - even for something common such as "the". The URL of the results page contains my search term but all the values in the page always reset to default.
This probably isn't used by many people but I think that the search is still a useful feature.
@postscript-dev That's expected as it is static hosting. There is no server side computation, so search won't work anymore. It is not a full Redmine deployment, as it would require a dedicated compute resource. My primary aim was to simply keep all the existing URLs working so that if any URL was indexed by a search engine, it would still work and won't throw a 404.
If it is really needed, one can write a one time automation to copy all issues to GitHub and close them and then one can use the search powered by GitHub. Unfortunately, I don't have the bandwidth to take on that task right now, at least not until mid May.
@nehaljwani: Thanks for the quick reply.
I rarely use Exiv2's Redmine website, so this isn't that important to me. Although the search is useful, unless there is a simple solution, I am happy to leave this.
@nehaljwani I really don't think it's worth spending more time on Redmine. We moved on from Redmine when v0.26 shipped in April 2017. (it's hard to believe it's 5 years ago now). What you have done seems good enough.
I'd like to echo Peter K's "Namaste" to You. Great Job, Nehal. I'm sure the rest of the gang will give @nehaljwani a round of applause. @kevinbackhouse @alexvanderberkel @hassec @Puffincloud @piponazo @paperdigits @postscript-dev
I spent another 30 minutes this morning trying to find my note to you from 2022-01-10 (or possibly 2022-01-11). Can't find it. It's somewhere.
Absolutely great work @nehaljwani!
@nehaljwani Some user feedback. No action required by you.
I find it impossible to clone the team resources over https (and therefore my book and bin directories).
/var/folders/7v/fb_nv0v142xfz_xy25rqjpf00000gn/T/smartgit7464908304192637754> git -c credential.helper=/Applications/SmartGit.app/Contents/Resources/credentials.sh clone -v --progress --branch main https://github.com/Exiv2/team.exiv2.org /Users/rmills/gnu/github/exiv2/team.exiv2.org
Cloning into '/Users/rmills/gnu/github/exiv2/team.exiv2.org'...
POST git-upload-pack (341 bytes)
POST git-upload-pack (252 bytes)
4986 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
early EOF
index-pack failed
I've cloned it with ssh by following this article: https://www.geeksforgeeks.org/using-github-with-ssh-secure-shell/
I believe it essential to use the username GIT on the git clone ssh command:
$ git clone ssh://git@github.com/Exiv2/team.exiv2.org
We've had a generous offer from Mica and/or Pat to host exiv2.org on their server. Currently it's hosted on AWS and I pay about $20/month (depends on bandwidth). Let's move the domain by the end of 2021. We should wait until after v0.27.5 ships on 2021-09-30. Let's aim for November 2021.
I am the current registered domain owner of Exiv2.org and I will totally cooperate. I'm confident Nehal (@nehaljwani) will contribute to getting this done. I think we should investigate transferring the registration for exiv2.org to Mica somebody involved with pixls.us.
The future of exiv2.org should be discussed by Team Exiv2. I think it should remain because it has unique documentation and copies of every release of Exiv2 going back to 2004. Additionally, closing exiv2.org broadcasts an incorrect and very negative message about the status of Exiv2.
The effort involved to make a release on exiv2.org can be easily reduced. Today, I build on Ubuntu, macOS/x66 MinGW, Cygwin64 and msvc2019. This can be replaced by the nightly build when it is augmented with MinGW.
If Nehal, or another Team Member, is happy to take on "Release Engineering", I will cooperate with the effort to modify the current release procedures which are here: svn://dev.exiv2.org/svn/team/website