Re: GNOME Summit pre-registration announcement
Le mercredi 07 septembre 2016 à 16:29 +0200, Andreas Nilsson a écrit : > > Do you mean 20 to 50 by this time of the year, or 20 to 50 at the event? > > > I'm not sure how it is for the Summit usually, but as far as I've seen for GUADEC, people sign up preeetty late in general. Nah, 20-50 at the time of the event. I just thought people would be so overjoyed of finally seeing that wiki page appearing that they would jump on the opportunity to write to it ;) ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
GNOME Summit pre-registration announcement
Hi all, I announced the GNOME Summit on Planet GNOME, my own social media, and on foundation list: https://mail.gnome.org/archives/foundati on-list/2016-September/msg6.html I'm a bit surprised by the low amount of registrations so far. We usually have between 20 and 50 participants signing up. Perhaps you could also broadcast this through your channels##SELECTION_END##?___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Merchandise page on gnome.org
Looks good to me, thanks for taking the time to work on this, Allan!___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Annual Report - Bugzilla stats?
Le mercredi 22 juin 2016 à 09:56 -0700, Adelia Rahim a écrit : > If I have to choose only one to include, I would choose the yearly > summary since the top 5 lists are more useful only when analysed and > extended and explained in the report. Yeah... > The summary however, makes sense when viewed together over the years (e.g. 3 > years) > –> since the objective is to give an idea of the level of activity > happening in the project – rather than broken up. Does it, though? Sure, I could plot a decade-long stacked bars or stacked lines chart that shows the activity varying slightly (and generally going slowly downwards), but is that helpful engagement-wise? Besides the moderate downwards trend, those stats are pretty much the same every year: about 25±3k new bug reports, 25±3k resolved reports, and 46±3k remaining open bug reports... so I'm not sure the multi-year comparison is terribly useful in the grand scheme of things?___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Annual Report - Bugzilla stats?
Just got an idea then: let's simply rip out the most significant stat(s) (ex: total number of opened/closed bugs) and turn them into factoids to be inserted somewhere along the text? ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Annual Report: layout draft done
Hi all, in the "Annual Report preparation" folder in OwnCloud you will find a render of the current state of the Annual Report. Texts and layout are final unless you spot last minute errors. Things I still need to do: Proper infographics (for the events/releases, and for the financial report) A table for the 2nd page of the financial report Proper credits (and updating the table of contents/page numbers) Finish the adboard logo wall Redo the appearance of the factoids (to use the texture of the cover/back), unless you folks would actually prefer I keep them the way they are :)##SELECTION_END## ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Annual Report - Bugzilla stats?
Le mardi 14 juin 2016 à 12:39 +0200, Bastien Nocera a écrit : > Apart from having your name in the report, if you're one of the > people in the list, this is useful when analysed, and would be even > more useful when extended. > > For example, you might want to have a list of people who don't work > for vendors to be listed, explain why some folks are high up on the > list (they're paid to work on a core component), highlight community > contributors, show that there is peer-review, that bugs are fixed > (maybe even long-standing bugs), etc. > > If it's a copy/paste of the yearly stats that the bugmasters send on > New Year's day, then it's not useful in the report except for one's > bragging rights. That would be very cool indeed... the problem is getting someone (or an easy technique) to do the analysis without too much difficulty. Do you have something in mind? Otherwise we get either the same formula or taking it out entirely... ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Annual Report - Bugzilla stats?
Hi all, A question came up during a discussion today: the Annual Report has traditionally had a full page dedicated to "Bugzilla stats". What is its fundamental purpose? Do you know people who read it or expect it in the report each year, vs other types of stats and facts? Would you rather keep it as is in the report this year or not?##SELECTION_END##___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Annual report: Drafts review
Le mardi 24 mai 2016 à 10:43 +0200, Andreas Nilsson a écrit : > Wasn't there even an xdg-app/flatpak for the unstable version? Oh, didn't know if there was such a thing... just grabbed the easiest thing I could get my hands on, which at that time was the F23 COPR! ___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Annual report: Drafts review
I have now pushed the current state of my initial layout work onto http s://github.com/gnome-design-team/gnome-marketing/tree/master/annual- report/FY2015 (just in case something terrible happens to my computers) Currently this is in Scribus format only; it's so rough that it's not really meant for the "public at large" to look at anyway (last time there was an incident where one particular news site picked up our work-in-progress report in that repository, and their readership started criticizing our report for not being complete/having errors/etc.)... Besides the missing texts (I really want a "text freeze" deadline where everything is proofread and fixed, so I can get the green light to use final texts—as things are too fuzzy at the moment, I haven't even set the margins and page numbering properly), I'll need to figure out the arrangement of images and graphics... But for that, we need to complete the image collection. Cassandra started choosing pictures for the events (hackfests, conferences) articles and outreach, but the rest remains to be found & triaged. Some of the existing pictures are too low resolution to be used in print, too. Cassandra, maybe you could rename your pictures folder "FY2015 Annual Report" (or something clear like that) and share it "read+write" with the "Engagement Team" group in OwnCloud to facilitate collection & triaging? TLDR: there's progress on the layout front, but until I get complete contents I would not obsess too much over this draft layout file—it's not the blocker currently.##SELECTION_END##___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: NOTES | GNOME Social Media Hackathon on March 5th
Le dimanche 6 mars 2016 à 00:33 -0800, Nuritzi Sanchez a écrit : > Twitter > There is only one login and password that multiple people share. This is suboptimal indeed. Twitter (or at least TweetDeck, which is a part of Twitter) allows delegating an account to owners of other accounts, without passwords involved (I think the feature is called "teams", but I thought I've been using that before it was announced as such). Check it out!___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Do we have a calendar?
Do we have such a thing as an online collaborative calendar for the Engagement team? Something where we can put deadlines for events/publications/etc., that people could subscribe to in Evolution, GNOME Calendar, etc. Looking at the Annual Report's planning wiki page, it occurred to me that this might be quite helpful to keep us all on track (well, at least those of us who live and die by calendars :) I created a calendar in cloud.gnome.org (and shared it with the "Engagement team" group) but it doesn't seem like one can just plug that into Google Calendar...##SELECTION_END##___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: infographic rev 0
Le lundi 08 février 2016 à 18:33 +, Allan Day a écrit : […] > I've had a rough go at sketching out an infographic that communicates > some of this information. Some things are missing, and some parts are > quite rough: https://dl.dropboxusercontent.com/u/5031519/gnome-year-i > nfographic.png Sorry folks, in the flurry of things here, and with my mail filters hiding this thread from my view, I forgot about this til today. I have to say wow, Allan, that version of yours looks really good. Other than the bottom part (specifically the "}", the arrows and the background of some of the distributors' logos), I'm not sure what else you could consider in need of work there. Do you have specific items that bug you? Otherwise I think we could roll with that and call it a day…___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Some branding guidelines and historical info lost in migration
Hi all, There were some interesting contents in https://wiki.gnome.org/action/r ecall/BrandGuidelines?action=recall=58 that were lost in the migration to https://www.gnome.org/logo-and-trademarks/ - namely, the detailed spacing guidelines and the origins of the logotype. For instance, this paragraph: > The font used in the GNOME logo type is a hand-tweaked version of > Bitstream Vera Sans, an openly-licensed font. There is no full > version of this tweaked font available - only the vector outlines of > the GNOME letters. It was tweaked to have similar features to the > older logotype - most notably how far the middle point of the 'M' > extends and at a point rather than flat. Shouldn't we add this information back somewhere? Maybe as an explanatory sub-item of "Don’t modify the word “GNOME” or compound it with other words." - you don't want folks to use the GNOME foot with "GNOME" written in Comic Sans Neue ;)___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: infographic rev 0
Beyond the execution, details and visual polish, what do you folks think of the concept in general? And the contents? FWIW, there are also alternative ways to represent a timeline generally (with a circle, spiral, serpent, or some other object metaphor). Open to any ideas.___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: app idea generation..
Le dimanche 31 janvier 2016 à 23:20 +, Sriram Ramkrishna a écrit : > How many food recipe apps are out there that look good, designed > well, and has the kind of features for the Internet age? Probably > none. As an aside and purely for your curiosity: there's http://jeff.ecchi.ca /blog/2010/10/13/introducing-recipe-manager/ but as you can see there was no community interest and one year down the road I didn't have time anymore to continue fixing all the remaining issues and implement new things (port to GTK3, have a website scraper, an online sharing system instead of the link-local/avahi one, a better UI/UX, etc.).___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Statement of support for the SFC's campaign
Thanks for continuing the work on this! Looking at the evolution of the draft, I see that there was this opening sentence that was removed: > The GNOME community dedicated the last 18 years to building a > cohesive desktop experience for our users. We have created a library > of work that is found not only in our desktop but also in various > other important software and hardware. It seemed okay/nice-to-have, so I'm just curious to hear the reasoning for removing it?___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Statement of support for the SFC's campaign
Hi all, It would be nice of us to make a public statement of support for the SFC's campaign* to raise funds for their continued existence and their legal battle to uphold the GPL (against infringement by VMWare)**. The FSF has made such a blog post already***. I discussed with the board, and they'd like the engagement team to send an announcement to that effect, also using our social media outlets. It should happen sooner rather than later, as there is a window of opportunity there: donations made until January 31st will be matched up by PIA and thus count twice. Thanks! *: https://sfconservancy.org/supporter/ **: https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/ ***: https://www.fsf.org/blogs/executive-director/support-the-software- freedom-conservancy___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: Kicking off some questions for the 2015 sysadmin sponsorship brochure (or fundraising campaign)
Hullo again, o wise ones! To help provide background and ammunition for the brochure, Andreas published a report on his activities in the sysadmin role: https://www. dragonsreach.it/2015/12/02/three-years-and-counting/ I would really appreciate the team giving me some input, on the questions I raised in my previous mail in this thread. It is much easier for me to do the work full-steam with the assurance that y'all agree on the principle.___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: current prospectus for LAS GNOME
I didn't see it in the "gnome-marketing" github repo, so could you throw the .odt/source file out here so I can polish its looks a bit?___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: I need a logo :)
Yes, technically it could only be a wordmark written with http://www.co micneue.com ;;)___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
Re: I need a logo :)
As usual I'm happy to work on the graphical execution (unless another
designer wants to go for it), if people here would like to discuss and
come up with the base idea ("concept"). Having a brainstorm as a
starting point can be helpful. There is also the question of if/how
"GNOME" gets incorporated into such a logo...___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list
Kicking off some questions for the 2015 sysadmin sponsorship brochure (or fundraising campaign)
Hi all, You may be familiar with the fact that circa 2010, we ran a successful fundraising campaign to allow the GNOME Foundation to hire a part-time sysadmin (see also http://www.vuntz.net/journal/post/2010/06/02/Hiring- a-sysadmin-for-the-GNOME-infrastructure for a memory refresher). This has served us well throughout the years: both the reliability and the scope of services offered on the GNOME infrastructure rose a lot since then. As of 2015, this fund has now been depleted. Personally, I find it rather impressive that we've managed to do so much, for as long as five years, with the money raised back then (around 45k total if we take into account the money contributed through Friends of GNOME during that campaign). For some time* now, I've had in my mind to prepare some "marketing collateral" (such as a brochure) to prepare a new campaign, seeing this as an opportunity to try bringing in a new set of sponsors this time around, and perhaps raise a bigger amount that would allow us to accomplish more work on our infrastructure. A while ago I started a draft/braindump on my end, but before I spam you with such a wall of text, I would like to know who would be interested to help with this. Globally, this project will involve: Thinking about the amount of money we want to aim for, what we'll achieve with it. To give you a rough idea, the work done with our part -time sysadmin (Andrea), over the past two years, costs an average of 1200 USD per month (roughly). In my view we ought to try to raise as much money as we can for this, and if we do raise significantly more than last round's 45K, it might mean we can assign additional resources or that we can keep going for longer. Figuring out who our target audience and sponsors would be. Besides the traditional prospects in our circles, I was thinking this can be a nice opportunity to involve cloud/hosting companies and get them closer to GNOME that way. We'll need contacts in those organizations for that to work, though. Thinking about the perks that sponsors get for various levels (if any?) of sponsorship Considering whether a traditional brochure-style print/PDF document is the way to go, or if it should be some sort of dynamic crowdfunding -style micro-site, or... Whether we take the "one big fundraiser every few years" approach, or if we do some sort of annual/recurrent "subscription" supporter model. I'm under the impression the monolithic fundraising approach is easier and better (not sure we want to be hunting for funds all the time for this particular aspect). What our timeframe should be. This has been an "ASAP" item for a while but we need a deadline here. Unfortunately it's quite late as corporate budgets are being set as we speak (end of year 2015), though there is the non-negligible opportunity of leveraging year-end donations by individuals. Thoughts? Going through the wealth of information in https://wiki.gnome.org/Sysadmin/ and digesting that into a compelling pitch. Or, alternatively, just taking the existing draft/plan I had written some time ago and extending (or simplifying!) it. Designing the documents (or website) that would serve as the medium for this message. I think once we start answering a couple of the initial questions above I should be able to complete my notes/draft and turn that into a wiki page for review (or we could have a collaborative editing session with etherpad if you prefer). We'll need to start pushing for this as soon as possible to ensure the continuity of our infrastructure work. I do think this a pretty interesting marketing project, so I thought I'd share the fun here! ;) Any takers who would like to help make this happen? *: In fact, I initially touched upon this subject here during the winter... https://mail.gnome.org/archives/engagement-list/2015-March/ms g00019.html___ engagement-list mailing list engagement-list@gnome.org https://mail.gnome.org/mailman/listinfo/engagement-list
