Update join guidelines

[gforcada]

At the Alpine City Sprint we (@ericof @fredvd @mauritsvanrees and me 😄 ) discussed that we need to update the guidelines on who and how to become a member of collective organization.

The action items where:

• update the guidelines in collective.github.io, see index.html
• create a news item on https://plone.org
• create an issue template in Collective repository

Did I miss anything? 🤔

[jensens]

guidelines on who and how to become a member of collective organization

I am curious what those are?

[ericof]

@jensens This is what @gforcada needs to write down. We had a productive discussion during Alpine City Sprint, and now it is time to make it happen.

[fredvd]

I have on my todo list to write summaries, also about this one.

@jensens the summary is that ‘beginning devs’ are abusing github with what reminds me of a kind of “seo backlinking scheme”. they hoard many small and not very meaningfull contributions to different open source code bases, also automated/scripted commits & comments to polish up their online developer profile.

We have to be very careful to not raise the bar too much for people handling in good faith, and not introduce biases for who gets access how quickly. But we should step away from the ‘allow collective access first, ask questions later’ policy.

You don’t need access to collective to contribute to Plone. For new packages: start an addon or other package on your own user namespace. Once there is something substantional/meaningfull there: ask for a repository transfer and you’ll get access.

For existing packages: fork to your user namespace, code, create PR’s. When someone has done a fee contributions this way, intends to continue contributing, and it becomes a hassle let them apply for access.

It means we will ask for some ‘proof’ of participation and intention and ask to send thar with their application. But one add’on or 5 contributions IMHO would already be enough.