From Fedora Project Wiki
(Redirect Package Maintainer wiki links to docs.fp.o)
 
(277 intermediate revisions by 21 users not shown)
Line 1: Line 1:
== Introduction ==
{{admon/caution|This project is no longer active|This project is no longer active. We're now working on [http://fedoramagazine.org Fedora Magazine] instead.}}


This is a project whose aims, broadly stated, are to help information dissemination about the Fedora community to the Fedora community. '''Better descript needed. JonRob, please help!'''
[https://insight.fedoraproject.org Fedora Insight] is a [http://drupal.org Drupal-based] website that serves as a place to publish and share news, articles related to Fedora and [[Marketing|Fedora marketing materials]] in various formats. Insight makes it easy for users, developers, and journalists -- people who aren't yet a part of the Fedora contributor community -- to keep up with recent highlights without following a dozen different blogs and mailing lists.


=== Current stage ===
This wiki page is for people interested in working on and contributing to [https://insight.fedoraproject.org Fedora Insight] itself.


Our current next step is to pick a platform. To achieve this, we need to:
{{admon/tip | 1=Need to file a request or bug? | 2=Visit the Infrastructure issue tracker to [https://fedorahosted.org/fedora-infrastructure/newtplticket?component=FedoraInsight&version=Test&cc=logistics@lists.fedoraproject.org file a new issue]. You'll need to log in with your Fedora account to file the issue.}}
* Determine requirements (owned by ianweller)
* Seek out other interested parties and have them determine requirements (owned by JonRob)


[[User:Mchua|Mel Chua]] 21:47, 10 July 2009 (UTC)
== Project details ==
{|width=100%
! width=20% | IRC Channel
| {{fpchat|#fedora-mktg}}
|-
! Mailing List
| {{fplist|logistics}}
|-
! Meetings
| Weekly at {{fpchat|#fedora-meeting}}, Tuesday at 4:00pm US Eastern time
|-
! Current issues
|
* [https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&component=FedoraInsight fedora-infrastructure Trac] - site development or production issues
* [https://bugzilla.redhat.com/showdependencytree.cgi?id=662103&hide_resolved=1 "InsightReviews" Bugzilla bug] - package review issues
|-
! Project planning
| [[Insight project plan]] --- [[Insight notes from FUDCon Blacksburg 2012-01-15]]
|-
! Development server
| https://insight02.dev.fedoraproject.org <br/>Uses [https://admin.fedoraproject.org/accounts FAS] for authentication. Access via SSH only for trusted sysadmin team members.
|-
! Staging server
| https://insight.stg.fedoraproject.org
|-
! Production server
| https://insight.fedoraproject.org <br/>
|-
! Related pages
|
* [[Insight customizations to Drupal]] -- Changes to core, additional modules and settings
* [[Insight content configuration]] -- Additional customization work such as filters
|-
! TRAC Tickets
| https://fedorahosted.org/fedora-infrastructure/query?status=assigned&status=new&status=reopened&component=FedoraInsight&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
|}


If you make a FooBar-related page, please add <nowiki>[[Category:Project FooBar]]</nowiki> to the bottom for now, so we can properly tag things. This category will be renamed after we pick a better name for FooBar.
{{Anchor|Agenda}}


===Background===
== Meeting agenda ==


For the F11 release cycle, Marketing switched from a task-based model to a schedule based model. This went well, allowing us to keep better in sync with what was going on and what types of information were needed to be created/put out at any given point in the cycle. However, there are still many kinks and areas for improvement as were defined in document: [[Marketing/F11_cycle_retrospect|F11 Cycle Retrospect]]. Bottom line, complacency is not a formula for success and we must always be looking towards the future and improving it.
* Review previous action items -- [http://meetbot.fedoraproject.org/fedora-meeting/2012-01-03/insight.2012-01-03-21.00.html Previous meeting]
* authfas update
* Office hours
* Hackfest info?


Looking forward, we have always floated the idea of having a Fedora Magazine and the going logic is that we may be able to model Fedora Marketing around such conventions which would not be dissimilar to a magazine.  The focus would be not only on producing the content that is required for each release cycle but also on producing relevant and interesting content, in many forms, audio, video and text-based for the consumption of both the general Fedora community and the Open Source community at large.
== How to help ==


===Present===
{{admon/important|Personal Information|Fedora is a very visible and transparent project. Its mailing lists are archived and mirrored in many places on the internet outside of our control. Please use caution when sharing personal information with Fedora on a mailing list, because it is not possible for us to remove any postings from the wider Internet universe after they are sent. For more details, please refer to [https://fedoraproject.org/wiki/Legal/PrivacyPolicy Fedora's Privacy Policy].}}


Currently, the state of project/community produced content is clearly scattered.  We have many groups, such as Marketing, Ambassadors, Docs, Design, etc. all creating great content for a variety of different purposes.  The amount of this content is effectively multiplied by how much we care to and/or use the services of the translation team to localize this content.  Once this is done, there are various and sundry methods of distributing this content.  We have Fedora Weekly News, Docs Beats, Fedora Planet, local ambassadors newsletters etc.  There is not one central process or policy for creating content and distribution channel/plan.  Also, much of our content is not clearly licensed.
=== Decide what you want to do ===


Much of this content is also centered milestones and it may be possible to fit it into recurring schedule-based publication which would help overall management and tracking.
{|
| '''I want to work on the theme and appearance of Insight.'''
| [[Design/Join | Join]] the [[Design]] team, and look at our page on [[How to work on the Insight theme]].
|-
| '''I want to help develop and maintain the Insight system.'''
| Introduce yourself to the team (see below), and look at our page on [[How to develop for Insight]].
|-
| '''I want to represent Fedora in the Drupal community.'''
| [[Ambassadors/Join | Join]] the [[Ambassadors]] team -- being a Fedora representative is more than just being a fan. We would love to have you on our team once you are versed in how the project works.
|}


===Future===
=== Become part of our team ===


There are many questions to ask. What do we want this to be?  Who should the audience be?  How well do we actually know our audience to make that assumption?  What types of content?  These questions are what we are trying to ask and answer now so we can get a solid picture of how we proceed further.  We need to clearly answer these questions to clarify our goals.  Goals are in the goals section below and they will and should be refined by the community as a whole.
# Join the {{fplist|logistics}} mailing list and introduce yourself. Let us know:
#* Your name
#* Your skills/experiences/interests -- Even if you're active within another Fedora team, there may be other Fedora folks who haven't had the chance to meet you yet, so let them know who you are and that you're around!
#* The first task or ticket you plan to work on (see "Current issues" above) -- if you want to work on something else, tell us what it is
# (optional) Check out any other [[#Communications]] channels that you might be interested in.


We might want to strive for something akin to a journal style format for community created/relevant content and including Fedora Marketing content might work best.  We should start by investigating sites with similar goals/audiences.  We look at sites like https://wiki.ubuntu.com/UbuntuWeeklyNewsletter, http://fullcirclemagazine.org/, http://planet.laptop.org/, http://www.olpcnews.com/, http://planet.sugarlabs.org/. 
=== Development ===


What we want might be a magazine, which is not really a magazine format, more journal-ish (technical, non-nephyte) but also not afraid to include some stuff for newbies, and mostly a platform where interesting content would show up for the community's consumption, which would act as a central hub.
If you know something about Drupal or are a fast learner, we welcome you! We are working on designing the next group of features for Insight.  Here are the use cases we've outlined thus far:


Also, the goal should be to create something which is well laid out visually and consistent with the design teams work and general philosophy.
* [[Insight use cases for calendar]]
* [[Insight use cases for status and microblogging]]
* [[Insight use cases for events]]


==Goals==
We're also starting to look forward to Drupal 7, and have started documenting critical path requirements for a future migration to Drupal 7 from Dupal 6:


===Centralized Content===
* [[Insight Drupal 7 Dependencies]]


There are too many avenues to information now, its innundating. Blogs/Planet, FWN, Ambassadors own work, etc.  Also, a majority of this content is text, whereas we would like to make more multimedia content.
=== Marketing ===


===Content Schedule===
The [[Marketing]] team will be publishing its [[Marketing#Release deliverables|release deliverables]] on Fedora Insight, and will be the second users of the platform after [[#FWN]].


Well established guidelines for what needs to be produced/is being worked and when it must be published by.
We're currently figuring out additional content (other than our release deliverables) that would go into the [[#Content_workflow]]. Our current thinking is several ideas that have been filed as [https://fedorahosted.org/marketing-team/query?status=new&status=assigned&status=reopened&component=Fedora+Insight&order=priority multiple tickets in the Marketing trac instance].  


This also helps in running a proper marketing campaign.
If you want to help with the Marketing side of things, do the following:
# Follow the instructions in the [[#How to help]] section of this page.
# [[Joining the Fedora marketing project|Join the Marketing team]], if you aren't already a member.
# Email the [https://admin.fedoraproject.org/mailman/listinfo/marketing marketing list] and let the Marketing team know you're interested in helping with Fedora Insight.


===Flexibility/Creativity of Presentation===
=== Packaging ===


Journal Format
We could always use packaging help for Drupal and related modules.  If you see an unassigned (''NEW'') bug in [https://bugzilla.redhat.com/showdependencytree.cgi?id=662103&hide_resolved=1 this tracking list], that means there is a package review needed so we can make more progress.  The [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/ Package Review Process] page will show you how to do a review.  It takes some time to do a good package review, but in the process you can learn some technical skills and about how this process ensures a good experience for Fedora users installing software.


Better able to target an audience
=== Content workflow ===


===Standardized Feeds===
This is a content workflow envisioned for Fedora Insight.


One OFFICIAL Feed for each media type--audio, video, text/print
<pre>
+-------------------------+    +-----+ +-------+ +-------------+ +-----------+
|Things that automatically|    |Press| |The Web| |Fedora Planet| |Original FI|
|get sent to the moderator|    +-----+ +-------+ +-------------+ |content    |
|queue for annotation    |        |      |          |        +-----------+
+-------------------------+        |      |          |              |
| * Board meeting minutes |        +-------+-----+-----+---------------+
| * FESCo meeting minutes |                            |
| * FAmSCo meeting minutes|                            |
| * etc.                  |                            |
+-------------------------+              +----------------------------+
            |                            | Discovered by interested  |
            |                    +----->| person, or submitted by    | 
            |                    |      | original author into...    | 
            |          resent to  |      +----------------------------+ 
            |          submitter  |                    |                           
            |          with rationale                  |                           
            |                    |          +------------------+                       
            +---------------------+--------->| Moderator  Queue |       
                                  |          +------------------+       
                                  |          | Selects content  |       
                                  <NO>--------| and annotates    |         
                                              | selected content |
+-------------------------+                  +------------------+
|Things that automatically|                          |
|get published (no mod)  |----+                    <YES>     
+-------------------------+    |                      |           
| * Fedora Weekly News    |    |      +----------------------------+
| * Fedora-announce-list  |    +------>| Published in Fedora Insight|
| * etc.                  |            +----------------------------+
+-------------------------+                          |         
                                                      |
                                                  (READERS!)
</pre>


===Translation/Press Distribution/Social Media Distribution===
== History ==


Process for getting things in Translation Queue.
For a history of the project and some of the rationale behind it, see [[Fedora Insight history]].


Better plan with regard to something like NDN.  Red Hat Intl PR is part of this
== Workflow ==


Develop strategies for syndicating media on social networks/news sites
[[Fedora Insight Workflow]]


== Questions ==
[[Insight development using Features module]]


* Who is our audience? 
[[Category:Fedora Insight]]
* What are they interested in?
* How can we better engage their interest?
 
== Platform selection criteria ==
 
''to be filled in by ianweller''
 
== Platform specs/requirements ==
 
=== Marketing Requirements ===
 
* Allow multiple editors
* Allow multiple contributors
* Separate feeds for different media - podcast, written, video etc
* Easy integration of rich media - see above
* Tags/Categories
 
=== News Requirements ===
 
=== General Requirements ===
 
* FAS_Auth integration
* Themable (presumably by Design Team)
* Software *and* required plugins packaged - including theme?
** software + plugins packaged, theme isn't necessarily a strict requires but it's kind of nice --[[User:Ianweller|Ian Weller]] 16:13, 8 July 2009 (UTC)
** Why is it not a strict requires? (JonRob - who doesn't know how to do ianweller's funky signiture)
 
'' This is a brainstorm list - what would you want a FooBar platform to have and do? Please add to the list below.''
 
== Platform options ==
 
''This is a brainstorm list; add your ideas and notes on various platforms below. Platforms are in alphabetical order.''
 
=== Drupal ===
 
* imo, way more features than we actually need. [[User:Mchua|Mel Chua]] 15:52, 8 July 2009 (UTC)
* bad security record, the sort of PHP app that infrastructure ''doesn't'' need --[[User:Ianweller|Ian Weller]] 15:54, 8 July 2009 (UTC)
* There's no way we would put up a Drupal instance ''in addition to'' Zikula.  If we can do this project with a CMS, we'll do it with Zikula, which has already been through the entire process of community requirement gathering, evaluation, and is well into testing and packaging phase. --[[User:Pfrields|stickster]] 17:47, 10 July 2009 (UTC)
 
=== Wordpress (wp) ===
 
* mizmo: i am hoping wp is chosen though because its a known quantity and [the Design team has] done themes for it before
* has it been integrated into infra's systems, and met their security/packaging requirements?
 
=== Wordpress, multiuser (wp-mu) ===
 
* ianweller: wp-mu i don't think is the right choice for foobar, it just complicates things and we don't need multiple blogs, unless of course we want to run the entire thing under the blogs.fp.o umbrella
** which, in general, we don't. --[[User:Ianweller|Ian Weller]] 16:11, 8 July 2009 (UTC)
** would it not be possible to take that as hosting though, and have it point to a different domain? it would give us all the power of a normal wp install, but have the happy side effect of already being deployed!
* A CMS isn't just for serving up somewhat static, undated content. It also can provide blogging capabilities as well; Zikula, Drupal, Joomla, et al., all do this just fine. --[[User:Pfrields|stickster]] 17:48, 10 July 2009 (UTC)
 
=== Zikula ===
 
* stickster: there's a great deal of crossover between what Foobar proposes, and what the new CMS (Zikula) can/will accomplish. Foobar sets out a lot of Marketing-specific goals, and I think most or all of them can be achieved through an implementation via the CMS.
* ke4qqq (Dave Nalley) summarizes Zikua: After a long period of input, eval, and testing by multiple groups (primarily Docs, but also Infrastructure and others), Zikula has been chosen as a CMS. It has a responsive upstream that's developing new modules for our needs and has even joined fp lists to help us collaborate on getting this up. It wil first be used for docs.fp.o, which currently has no CMS; FPC and F-Legal are also interested in using it - but we haven't mapped out that really well thus far - but it's after docs.fp.o makes the move. polecat (John Poelstra) has stepped up to coordinate teams for a production schedule and some meetings.
 
== Name brainstorming ==
 
''Because we can't call it FooBar forever.''
 
* furchtbar
* fruitbar
* crème brûlée
* furth3r or just further
 
== Upcoming things ==
 
* design (mizmo): waiting on platform selection
* getting a test version up: also waiting on platform selection
 
== Sketches ==
 
Here's a mockup by mizmo of what this might look like. (Click for full size.)
 
[[File:FooBar.png|300px]]
 
[[Category:Project FooBar]]

Latest revision as of 11:13, 9 October 2021

This project is no longer active
This project is no longer active. We're now working on Fedora Magazine instead.

Fedora Insight is a Drupal-based website that serves as a place to publish and share news, articles related to Fedora and Fedora marketing materials in various formats. Insight makes it easy for users, developers, and journalists -- people who aren't yet a part of the Fedora contributor community -- to keep up with recent highlights without following a dozen different blogs and mailing lists.

This wiki page is for people interested in working on and contributing to Fedora Insight itself.

Need to file a request or bug?
Visit the Infrastructure issue tracker to file a new issue. You'll need to log in with your Fedora account to file the issue.

Project details

IRC Channel #fedora-mktg[?]
Mailing List logistics
Meetings Weekly at #fedora-meeting[?], Tuesday at 4:00pm US Eastern time
Current issues
Project planning Insight project plan --- Insight notes from FUDCon Blacksburg 2012-01-15
Development server https://insight02.dev.fedoraproject.org
Uses FAS for authentication. Access via SSH only for trusted sysadmin team members.
Staging server https://insight.stg.fedoraproject.org
Production server https://insight.fedoraproject.org
Related pages
TRAC Tickets https://fedorahosted.org/fedora-infrastructure/query?status=assigned&status=new&status=reopened&component=FedoraInsight&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority

Meeting agenda

  • Review previous action items -- Previous meeting
  • authfas update
  • Office hours
  • Hackfest info?

How to help

Personal Information
Fedora is a very visible and transparent project. Its mailing lists are archived and mirrored in many places on the internet outside of our control. Please use caution when sharing personal information with Fedora on a mailing list, because it is not possible for us to remove any postings from the wider Internet universe after they are sent. For more details, please refer to Fedora's Privacy Policy.

Decide what you want to do

I want to work on the theme and appearance of Insight. Join the Design team, and look at our page on How to work on the Insight theme.
I want to help develop and maintain the Insight system. Introduce yourself to the team (see below), and look at our page on How to develop for Insight.
I want to represent Fedora in the Drupal community. Join the Ambassadors team -- being a Fedora representative is more than just being a fan. We would love to have you on our team once you are versed in how the project works.

Become part of our team

  1. Join the logistics mailing list and introduce yourself. Let us know:
    • Your name
    • Your skills/experiences/interests -- Even if you're active within another Fedora team, there may be other Fedora folks who haven't had the chance to meet you yet, so let them know who you are and that you're around!
    • The first task or ticket you plan to work on (see "Current issues" above) -- if you want to work on something else, tell us what it is
  2. (optional) Check out any other #Communications channels that you might be interested in.

Development

If you know something about Drupal or are a fast learner, we welcome you! We are working on designing the next group of features for Insight. Here are the use cases we've outlined thus far:

We're also starting to look forward to Drupal 7, and have started documenting critical path requirements for a future migration to Drupal 7 from Dupal 6:

Marketing

The Marketing team will be publishing its release deliverables on Fedora Insight, and will be the second users of the platform after #FWN.

We're currently figuring out additional content (other than our release deliverables) that would go into the #Content_workflow. Our current thinking is several ideas that have been filed as multiple tickets in the Marketing trac instance.

If you want to help with the Marketing side of things, do the following:

  1. Follow the instructions in the #How to help section of this page.
  2. Join the Marketing team, if you aren't already a member.
  3. Email the marketing list and let the Marketing team know you're interested in helping with Fedora Insight.

Packaging

We could always use packaging help for Drupal and related modules. If you see an unassigned (NEW) bug in this tracking list, that means there is a package review needed so we can make more progress. The Package Review Process page will show you how to do a review. It takes some time to do a good package review, but in the process you can learn some technical skills and about how this process ensures a good experience for Fedora users installing software.

Content workflow

This is a content workflow envisioned for Fedora Insight. 

 +-------------------------+    +-----+ +-------+ +-------------+ +-----------+
 |Things that automatically|    |Press| |The Web| |Fedora Planet| |Original FI|
 |get sent to the moderator|    +-----+ +-------+ +-------------+ |content    |
 |queue for annotation     |        |       |           |         +-----------+
 +-------------------------+        |       |           |               |
 | * Board meeting minutes |        +-------+-----+-----+---------------+
 | * FESCo meeting minutes |                            |
 | * FAmSCo meeting minutes|                            |
 | * etc.                  |                            |
 +-------------------------+              +----------------------------+
             |                            | Discovered by interested   |
             |                     +----->| person, or submitted by    |   
             |                     |      | original author into...    |   
             |          resent to  |      +----------------------------+   
             |          submitter  |                    |                            
             |          with rationale                  |                             
             |                     |          +------------------+                        
             +---------------------+--------->| Moderator  Queue |         
                                   |          +------------------+         
                                   |          | Selects content  |         
                                  <NO>--------| and annotates    |          
                                              | selected content |
 +-------------------------+                  +------------------+
 |Things that automatically|                           |
 |get published (no mod)   |----+                    <YES>      
 +-------------------------+    |                      |             
 | * Fedora Weekly News    |    |       +----------------------------+
 | * Fedora-announce-list  |    +------>| Published in Fedora Insight|
 | * etc.                  |            +----------------------------+
 +-------------------------+                           |           
                                                       |
                                                   (READERS!)

History

For a history of the project and some of the rationale behind it, see Fedora Insight history.

Workflow

Fedora Insight Workflow

Insight development using Features module

Retrieved from "https://fedoraproject.org/w/index.php?title=Fedora_Insight&oldid=627128"