[prev in list] [next in list] [prev in thread] [next in thread]
List: olpc-sugar
Subject: Re: [Sugar-devel] Meeting Log
From: Jaskirat Singh <juskirat2000 () gmail ! com>
Date: 2018-09-17 6:41:19
Message-ID: CAO3SuQ9ohHXbhWC+bR5OEQVfDfN1uxXt0RhSm_AELK__=pBr2A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks a lot James for this valuable information.
On Mon, 17 Sep 2018, 8:12 am James Cameron, <quozl@laptop.org> wrote:
> On Fri, Sep 14, 2018 at 02:33:52PM +0100, Ojemeh Peace Ozioma wrote:
> > Hello everyone,
> >
> > Here is the log for today's meeting:
> > [1]https://wiki.sugarlabs.org/go/Design_Team/Meetings/2018-09-15
>
> Thanks.
>
> Sorry, I couldn't make it. I was travelling and didn't realise that
> the meeting was on that date. Now I see you said the second Friday of
> the month. You might mention the date in your next announcement.
>
> I've reviewed the log, and have some comments;
>
> The horse is in front of the cart; Perrie and Jaskirat speak as if the
> design team is for creating new features or improving existing
> features. That's not how we have worked at Sugar Labs. Features are
> proposed more generally, and the design team is for coordinating the
> developers when developers ask for coordination. We have a weekly
> development team meeting each week on #sugar-meeting, and can handle
> feature discussions there already.
>
> Please do not restrict new features to this new design team. New
> features are to come from developers, learners, teachers, and
> integrators. Use the Issues in GitHub. Use the Features pages in the
> Wiki. Only if coordination is needed should a design team be needed.
> Add the [DESIGN] tag to subject line on mailing list.
>
> Walter's changes to the toolbars don't need much coordination yet;
> next steps are to prepare a mock-up, discuss on mailing list, work out
> what software components must change, and then begin the change.
>
> Jaskirat wants the icons to match Microsoft Windows; again this
> doesn't need much coordination yet; please prepare a mock-up, discuss
> on mailing list, add an icon theme choice to My Settings, and add the
> new theme to Sugar Artwork component.
>
> Perrie wants to fix the font sizes and widget styles for large
> displays. This is a bug not a feature. Use the Issues in GitHub.
> Please make the changes to gtk-widgets.css files, test, and create a
> new pull request in GitHub for Sugar Artwork component.
>
> Above all, don't expect other people to develop your feature for you;
> you will likely have to do it yourself. Only exceptional features
> with much interest will have volunteers joining in to develop. Hiding
> an unpopular and not agreed feature inside GSoC project or GCI task is
> no substitute for transparency, and will often not be merged.
>
> The later discussion about the Sugar Labs logo shouldn't be part of
> the design team; it's not a developer issue, and doesn't need
> developer coordination. Please use the marketing team, or if they
> don't respond, use the iaep and sugar-devel mailing lists to get wide
> community input. Confining the discussion to this design team will
> bring up complaints about not consulting widely enough.
>
> --
> James Cameron
> http://quozl.netrek.org/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
[Attachment #5 (text/html)]
<div dir="auto">Thanks a lot James for this valuable information. </div><br><div \
class="gmail_quote"><div dir="ltr">On Mon, 17 Sep 2018, 8:12 am James Cameron, <<a \
href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On Fri, Sep 14, 2018 at 02:33:52PM +0100, Ojemeh Peace Ozioma \
wrote:<br> > Hello everyone,<br>
> <br>
> Here is the log for today's meeting:<br>
> [1]<a href="https://wiki.sugarlabs.org/go/Design_Team/Meetings/2018-09-15" \
rel="noreferrer noreferrer" \
target="_blank">https://wiki.sugarlabs.org/go/Design_Team/Meetings/2018-09-15</a> \
<br> <br>
Thanks.<br>
<br>
Sorry, I couldn't make it. I was travelling and didn't realise that<br>
the meeting was on that date. Now I see you said the second Friday of<br>
the month. You might mention the date in your next announcement.<br>
<br>
I've reviewed the log, and have some comments;<br>
<br>
The horse is in front of the cart; Perrie and Jaskirat speak as if the<br>
design team is for creating new features or improving existing<br>
features. That's not how we have worked at Sugar Labs. Features are<br>
proposed more generally, and the design team is for coordinating the<br>
developers when developers ask for coordination. We have a weekly<br>
development team meeting each week on #sugar-meeting, and can handle<br>
feature discussions there already.<br>
<br>
Please do not restrict new features to this new design team. New<br>
features are to come from developers, learners, teachers, and<br>
integrators. Use the Issues in GitHub. Use the Features pages in the<br>
Wiki. Only if coordination is needed should a design team be needed.<br>
Add the [DESIGN] tag to subject line on mailing list.<br>
<br>
Walter's changes to the toolbars don't need much coordination yet;<br>
next steps are to prepare a mock-up, discuss on mailing list, work out<br>
what software components must change, and then begin the change.<br>
<br>
Jaskirat wants the icons to match Microsoft Windows; again this<br>
doesn't need much coordination yet; please prepare a mock-up, discuss<br>
on mailing list, add an icon theme choice to My Settings, and add the<br>
new theme to Sugar Artwork component.<br>
<br>
Perrie wants to fix the font sizes and widget styles for large<br>
displays. This is a bug not a feature. Use the Issues in GitHub.<br>
Please make the changes to gtk-widgets.css files, test, and create a<br>
new pull request in GitHub for Sugar Artwork component.<br>
<br>
Above all, don't expect other people to develop your feature for you;<br>
you will likely have to do it yourself. Only exceptional features<br>
with much interest will have volunteers joining in to develop. Hiding<br>
an unpopular and not agreed feature inside GSoC project or GCI task is<br>
no substitute for transparency, and will often not be merged.<br>
<br>
The later discussion about the Sugar Labs logo shouldn't be part of<br>
the design team; it's not a developer issue, and doesn't need<br>
developer coordination. Please use the marketing team, or if they<br>
don't respond, use the iaep and sugar-devel mailing lists to get wide<br>
community input. Confining the discussion to this design team will<br>
bring up complaints about not consulting widely enough.<br>
<br>
-- <br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer noreferrer" \
target="_blank">http://quozl.netrek.org/</a><br> \
_______________________________________________<br> Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank" \
rel="noreferrer">Sugar-devel@lists.sugarlabs.org</a><br> <a \
href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" \
target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> \
</blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic