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
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:
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 essenti
y
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 Engag
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
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
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
> >
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 thi
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
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
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,
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
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
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
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
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
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.
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
> sec
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>
> wr
> 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 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
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
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
23 matches
Mail list logo