Hi Jörg, I like the idea! Regarding the naming, we may want to adapt the naming Github uses for that: "good-first-issue"
https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels#about-default-labels Maybe we will even find a way to make it into services like goodfirstissue.dev . Dirk On Thu, 20 Jan 2022 at 10:03, Jörg Hoh <[email protected]> wrote: > > Hi, > > I plan to create a few SLING issues which replicate the changes of > https://issues.apache.org/jira/browse/SLING-11025 to other parts of the > Sling codebase. These changes would be straight forward and not hard to do > (we have a working sample plus the documentation for it already available). > I think that these issues would be a good starter for people getting > involved in Sling (and maybe Apache at all). > > But I think that we have more of such tickets, which are probably neither > hard nor that important for us as a community, but which can act as a > perfect starting point into Sling. > > I suggest that we mark these tickets with a label "slingBeginner" (much > appreciated if you can come up with a better name) and add a new section to > https://sling.apache.org/documentation/getting-started.html which outlines > how you can get involved into the development part of Sling. > > I have some reach on social media into the wider AEM community. I hope to > attract a few contributions from that side, if we can explicitly point out > an easy way to get involved. > > > WDYT? > Jörg > > > -- > Cheers, > Jörg Hoh, > > https://cqdump.joerghoh.de > Twitter: @joerghoh
