Greetings all, This is Marwan Atef, a recent Computer and Software Engineering University graduate and a GSoC'20 student who is interested in contributing to Plone in GSoC'22, specially in the Web Authn project idea.
I love open source contribution generally, and contribution in an organized manner/program as GSoC specially, I contributed in GSoC'20 with "Submitty" and it was a fruitful experience, that's why I'm aiming to doing it once again but this time with "Plone", hopefully.
I worked with different stacks including Python, php, ASP .NET Core on C#, Angular on Typescript, I have worked as well with different authentication frameworks/protocols as SAML, oAuth, and OpenID connect, that's why "Web Authn" as a project idea seems the most interesting to me but I'm still open for other ideas as well.
I have a question tho, I managed to run a local instance of Plone, thanks to the clear documentation, and I found what needs to be fixed in an open issue that I'm willing to tackle with a PR. However, Should I sign the Contributor Agreement first before I can open the PR?
One other related question tho, I managed to run a local instance for development as described here -> https://docs.plone.org/develop/plone/getstarted/index.html, Is this for developing add-ons (custom modules) only, while to develop for the core I should make my changes in the instance following the docs here -> https://docs.plone.org/develop/coredev/docs/intro.html as I feel a little bit confused.
Ah, yes, to contribute code to that repo (or anything in the plone GitHub organization) you would have to sign the contributor's agreement first. Maybe for now please hold off doing that. Anything in the collective or anything in the Plone documentation (or training documentation) can be contributed to without that contributor agreement.
Dears, I'm following the training, but all the changes I have to take like in here
Add a file browser/templates/training.pt
are already done for me (even with further changes that I'll probably meet later on in the training), and changing them doesn't seem to make any effect, even though I have configured the buildout.cfg to use ploneconf.site = fs ploneconf.site path=src instead of the remote version and re-ran the buildout, but trying to access http://localhost:8080/Plone/@@training as described in the training gives me this error