OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

csaf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [csaf] [OASIS Issue Tracker] (CSAF-12) Document CSAF TC meeting collaboration and minuting chat


Hi Bret,

On 02/12/16 17:37, Bret Jordan (CS) wrote:
> It feels like we are trying to use the issue tracker in JIRA in place of
> things that should just happen on the email list.  Can we please avoid
> this?  

these are just notifications from the tracker as 
indicated by the subject line and indicated by the 
formal structure of the mail content.

Mail clients can always filter nicely to separate 
these mails from human to human mails, in case this 
irritates someone.


> 
> 
> It would be nice to have discussion just over email vs in the JIRA issue
> tracker.  Further, can we please move to the Github Issue tracker?  JIRA
> is so 1990...

I hope we will have discussions during the meetings 
and via email where applicable and best matching 
the topic and structure of information /arguments 
to be exchanged.

E-Mail is so 1982 but it fits well the tasks it fits.

JIRA helps us track important and document decisions 
in an unmatched granularity and quality with ease. 
Also the TC members are automatically also JIRA users, 
so accessibility is premium.
Creating working standards in my experience is easy 
supported with such a tool. 
The OASIS setup might benefit greatly from preview, 
some plugins for better showing off code snippets and 
maybe some formatting here and there, but it works.

Github tracker is ok for software only projects, 
but - similar to email only discussions, and at least in 
my experience hard to focus, easy to forget something,
and close to impossible to summarize at given points 
in time (e.g. meetings).

It is not always matching strategy, to offer pull 
requests regardless of the work product format. 
With software on source level this is piece of cake, but 
with documents a somehow detached issue tracking with 
a proven workflow is very 2017 ;-)

All the best,
Stefan.

> 
> Bret
> 
> ------------------------------------------------------------------------
> *From:* csaf@lists.oasis-open.org <csaf@lists.oasis-open.org> on behalf
> of OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
> *Sent:* Friday, December 2, 2016 4:37:43 AM
> *To:* csaf@lists.oasis-open.org
> *Subject:* [csaf] [OASIS Issue Tracker] (CSAF-12) Document CSAF TC
> meeting collaboration and minuting chat
>  
> Stefan Hagen created CSAF-12:
> --------------------------------
> 
>              Summary: Document CSAF TC meeting collaboration and
> minuting chat
>                  Key: CSAF-12
>                  URL: https://issues.oasis-open.org/browse/CSAF-12
>              Project: OASIS Common Security Advisory Framework (CSAF) TC
>           Issue Type: Task
>             Reporter: Stefan Hagen
>             Assignee: Stefan Hagen
> 
> 
> To optimise collaboration for all participating members, we should
> document the proven chat, that many TC's successfully use since a long time.
> 
> 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.2.2#6258)
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]