We have 76 bug fixes slated for Gramps 6.1. Regardless of what the FamiliySearch status is, we should proceed normally: merging bugs, and releasing release-candidates:
The FS integration seems to have put a major hurdle in our normal process, where I don’t think it needs to. We are going to really have to adjust our process to meet an October release goal for Gramps 6.2.
I am extremely disappointed with the lack of progress with the FamilySearch integration. I have requested that @SourceAirbender be given admin access to our web server. However, since the project is run by volunteers, I can’t really put any pressure on people and I’m unwilling to do the job myself at this time.
Instead of taking on more work myself, I will look at the 76 outstanding bug fixes. I’ll probably just either approve or reject them and let others do the work of testing and merging.
Version 6.1 was always intended as an extra release that we needed for the FamilySearch integration. I did mention at the beginning that it may never make it past the beta stage. If we do decide to continue with v6.1, then it may be sensible to delay v6.2 for a couple of months.
I’m surprised as well. This middleware has been done since April, all we need is one of the GRAMPS web admins to install it, and I’m happy to do it myself but someone needs to give me access to do that. All that’s left is to install the already working middleware and have our meeting with Gordon. We’re basically already finished.
@Nick-Hall Maybe I could purchase a server to have it exclusively serve as the foundation’s middleware for now while we wait? You’d have to email Gordon and ask him to change the callback URL for the foundation’s Beta Key, though. I don’t mind the incurred cost for a few months. What are your thoughts?
@Nick-Hall and @gramps-project
The main server hosting that the Gramps-project.org uses for WordPress, MediaWiki, MantisBT, and Sphinx community service is already frequently hit by DDoS attacks that Cloudflare blocks.
Will the traffic to this middleware aggravate that frequency? Would it be a good idea to contract separate hardware (domain? dedicated IP? SSL certificate?) with our hosting for it?
(Maybe we could use such separate hosting to put up a Gramps Web instance where a shared example.gramps could evolve. @DavidMStraub would that have multiple uses?)
I have tried to gain access to our web server using some account details that @bmatherly gave me. Unfortunately, they do not work.
If we cannot gain access then setting up a new server is our only option. It is not a bad idea anyway.
Just finished setting up the foundation middleware. Now we just need to ask Gordon to setup the redirect for the FS oauth
Any progress? It is hard to test new features without access.
The Windows AIO build is failing. Perhaps one of our Windows experts would look at it for us.
I’m creating a fix: Make maclocale_test independent of the host locale module by dsblank · Pull Request #2505 · gramps-project/gramps · GitHub
It is basically just a bad test (testing a windows locale in a mac environment). Should be ready for review shortly.
Tests now passing 
Is there anything new to report?
When is it happening?
This is more exciting than a crime movie…
Just finished the meeting with the FamilySearch Rep and we’re good to go to start Beta access on their end. Whenever @Nick-Hall decides to start we can do the access request roll out