GSoC 2019 Brainstorming

Yup, I guess I should have been clearer that "app" means "desktop app and mobile app"! Now clarified in my response above.

So I'm seeing a lot of really good ideas in here. I suggest these next steps:

All y'all who are kicking ideas around, self-organize around one or more that you are enthusiastic about. See if you can write up your idea as a project proposal. What does a proposal need? Take a look at the project ideas for 2018. You'll need a summary, a sketch of the "implementation" needed, a list of the skills a student would want to have to work on the project, a list of one or more mentors willing to work on the project, and a concrete "aim" or outcome to the project.

The application period for organizations begins on the 15th of January (four days from now) and applications are due on February 6th. I will include in our project application any projects that have solid proposals with listed mentors by Feb 1st. That gives me the weekend before the due date to get the projects formatted for listing.

As @polyester noted above, the awarding of slots is determined by the number of projects we list and the available pool of mentors, so the more projects and mentors we have, the more slots we may be awarded. Ideally every project should have three members for the mentoring team. One is the "project owner" who plays the role of stakeholder and reviews work in progress in light of the overall goals of the project. The other two are the primary and backup mentors. We used this organization last year and it was quite successful.

Keep up the great work folks. I'm liking what I'm seeing so far!

1 Like

Thanks to @tkimnguyen, we have a very nice form for submitting Ideas. Please, as you come up with solid ideas, fill out the form and submit it. Please also make sure that there are listed mentors and a stakeholder.

2 Likes

So sorry, perhaps I'm a bit late here, but a cool idea for a GSOC project, is
to integrate the gutenberg editor into plone. Thought there is already an integration
with Drupal, but anyway, is a game changer on the cms land.

Not at all! I think by now four individual devs looked into Gutenberg and if we could adopt it in Plone. Though, it seems it is pretty tightly coupled to Wordpress and the code quality seems to be not very good.

I'd be open to a GSoC project but I wouldn't expect to much from it. Just my 2c...

1 Like

Have you seen this: https://github.com/front/storypage
I know there are some trade offs on the waty gutenberg is built (they isollate it inside a common react/redux) app, but they provide an "external" API (ala backbone style). For exemple, all async calls are wrapped around a global function on the WP namespace (If i'm not wrong) window.WP.fetch (or something like). On the github.com/front repos there are more examples, and also a mantained gutenberg.js package.
The only reason I still have an eye on it, is that gutenberg has lot's of resources inside (400 contributors), 9000 commits... this is something that only can be done by a paid team (wordpress.com) with lot's of resources.. There is also a rising ecosystem of "plugins" (ex: https://github.com/thatplugincompany/coblocks)... To have something like this around something like plone it's really a dream!

I was thinking about the same, we realy need a solit export and import solution for Plone.
Is the code from last years GSoC projects useable already?

I like this idea more and more and should be doable in GSoC. It could also be useful for another project, like a good VS Code integration of Plone. We already have some snippets, but the whole indexing/code intel is far from being great. And a buildout free Plone version could help here too.

I would mentor the VS Code integration and can also help on the buildoutless installation.

Start with just getting a buildout awareness into the VS code ecosystem. A good smoke test is whether pylint works or not.

2 Likes

Sort of. for some limited usecases. We've used it in production.

NB it was 2017 GSoC not last year
NBB we need a more flexible solution for a project this month so we are aiming implement some of the UI I've proposed in UX Roadmap (control panel, query widget, profiles, non-content settings etc) · Issue #15 · collective/plone.importexport · GitHub this week. Not sure how much will be left over to do for a GSoC. It would be good to get feedback on this set of features and the other ones proposed.

1 Like

I don't need buildout. What I need is code completion and inspection, which is not freezing my machine while analysing the code.

I tried the importexport addon, at least the import of simple news items and folder with leadimages was not working. But the export seems to work. We would need a search function for users to fulfill the requirements on data privacy as GDPR. So that we can export all content of a user.

Exactly why you need to make all the linter tooling aware of the buildout.

A post was split to a new topic: Interested in Volto and Gatsby

Nice use case. This would be covered by the proposed changes in UX Roadmap (control panel, query widget, profiles, non-content settings etc) · Issue #15 · collective/plone.importexport · GitHub.
Lets see how far we get in the next few days.

1 Like

Great ideas are germinating here. That's wonderful.

When you feel like you've got something solid to propose, please head on over to plone.org and submit it so we have an official description to use on our ideas page.

In the meantime, if you are interested in mentoring this year, please fill out this form so I can get in touch and put your name on my list :slight_smile:

Keep the ideas flowing folks. Good stuff so far!

If someone is interested in building an Aurelia #aureliajs SDK/UI for Plone, I would mentor the project.
Aurelia is realy easy to learn and use Javascript framework wich combines good conventions with standard conform ES6 or Typescript support. It simply makes building app's fun. I used it together with the Rest-API already and could help to build useful components for Plone.

1 Like

Alright Plonistas!. We're running up against the deadline here. Eight days left and so far we have two proposals submitted and only one mentor signed up. We can do better!

@ebrehault, @vangheem, @ramon, @b4oshany, you've all spoken up directly about mentoring. How about filling out the form to make it official? @robgietema, @sneridagh, @tisto, @cekk, @datakurre, you've all been mentioned as possible mentors. Care to step up to the plate once again? @djay, you've always got great ideas for projects. Would you care to mentor a student? @ajayns, @kakshay21, @Shriyanshagro, @nileshgulia1, you finished successful projects last year. How about stepping up and co-mentoring a project this year? It takes a village, folks!

We've got very interesting project ideas floating around in here. But they need fleshing out and writing up. Here's a list of the ideas I see floating around so far:

  • plone import/export (already has a solid write-up, probably doesn't need more)
  • vscode integration for plone/buildout
  • GDPR search/export
  • AureliaJS SDK/UI
  • AngularJS Pastanaga frontend (Volto in Angular)
  • REST API Evolution, versioning support, JSON LD/jsonapi, swagger 3
  • Guillotina API for dynamic field sets (behavior support)
  • Guillotina Object server in rust / rocksdb
  • Guillotina glue for transmogrifier to support moving data between Plone/Guillotina
  • Guillotina performance testing
  • pip-based Plone installation
  • GraphQL Implementation on top of REST API

None of these ideas has an official write up yet. The Import/Export idea had write-ups from last year, but these could use the same. Any idea that gets a solid write up can be a candidate for this year's listings, so let's get going and get some more ideas submitted.

Go Plonistas Go!

3 Likes

@cewing I think that this year I will have less time to spend on gsoc, but i'd like to help as a backup mentor if there are some projects where i can help.

As last year, i created a separat topic in this forum to discuss, the idea further GSoC 2019 ideas: AureliaJS SDK for Plone Rest-API.

1 Like