Re: If anyone wants a writing task during GUADEC

[Link Dupont]

Rosanna, All,

Thanks for the reminder about this. I attached the list of questions 
for the interview to the issue. If you feel like interviewing anyone, 
please just take notes. Don't worry about detailed or complete answers 
to all the questions.


Once I have an interview form completed, I will take the responses and 
format them into an article. This is the same process the "How Do You 
Fedora" series uses.


Have fun at GUADEC!

On Thu, Jul 5, 2018 at 12:30 AM, Rosanna Yuen  wrote:

Hi,

GUADEC is a great time to do interviews with attendees for the GNOME 
Engagement Blog. If you are interested in meeting more GNOME people 
and helping out the engagement team by writing a blog post for it, 
that would be awesome!  The gitlab issue with some suggested people 
we want to cover is 
https://gitlab.gnome.org/Community/Engagement/General/issues/93


Please remember the goal of the engagement blog is to highlight the 
people in GNOME and not the technologies. In addition, highlighting 
the diversity in GNOME is highly encouraged.


See you at GUADEC!
-Rosanna

--
Rosanna Yuen
Director of Operations
GNOME Foundation, Inc.


___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Position of Activities Button

[Link Dupont]

Hi Pierre,

You can do just that with the Dash-to-Dock extension. As for making 
that change the default in the shell, that's a discussion for the 
design team, not the engagement team.


Link

On Thu, May 31, 2018 at 2:57 PM, Pierre Muller 
 wrote:

Hello,

I use gnome intensively and I think it is a good good interface.
But I regret that the button for further programms is positionned
under the shortcuts. I suggest something like in the attached picture.

What do you think about that?

Regards,
Pierre
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Section from "What's New in Fedora 28 Workstation?" article for Fedora Magazine

[Link Dupont]

I've created a Gitlab issue to track the status of drafting this
article.

https://gitlab.gnome.org/Community/Engagement/Social-Media-and-PR/issue
s/14

On Mon, 2018-04-23 at 21:56 -0700, Link Dupont wrote:
> Thanks for your feedback everyone! I spent some time rewriting the
> article, and it has expanded into a much larger piece. I will
> probably
> be writing this as a separate article, or at least as a part of a
> larger article about GNOME.
> 
> Considering the size, I drafted it in a wiki page instead of a paste
> in
> an email.
> 
> https://wiki.gnome.org/LinkDupont/FilesDesktopIcons
> 
> I feel like the larger format was necessary to explain the scenario
> in
> more detail.
> 
> On Mon, 2018-04-23 at 07:10 -0700, Link Dupont wrote:
> > Thank you, that makes a ton of sense. I'll see what I can create
> > for
> > a
> > second draft.
> > 
> > Link
> > 
> > On Mon, 2018-04-23 at 09:42 +0100, Allan Day wrote:
> > > Thanks for reaching out about this, Link. I know from experience
> > > that
> > > writing about contentious decisions can be tricky to get right.
> > > 
> > > Liam R. E. Quin <l...@w3.org> wrote:
> > > ...
> > > > Remember that the only people made happy by removing features
> > > > generally
> > > > are developers...
> > > 
> > > I agree with Liam here. Introducing features that users
> > > appreciate
> > > as
> > > "technical debt" is only going to irritate them.
> > > 
> > > My suggestion would be to:
> > > 
> > >   1. Start with a more positive, user-centered, narrative: how
> > > the
> > > Nautilus developers are working to improve the experience for
> > > users.
> > > What they've done recently to do that, what they're planning to
> > > do.
> > >   2. The current draft makes the removal sound like an
> > > implementation
> > > failure rather than a technical design question. I think it's
> > > important to explain it in terms of the intrinsic nature of icons
> > > on
> > > the desktop - it's a very different file browsing experience.
> > >   3. Stress that the Nautilus developers do care about those who
> > > use
> > > icons on the desktop. Emphasise that alternatives have been
> > > considered. Argue that the people using those alternatives is a
> > > better
> > > option for them and for everyone as the code base moves forward.
> > > 
> > > Allan
> > 
> > ___
> > engagement-list mailing list
> > engagement-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/engagement-list
> 
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Section from "What's New in Fedora 28 Workstation?" article for Fedora Magazine

[Link Dupont]

Thanks for your feedback everyone! I spent some time rewriting the
article, and it has expanded into a much larger piece. I will probably
be writing this as a separate article, or at least as a part of a
larger article about GNOME.

Considering the size, I drafted it in a wiki page instead of a paste in
an email.

https://wiki.gnome.org/LinkDupont/FilesDesktopIcons

I feel like the larger format was necessary to explain the scenario in
more detail.

On Mon, 2018-04-23 at 07:10 -0700, Link Dupont wrote:
> Thank you, that makes a ton of sense. I'll see what I can create for
> a
> second draft.
> 
> Link
> 
> On Mon, 2018-04-23 at 09:42 +0100, Allan Day wrote:
> > Thanks for reaching out about this, Link. I know from experience
> > that
> > writing about contentious decisions can be tricky to get right.
> > 
> > Liam R. E. Quin <l...@w3.org> wrote:
> > ...
> > > Remember that the only people made happy by removing features
> > > generally
> > > are developers...
> > 
> > I agree with Liam here. Introducing features that users appreciate
> > as
> > "technical debt" is only going to irritate them.
> > 
> > My suggestion would be to:
> > 
> >   1. Start with a more positive, user-centered, narrative: how the
> > Nautilus developers are working to improve the experience for
> > users.
> > What they've done recently to do that, what they're planning to do.
> >   2. The current draft makes the removal sound like an
> > implementation
> > failure rather than a technical design question. I think it's
> > important to explain it in terms of the intrinsic nature of icons
> > on
> > the desktop - it's a very different file browsing experience.
> >   3. Stress that the Nautilus developers do care about those who
> > use
> > icons on the desktop. Emphasise that alternatives have been
> > considered. Argue that the people using those alternatives is a
> > better
> > option for them and for everyone as the code base moves forward.
> > 
> > Allan
> 
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Section from "What's New in Fedora 28 Workstation?" article for Fedora Magazine

[Link Dupont]

Thank you, that makes a ton of sense. I'll see what I can create for a
second draft.

Link

On Mon, 2018-04-23 at 09:42 +0100, Allan Day wrote:
> Thanks for reaching out about this, Link. I know from experience that
> writing about contentious decisions can be tricky to get right.
> 
> Liam R. E. Quin  wrote:
> ...
> > Remember that the only people made happy by removing features
> > generally
> > are developers...
> 
> I agree with Liam here. Introducing features that users appreciate as
> "technical debt" is only going to irritate them.
> 
> My suggestion would be to:
> 
>   1. Start with a more positive, user-centered, narrative: how the
> Nautilus developers are working to improve the experience for users.
> What they've done recently to do that, what they're planning to do.
>   2. The current draft makes the removal sound like an implementation
> failure rather than a technical design question. I think it's
> important to explain it in terms of the intrinsic nature of icons on
> the desktop - it's a very different file browsing experience.
>   3. Stress that the Nautilus developers do care about those who use
> icons on the desktop. Emphasise that alternatives have been
> considered. Argue that the people using those alternatives is a
> better
> option for them and for everyone as the code base moves forward.
> 
> Allan

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Section from "What's New in Fedora 28 Workstation?" article for Fedora Magazine

[Link Dupont]

Hello Engagement team,

I am writing an article for Fedora Magazine titled "What's New in
Fedora 28 Workstation?" Among the new features, I wanted to use this as
a platform to communicate to the Fedora users about the Nautilus
desktop changes in 3.28. The Fedora Magazine is a very popular site for
Fedora users and it is an excellent conduit for distributing news about
the project.

Here is my current draft of the section about Nautilus. Please let me
know if we (as the GNOME engagement team) like the way this is
messaged, of if we want to change it:

