From Fedora Project Wiki

(We can get rid of the name brainstorming since the name's finalized. History still has this content.)
(Redirect Package Maintainer wiki links to docs.fp.o)
 
(250 intermediate revisions by 16 users not shown)
Line 1: Line 1:
'''The page has been moved and renamed, but the content still has the old name (FooBar). Can someone please take a pass and fix this? If not, I will when I am back in Boston. [[User:Mchua|Mel Chua]] 17:10, 28 July 2009 (UTC)'''
{{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.}}


== Introduction ==
[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.


Fedora Insight aims to provide a central location through which we can disseminate information about the Fedora community. By providing a central location, we hope to increase collaboration between teams who are currently producing relevant content, as well as reducing duplicated effort, and to make it easier for those who wish to keep up with the goings on of the community without following a dozen different blogs and mailing lists. With this in mind, the content created by Fedora Insight should appeal to users, developers and journalists, take a number of different forms --- including interviews, feature length articles, news reports etc --- and a number of different mediums --- including podcasts, written text and video.  
This wiki page is for people interested in working on and contributing to [https://insight.fedoraproject.org Fedora Insight] itself.


=== Current stage ===
{{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.}}


Our current next step is to pick a platform. To achieve this, we need to:  
== Project details ==
* Determine requirements (owned by ianweller)
{|width=100%
* Seek out other interested parties and have them determine requirements (owned by JonRob)
! 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
|}


[[User:Mchua|Mel Chua]] 21:47, 10 July 2009 (UTC)
{{Anchor|Agenda}}


If you make a Fedora Insight-related page, please add <nowiki>[[Category:Project Fedora Insight]]</nowiki> to the bottom for now, so we can properly tag things. This category will be renamed after we pick a better name for Fedora Insight.
== Meeting agenda ==


===Background===
* 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?


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.
== How to help ==


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.
{{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].}}


''below are the notes I took at the first Fedora Insight meeting I know of, which was in the red hat westford office at the start of june.'' [[User:Mchua|Mel Chua]] 12:37, 25 July 2009 (UTC)
=== Decide what you want to do ===


* ja = themayor
{|
* md = mizmo
| '''I want to work on the theme and appearance of Insight.'''
* ss = smooge
| [[Design/Join | Join]] the [[Design]] team, and look at our page on [[How to work on the Insight theme]].
* mc = mchua
|-
| '''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.
|}


<pre>
=== Become part of our team ===
ja: explains task-based to milestone-based switch to stephen. we want more marketing metrics - let's do a magazine.
md: why not spruce up fwn? what audience are we trying to reach:
ss: what I'd like to do is bring (non-fedora-dev) people in to show what we're doing... are we reaching people who are not fedora devs?
md: how often are we trying to do this? what do we want to accomplish?
ja: let's break it down. fwn is more short-term oriented; we want more media stuff, fwn is very text-heavy. we have multiple sources creating content, and none of it is coordinated.
md: what are those sources?
ja: fwn, the beat...
md: the beat = docs? that's not really magazine-style content.
ss: these are summaries?
md: yes.
ss: we're looking at doing a full blog... like a post blog, edited.
ja: let me clarify what I mean by a magazine. more of an aggregate/feed, something like linuxjournal's website, this would be the standardized feed for getting interesting featurettes.
md: so this isn't about getting more people to write more content; it's that people are writing content but it's all over the place, so let's get it in one bucket.
ss: we have planet.fp.o, but this would be not your personal blog.
ja: at the same time, I don't want to make planet defunct. another reason this is important is that we want a steady list of stuff we (mktg) need to make - so that every month we know we need to do X. Right now, the list of stuff we make is scattered. But we need a regular cycle for marketing deliverables too.
mc: making sure I understand - examples?
md: gnome journal - it's published monthly
mc: planet sugar labs, planet laptop, and olpcnews, also full circle - similar?
ja: yes, more on the news than the tutorials front, so more gnome journal/olpcnews than full circle
md: sounds like the primary goal is to have a central edited place for this content.
ss: how would this fit into community-the-platform?
md: we could probably fit a module into community, with zikula...
ss: would this be a way to help with community villages? would communty be a good steppingstone?
md: audience = already in the community, not afraid of technical stuff, but who might want a good central content source and a routine for finding information
ja: that's pretty much it. also, from the design end of things, we want to have it fit with whatever design is doing, so it looks consistent. also, when i was up here a month ago and you showed me the apple.com tour, let's get sketches for that, b/c the more consistent we look the more professional we look as well.
md: a look for fedoramagazine.com?
ja: oh, we need a name
ss: "Rob"
md: we have some branding templates we can plug this into.
ss: let's stay away from "magazine" since we're not going there... "magazine" seems brand-y, flash-y...
md: "journal" tends to be like a magazine but more technical... what existing publications are out there that we should model ourselves on?
ja: it's similar to lj but not... or lwn...
ss: what would the licensing be on this, btw?
ja/md unision: CC
md: I'd prefer non-ND license, stuff should be modifiable. name: "fedora first"?
ss: what are the foundations?
md: freedom, first, features, friends. first is like "the first place you go to get news..."
ss: freedom is more a newspaper title...
md: 'first' has a contemporary edginess.
ss: let's ask the list
ja: yeah, I'm going to solicit feedback on everything
md: much of our media content comes from rh and it's not remixable
ss: if we point to it instead of republishing, the licensing problem goes away
mc: fedoraproject.org/first?
md: *starts making a mockup!*
mc: how about i18n, accessibility?
md: *adds a language drop-down chooser*
ja: are there transcription tools for podcasts?
mc: yep, OSS ones.
ss: I also want to make sure we don't overwork the transcribers.
ja: there will be a workflow.
mc: let's go through planet.fp.o and give a quick yes/no to headlines to figure out what sort of content everyone thinks should be in this
everyone: *triages real quick*
md: we should do quick profiles of contributors
ss: if you know someone, you don't flame them
(meeting ends)
</pre>


===Present===
# 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.


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.
=== Development ===


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.   
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:


===Future===
* [[Insight use cases for calendar]]
* [[Insight use cases for status and microblogging]]
* [[Insight use cases for events]]


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.
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:


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/ -- not to mention [[FWN/LatestIssue]].
* [[Insight Drupal 7 Dependencies]]


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.
=== Marketing ===


Also, the goal should be to create something which is well laid out visually and consistent with the design teams work and general philosophy.
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]].  


==Goals==
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].


===Centralized Content===
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.


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.
=== Packaging ===


===Content Schedule===
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.


Well established guidelines for what needs to be produced/is being worked and when it must be published by.
=== Content workflow ===
 
This also helps in running a proper marketing campaign.
 
===Flexibility/Creativity of Presentation===
 
Journal Format
 
Better able to target an audience
 
===Standardized Feeds===
 
One OFFICIAL Feed for each media type--audio, video, text/print
 
===Translation/Press Distribution/Social Media Distribution===
 
Process for getting things in Translation Queue.
 
Better plan with regard to something like NDN.  Red Hat Intl PR is part of this
 
Develop strategies for syndicating media on social networks/news sites
 
== Questions ==
 
* Who is our audience? 
* What are they interested in?
* How can we better engage their interest?
 
== Content categories ==
 
''this is a draft, for discussion - please edit!''
 
* interviews with community members
* feature focus/update (tour)
* howto (for experienced users)
* upcoming event announcement/reminder
* past event report
* neutral reporting on debates
* rawhide report
* meeting coverage - upcoming-meetings calendar, minutes
 
== Content examples ==
 
''these are drafts, for discussion - they were taken mostly from Planet headlines on the day we looked (at the beginning of June). Please add/remove/edit/comment - what do you think should be here?'' [[User:Mchua|Mel Chua]] 12:38, 25 July 2009 (UTC)
 
=== Yes ===
 
* What's new in Fedora 11 from SELinux
* Western Digital MyBook as a Backup System (Fedora-specific existing-user tutorial)
* "you should vote; here are upcoming elections" posts
* "people voted, here are election results" posts
* Fedora 11 Release Party Wau Report
* npov coverage of things like "there is a debate on dropping cd media, here are links to several views expressed"
* Read All About the Fedora 11 Retrospective (past event coverage)
 
=== No ===
 
* HAPPY BIRTHDAY SPACEWALK! (not Fedora-specific)
* lolcats
* "I voted!" posts
* "Initial KMS support for radeons merged to Linus tree" (the blogpost-as-commit-message)
* SoaS for the XO-1 uses Fedora
* State of the Poulsbo Address
* Chinese translation of [a book I wrote] is being worked on
* So you’re looking for a hosting provider?
* Social Desktop contest
* Announcing kernelpodcast.org
* The downfall of modern civilization... (on the 'drop cd media?' debate - we're not looking for editorials, but npov coverage)
* Simplez! Simple Pairing support now in gnome-bluetooth. (more of a blog-as-commit-message than a feature report)
 
== 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
* "Push" capabilities. From kanarip: if i have to look it up, as in, actively, it's a fail; it needs to be pushed in my direction somehow; rss feeds will suffice for that purpose
 
=== News Requirements ===
 
(Extrapolated from the [[https://www.redhat.com/archives/fedora-news-list/2009-July/msg00000.html this fedora-news-list thread]] - please correct me if I've misinterpreted. [[User:Mchua|Mel Chua]] 18:44, 14 July 2009 (UTC))
 
* graphical branded presence
* syndication
* potentially retaining the FWN name? (has name recognition... open question for discussion.)
* keep current FWN sections. "Certainly Ambassadors, Planet, Art/Design, Translation, Development. Dale's virtualization beat is a creation unto itself, covering several different areas."
* easy workflow - currently, FWN is edited as one block of text, which is easier on editors than working on many separate posts.
 
=== Design requirements ===
 
* mizmo: lets you add custom CSS across the whole site design. i think its just going to be one blog (or maybe one per feed - text / audio /video ) so i dont think user level css would come into play.
* mizmo: lets you modify html output
* mizmo: tagging - to support the way we laid the mockup up, you either need multiblogs or better tagging, and tag based feeds. so like we were talking about, having a developer of the month interview, would be good to tag it with 'interview' and 'dotw', and then for each tag to have its own feed. it could be accomplished with separate blogs too, but that would then split related content, like if you had a dotw blog and an interview blog, when you do an interview for dotw it won't be in the interview blog feed
* Ability to easily pull archives, by month and year and list out (see footer of mockup)
** Same for latest posts per category, in footer of mockup
* Rawhide Weather report ability?
* live Identi.ca feed?
* allows for the pulling-in of external feeds/items or the super-easy creation of plugins to add special features - for instance, Mo's idea of the "rawhide weather report" (or Jeff Spaleta's variant of forest fire levels) may be automatically generated from buildbot logs (or something) - how can that get implemented? [[User:Mchua|Mel Chua]] 23:34, 14 July 2009 (UTC)
 
=== 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 Fedora Insight 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)
 
=== OpenEMM ===
 
* this wouldn't be the Fedora Insight platform, but instead something to support/plug-into it.
* kanarip: for sharing news and sending it around the globe (to various contacts or press-agents or whatever), may i suggest [http://www.openemm.org/ OpenEMM]
 
=== 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 Fedora Insight, 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)
*** it doesn't necessarily matter where the feeds are originating from, so it could just be one of the blogs.fpo blogs that is aggregated on a turbogears page that combines the various feeds? or it could be organized by a wordpress theme and the blogs.fpo domain is masked with a Fedora Insight.fpo domain? --[[User:Duffy|Duffy]] 21:21, 14 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 Fedora Insight proposes, and what the new CMS (Zikula) can/will accomplish. Fedora Insight 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.
* If zikula fits all of our requirements, or can/will be modified to do so, I would be strongly in favor of going with this and working with the existing cross-team effort - it just makes sense to Work Together. I think sitting down with someone who knows Zikula's feature set well, and going through our requirements list (once that is more solidified) with them, would enable us to make a final yes/no decision. [[User:Mchua|Mel Chua]] 14:45, 13 July 2009 (UTC)


This is a content workflow envisioned for Fedora Insight.


<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>


== Upcoming things ==
== History ==


* design (mizmo): waiting on platform selection
For a history of the project and some of the rationale behind it, see [[Fedora Insight history]].
* getting a test version up: also waiting on platform selection


== Sketches ==
== Workflow ==


Here's a mockup by mizmo of what this might look like. (Click for full size.)
[[Fedora Insight Workflow]]


[[File:FooBar.png|300px]]
[[Insight development using Features module]]


[[Category:Fedora Insight]]
[[Category:Fedora Insight]]

Latest revision as of 11:13, 9 October 2021

Stop (medium size).png
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.

Idea.png
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

Important.png
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"