<div dir="auto">I meant if the color palette update(actual update in the code), Improvised look(in the code), suggestion etc is of some value, then their PR can directly be merged. <div dir="auto"> </div><div dir="auto">Also we can have a section in each repo Readme for some 'expected functionalities' to have, which the newcomers can directly update. So that they can get the feel of getting the PR merged. </div><div dir="auto"> </div><div dir="auto">For redundant codes, the newcomers may find 2 places where similar code is appearing and remove either of them and send corresponding PR. </div><div dir="auto"> </div><div dir="auto">Regarding console errors, we may have basic issues, specific to each error say of datatype mismatch etc which doesn't block the expected behavior but better to fix them. These issues can be worked upon by the newcomers and will require finding out which module is located where. This will help them dig deeper into the code base and contribute further. </div><div dir="auto"> </div><div dir="auto">I hope it makes sense. </div><div dir="auto"> </div><div dir="auto"> </div><div dir="auto">Thanks, </div><div dir="auto">Amaan </div></div><div class="gmail_extra"> <div class="gmail_quote">On May 3, 2019 9:37 AM, "James Cameron" <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Interesting idea. But I've an ethical problem with creating issues that don't need to be fixed, and will never merge. It seems arbitrary and unfair to a new contributor. On the other hand, some of the issues you listed have general value; such as minimising console output. On Fri, May 03, 2019 at 09:05:07AM +0530, Amaan Iqbal wrote: > 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. > > 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. > > 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. > > These can be marked as 'reserved for beginners'. Some examples of these issue > can be > * Try color palette ABC to our website > * Try color palette EFG to our website > * Change the border radius of xyz element to make it look better > * Update padding/look of xyz section of abc activity > * Come up with 2 instances of redundant codes in xyz repo of SugarLabs > * Come up with the idea of 2 features improvement for xyz repo > * Come up with an idea to implement xyz functionality > * Minimize console errors of abc activity > > 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. > > 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. > > Thanks, > Amaan > > > On May 3, 2019 4:07 AM, "James Cameron" <[1]<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote: > > You're saying leave some flaws rather than fix them. > > In general that's a good idea for attracting new members to a > community, but it takes investment in preparing the issue, and if that > investment is greater than fixing the flaw there's not much benefit. > > Also, when I do create issues, some experts use it as an opportunity > to post off-topic criticism, and some beginners don't apply any > diligence before asking questions. The issues sit there with the > criticism or questions and answers, and nothing else gets done. We > have plenty of them. > > What we really need is a well-functioning community of people with a > common goal who will listen to each other. Create that first, then > the beginner issues can be created. > > On Thu, May 02, 2019 at 06:23:13PM +0530, Sumit Srivastava wrote: > > I've already been saying we need more issues that are marked as beginner > > issues. > > > > We have too few! > > > > To the community: Let me know if you see an issue that needs to be marked > as a > > beginner issue, or comment on it and someone will tag it. > > > > Regards > > Sumit > > > > On Thu, 2 May 2019, 5:29 pm Walter Bender, <[1][2]<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a> > > wrote: > > > > Something to consider: [2][3]<a href="https://publiclab.org/notes/gauravano/" rel="noreferrer" target="_blank">https://publiclab.org/notes/gauravano/</a> > 03-29-2019/software-community-growth-through-first-timers-only-issues > > > > -- > > Walter Bender > > Sugar Labs > > [3][4]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a> > > [4] > > _______________________________________________ > > Sugar-devel mailing list > > [5][5]<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > > [6][6]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > > References: > > > > [1] mailto:[7]<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a> > > [2] [8]<a href="https://publiclab.org/notes/gauravano/03-29-2019/software-" rel="noreferrer" target="_blank">https://publiclab.org/notes/gauravano/03-29-2019/software-</a> > community-growth-through-first-timers-only-issues > > [3] [9]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > > [4] [10]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > > [5] mailto:[11]<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > > [6] [12]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > _______________________________________________ > > Sugar-devel mailing list > > [13]<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > > [14]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > -- > James Cameron > [15]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > _______________________________________________ > Sugar-devel mailing list > [16]<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > [17]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > References: > > [1] mailto:<a href="mailto:quozl@laptop.org">quozl@laptop.org</a> > [2] mailto:<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a> > [3] <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/gauravano/03-29-2019/software-community-growth-through-first-timers-only-issues</a> > [4] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [5] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > [6] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [7] mailto:<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a> > [8] <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/gauravano/03-29-2019/software-community-growth-through-first-timers-only-issues</a> > [9] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [10] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [11] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > [12] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [13] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > [14] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [15] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > [16] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > [17] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> </blockquote></div></div>