> New features isn't always about addition; sometimes, a new feature
> means removing something. For years (since GNOME 3.0 was released),
> Files has been carrying some technical debt. In GNOME 3.28, the
> development team finally removed a long-unmaintained section of
> Files. In contrast to other commercial desktop operating systems and
> even other Linux desktop platforms, GNOME does not present icons on
> the desktop. This was a deliberate design decision, and continues to
> be the normal desktop behavior.
> 
> However, Files continued to include the option to put icons on the
> desktop, should the user choose to enable the option. Over the years,
> the development team tried to preserve and isolate the desktop icon
> code from the rest of Files. While they achieved some level of
> isolation, ultimately the changes introduced more problems than they
> intended to solve. Now the desktop icon code is actively blocking
> future development and feature enhancements. So in GNOME 3.28, this
> option (along with all the code that enabled it) has been removed. A
> lengthy technical discussion about the merits and reasoning behind
> this decision is available on the GNOME team's development website.
> 
> Many Fedora users should not be affected by this; the default
> behavior shipped in "upstream" GNOME (to not put icons on the
> desktop) is mirrored in Fedora's implementation of GNOME. Advanced
> users who have previously enabled desktop icons will find that Files
> no longer presents icons on the desktop. Those files can still be
> accessed via the Desktop folder inside Home.
> 
> For those users who do still want desktop icons, there are two
> solutions. The immediate solution is to use a different file browser,
> such as nemo. See Alternative Solution on the GNOME development
> website for instructions on how to install nemo and launch it on
> login.
> 
> The long-term solution proposed by the developers is to create a
> GNOME Shell extension that puts icons on the desktop. While a
> prototype is available, it is not ready for daily use.

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: No more release notes for me

[Link Dupont]

Hey all,

Just to close the loop on this, I'll be taking an active role in
wrangling the release notes for the upcoming 3.30 and beyond.

Link

On Sat, 2018-03-03 at 09:03 -0800, Link Dupont wrote:
> 
> 
> On Mar 2, 2018, at 11:22 PM, Alexandre Franke <afra...@gnome.org>
> wrote:
> 
> > On Sat, Mar 3, 2018 at 6:16 AM, Link Dupont <l...@sub-pop.net>
> > wrote:
> > > Could we migrate the release-notes repo to a project under
> > > gitlab? That might
> > > make collaboration on them easier for the team.
> > 
> > I suggest not making that move not that we’re in the middle of
> > translations and that the notes for this release are done anyway.
> > As the plan is to migrate all of the remaining modules in the
> > coming months, it should be on Gitlab for the next release.
> > 
> > ___
> > engagement-list mailing list
> > engagement-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/engagement-list

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: engagement hackfest

[Link Dupont]

Who's going to LinuxFest Northwest in April?

On Fri, 2018-03-16 at 05:41 +, Sriram Ramkrishna wrote:
> Agreed! 
> 
> On Tue, Mar 6, 2018 at 2:19 AM Allan Day  wrote:
> > Sriram Ramkrishna  wrote:
> > > I'd like to start on an engagement hackfest.  Mostly I'm interested in
> > > fixing our website and wiki.  I'd like to use the notes from our last
> > > hackfest we had a couple years ago because I think we had some good
> > > information there that I feel we didn't quite follow up the last time.
> > 
> > This is a great idea, Sri. It's been far too long since there's been a
> > dedicated Engagement Hackfest.
> 
> Let's try to figure out a good time then.  I'd like to do it before GUADEC if
> possible.  We'll need to figure out a location and month.  More importantly,
> an agenda.
> 
> I would start building better process, the beginnings of a new website design
> with a purpose.  that might be too big of a scope for the two or three days?
> 
> Once we nail down what is important to us to focus on what we want to work on.
> 
> sri
>  
> > Allan
> 
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list


signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: No more release notes for me

[Link Dupont]

> On Mar 2, 2018, at 11:22 PM, Alexandre Franke <afra...@gnome.org> wrote:
> 
>> On Sat, Mar 3, 2018 at 6:16 AM, Link Dupont <l...@sub-pop.net> wrote:
>> Could we migrate the release-notes repo to a project under gitlab? That might
>> make collaboration on them easier for the team.
> 
> I suggest not making that move not that we’re in the middle of translations 
> and that the notes for this release are done anyway. As the plan is to 
> migrate all of the remaining modules in the coming months, it should be on 
> Gitlab for the next release.
> 
> -- 
> Alexandre Franke
> GNOME Hacker & Foundation Director

Yea, that was what I was thinking. No need to rush and do it now.___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

[PATCH] Fix incorrect screenshot name

[Link Dupont]

Hi all,

I couldn't find a product to file a bug under for the release-notes repo, so I'm
doing it old school. Here's a patch that fixes a typo in help/Makefile.am. The
incorrect filename was causing make to fail.From ddcc54a87f02bec33cc9738484c5f82a7fc5cda7 Mon Sep 17 00:00:00 2001
From: Link Dupont <l...@sub-pop.net>
Date: Fri, 2 Mar 2018 21:23:03 -0800
Subject: [PATCH] Fix incorrect screenshot name

---
 help/Makefile.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/help/Makefile.am b/help/Makefile.am
