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.

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

Invoke-SqlCmd2 going forward #28

Open
RamblingCookieMonster opened this issue Aug 1, 2020 · 1 comment
Open

Invoke-SqlCmd2 going forward #28

RamblingCookieMonster opened this issue Aug 1, 2020 · 1 comment

Comments

@RamblingCookieMonster
Copy link
Collaborator

Some questions!

  • Do you still want to maintain this externally to dbatools? Personally I would suggest keeping it, even if it gets less attention, as it is a far smaller dependency for a variety of tasks
  • Governance stuff - who has access to merge, is approval required for merging and by who or how many folks, etc.
  • Publishing - This is tied to my powershellgallery account. I would be totally happy to transfer it to you all!

I'm happy to do a one time publish again, but I rarely see this and so things will go a long time between publishing it if we don't transfer it to you all

Thanks!

@niphlod
Copy link
Contributor

niphlod commented Aug 26, 2020

hi @RamblingCookieMonster , I was just popping here after reading in RamblingCookieMonster/PowerShell#20 and saw this. We need to put a little bit of work to continue maintaining this, and unfortunately when I promised to @potatoqualitee to spend a bit of time on this I was drawn away by real life.
I'm starting now to regain a bit of control of my free time and would really like to fix this once and for all going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants