<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hey Esteban,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 10 Jul 2020, at 00:37, Esteban Maringolo <<a href="mailto:emaringolo@gmail.com" class="">emaringolo@gmail.com</a>> wrote:</div><div class=""><div class=""><br class="">As I've been using Seaside continuously during the last year I also<br class="">felt guilty of not contributing back to the development of it.<br class=""></div></div></blockquote><div><br class=""></div><div>You are very actively responding to questions and discussions both on Discord and the mailinglist, and that too is a contribution!</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">What would be the best way to do it? I see there are a lot of issues,<br class="">but many are tagged as 3.5 and 3.6.<br class="">Is there a priority list? Are there low hanging fruits that can be<br class="">used to gain momentum in the contribution process?<br class=""></div></div></blockquote><div><br class=""></div><div>We (well, mostly Philippe) did tag some issues as ‘BiteSize’: <a href="https://github.com/SeasideSt/Seaside/labels/BiteSize" class="">https://github.com/SeasideSt/Seaside/labels/BiteSize</a></div><div>It’s probably not very up-to-date and I should run over the list to classify the issues again.</div><div>There is also the (still unfinished) list of issues we tagged for the last camp smalltalk at esug in Koln: <a href="https://github.com/SeasideSt/Seaside/labels/CampSmalltalk 2019" class="">https://github.com/SeasideSt/Seaside/labels/CampSmalltalk%202019</a></div><div><br class=""></div><div>But I would say anything you have done yourself to extend or change Seaside which might be useful for others is interesting.</div><div>I am very much aware that this often requires additional work, which is also why not all changes and extensions we made at Yesplan found their way into Seaside… </div><div>And many times, it should not even become part of core Seaside…. Which reminds me of a website we should setup and gather those references there ;)</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">I'm currently exploring changes or extensions (that I think are<br class="">enhancements) to the core model, to expose an app to be session-less<br class="">for most of its use, but it's an exploratory long road that I take<br class="">in my spare time that might end up being a dead-end.<br class=""></div></div></blockquote><div><br class=""></div>Haha, I can totally sympathise there :) I have many images of started experiments I never actually finished…</div><div><br class=""></div><div>Cheers!</div><div>Johan</div></body></html>