💥 Reenergizing Our Contribution and Pull Request Processes!

Andrew Chekanov

🚀 Calling All Developers in Our Cosmic Community! 👨‍🚀

Are you ready for an astronomical journey with Spryker? 

We're reinvigorating our pull request process, unveiling a stellar initiative to revolutionize contributions to our commerce platform! 

As well as offering new ways to contribute, Spryker will endeavor to acknowledge all submissions within two weeks.

We’ll also post regular recoginition and shout-outs to top contributors, as well as unveil a cosmic rewards system in the near future!

https://youtu.be/K1CrDERGl50

–

💥 As part of this mission, we're introducing two contribution types:

1️⃣ Platform Contributions - Enhance Spryker with bug fixes, improvements, and documentation updates, fueling the evolution of commerce tech. 

Platform Contributions are ecosystem-led contributions to be built into and enhance Spryker’s core product. These include bug fixes, core improvements, and documentation updates across Spryker's product portfolio. All Platform Contributions can be submitted as pull requests towards the dedicated GitHub repositories related to the Spryker GitHub organizations.

Spryker Cloud Commerce OS (SCCOS) and development tools

Contribution Guidelines

Documentation

Updating Documentation (SCCOS)

Spryker Documentation accepts contributions in the form of edits and new documents. 

To edit existing documents, contributors can use the “Edit on GitHub” button in Spryker Documentation to create pull requests with suggestions.

To create a new document, contributors can create pull requests directly to the relevant Spryker doc repository.

Alternatively, the following guides advise how to create pull requests toward documentation:

Edit Documentation via a Web Browser

Edit Documentation Locally

2️⃣ Innovation Lab - A universe of innovative projects, hackathon gems, and experimental ideas destined to soar alongside our platform.

Innovation Lab contributions are ecosystem-led open-source contributions, demonstrating innovative but often experimental use cases. These are built for use with, but not maintained by, Spryker. These include hackathon projects, tools, and customer & partner innovation ideas. These can be utilized in any part of the Spryker platform, including the products listed above. 

There are two distinct ways to contribute to Innovation Lab:

1. Ask Spryker to create a repository within the Spryker Community & Innovation Lab GitHub organization

• Request access by emailing community@spryker.com or post your request in the Community Projects subforum.
• Once you have access, start your project and upload your first code.
  
  And, of course, we encourage everyone to evaluate current projects, suggest improvements, or even submit pull requests!
  

2. Create an Innovation in your own organization

• Create an Innovation Lab repository in your own GitHub organization and communicate with the Spryker team to have this reviewed. Reviews can be requested by emailing community@spryker.com or post your request in the Community Projects subforum in CommerceQuest.
• If your Innovation is accepted, we will mirror it with the Spryker Community & Innovation Lab GitHub organization and add your contribution to our Community Tools list to allow other Spryker developers to find it. 

Please bear in mind that Spryker does not maintain Innovation Lab submissions.

Contribution Guidelines need to be followed in both cases listed above.

Innovation Lab Documentation 

—

We expect to announce more information regarding a third channel, Commercial Contributions, later this year.

—

When Spryker and our intrepid community join forces, the possibilities are endless. Unite with us in shaping the cosmos of commerce tech!

Any questions? Drop them in this thread!

And watch this space for further updates! 🚀

Samuel Pais

Awesome news @Andrew Chekanov! Let's cook some good stuff 🧑🏻‍🍳

Guido X Jansen

So excited to see what comes out of this!

amansilla

This are great news @Andrew ChekanovI can't remember how long I have been waiting for this chance to contribute to the Spryker ecosystem.

Super excited to start seeing the first contributions!

Andrew Chekanov

I'm happy that it inspires you as much as I do! @amansilla

mohammedalama

as @amansilla
said it's a great news because since I'm ex Sprykee that working on SCCOS and I'm have been amazed of how Spryker build their products , my time there was not too much but it's gives me more insightful vision about how a cool software is being made
so now shit up and give me bugs 😂
no for real how to find bugs , Is there is a board for it?

and how much of Spryker code conventions would be public for that kind of contributions?

I'm aware of this course but AFAIK Core is more strict