Re: [Design-team] Badge Ticket #414
by Justin W. Flory
On 06/14/2016 01:14 PM, Mary Shakshober wrote:
> Hi everyone, I'm new to the Fedora project and I just submitted my first design for a badge (ticket #414) and would love some feedback on the design. Thanks!
> https://fedorahosted.org/fedora-badges/ticket/414
>
Hi Mary, just wanted to say thanks for working on this one! This will be
a great one to have for the Community Blog, and can't wait to see what
the final badge looks like. I see mleonova already offered you some
feedback, and I'll also keep a watch on the ticket to offer any other
ideas / thoughts later.
Thanks again for tackling this one!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
CommOps Weekly Meeting Recap 2016-06-14
by Justin W. Flory
Meeting ended Tue Jun 14 17:35:52 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-06-14)
============================================
Meeting started by jflory7 at 15:58:53 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:59:10)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-14
(jflory7, 15:59:15)
* (1) Roll Call / Q&A (jflory7, 15:59:19)
* (2) Announcements (jflory7, 15:59:32)
* (3) Action items from last meeting (jflory7, 15:59:38)
* (4) Tickets (jflory7, 15:59:43)
* (5) Wiki Gardening (jflory7, 15:59:48)
* (6) Community Blog (jflory7, 15:59:53)
* (7) Release Schedule (jflory7, 15:59:59)
* (8) Open Floor (jflory7, 16:00:04)
* Roll Call / Q&A (jflory7, 16:00:17)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 16:00:22)
* decause; UTC-4; CommOps, GSoC, Budget, Council, * (decause,
16:00:37)
* Tummala Dhanvi (c0mrad3); UTC+5:30; CommOps, Security, Docs, GSoC, *
(c0mrad3, 16:01:32)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Infrastructure-fi, Join, Diversity, etc. (jflory7, 16:01:33)
* Corey Sheldon (linuxmodder) utc -4 / GPG D2264944 / Ambassadors,
join,security,docs,commops,diversity,mktg,GSoC (linuxmodder,
16:01:42)
* Sachin S. Kamath; UTC +5.30; CommOps, GSoC, Metrics, Badges etc
(skamath, 16:02:09)
* Sayan Chowdhury;UTC+5:30; Infrastructure, Cloud, CommOps, Marketing,
Ambassadors etc. (sayan, 16:05:02)
* Huiren Woo; UTC+0800; Ambassador, CommonOps, Marketing (GIANT_CRAB,
16:06:16)
* Announcements (jflory7, 16:07:27)
* === Last week: Fedora 24 no-go, delayed to June 21 === (jflory7,
16:07:33)
* LINK:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
(jflory7, 16:07:39)
* Due to a remaining blocker bug in F24, the release has been delayed
by one week to June 21st, 2016. If all goes well, we should be back
again here next week with a new Fedora release on our hands.
(jflory7, 16:07:44)
* === Events coming soon: Red Hat Summit, Flock === (jflory7,
16:07:49)
* LINK: https://www.redhat.com/en/summit (jflory7, 16:07:53)
* LINK: https://flocktofedora.org/ (jflory7, 16:07:58)
* Two upcoming events on the Fedora calendar are Red Hat Summit (June
27-29) and Flock, Fedora's annual contributor conference (August
2-5). (jflory7, 16:08:03)
* === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
(jflory7, 16:08:09)
* LINK: https://youtu.be/AQWybn1QVKc (jflory7, 16:08:15)
* Yesterday at the Fedora Council meeting, decause gave a report on
the status, work, and accomplishments of the CommOps sub-project.
Thanks to everyone who helped pull together information and the
presentation yesterday! decause++ bee2502++ skamath++ meskarune++
commops++ It's worth a watch if you haven't checked it out already.
(jflory7, 16:08:22)
* Action items from last meeting (jflory7, 16:10:45)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-...
(jflory7, 16:10:51)
* How This Works: We look at past #action items from the last meeting
for quick follow-up. If a task is completed, we move on to the next
one. If it isn't, we get an update and re-action it if needed. If no
status, we'll try to get a quick update and move forward. (jflory7,
16:10:56)
* === decause Follow up with tatica and diversity team about
LimeSurvey availability === (jflory7, 16:11:02)
* === [COMPLETE] skamath File a ticket in the Fedora Badges Trac for a
CommOps on-boarding badge that is dependent on other badges and/or
hooks to be awarded; ask in #fedora-commops if assistance is needed
=== (jflory7, 16:14:00)
* LINK: https://fedorahosted.org/fedora-badges/ticket/464 (jflory7,
16:14:09)
* === [COMPLETE] jflory7 Write a first draft of objectives / goals for
the vFAD on wiki page, share with commops, get feedback, look at
finding open dates (cc: decause) === (jflory7, 16:14:11)
* LINK: https://fedorahosted.org/fedora-commops/ticket/10#comment:5
(jflory7, 16:14:16)
* LINK:
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject...
(jflory7, 16:14:21)
* === [COMPLETE] jflory7 Post to the CommOps mailing list about Ticket
#71 about creating the Ambassador guidelines for artwork assets
based on mizmo's feedback === (jflory7, 16:14:31)
* LINK:
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject...
(jflory7, 16:15:25)
* === decause Follow up with tatica and diversity team about
LimeSurvey availability === (jflory7, 16:15:38)
* ACTION: decause review the vFAD goals/objectives/etc (decause,
16:15:47)
* In-progress; working on getting data back for the survey questions,
will work on transferring credentials soon (jflory7, 16:16:07)
* === decause Work with jzb to organize the release party in Raleigh,
NC area === (jflory7, 16:16:13)
* ACTION: decause Work with jzb to organize the release party in
Raleigh, NC area (jflory7, 16:16:55)
* === decause nail down Flock arrangements, add them to Fedocal ===
(jflory7, 16:17:01)
* ACTION: decause nail down Flock arrangements and add to fedocal
(decause, 16:17:18)
* === decause / spot look into booking conference rooms in the Tower
(Fedora on 9 if it is available) === (jflory7, 16:17:30)
* ACTION: decause / spot look into booking conference rooms in the
Tower (Fedora on 9 if it is available) (jflory7, 16:18:07)
* === decause ship "final" version for review by EoB thursday of F24
GA Release Announcement === (jflory7, 16:18:15)
* ACTION: decause Finish "final" version of F24 GA Release
Announcement for review after go/no-go meeting on Thursday
(jflory7, 16:21:21)
* === [COMPLETE] jflory7 Create a Fedocal event for the hack session,
2016-06-08 22:00 UTC === (jflory7, 16:21:27)
* LINK: https://apps.fedoraproject.org/calendar/meeting/4145/
(jflory7, 16:21:30)
* Tickets (jflory7, 16:22:06)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7,
16:22:12)
* === Ticket #10 === (jflory7, 16:22:17)
* "CommOps vFAD 2016" (jflory7, 16:22:22)
* LINK: https://fedorahosted.org/fedora-commops/ticket/10 (jflory7,
16:22:27)
* LINK: https://fedoraproject.org/wiki/FAD_CommOps_2016 (jflory7,
16:22:31)
* BAD TIMES: June 26-30 (Red Hat Summit), July 15-17 (Fedora Women Day
/ weekend), end of July (Design FAD / Flock right around corner)
(jflory7, 16:24:56)
* LINK: https://fedoraproject.org/wiki/FAD_KualaLumpur_2016
(GIANT_CRAB, 16:28:46)
* IDEA: Proposed Dates: June 25-26 (little soon) (jflory7, 16:29:45)
* IDEA: Proposed Dates: July 2-3 (jflory7, 16:29:54)
* IDEA: Proposed Dates: July 30-31 (jflory7, 16:30:12)
* AGREED: with July 2-3 (GIANT_CRAB, 16:30:30)
* ACTION: jflory7 Create a WhenIsGood and share with CommOps mailing
list to decide on vFAD dates of July 2-3 or June 25-26 (jflory7,
16:33:44)
* AGREED: We decided on two "best case" dates for vFAD, will throw out
to list with a WhenIsGood to get more input (jflory7, 16:34:45)
* === Tickets #34, 49, 69 === (jflory7, 16:34:52)
* #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 16:34:58)
* #49: "[Onboarding Series] CommOps!" (jflory7, 16:35:03)
* #69: "Fedora Modularity onboarding" (jflory7, 16:35:08)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:35:13)
* LINK: https://fedorahosted.org/fedora-commops/ticket/57 (jflory7,
16:35:17)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69 (jflory7,
16:35:21)
* CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs
Team Badges Tracks and Widgets (jflory7, 16:35:28)
* LINK: https://fedorahosted.org/fedora-badges/ticket/464 (jflory7,
16:37:08)
* LINK: https://fedoraproject.org/wiki/CommOps/Join (jflory7,
16:41:13)
* ACTION: jflory7 Write YAML file for CommOps on-boarding badge based
on FAS group sponsorship (jflory7, 16:45:34)
* IDEA: instuite a monthly mailing like infra has for weeding out
inactive members (linuxmodder, 16:46:27)
* ACTION: jflory7 Open a ticket to look into drafting an (automated?)
check-in email with members of CommOps to determine activity
(jflory7, 16:49:36)
* === Ticket #71 === (jflory7, 16:50:28)
* "Centralizing Ambassadors / Events resources and utilities"
(jflory7, 16:50:33)
* LINK: https://fedorahosted.org/fedora-commops/ticket/71 (jflory7,
16:50:38)
* LINK: https://pagure.io/designassets/tree/master (jflory7,
16:50:47)
* LINK: https://wiki.archlinux.org/index.php/ArchWiki:News
(meskarune, 16:58:23)
* IDEA: Create a "News" dashboard / widget in Fedora Hubs for
at-a-glance news about what's good in the Fedora Project (jflory7,
17:01:43)
* IDEA: Taking advantage of categories on the Community Blog to
aggregate news about each sub-project (jflory7, 17:02:10)
* ACTION: commops File a ticket on the Pagure repository for Fedora
Hubs about creating a News widget that aggregates different sources
of information and puts it together for easy consumption by a reader
(jflory7, 17:04:10)
* LINK: https://pagure.io/fedora-hubs/issues (jflory7, 17:04:32)
* ACTION: jflory7 Update Ticket #71 with the "WHY" perspective in
relation to FOSCo (jflory7, 17:07:53)
* LINK:
https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue469?action=show&redir...
(meskarune, 17:11:16)
* Wiki Gardening (jflory7, 17:13:34)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7, 17:13:38)
* LINK:
https://fedoraproject.org/wiki/Red_Hat_Summit_2016#Fedora_Booth_Staffing
(decause, 17:13:49)
* ACTION: decause Drop a line to the devel list to have anyone going
to Red Hat Summit add their info to the wiki page (jflory7,
17:18:12)
* Community Blog (jflory7, 17:18:45)
* How This Works: There is a quick blast of information about what was
published in the past week with some metrics, followed by posts that
are being drafted. After the information blast, the floor is opened
for any Community Blog-related discussion. Here we go! (jflory7,
17:18:54)
* === This Week in CommBlog === (jflory7, 17:19:00)
* (1) "Getting started with Fedora QA (Part 1)" (jflory7, 17:19:06)
* LINK:
https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
(jflory7, 17:19:12)
* Total Views (June 9 - June 14): 510 (jflory7, 17:19:17)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&vie...
(jflory7, 17:19:34)
* === Coming Up in CommBlog === (jflory7, 17:19:40)
* (1) "Cloud Working Group FAD" (jflory7, 17:19:46)
* LINK: https://public.etherpad-mozilla.org/p/fad-summary-2016-june
(jflory7, 17:19:50)
* Written by jzb, looking at publishing this week. (jflory7,
17:19:56)
* (2) "Event Report: PyCon 2016" (jflory7, 17:20:02)
* LINK:
https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=d3705befb7
(jflory7, 17:20:06)
* (3) "Getting started with 'update-testing' Fedora QA part 2"
(jflory7, 17:20:10)
* LINK:
https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8a0d20416e
(jflory7, 17:20:14)
* (4) "Getting started with Fedora QA part 3" (jflory7, 17:20:20)
* LINK:
https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=676163dcfd
(jflory7, 17:20:24)
* Release Schedule (jflory7, 17:21:45)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(jflory7, 17:21:49)
* Final Release Public Availability (GA) Tue 2016-06-21
(jflory7, 17:22:06)
* Fedora 22 EOL auto closure Tue 2016-07-19 (jflory7, 17:22:15)
* Open Floor (jflory7, 17:23:54)
* ACTION: jflory7 Look into filing a ticket on Pagure for CCing users
/ lists from a Pagure issue (jflory7, 17:27:13)
* LINK: https://pagure.io/pagure/issue/746 (nirik, 17:27:14)
* Parting Thoughts (decause, 17:31:15)
Meeting ended at 17:35:52 UTC.
Action Items
------------
* decause review the vFAD goals/objectives/etc
* decause Work with jzb to organize the release party in Raleigh, NC
area
* decause nail down Flock arrangements and add to fedocal
* decause / spot look into booking conference rooms in the Tower (Fedora
on 9 if it is available)
* decause Finish "final" version of F24 GA Release Announcement for
review after go/no-go meeting on Thursday
* jflory7 Create a WhenIsGood and share with CommOps mailing list to
decide on vFAD dates of July 2-3 or June 25-26
* jflory7 Write YAML file for CommOps on-boarding badge based on FAS
group sponsorship
* jflory7 Open a ticket to look into drafting an (automated?) check-in
email with members of CommOps to determine activity
* commops File a ticket on the Pagure repository for Fedora Hubs about
creating a News widget that aggregates different sources of
information and puts it together for easy consumption by a reader
* jflory7 Update Ticket #71 with the "WHY" perspective in relation to
FOSCo
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* decause Drop a line to the devel list to have anyone going to Red Hat
Summit add their info to the wiki page
* jflory7 Look into filing a ticket on Pagure for CCing users / lists
from a Pagure issue
Action Items, by person
-----------------------
* commops
* commops File a ticket on the Pagure repository for Fedora Hubs about
creating a News widget that aggregates different sources of
information and puts it together for easy consumption by a reader
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* decause
* decause review the vFAD goals/objectives/etc
* decause Work with jzb to organize the release party in Raleigh, NC
area
* decause nail down Flock arrangements and add to fedocal
* decause / spot look into booking conference rooms in the Tower
(Fedora on 9 if it is available)
* decause Finish "final" version of F24 GA Release Announcement for
review after go/no-go meeting on Thursday
* decause Drop a line to the devel list to have anyone going to Red
Hat Summit add their info to the wiki page
* jflory7
* jflory7 Create a WhenIsGood and share with CommOps mailing list to
decide on vFAD dates of July 2-3 or June 25-26
* jflory7 Write YAML file for CommOps on-boarding badge based on FAS
group sponsorship
* jflory7 Open a ticket to look into drafting an (automated?) check-in
email with members of CommOps to determine activity
* jflory7 Update Ticket #71 with the "WHY" perspective in relation to
FOSCo
* jflory7 Look into filing a ticket on Pagure for CCing users / lists
from a Pagure issue
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (293)
* decause (122)
* skamath (36)
* meskarune (33)
* linuxmodder (32)
* GIANT_CRAB (25)
* c0mrad3 (18)
* zodbot (17)
* nirik (14)
* sayan (10)
* danofsatx (2)
* adamw (1)
* nb (1)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
Re: [fedora-badges] #464: CommOps Onboarding Series Badge
by fedora-badges
#464: CommOps Onboarding Series Badge
-------------------------------------+-------------------------------------
Reporter: skamath | Owner:
Type: New badge | skamath
idea | Status:
Priority: minor | new
Keywords: commops | Resolution:
Has a description: 1 | Has a name:
Artwork status: Concept | 1
External requirements: | Concept approved (reviewers only):
Triaged (triagers only): 1 | 0
| Badge definition status:
| None
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Changes (by jflory7):
* cc: decause, commops@…, riecatnor, mleonova, duffy (added)
* has_name: 0 => 1
* triaged: 0 => 1
* has_artwork: None => Concept
* keywords: => commops
* has_description: 0 => 1
Comment:
Thanks for filing this ticket, skamath. :) I'm going to triage up this
ticket. If anyone has different ideas for any of the info I add / suggest
below, please add your thoughts.
= Badge metadata =
* '''Name''':
* Tying the Knot, ''OR''
* Dialed In
* '''Description''':
* "Congratulations, you are now a sponsored member of the Fedora
Community Operations (CommOps) team, helping tie the project together.
= Badge automation ideas =
We've been trying to discuss how to best automate the awarding of a badge
like this. Maybe it would be better to award it for sponsorship into the
FAS group for CommOps (which is a manual process to begin with and would
require someone to review the on-boarding steps we have above).
Alternatively, we could try to automate this badge being awarded based on
meeting criteria by what badges someone already has. For the examples
above, we could run a check for the following badges:
* Speak Up! (attend IRC meting)
* Let Me Introduce Myself (edit your user page on the wiki)
* Junior Editor (edit 10 wiki pages)
* White Rabbit (indicate time zone...?)
Some of the requirements above are not yet badges (but some are proposals,
like the mailing list activity). This is something worth discussing,
probably on a more technical side, and we will bring up this point in our
meeting today.
= Badge art concept =
I had a few ideas for the badge depending on which name idea has the most
flexibility for the Design Team… we are totally open to ideas and other
suggestions too based on what you all think is best or most doable. :)
The following two ideas are just suggestions!
=== Tying the Knot ===
You could have a "superhero" panda or badger who has a coiled rope around
his shoulder, a belt with a phone-like object on it (or maybe a radio on
its back?), and a headset on their head to keep the panda "looped in" on
all the different things happening in Fedora.
=== Dialed In ===
This one is more a hint towards communication and staying alert to things
happening around the panda / badger. In this one, you could have the
headset on their head / radio on their back again, but maybe one of the
computer assets (or a couple of them) with the panda / badger checking
back between the info scrolling by on both.
= Triaged! Bringing in Design Team members =
This should be all of the needed information on the ticket to start some
discussion. I'm CC'ing some members of the Design Team to get their
thoughts and opinions on the proposed concepts.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/464#comment:1>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 10 months
Understanding how the Design Team workflow
by Justin W. Flory
Hello Design team,
In this week's CommOps meeting, we were reviewing a ticket discussing
how to help make it easier for Ambassadors to find and discover
marketing and design resources that have been created for long-term use.
It was noted by an Ambassador that it can be difficult to find certain
resources and know where to look to find things that are useful for
events and other advocacy-related efforts.
You can read more about the current discussion in this ticket.
https://fedorahosted.org/fedora-commops/ticket/71#comment:5
We were hoping to get some background to understand how exactly the
Design Team workflow is like and how we could try to solve this problem
without causing disruption to how things are done and work already in
the team.
If anyone has a moment to review the ticket and add a comment, or reply
back to this email with thoughts / an explanation, it would be greatly
appreciated as we help figure out a solution for this issue! Thanks all.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
Re: [Fedocal] Reminder meeting : CommOps Hack Session
by Justin W. Flory
Hey Viorel, I'm trying to troubleshoot some connectivity issues. I should be around shortly but I'm not sure if I'll be able to do a Jitsi hangout. :(
Cheers,
————————————
Justin W. Flory
jflory7(a)gmail.com
Sent from my phoneOn Jun 8, 2016 18:24, Viorel Tabara <viorel(a)fedoraproject.org> wrote:
>
> On Wed Jun 08 2016 00:00:03 GMT-0600 (MDT) jflory7(a)fedoraproject.org wrote:
> > Dear all,
> >
> > You are kindly invited to the meeting:
> > CommOps Hack Session on 2016-06-08 from 18:00:00 to 21:00:00 US/Eastern
> > At fedora-meeting-3(a)irc.freenode.net
>
> no one around?
>
> --
> Viorel
> _______________________________________________
> Fedora Community Operations (CommOps) mailing list
> commops(a)lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org
7 years, 10 months
Re: [Magazine] "Getting started with Fedora QA" series
by Justin W. Flory
On 06/04/2016 05:02 AM, Sumantro Mukherjee wrote:
> Hey Justin!
>
> I have created my account. Its good to hear that it will be published in the coming week.
>
> Thanks
> Sumantro
>
Hey Sumantro!
As an update, the first article in this series will publish on the
Community Blog tomorrow, June 9, at 8:00 UTC. Watch for it to pop up
there early tomorrow!
https://communityblog.fedoraproject.org/?p=1608&preview=1&_ppp=7dcf2ea97b
I've also drafted a small "pointer" on the Magazine that could go out
either Friday or possibly next week (since we already published
something on QA this morning).
https://fedoramagazine.org/?p=13265&preview=1&_ppp=10848cd6de
Thanks!
> ----- Original Message -----
>> From: "Justin W. Flory" <jflory7(a)gmail.com>
>> To: "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
>> Cc: "Sumantro Mukherjee" <sumukher(a)redhat.com>
>> Sent: Saturday, June 4, 2016 1:19:13 AM
>> Subject: [Magazine] "Getting started with Fedora QA" series
>>
>> Hey Sumantro,
>>
>> In last night's Magazine meeting, we reviewed all of the pitches for the
>> Fedora QA series you've been working on. After discussing it for a bit,
>> we thought this would actually be a better fit for the Fedora Community
>> Blog, where all contributor-specific news, guides, and information is
>> published.
>>
>> https://communityblog.fedoraproject.org/
>>
>> The Community Blog is managed by the CommOps team.
>>
>> https://fedoraproject.org/wiki/CommOps
>>
>>
>> https://lists.fedoraproject.org/admin/lists/commops%40lists.fedoraproject...
>>
>> I went ahead and ported your articles from the Magazine to the Community
>> Blog. They are both WordPress sites, so using the Community Blog will be
>> the exact same. You also will just have to log in with your FAS to
>> create an account there.
>>
>> Let me know once you have created an account and I will assign
>> authorship rights back to you (at the moment, they list me as the
>> author). Your first article in the series should be published this
>> coming week. :)
>>
>> Thanks for contributing this series again!
>>
>> --
>> Cheers,
>> Justin W. Flory
>> jflory7(a)gmail.com
>>
>>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
Communicating art asset requests from Design to Ambassadors
by Justin W. Flory
Hey CommOpsers,
This discussion is related to Ticket #71 in our Trac, detailing how to
best centralize the resources produced by the Design Team for other
groups like the Ambassadors. There was a previous thread on this
cross-posted to both CommOps and the Design team mailing lists, but I
wanted to start a new one only on CommOps to reduce noise a little bit
on their list.
I added a new comment detailing the new approach I believe we should
consider taking on this ticket and how we might accomplish this task.
https://fedorahosted.org/fedora-commops/ticket/71#comment:8
Like with the vFAD ticket, it would be great if others could please
leave +1/0/-1 votes on this ticket so as to gauge what you all think
about this topic too (since a notable number of you are also Ambassadors
too). I'd like to begin working on a draft for this proposal in possibly
another two days or so, and then begin opening it up to feedback from
the Design Team next week.
Thanks all!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 10 months
