ethdevberlin / OIPS

Office Improvement Proposals
10 stars 1 forks source link

OIPS-23 Meta-OIP: make this repo private #23

Open gumb0 opened 4 years ago

gumb0 commented 4 years ago

Office is not really a public space, and I don't see the reason to discuss office matters in public.

I guess people differ in how much of their everyday life they are comfortable to open to the public, and to be on the safe side and make everyone comfortable we should keep the repo private. We don't have any necessity to keep it public, right?

I think it's not only me, I've heard the same sentiment from a couple of others.

ligi commented 4 years ago

Thanks for this OIP - would love to hear what others think about it. I see a lot of value in doing things in the open - but I have no problem having a private OIP repo. Would the following also work for you?: Having both a private and a public one? So you or everyone else can open your OIPs that should not be public there? Can also be used to make private comments on public OIPs. Just making this repo private would have the downside that some links would break and OIP is used for an example in the process of bootstrapping DIP. Also really hope no detail you consider private leaked to the public via an OIP - If so please LMK ASAP. You can do via an OIP in the private repo here: https://github.com/ethdevberlin/OIPS_private - Or you know where I sit ;-)

gumb0 commented 4 years ago

Would the following also work for you?: Having both a private and a public one? So you or everyone else can open your OIPs that should not be public there? Can also be used to make private comments on public OIPs.

I don't know, sounds cumbersome. If nobody else cares, I'm probably not going to use it alone.

Just making this repo private would have the downside that some links would break and OIP is used for an example in the process of bootstrapping DIP.

What's DIP?

ligi commented 4 years ago

will tell you what a DIP is in private - this is not yet public info (yea this becomes quite meta now ;-)