Private repos in collective

Plone Support Add-on Development
1

Yesterday I created collective.exportimport (GitHub - collective/collective.exportimport: Export and import content, members, relations and translations) and accidentally created it as a private repository in the collective. @ksuess saw that and I changed it to public.

The reason was that the default setting for new repos was private which makes no sense imho. So I changed the setting so that now only public repos can be created. I hope that's ok.

The following repos are still private (I think by accident) and I suggest to make them public instead:

https://github.com/collective/collective.fancybox
https://github.com/collective/ploneconf.policy2020
https://github.com/collective/elmirador
https://github.com/collective/fury_shipping-backoffice-frontend

1 Like
2

Yes, private repos in collective are pointless.

3

I will delete collective.fancybox and recreate it after I go through it to rename it all the way down. I should have checked the name before creating it.

4

It is easy to make the repos public. Shall I do that?

5

I would say, go go go!

6

I made ploneconf.policy2020 public, the last two can't be made public because they are forks of private repos and need to be duplicated first. I'll leave them alone for now.