index 9e4fc5e0..8dafce26 100644
--- a/help/Makefile.am
+++ b/help/Makefile.am
@@ -15,7 +15,7 @@ HELP_MEDIA = \
  figures/files-starred.png \
  figures/flatpak.png \
  figures/osk.png \
- figures/photo-import.png \
+ figures/photos-import.png \
  figures/placeholder.png \
  figures/usage-performance.png
 
-- 
2.14.3



signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: No more release notes for me

[Link Dupont]

On Fri, 2018-03-02 at 21:00 -0800, Link Dupont wrote:
> On Fri, 2018-03-02 at 19:13 +, Allan Day wrote:
> > Sriram Ramkrishna <s...@ramkrishna.me> wrote:
> > ...
> > > Totally respect this decision and it gives a chance for someone else new
> > > to
> > > the team to take over and do them.
> > 
> > Thanks Sri! Ideally, I think the release notes would be owned by the
> > whole team and would form part of the overall engagement schedule,
> > rather than being the sole preserve of a single individual. It's
> > important that we have some collective responsibility and some
> > oversight, to make sure that things happen when they're supposed to.
> > 
> > > Let's try to figure out how to do them
> > > for the next year and see who would be willing to them forthwith.
> > 
> > My suggestion would be to start looking at release marketing about two
> > months out - so mid-July for the next release.
> > 
> > Allan
> > ___
> > engagement-list mailing list
> > engagement-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/engagement-list
> 
> I agree it should be a shared responsibility of the whole team. I personally
> have an interest in the release notes as I've always imagined writing a
> "What's
> new in GNOME in Fedora $NEXT" article for the magazine. Having release notes
> is
> key to that article. I can see them being used as the basis for social media
> posts too.
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list

Could we migrate the release-notes repo to a project under gitlab? That might
make collaboration on them easier for the team.

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: No more release notes for me

[Link Dupont]

On Fri, 2018-03-02 at 19:13 +, Allan Day wrote:
> Sriram Ramkrishna  wrote:
> ...
> > Totally respect this decision and it gives a chance for someone else new to
> > the team to take over and do them.
> 
> Thanks Sri! Ideally, I think the release notes would be owned by the
> whole team and would form part of the overall engagement schedule,
> rather than being the sole preserve of a single individual. It's
> important that we have some collective responsibility and some
> oversight, to make sure that things happen when they're supposed to.
> 
> > Let's try to figure out how to do them
> > for the next year and see who would be willing to them forthwith.
> 
> My suggestion would be to start looking at release marketing about two
> months out - so mid-July for the next release.
> 
> Allan
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list

I agree it should be a shared responsibility of the whole team. I personally
have an interest in the release notes as I've always imagined writing a "What's
new in GNOME in Fedora $NEXT" article for the magazine. Having release notes is
key to that article. I can see them being used as the basis for social media
posts too.

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: community input..

[Link Dupont]

On Thu, Dec 7, 2017 at 8:00 PM, Christian Hergert 
 wrote:
We need more contributors to GNOME that aren't burdened by being knee 
deep in code every day. We need people focusing on the product 
road-map. That requires user feedback, analyzing bug velocity and 
common issues, helping developers prioritize while maintaining the 
product vision, and responsibility for the quality of the end product.


This is an idea worth exploring. It certainly opens avenues for people 
to contribute who aren't software developers.


There are endless arguments at companies about how to do this. Do you 
have specialized teams by role (ie: "design team" or "QA team") or a 
representative of each product performing these roles (or a hybrid).


Could we run an experiment on a specific project and see how it goes? 
For example with Builder, what function do you feel is lacking the most?


~link

___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: testing a new process for social media

[Link Dupont]

FWIW, FESCo and other Fedora teams often use Pagure projects to track 
issues. It might be worth seeing how some of those teams sort and 
organize tasks into issues.


https://pagure.io/fesco
https://pagure.io/fedora-marketing

On Sun, Nov 5, 2017 at 6:21 PM, Sriram Ramkrishna  
wrote:



On Sat, Nov 4, 2017 at 9:05 AM Rosanna Yuen  wrote:
Is there documentation/walkthrough as to how this process would 
work? Especially for those of us who have never used gitlab before?


Otherwise this seems like another technical barrier to entry for 
what should be a relatively nontechnical task.


