Re: No more release notes for me

[Alexandre Franke]

On Sat, Mar 3, 2018 at 6:16 AM, Link Dupont  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
___
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 
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

engagement hackfest

[Sriram Ramkrishna]

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.

We could do it either in Denver, SFO, or some other place.  It seems most
of the engagement people are in the U.S.  But it would be nice to get
people from Asia involved.

How about we do something either prior to GUaDEC or afterwards.

One other possibility is doing it during LAS or after LAS.

sri
___
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  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: No more release notes for me

[Sriram Ramkrishna]

Hi Allan!

On Fri, Mar 2, 2018 at 11:02 AM Allan Day  wrote:

>
> Fast-forward six years, and I've been the principle author of the
> release notes for pretty much every GNOME 3 release - that's 15
> releases in total. I think that it's well time for me to pass the
> baton on to someone else, so I've decided that GNOME 3.28 will be the
> last time that I take charge of the release notes.
>

Thank you for doing them all these years!  Much appreciated!


>
> I'm giving you all plenty of notice, so that you can plan for 3.30.
> Also, I'll still be around to advise, and I'm happy to onboard anyone
> who wants help getting started. However, I don't intend to be the
> primary author in the future.
>
>
Totally respect this decision and it gives a chance for someone else new to
the team to take over and do them.  Let's try to figure out how to do them
for the next year and see who would be willing to them forthwith.

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