Re: [Sugar-devel] first-time only issues

Hi There, As a newcomer I personally think that *suggestions *section would be nice. and that seasonal competition. Everybody loves some gifts no? Thanks! RM Rishan On Fri, 3 May 2019 at 22:26, Amaan Iqbal wrote: > I meant these trivial tasks should just be for providing confidence to the >

Re: [Sugar-devel] first-time only issues

I meant these trivial tasks should just be for providing confidence to the newcomers so that they can at least get started. It may be less productive but will help them keep going. We can also have a *Suggestions *section on the readme of every repo. I just thought about this. And there can be a

Re: [Sugar-devel] first-time only issues

Incredible! We are having trouble identifying tasks that need doing. Try:     Over 100 Sugar Activities in ASLO which fail to start.     Many activities which do not have a repository in github.com/sugarlabs     Many activities still dependent on gtk3 and other deprecated moduless Tony On

Re: [Sugar-devel] first-time only issues

On Fri, May 03, 2019 at 04:02:03PM +1000, James Cameron wrote: > I'm not sure that this is true. I think the reasons why we don't have > newcomers doing anything this are far more profound; > > 1. very few other people are doing anything; development has slowed, > > 2. work done by others

Re: [Sugar-devel] first-time only issues

Thanks. Yes, it makes sense. But it is like directing an investigation. A true and well-done investigation is one where the investigator is independent of bias. When we bias the newcomers toward certain tasks, we tend only to get those tasks done. An example is how we've had many activities

Re: [Sugar-devel] first-time only issues

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. Also we can have a section in each repo Readme for some 'expected functionalities' to have, which the newcomers can directly update.

Re: [Sugar-devel] first-time only issues

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

Re: [Sugar-devel] first-time only issues

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

Re: [Sugar-devel] first-time only issues

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

Re: [Sugar-devel] first-time only issues

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,

[Sugar-devel] first-time only issues

Something to consider: https://publiclab.org/notes/gauravano/03-29-2019/software-community-growth-through-first-timers-only-issues -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list