Fedora Handbook - Call for Native Speakers
by Jiri Eischmann
Hi,
at last year's Flock I announced Fedora Handbook (a "getting started
with Fedora" guide that is printed and can be give away at event etc.).
Because it was created in the Czech community, the original is in
Czech. The handbook was very successful at Czech events, so we
translated it to English, so that it could be used abroad and
translated to other languages.
We have initial English translation, but it's rough and it needs a lot
of proofreading and rewriting which is something that needs to be done
by a native speaker.
It's written in AsciiDoc, easily readable and editable format: https://
github.com/lukaskotek/fedora-handbook-doc
Any volunteer to help? It'd be great to have it finished and printed
for Flock 2016. All I need is final text, we'll take care of
typesetting and printing.
Jiri
6 years, 6 months
Marketing-trac: #229: Shared, secure password distribution
by Marketing Team
#229: Shared, secure password distribution
---------------------------------+-------------------------
Reporter: jflory7 | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 24
Component: Internal operations | Severity: not urgent
Keywords: meeting | Blocked By:
Blocking: |
---------------------------------+-------------------------
= Problem =
In
[https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproje...
previous discussions], we had talked about secure password management and
distribution to safely and securely distribute confidential information
such as passwords for social media accounts or other Fedora-related,
shared accounts.
We need a system that can handle having multiple "caretakers" that manage
all the passwords, user accounts that can individually access certain
accounts / passwords, have some kind of convenient way to regenerate
passwords if a user is removed or has their privileges changed.
= Analysis =
When we discussed this originally, we decided to approach the
Infrastructure team to get their feedback / ideas on such an idea about
how to manage this. We also wanted to answer questions such as…
* How many people will need access to the passwords?
* How much data would be stored (e.g. how many passwords, for what
services, is it small-scale or large-scale, etc.)?
* How often will access to a password be granted?
* How often will access to a password be revoked?
= Enhancement Recommendation =
=== pass ===
The Infrastructure team originally proposed for us to consider using
[https://www.passwordstore.org/ pass], a Unix command line password
management utility. Pass uses GPG keys to encrypt passwords and can
synchronize them via git.
'''Advantages'''
* Lightweight, easy to maintain (theoretically)
* Uses tried and trusted tech to secure passwords (GPG)
* Little overhead to maintain a secure repository within Fedora's
Infrastructure
'''Disadvantages'''
* No per-user customization (anyone whose GPG key id is added to the
repository has access to all passwords)
* Requires anyone with access to have understanding and reliability to use
GPG as expected
* A compromised key could cause issues if someone who needs access is not
extremely familiar with using GPG.
* Changing passwords in the event of a dropped GPG key means changing ALL
passwords in the entire repository for everyone (no modularity in terms of
a user who should have access to a subset / specific password)
=== Rattic ===
I've never used Rattic or do I know much about it, but it seems like a
more complete solution than pass. I'm going to CC Brian Proffitt to this
ticket in case he can add more context to this discussion.
Eventually, after discussing in a meeting, we'd like to take a vote on
this and bring a formal proposal to the Infrastructure team.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/229>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
6 years, 10 months
Marketing-trac: #230: Moving to Pagure
by Marketing Team
#230: Moving to Pagure
---------------------------------+-------------------------
Reporter: jflory7 | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 24
Component: Internal operations | Severity: not urgent
Keywords: meeting | Blocked By:
Blocking: |
---------------------------------+-------------------------
= Problem =
The Fedora Infrastructure team is planning on sunsetting Fedora Hosted
repositories in the coming future (tried finding where this announcement
or discussion originally happened, but had a hard time finding it).
Eventually, the idea is for all projects using Fedora Hosted to migrate to
Pagure. We will be expected / planned to be migrated in the foreseeable
future.
= Analysis =
There are some tools available to assist in migrating Trac to Pagure,
although it is under testing and not yet fully tested. We would need to
check with the Infrastructure team about the status of this tool.
= Enhancement Recommendation =
We have one of two options.
=== Start fresh ===
We could move to Pagure and begin using it today, at the expense of losing
past history / discussions on old tickets.
=== Try the migration tool ===
We could try using the migration tool being developed to move our project
over (since we are only tickets and not a git repository, I imagine this
will be easier to do?).
To be discussed at the next meeting.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/230>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
6 years, 10 months
Re: [commops] Re: FedoraMag Wordpress Blog API
by Arvind Chembarpu
----- Original Message -----
> From: "Justin W. Flory" <jflory7(a)gmail.com>
> To: "Fedora Marketing team" <marketing(a)lists.fedoraproject.org>
> Cc: "Sudhir D" <sdharane(a)redhat.com>, "Fedora + Community + Operations = Fedora CommOps"
> <commops(a)lists.fedoraproject.org>
> Sent: Wednesday, June 29, 2016 10:05:24 PM
> Subject: [commops] Re: FedoraMag Wordpress Blog API
>
> On 06/29/2016 04:06 AM, Arvind Chembarpu wrote:
> > Hey everyone,
> >
> > I'm Arvind, and I'm working as a Fedora QA Intern, with Sudhir D (Fedora QA
> > Manager) at Red Hat Bangalore.
> >
> > I was working on a hub to view all Fedora news in a seamless interface, and
> > I was hoping to use the default Wordpress API to accomplish this.
> > However, it looks like the API has been disabled manually, since all the
> > endpoints under `http://fedoramagazine.org/wp-json/v2/` and
> > `http://fedoramagazine.org/wp-json/` are returning 404 error statuses.
> > Would it be possible to re-enable these? If not, could you point me towards
> > another way to obtain FedoraMagazine post links?
> >
> > Cheers,
> > Arvind Chembarpu
> > [achembar(a)redhat.com]
> >
>
> Hi Arvind!
>
> For the Fedora Magazine, the best place to discuss it is on the
> Marketing mailing list, which I am including in this response. The
> Community Operations team handles the Community Blog (which is also a
> WordPress site).
Ah, OK. I'm replying only on the Marketing List now, then.
> I think discussion about the API came up before, but I don't remember
> what came of it or where it went. The best points of contact about this
> would probably be Patrick Uiterwijk (puiterwijk on freenode IRC) or Paul
> Frields (stickster on freenode IRC). I know Paul is at Summit this week,
> so you might not hear from him this week, but you can probably find
> Patrick on IRC, and he could tell you more about whether this is
> feasible or not.
Great, will contact both Patrick and Paul on IRC about this.
Since this reply is on the mailing list anyway, if anyone else has an idea about the WP API, please do let me know. :)
Since the `wp-json` API is a default Wordpress plugin, so anyone with access to the Fedora Magazine WP-admin should be able to re-enable it.
Essentially, I am hoping for a way to just fetch Fedora Magazine post links, banner images, and maybe article summaries. This is all provided by the `wp-json` API.
This isn't meant to drive any traffic away from the Blog, since clicking on any links will still lead to the actual webpage.
Rather I want to just to give users a sort of feed reader, from where they can access the Magazine and other resources, at once.
> Hope this helps!
Thanks, Justin! Appreciate the help. :D
Cheers,
Arvind Chembarpu
Fedora QA Intern
[achembar(a)redhat.com]
6 years, 11 months
Marketing-trac: #226: Screenshots for Fedora 24
by Marketing Team
#226: Screenshots for Fedora 24
----------------------------------+------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 24
Component: Release deliverables | Severity: urgent
Keywords: meeting | Blocked By:
Blocking: |
----------------------------------+------------------------
= Phenomenon =
'''Discussed in [https://meetbot.fedoraproject.org/fedora-
meeting-1/2016-05-18/marketing.2016-05-18-20.55.html 2016-05-18 meeting].
In the [https://fedorapeople.org/groups/schedule/f-24/f-24-marketing-
tasks.html upcoming marketing tasks] for Fedora 24, it lists taking
screenshots for the next release as an objective.
= Background Analysis =
This was completed for
[https://fedoraproject.org/wiki/Marketing/F23_Screenshots Fedora 23].
Important questions to ask:
* What screenshots are needed?
* Who needs the screenshots?
* Where will they be used?
= Implementation Recommendation =
If needed, we can have someone run the F24 Beta to take screenshots.
cprofitt volunteered to do this earlier if needed.
mailga, since you led this task for Fedora 23, could you explain the
process and what needs to be done for F24 (e.g. do we only need
screenshots of new things or all the DEs)?
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/226>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
6 years, 11 months
Marketing-trac: #222: Publicizing "Fedora affiliates" (or groups using Fedora)
by Marketing Team
#222: Publicizing "Fedora affiliates" (or groups using Fedora)
-----------------------------+-------------------------
Reporter: jflory7 | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 23
Component: Feature stories | Severity: not urgent
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+-------------------------
'''Discussed in
[https://meetbot.fedoraproject.org/teams/marketing/marketing.2016-02-24-22...
2016-02-24 meeting].'''
= What =
It was mentioned during the meeting that it would be helpful and useful
for Ambassadors to have a place to show people / groups examples of other
groups successfully running Fedora on their own infrastructure.
Ideas for this would be companies powering their infrastructure with
Fedora, schools or universities that have Fedora computer labs, and other
similar types of cases.
= How =
The difficult part in accomplishing this is identifying the list of
entities that are using Fedora in applications like this. Would a call for
action be needed, such as on the Magazine / Community Blog? Do we have a
past list like this somewhere?
Once these questions are answered and we have the list, we can ''then''
move on to how we want to publish and publicize the list.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/222>
Marketing Team <https://fedoraproject.org/wiki/Marketing>
The Trac site for the Fedora Project Marketing team. This Trac serves as a place to list out tasks, define objectives, and work on monitoring our progress with key tasks and goals.
6 years, 11 months
Deciding on a secure password distribution system
by Justin W. Flory
Hello all,
In today's meeting, we briefly reviewed the ticket regarding choosing a
secure password distribution system for marketing efforts. The two
options we currently have in the ticket are Pass and Rattic (although
the latter could use some more context / explaining).
If you all could please look over this ticket, add any thoughts /
comments to the proposal, and leave a vote, that would be appreciated.
Thanks.
https://fedorahosted.org/marketing-team/ticket/229
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
6 years, 11 months
EMEA Sponsorship Program for Flock
by Giannis Konstantinidis
Hello everyone,
in the past we have had a tradition of sponsoring EMEA contributors that would like to attend Flock[0] but are not going to receive funding as speakers.
The allocated budget for this year was only $800, initially. The adjusted budget is even less. As we wish to assist as many contributors in need as possible, we are going to try and raise that budget. However, no promises made at this point.
This program is intended for contributors that currently reside in EMEA. Other regions may feel free to come up with similar programs for their contributors as they see fit. Priority will be given to contributors that have recently maintained a record of activity and also have some kind of work agenda for the conference (e.g. meet with fellow contributors, actively contribute on site).
In any case, the budget we are going to end up with will be limited. Most likely we will be able to offer only -partial- subsidies. Do not apply if you are not okay with that. If you are able to receive funding from other sources (e.g. your employer), please do so.
To request for sponsorship, file a ticket on the EMEA Trac[1], state the reason(s) for applying and what you expect to accomplish by attending the conference. Deadline should be July 5, 23:59:59 UTC +0. All tickets will be later evaluated by FAmSCo, same as last time.
We will get back to you once we have more information regarding the budget. Please spread the news to your fellow Fedorians.
Thank you and good luck!
-Giannis
[0] https://flocktofedora.org/
[1] https://fedorahosted.org/emea-swag-tracking/
--
Giannis Konstantinidis
giannis(a)konstantinidis.cc
http://konstantinidis.cc
giannisk on irc.freenode.net
6 years, 11 months