Not yet, as I'm still familiarizing myself with gitlab.  It'll try to 
document something this week and we can poke at it and see if it is 
the right tool.  I'm hesitant to add new tools because it just adds 
more burden to the sysadmin team.  But I think something to track it 
as a ticket I think would be useful than none at all.


sri



On Fri, Nov 3, 2017 at 10:34 PM, Sriram Ramkrishna 
 wrote:

Carlos Soriano was kind enough to create
http://gitab.gnome.org/GNOME/engagement, and so you can now create 
issues for things like we want to advertise.  As a test, I have put 
in November Bug Squash Month - 
https://gitlab.gnome.org/GNOME/engagement/issues/1.


This way we have some way to track the things that need to be done 
and close them out easily when complete.


sri

___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list





--
Rosanna Yuen
Director of Operations
GNOME Foundation, Inc.


___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: 3.26 release marketing - outstanding tasks

[Link Dupont]

On Sat, 2017-09-09 at 06:35 +, Sriram Ramkrishna wrote:
> On Fri, Sep 8, 2017 at 9:52 PM Link Dupont <l...@sub-pop.net> wrote:
> > On Fri, Sep 8, 2017 at 12:20 PM, Allan Day <a...@gnome.org> wrote:
> > > Screenshot pack: this isn't essential, but if someone wants to do it,
> > > there are instructions on the wiki [3] and you can see what we've
> > > done in previous releases. You'll need to combine the screenshots I
> > > took (which are in Nextcloud) with Andreas's and the ones from the
> > > release notes.
> > 
> > I noticed an inconsistency in the screenshots in the 3.24 pack. Some
> > are taken with HiDPI while others are clearly not. Is there a desired
> > DPI and resolution that all screenshots should be taken at?
> > 
> 
> I would just go with HiDPI but not sure what resolution and DPI that would be.
> 
> sri

I wonder if we could take a more systematic approach to the screenshots in
general. There are discrepancies between screenshots shown in the shell and
other minor preferences that differ from the shipped GNOME defaults.

Is Continuous up to the task of being used for screenshots? Could some even be
automatically taken by injecting keypress events?

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: @planetgnome Twitter account?

[Link Dupont]

Hi Bastien,

I'm not sure if anyone answered you off list, but I don't see 
@planetgnome listed on the Engagement Communication Channels page[1] 
(I'm sure this list is not exhaustive, though).


@planetgnome is following Nuritzi though, so maybe Nuritzi knows?

1: https://wiki.gnome.org/Engagement/Channels

On Sun, Sep 10, 2017 at 8:52 AM, Bastien Nocera  
wrote:

Hey,

This account came to my attention:
https://twitter.com/planetgnome

Is this one we control? Could we remove it, or update whichever bot is
used to proxy the posts?

Cheers
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list


___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: RFC Release Party Engagement Blog post

[Link Dupont]

Oh good catches, all of them. I've made those changes and posted it as 
a draft on the engagement blog. Others with access can view/edit it 
there.


~link

On Sat, Sep 9, 2017 at 5:56 PM, Cassandra Sanchez 
<cassandra.s...@gmail.com> wrote:

Hey Link,

As you know, I love your post idea! I just noticed a couple of 
changes I'd suggest:
First sentence "GNOME 3.26 is almost here" - looks like you're 
missing that middle "is"

Might change "Plan one, obviously!" to "You can plan your own!"
In the sentence "The Engagement Team may have extra stickets on hand" 
there's a typo in the word "stickers"
I might change: "There is funding available to help organize release 
parties. Check out the Events page for details" to " Whether you're a 
foundation member or not, you can request funding for your party by 
following the steps on the Events page."
Let me know if you have any questions :) and feel free to use or not 
use any of the above!


- Cassandra

On Fri, Sep 8, 2017 at 9:38 PM, Link Dupont <l...@sub-pop.net> wrote:

Hello Engagement,

I've drafted a post that we hope to put up on the Engagement Blog on 
Monday about hosting a GNOME Release Party. I borrowed *heavily* 
from a post Rosanna made on her blog about a year ago, so much 
credit goes to her for this. I reworded it slightly with the 
intention of making it more clear to non-native English speakers. 
And I hope to write something that can be reposted (with minor 
updates) each new release. Please let me know if you feel anything 
should be added/removed/changed.


~link

--

Celebrate GNOME with a Release Party

GNOME 3.26 almost here. A new GNOME release is a milestone worth 
celebrating. It is a great reason to get together with other GNOME 
community members and celebrate.


