Thanks, that worked better.

https://codein.withgoogle.com/dashboard/tasks/5202335932874752/ is
already completed.

https://codein.withgoogle.com/dashboard/tasks/5095174972112896/ is
already completed.

https://codein.withgoogle.com/dashboard/tasks/5752323406561280/ makes
no sense; there was no general agreement by any of the maintainers to
use this tool, and if there was, it should be attached to the specific
project not Sugar Labs in general.  Perhaps something for the
oversight board rather than a GCI student.

https://codein.withgoogle.com/dashboard/tasks/5643490613002240/ is
already assigned (to me), the cause is well understood, and anyway the
changes likely to be done aren't to configure.ac file.

https://codein.withgoogle.com/dashboard/tasks/5174561855766528/ seems
to be a duplicate of
https://codein.withgoogle.com/dashboard/tasks/5990706573737984/ with
the latter being better defined.

https://codein.withgoogle.com/dashboard/tasks/5416369386946560/
makes no sense because the activity does not support collaboration,
and so there's no way to test if the task was completed properly.

https://codein.withgoogle.com/dashboard/tasks/5756584903311360/ makes
no sense; Pippy is a Fructose activity therefore it is always
installed with Sugar.

--

Some of the tasks I've changed;

https://codein.withgoogle.com/dashboard/tasks/6283229045194752/ was
not well explained; fixed.

https://codein.withgoogle.com/dashboard/tasks/5663050028285952/
suggested changing the style and appearance of Pippy documentation,
but as this is part of the Help activity it can't be done that way;
fixed.

https://codein.withgoogle.com/dashboard/tasks/5572284450865152/ failed
to mention our trademarks and referred to Sugar Labs by the wrong
name, and didn't have enough instances; fixed.

https://codein.withgoogle.com/dashboard/tasks/6240060362457088/ also
failed to mention the trademark concerns; fixed.

https://codein.withgoogle.com/dashboard/tasks/5667733656567808/ can't
be done until a Port to GTK 3 is completed, so changed instance
count to zero.

https://codein.withgoogle.com/dashboard/tasks/5662089583001600/ lesson
plans go in the Help activity.

--

Tasks suggested;

- complete a code review or test on someone else's pull request, with
  reference to our contribution guide section for reviewers,

- further work on Jappy, or Develop, rather than only Pippy,

On Sun, Nov 24, 2019 at 01:17:16PM +0100, Chihurumnaya Ibiam wrote:
> Hi James,
> 
> The 63 you're seeing might be the tasks you've been assigned to, you can
> uncheck the "My task" button below the tasks page to see all tasks.
> 
> Can you point out the tasks that make no sense or are for already completed
> work?
> 
> On Sun, Nov 24, 2019, 10:17 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
>     I'll have to take your word for it on "almost 200", as the dashboard
>     only shows me 63.
> 
>     For those I can see, quality of the tasks is a problem.
> 
>     Several of them make no sense or are for already completed work.
> 
>     Yet all I can do is change the description or the instance count.  I
>     don't even know who made the tasks.
> 
>     The tasks need better review before they are published.  There's
>     nothing so demoralising for a student to realise they are being
>     misguided into wasting their time.
> 
>     On Sat, Nov 23, 2019 at 10:07:21AM -0500, Walter Bender wrote:
>     > GCI begins on 2 December. We are in pretty good shape: almost 200 tasks
>     > published with a nice balance between Sugar Desktop, Music Blocks and
>     > Sugarizer. (Thanks to everyone who has been helping with task creation.)
>     >
>     > Note that we can continue to add more tasks throughout the contest.
>     >
>     > Most tasks have 4-6 mentors, so I think we should have decent coverage 
> in
>     terms
>     > of feedback to the participants. Please, where as the primary channel 
> for
>     > communication with the participants will be IRC, try to hang out in #
>     sugar as
>     > much as possible. We are here to help the students learn, so please keep
>     that
>     > in mind. (We also expect some solid contributions to Sugar.)
>     >
>     > Reminder: We expect that the quality of submissions be the same as for
>     any
>     > contribution. Please do not sign off on tasks that are not complete or 
> of
>     high
>     > quality.
>     >
>     > GCI is fun and productive.
>     >
>     > Enjoy.
>     >
>     > regards.
>     >
>     > -walter
>     >
>     > --
>     > Walter Bender
>     > Sugar Labs
>     > [1][2]http://www.sugarlabs.org
>     > [2]
>     >
>     > References:
>     >
>     > [1] [3]http://www.sugarlabs.org/
>     > [2] [4]http://www.sugarlabs.org/
> 
>     > _______________________________________________
>     > Sugar-devel mailing list
>     > [5]Sugar-devel@lists.sugarlabs.org
>     > [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
>     --
>     James Cameron
>     [7]http://quozl.netrek.org/
>     _______________________________________________
>     Sugar-devel mailing list
>     [8]Sugar-devel@lists.sugarlabs.org
>     [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] http://www.sugarlabs.org/
> [3] http://www.sugarlabs.org/
> [4] http://www.sugarlabs.org/
> [5] mailto:Sugar-devel@lists.sugarlabs.org
> [6] http://lists.sugarlabs.org/listinfo/sugar-devel
> [7] http://quozl.netrek.org/
> [8] mailto:Sugar-devel@lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
James Cameron
http://quozl.netrek.org/
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Reply via email to