Bug on switching community from private to public

[lifenautjoe]

An Okuna user found a bug that occurs when switching a community from private to public. If you happened to deactivate the option for community members to invite new members into a private community and then switch the community to public, this setting is kept active. Meaning ppl can't invite new members to a public community and the owner can't change this setting unless he switches back to private, adjusts the setting accordingly and switches back to public again.
I could confirm and recreate this behavior in a test community I created for this purpose. (edited)

[uiboy]

hmm 🤔 i thought we were going to disable changing communities from private to public... since it could compromise comments people shared in confidence. I understand some groups may start private n then decide to go public... but we have to think about how to handle that.
Some ideas (but needs more thought in a separate issue)

• could be consensus via an agree button from the members to go public ( not scalable beyond 50 members)
• Option to have their community activity n data deleted when it goes public but stay in the community

[lifenautjoe]

Ah right. Then nvm this issue. Should be made about restricting private communities from being made public

…

On Mon, 13 Jan 2020 at 10:13, Shantanu ***@***.***> wrote: hmm 🤔 i thought we were going to disable changing communities from private to public... since it could compromise comments people shared in confidence. I understand some groups may start private n then decide to go public... but we have to think about how to handle that. Some ideas (but needs more thought in a separate issue) - could be consensus via an agree button from the members to go public ( not scalable beyond 50 members) - Option to have their community activity n data deleted when it goes public but stay in the community — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#668?email_source=notifications&email_token=ADBFXZJVMRR2PEKSJYWKHW3Q5QWEHA5CNFSM4KCWEOW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIX7TWQ#issuecomment-573569498>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBFXZL5UNHYU36GRJRRW33Q5QWEHANCNFSM4KCWEOWQ> .

[uiboy]

Made a new issue as discussed : #670
Separate issue on the handling already exists #210
closing this