Repository Access/Transfer Ownership

[NightOwl888]

@synhershko

Hope you are well. I am working on updating the Lucene.NET dependencies to use SourceLink and we have switched to using Azure DevOps for multi-platform testing, enabling GitHub Sponsors, and fixing the invalid .pdb types that are in the latest NuGet packages. For GitHub Sponsors and Azure DevOps, I don't have permission to enable the settings on this repository.

While I could just update my spatial4n fork and do all future releases from there, it would be better if we did all of the updates in the original repository. It isn't clear whether you wish to continue maintaining this project, but either way is fine with me. It would also be fine if you wish to add your own sponsorship links to the FUNDING.yml file.

Options

1. Enable the following GitHub settings
   1. GitHub Sponsors
   2. Azure DevOps
   3. Git push access so I can update this repo
2. Transfer ownership of this repo from synhershko to NightOwl888.

In all fairness, it would be better to transfer the repo ownership so I don't have to keep coming back to you to enable settings for future GitHub features. In that case, I would be happy to keep you as a collaborator if you wish to continue contributing to this project.

[NightOwl888]

@synhershko

Thanks for making me a collaborator.

I have setup an Azure DevOps organization for Spatial4n, however I am unable to add the build and release pipelines due to insufficient permissions.

Please install the GitHub App for authentication with Azure DevOps and let me know once it is completed.

[synhershko]

I lack the authorization on Azure DevOps :)

[synhershko]

Any reason not to use github actions for this, btw?

[NightOwl888]

Any reason not to use github actions for this, btw?

We have 4 other projects that use Azure DevOps and they share similar templates. It makes it easy to manage releases of all of these components.

I sent an invitation to the Azure DevOps account to the email address in your GitHub profile. Do you have a different email address that you prefer to use for this?

[NightOwl888]

I have changed the Azure DevOps settings, inviting both your bigdataboutique and code972 email accounts.

That being said, I don't believe you actually need to login to Azure DevOps in order to install the app into your GitHub account, you simply need to configure it here: https://github.com/apps/azure-pipelines. I believe that once you install it, the fact that I have collaborator access to this repo is enough for me to setup the build and release pipelines.

[NightOwl888]

Or Click 'Run' here to create the build pipeline. Once the build pipeline is created, I should be able to configure the rest of it.

[NightOwl888]

@synhershko

It would be appreciated if you could install the Azure DevOps app and configure it with permissions to this repo (or all repos if that suits you).

Alternatively, transfer this repository to a new organization named Spatial4n and setup the permissions so I can enable the app and all features going forward. Note that many of the projects on NuGet.org are setup under an organization rather than a personal account so they don't have to go back to the account owner to enable permissions, since there is no way for the account owner to enable full control over the repository (for example, I cannot rename the master branch to main without your assistance).

https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch

[NightOwl888]

@synhershko

All of the other Lucene.NET dependencies have been released. This is now holding up the show. Is there any chance you could enable this soon?