GSOC Students, Please focus on your application. Restrictions on Developer Team access on GitHub

Dear GSOC students,

Many of you have become active in our community during the last three months. You have done this to learn more about the Plone Software stack and our development process, so that you can prepare your application for one of our GSOC 2023 Proposals.

Please be aware that becoming an active member of the community and participating in the current development activity is not a requirement and also will not influence or increase your chance to be selected for one of the proposals. The mentors in our community will evaluate the proposals and judge their quality and viability alone.

Getting to know Plone a bit is essential for writing a good application/proposal, but you have to realise that we are a volunteer organisation and we cannot support every one of you with every question that you might have about Plone or the proposals. Community members have day jobs and provide their limited free time to Plone.

Part of our development process is that we need Contributor Agreements from every person who wants to help us with code, documentation or other contributions, before we can merge it. Applying for, and getting your contributor agreement accepted, does however not mean that you should start using that 'permission' and start editing existing issues and PLIP's (Plone Improvement Proposals). Or create PR's (Pull requests) with your implementation without consulting first with other Developers. They have already been working on Plone for many years. The first solutions that come to your mind after evaluating our code for a week is often not the best solution. We need consensus on many decisions, which takes time, effort, skill and communication between members.

The last few weeks a minority of students who have been granted Developer team membership on GitHub have started abusing the permissions they received on our repositories, have edited existing comments, PLIP's, and already created PR's. This is likely not because of bad intentions, but you have to realise we are a volunteer organisation, we cannot handle this amount of input.

Receiving 'Developer' access to our code base and repositories on GitHub is based on the implicit trust that you treat other Developers and GSOC mentors with respect, both in text and communication. And also respect their limited time that they make available to our project and cause. If you don't receive an answer from a Team Lead, other developer or Release Manager, it is considered impolite to start pinging them in comments every day for an answer. Pinging 4 or 5 other developers because you didn't get an answer is considered rude as well. Don't ask to get issues assigned to you to 'prove' that you are actively participating. It will not increase your chance of getting selected into GSOC 2023.

As the System Administration and Infrastructure team lead I have contacted a number of other senior members this morning and we have decided to move new members that have received full access recently based on their Contributor Agreement to a new 'Contributors' Team. Also we have removed them from the 'Developers' Team on GitHub for now.

As a Contributor you can create issues, and respond to issues. And your code can get merged.

If you want to help out at the moment with our development and need to create a PR, after you have discussed its merits and viability with other (Senior) Developers, fork the repo you want to work on to your personal work space. Once it is ready for merging, create a Pull request to the official repo. And be patient.

Again: we value your contributions if you desire to make them, but please focus on your application for one of our GSOC 2023 proposals. We do not require any contribution prior to be selected as a GSOC 2023 student.

With kind regards,

Fred van Dijk - Plone AI-Team team lead

This message has been discussed with and agreed upon by:

Eric Steele - Plone Community Manager
Victor Fernandez d'Alba - Volto Release Manager
Maurits van Rees - Plone Release Manager
Jens Klein - Core Plone Developer
Erico Andrei - Plone Foundation President


Thank you. Sounds pretty straightforward to me.

1 Like

ok so can i Summit my Proposal today @fredvd

Use the GSOC portal to submit your proposal.
As a GSOC aspirant, you don’t have to have access to Plone repos.
The GSOC process is clearly documented and we mentors explained already a couple of times, in various postings and answers how the process works.


@fredvd @zopyx Please how can we get feedback on our draft proposal? Can we message the project mentors privately?

As written a couple of times: the mentors of the related topics are in charge of providing feedback.
According to the GSOC rules, mentors are encouraged but don't have an obligation, in particular no obligation to react in a particular timeframe. We do this on a voluntary basis. Only talking for my own "WebAuthn" topic: I received five proposals and gave feedback to the aspirants after one day. I am not in charge of other proposals.

1 Like

@zopyx I received feedback on my proposal and am taking in the recommendations. After, I get feedback is it okay to email the mentor directly with questions and other draft proposals or Should we stick to using the Plone community forum

In addition, aspirants should check their proposals carefully. A bunch of proposals are just poorly written, are missing basic information like contact and personal information, proposal contain pasted test from the original proposal. Many proposals don't

This also has been communicated a couple of times: ask questions in public - either here or on Discord (I am not following on Discord). Honestly, I am a bit annoyed that we have to repeat this over and over again.

Nice to hear that

Hello Everyone! My name is Puja, a final year student. I am really interested in open-source and looking for ways to kick stat my journey and have been looking for ways to get more involved in the community.