[Sugar-devel] first-time only issues

[Amaan Iqbal]

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" <quozl at laptop.org> 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]walter.bender at gmail.com>
> wrote:
> >
> >     Something to consider: [2]https://publiclab.org/notes/gauravano/
> 03-29-2019/software-community-growth-through-first-timers-only-issues
> >
> >     --
> >     Walter Bender
> >     Sugar Labs
> >     [3]http://www.sugarlabs.org
> >     [4]
> >     _______________________________________________
> >     Sugar-devel mailing list
> >     [5]Sugar-devel at lists.sugarlabs.org
> >     [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] mailto:walter.bender at gmail.com
> > [2] https://publiclab.org/notes/gauravano/03-29-2019/software-
> community-growth-through-first-timers-only-issues
> > [3] http://www.sugarlabs.org/
> > [4] http://www.sugarlabs.org/
> > [5] mailto:Sugar-devel at lists.sugarlabs.org
> > [6] http://lists.sugarlabs.org/listinfo/sugar-devel
>
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190503/ba6d88cf/attachment.html>