<div dir="auto">I have a suggestion here. We may create some issues with beginner labels, such that solving it may not be really helpful to us at first, but it can give insights of the code base to the new contributors. <div dir="auto"><br></div><div dir="auto">For instance, an issue for trying new color palette for our SugarLabs website. Or an issue for trying different border radius, color to a section of any activity etc. </div><div dir="auto"><br></div><div dir="auto">These may be useful in the long run especially if a new contributor can come up with something out of the box. Or atleast it will help them get familiar to our code base. </div><div dir="auto"><br></div><div dir="auto">These can be marked as 'reserved for beginners'. Some examples of these issue can be </div><div dir="auto">* Try color palette ABC to our website </div><div dir="auto">* Try color palette EFG to our website </div><div dir="auto">* Change the border radius of xyz element to make it look better</div><div dir="auto">* Update padding/look of xyz section of abc activity </div><div dir="auto">* Come up with 2 instances of redundant codes in xyz repo of SugarLabs</div><div dir="auto">* Come up with the idea of 2 features improvement for xyz repo</div><div dir="auto">* Come up with an idea to implement xyz functionality </div><div dir="auto">* Minimize console errors of abc activity</div><div dir="auto"><br></div><div dir="auto">I guess some of these would be interesting to the user even if they don't know how to code. It will definitely help in attracting a good number of new contributors. </div><div dir="auto"><br></div><div dir="auto">Also, it would not affect the development time of the experienced contributors since these issues would not require deep understanding of the code base or any skill. </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto">Amaan</div><div dir="auto"> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On May 3, 2019 4:07 AM, "James Cameron" <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You're saying leave some flaws rather than fix them.<br> <br> In general that's a good idea for attracting new members to a<br> community, but it takes investment in preparing the issue, and if that<br> investment is greater than fixing the flaw there's not much benefit.<br> <br> Also, when I do create issues, some experts use it as an opportunity<br> to post off-topic criticism, and some beginners don't apply any<br> diligence before asking questions. The issues sit there with the<br> criticism or questions and answers, and nothing else gets done. We<br> have plenty of them.<br> <br> What we really need is a well-functioning community of people with a<br> common goal who will listen to each other. Create that first, then<br> the beginner issues can be created.<br> <br> On Thu, May 02, 2019 at 06:23:13PM +0530, Sumit Srivastava wrote:<br> > I've already been saying we need more issues that are marked as beginner<br> > issues.<br> > <br> > We have too few!<br> > <br> > To the community: Let me know if you see an issue that needs to be marked as a<br> > beginner issue, or comment on it and someone will tag it.<br> > <br> > Regards<br> > Sumit<br> > <br> > On Thu, 2 May 2019, 5:29 pm Walter Bender, <[1]<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> wrote:<br> > <br> > Something to consider: [2]<a href="https://publiclab.org/notes/gauravano/03-29-2019/software-community-growth-through-first-timers-only-issues" rel="noreferrer" target="_blank">https://<wbr>publiclab.org/notes/gauravano/<wbr>03-29-2019/software-community-<wbr>growth-through-first-timers-<wbr>only-issues</a><br> > <br> > --<br> > Walter Bender<br> > Sugar Labs<br> > [3]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a><br> > [4]<br> > ______________________________<wbr>_________________<br> > Sugar-devel mailing list<br> > [5]<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.<wbr>sugarlabs.org</a><br> > [6]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br> > <br> > References:<br> > <br> > [1] mailto:<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a><br> > [2] <a href="https://publiclab.org/notes/gauravano/03-29-2019/software-community-growth-through-first-timers-only-issues" rel="noreferrer" target="_blank">https://publiclab.org/notes/<wbr>gauravano/03-29-2019/software-<wbr>community-growth-through-<wbr>first-timers-only-issues</a><br> > [3] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br> > [4] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br> > [5] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.<wbr>sugarlabs.org</a><br> > [6] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br> <br> > ______________________________<wbr>_________________<br> > Sugar-devel mailing list<br> > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br> <br> <br> -- <br> James Cameron<br> <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br> ______________________________<wbr>_________________<br> Sugar-devel mailing list<br> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br> </blockquote></div></div>