Is there already a release party in your area? If there is, feel 
free to join. Release Parties are open to all GNOME enthusiasts. 
It's a wonderful opportunity to meet other GNOME users.


But what if there isn't one planned near enough for you attend? Plan 
one, obviously!


A release party can be as simple or elaborate as you want it to be; 
anything from getting a group together for celebratory drinks to a 
big event with decorations, food, and swag.


Some quick tips on organizing your own party:

* Have a rough estimate of the number of guests. While release 
parties tend to be open to anyone, it's a good idea to take a quick 
measure of who might be attending. Send a note on social media or 
local mailing lists asking who is interested.


* Have swag! If you have time and inclination, having GNOME stickers 
or other swag to give out is always popular. The Engagement Team may 
have extra stickets on hand; don't hesitate to ask.


* Have provisions! No party is complete without food. It can be 
something you provide, a potluck, or even a restaurant where guests 
can purchase food. There is funding available to help organize 
release parties. Check out the Events page for details.


* Select a time and location. Knowing what kind of party you are 
planning should help you decide on a location. Is there a local 
coffee house that would let you host your event if people plan on 
purchasing food and drink there? Or if it is a smaller group, maybe 
a local bar. For a larger group, consider a local park or a room in 
the local community center.


* Announce your bash. Let others know about your event by announcing 
it to the local user groups, posting it on social media, and adding 
it to the Events page. Have fellow enthusiasts help spread the word.


* Take lots of pictures! Everyone loves to see what fun release 
parties can be. Make sure you take pictures of the party in action 
and share your photos with GNOME so we can share them among the 
community.


* Pat yourself on the back. Thank you! You are helping cultivate the 
feeling of community that GNOME relies on.


___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list





___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: 3.26 release marketing - outstanding tasks

[Link Dupont]

On Fri, Sep 8, 2017 at 12:20 PM, Allan Day  wrote:
Screenshot pack: this isn't essential, but if someone wants to do it, 
there are instructions on the wiki [3] and you can see what we've 
done in previous releases. You'll need to combine the screenshots I 
took (which are in Nextcloud) with Andreas's and the ones from the 
release notes.


I noticed an inconsistency in the screenshots in the 3.24 pack. Some 
are taken with HiDPI while others are clearly not. Is there a desired 
DPI and resolution that all screenshots should be taken at?


___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

RFC Release Party Engagement Blog post

[Link Dupont]

Hello Engagement,

I've drafted a post that we hope to put up on the Engagement Blog on 
Monday about hosting a GNOME Release Party. I borrowed *heavily* from a 
post Rosanna made on her blog about a year ago, so much credit goes to 
her for this. I reworded it slightly with the intention of making it 
more clear to non-native English speakers. And I hope to write 
something that can be reposted (with minor updates) each new release. 
Please let me know if you feel anything should be added/removed/changed.


~link

--

Celebrate GNOME with a Release Party

GNOME 3.26 almost here. A new GNOME release is a milestone worth 
celebrating. It is a great reason to get together with other GNOME 
community members and celebrate.


Is there already a release party in your area? If there is, feel free 
to join. Release Parties are open to all GNOME enthusiasts. It's a 
wonderful opportunity to meet other GNOME users.


But what if there isn't one planned near enough for you attend? Plan 
one, obviously!


A release party can be as simple or elaborate as you want it to be; 
anything from getting a group together for celebratory drinks to a big 
event with decorations, food, and swag.


Some quick tips on organizing your own party:

* Have a rough estimate of the number of guests. While release parties 
tend to be open to anyone, it's a good idea to take a quick measure of 
who might be attending. Send a note on social media or local mailing 
lists asking who is interested.


* Have swag! If you have time and inclination, having GNOME stickers or 
other swag to give out is always popular. The Engagement Team may have 
extra stickets on hand; don't hesitate to ask.


* Have provisions! No party is complete without food. It can be 
something you provide, a potluck, or even a restaurant where guests can 
purchase food. There is funding available to help organize release 
parties. Check out the Events page for details.


* Select a time and location. Knowing what kind of party you are 
planning should help you decide on a location. Is there a local coffee 
house that would let you host your event if people plan on purchasing 
food and drink there? Or if it is a smaller group, maybe a local bar. 
For a larger group, consider a local park or a room in the local 
community center.


* Announce your bash. Let others know about your event by announcing it 
to the local user groups, posting it on social media, and adding it to 
the Events page. Have fellow enthusiasts help spread the word.


* Take lots of pictures! Everyone loves to see what fun release parties 
can be. Make sure you take pictures of the party in action and share 
your photos with GNOME so we can share them among the community.


* Pat yourself on the back. Thank you! You are helping cultivate the 
feeling of community that GNOME relies on.
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Reddit IAMA to support release

[Link Dupont]

On Fri, 2017-09-01 at 23:25 +, Sriram Ramkrishna wrote:
> We had talked in today's engagement meeting about doing an IAMA in /r/IAMA.  I
> was going to do it, but I would of course prefer if we had a group of people
> willing to help answer questions.  I figure that we can set some ground rules
> about what questions we won't answer.  Although I've noticed that in these
> IAMAs people tend to pick and choose anways.
> 
> It is a new kind of engagement for sure, but it's worth trying out once and
> see what the experience is.  As I said I'm willing to do it, but sometimes I
> don't always know what I'm talking about off the top of my head and it would
> be nice if people can flag questions worth answering.
> 
> I'm thinking I will put myself on whatever queue the IAMA people have.  Let me
> know what people think and whether they can help.
> 
> sri
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list

If I can make the time, I'm happy to help answer questions. I know a bit about
GNOME history, being a 1.x -> 2.x -> 3.x "survivor". I don't get offended by
hateful content on the Internet, so I can objectively decide what questions to
ignore or down-vote.

Logistically, if there's a few of us on the team, we might want to be on a
conference call during the AMA to coordinate/discuss what questions to answer.

Are there basic ground rules that the AMA subreddit enforces?

~link

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Community Guide Draft

[Link Dupont]

On Wed, 2017-08-23 at 15:27 +0100, Allan Day wrote:
> Link Dupont <l...@sub-pop.net> wrote:
> ...
> > I'm not sure. I know GNOME has a code of conduct[1] already, and this
> > certainly
> > overlaps a good deal. I read a few different CoC documents as I was thinking
> > about this, and many of them boil down to "be excellent to each other".
> > 
> > What is missing, and what I hoped to fill with a guide like this, is the
> > *how
> > to* "be excellent to each other". A guide on how to interpret and implement
> > the
> > Code of Conduct advice from the various perspectives in the community.
> 
> ...
> 
> The Contributor Covenant Code of Conduct [1] does something like that...
> 
> Allan
> 
> [1] https://www.contributor-covenant.org/version/1/4/
> 

Yea, like the examples, but specific for the GNOME community. I'll try to see if
other organizations have something like this already.

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: Community Guide Draft

[Link Dupont]

On Wed, 2017-08-23 at 11:55 +0100, Allan Day wrote:
> Hey Link,
> 
> Link Dupont <l...@sub-pop.net> wrote:
> ... 
> > After a lively discussion in #engagement about interacting with the
> > GNOME community, I thought about the idea of putting together a guide
> > that can be shared with both GNOME developers and GNOME users.
> 
>  ...
> > 1: https://wiki.gnome.org/LinkDupont/CommunityGuideDraft
> 
> You've got some good points there and I really like the idea of covering
> different perspectives.
> 
> Question: is this a code of conduct? :)
> 
> Allan

I'm not sure. I know GNOME has a code of conduct[1] already, and this certainly
overlaps a good deal. I read a few different CoC documents as I was thinking
about this, and many of them boil down to "be excellent to each other".

What is missing, and what I hoped to fill with a guide like this, is the *how
to* "be excellent to each other". A guide on how to interpret and implement the
Code of Conduct advice from the various perspectives in the community.

Maybe this does amount to simply expanding the existing Code of Conduct with
some of the perspective-oriented guidelines?

~link

1: https://wiki.gnome.org/Foundation/CodeOfConduct

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Community Guide Draft

[Link Dupont]

Hi everyone,

After a lively discussion in #engagement about interacting with the
GNOME community, I thought about the idea of putting together a guide
that can be shared with both GNOME developers and GNOME users. The goal
of this guide is to frame the conversation for both sides. Give them a
set of expectations and guidelines to understand how the other side is
viewing the conversation. I put together a brainstormed list of talking
points that I think the guide should cover[1]. Please comment/critique.

~link

1: https://wiki.gnome.org/LinkDupont/CommunityGuideDraft

signature.asc
Description: This is a digitally signed message part
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list