[prev in list] [next in list] [prev in thread] [next in thread] 

List:       scap-security-guide
Subject:    Restructuring/Update of Trac
From:       scapafterhours () gmail ! com (Jeffrey Blank)
Date:       2012-11-25 23:21:37
Message-ID: CALjtS7JB9gbDnNV+y7keOEEVusKr+=AfviBvU-MK=p2OzOdq_g () mail ! gmail ! com
[Download RAW message or body]

This is great!   Ditto on "sub-milestones" being desirable, but hey -- Trac
works pretty well overall.

Many of the recent tickets seem to involve copy editing, and indicate a
careful proofreading, which is great.  That said, there are also some
consistently odd bits (as we'd discussed).  It's preferable to resolve this
quickly so that the tickets with copy editing requests can be completed to
the satisfaction of all parties.

How does a concall on Thursday look, to invite all relevant parties to
discuss some of the typographical conventions?  I propose 11am, but it's
certainly negotiable. Shawn -- can you handle setup?

My inclination is to defer to Red Hat, as vendors are most capable of
expressing how to configure their products a particular way.  (Vendors also
tend to know a thing or two about this, given their expertise/investment in
documentation and support.)  We may also want to discuss where we stand
with regard to formatting of final output in the short term and medium term
(support for bold/italics/lists/linebreaks using XHTML, etc).

In any event it's best to have a quick discussion and move forward.

Jeff




On Sun, Nov 25, 2012 at 10:14 AM, Shawn Wells <shawn at redhat.com> wrote:

> Hey Guys,
> 
> I had some time to go in and (finally!) restructure Trac, the Fedora
> Hosted provided ticketing system. In short:
> 
> - Killed off stale milestones and reassigned open tickets to new ones
> which make sense. Note many items, such as CCE mappings, I'm considering a
> ticket of a milestone (vs a milestone itself). To my knowledge we cannot
> setup "sub milestones," so this approach seems best for now. Current OPEN
> milestones are below:
> * Remediation Content Synchronization (adding in TBD remediation
> scripts)
> * RHEL6 STIG - DISA InitialDraft Submission Feedback
> 
> - Updated "Components" of the project, which allows users to place tickets
> against specific subsections. The updated list:
> * Build System
> * OVAL Content
> * Remediation Content
> * Tools
> * XCCDF Content
> 
> - By default all new tickets will be owned by Michele Newman, who will
> screen them and pass along as appropriate.
> 
> 
> For those interested, here is a list of all open tickets by milestone:
> https://fedorahosted.org/scap-**security-guide/report/3<https://fedorahosted.org/scap-security-guide/report/3>
>  
> -Shawn
> ______________________________**_________________
> scap-security-guide mailing list
> scap-security-guide at lists.**fedorahosted.org<scap-security-guide at \
> lists.fedorahosted.org> \
> https://lists.fedorahosted.**org/mailman/listinfo/scap-**security-guide<https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide>
>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20121125/112812fd/attachment.html>



[prev in list] [next in list] [prev in thread] [next in thread]