Re: [Usability] GNOME Quarterly Report Q2/2012

--===============1163062552==
Content-Type: multipart/alternative; boundary=f46d042f97908900eb04c3ce923c

--f46d042f97908900eb04c3ce923c
Content-Type: text/plain; charset=ISO-8859-1

Sounds like a good idea in terms of making sure all newsworthy pieces are
covered. This will also help show what dimensions of GNOME are/should be
covered, which will ultimately identify what teams are necessary for
GNOME's success. This may show us the need to split, merge, or modify teams.

On the other hand, an advantage of listing teams is helping ensure they're
all moving forward every quarter. The idea is those different teams are
covering needs that are required to keep GNOME healthy. If they aren't
active enough to even write a short report on time, a dimension of GNOME
might be unattended.

Maybe a combination of starting from the newsworthy and starting from the
team would work.

Thoughts?

On Monday, July 2, 2012, Dave Neary wrote:

> Hi,
>
> On 06/30/2012 08:22 PM, Andre Klapper wrote:
>
>> it's time again for a quarterly GNOME report to let community and
>> companies know what has been going on between April and June 2012.
>>
>> Please update your section for Q2/2012 here:
>>
>>        https://live.gnome.org/**GnomeMarketing/**QuarterlyReports/2012/Q2<https://live.gnome.org/GnomeMarketing/QuarterlyReports/2012/Q2>
>>
>>
>> The list of potential teams and writers:
>>
>
> <snip>
>
> Just to turn this on its head for a second, can we come at this from
> another angle? Instead of identifying teams who should report, how about we
> think about what's happened that might be newsworthy, and then figure out
> who's best placed to report on it?
>
> The stuff that comes to mind for me is:
>  * Board elections + review of last board year
>  * GUADEC 2013 call for hosts out (and, related, no Desktop Summit in 2013)
>  * GUADEC 2012 keynotes to be announced
>  * Half-way point in Women's Outreach Program
>  * GNOME in Google Summer of Code
>
>
> Anything else? I haven't been following too closely this quarter.
>
> Cheers,
> Dave.
>
>
> --
> Dave Neary
> GNOME Foundation member
> [email protected]
> Jabber: [email protected]
>
>
> ______________________________**_________________
> usability mailing list
> [email protected]
> https://mail.gnome.org/**mailman/listinfo/usability<https://mail.gnome.org/mailman/listinfo/usability>
>


-- 
Regards,*
*
*@AllanCaeg*
User Experience + Product Management

allancaeg.com
+63 918 948 2520

--f46d042f97908900eb04c3ce923c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sounds like a good idea in terms of making sure all newsworthy pieces are c=
overed. This will also help show what dimensions of GNOME are/should be cov=
ered, which will ultimately=A0identify what teams are necessary for GNOME&#=
39;s success. This may show us the need to split, merge, or modify teams.<d=
iv>
<br></div><div>On the other hand, an advantage of listing teams is helping =
ensure they&#39;re all moving forward every quarter. The idea is those diff=
erent teams are covering needs that are required to keep GNOME healthy. If =
they aren&#39;t active enough to even write a short report on time, a dimen=
sion of GNOME might be unattended.=A0</div>
<div><br></div><div>Maybe a combination of starting from the newsworthy and=
 starting from the team would work.=A0</div><div><br></div><div>Thoughts?<s=
pan></span><br><br>On Monday, July 2, 2012, Dave Neary  wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
Hi,<br>
<br>
On 06/30/2012 08:22 PM, Andre Klapper wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
it&#39;s time again for a quarterly GNOME report to let community and<br>
companies know what has been going on between April and June 2012.<br>
<br>
Please update your section for Q2/2012 here:<br>
<br>
=A0 =A0 =A0 =A0<a href=3D"https://live.gnome.org/GnomeMarketing/QuarterlyRe=
ports/2012/Q2" target=3D"_blank">https://live.gnome.org/<u></u>GnomeMarketi=
ng/<u></u>QuarterlyReports/2012/Q2</a><br>
<br>
<br>
The list of potential teams and writers:<br>
</blockquote>
<br>
&lt;snip&gt;<br>
<br>
Just to turn this on its head for a second, can we come at this from anothe=
r angle? Instead of identifying teams who should report, how about we think=
 about what&#39;s happened that might be newsworthy, and then figure out wh=
o&#39;s best placed to report on it?<br>

<br>
The stuff that comes to mind for me is:<br>
=A0* Board elections + review of last board year<br>
=A0* GUADEC 2013 call for hosts out (and, related, no Desktop Summit in 201=
3)<br>
=A0* GUADEC 2012 keynotes to be announced<br>
=A0* Half-way point in Women&#39;s Outreach Program<br>
=A0* GNOME in Google Summer of Code<br>
<br>
<br>
Anything else? I haven&#39;t been following too closely this quarter.<br>
<br>
Cheers,<br>
Dave.<br>
<br>
<br>
-- <br>
Dave Neary<br>
GNOME Foundation member<br>
<a>[email protected]</a><br>
Jabber: <a>[email protected]</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
usability mailing list<br>
<a>[email protected]</a><br>
<a href=3D"https://mail.gnome.org/mailman/listinfo/usability" target=3D"_bl=
ank">https://mail.gnome.org/<u></u>mailman/listinfo/usability</a><br>
</blockquote></div><br><br>-- <br><font color=3D"#666666">Regards,<b><font =
size=3D"4"><br></font></b></font><div><b><font size=3D"4" color=3D"#c0c0c0"=
>@</font><font size=3D"4" color=3D"#666666">AllanCaeg</font></b><div><div><=
font color=3D"#666666">User Experience + Product Management</font></div>
<div><font color=3D"#666666"><br></font></div><div><font color=3D"#666666">=
<a href=3D"http://allancaeg.com" target=3D"_blank">allancaeg.com</a></font>=
</div><div><font color=3D"#666666">+63 918 948 2520</font></div></div></div=
><br>

--f46d042f97908900eb04c3ce923c--

--===============1163062552==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline