You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by Mike Beckerle <mb...@tresys.com> on 2017/10/11 17:58:38 UTC
When to discuss in email thread, when to use a document, or wiki
page, or other?
Lots of things are just too complicated to discuss and comment on in an email thread.
E.g., code. E.g., design documents.
We have a big backlog of design notes/specs to create. My immediate task is to start writing these and getting them into review.
How should I be creating these? Where should I be putting these?
I looked at Apache Spark - their wiki has been deprecated in favor of markdown files that live in the docs tree of their git repo. However, those pages are also published in presentation form on a web site, and that's not a interactive environment for messing with them.
Suggestions?
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by "John D. Ament" <jo...@apache.org>.
I already gave you access since it was in the JIRA ticket. Feel free to
add anyone else.
On Oct 12, 2017 8:57 AM, "Steve Lawrence" <sl...@apache.org> wrote:
> Thanks John. My confluence username is 'slawrence'.
>
> - Steve
>
> On 10/12/2017 08:14 AM, John D. Ament wrote:
> > I've taken care of the wiki creation for you -
> > https://cwiki.apache.org/confluence/display/DAFFODIL/Home
> >
> > I'll need a list of users to add as admins. Note that confluence isn't
> > tied to your Apache accounts, so you'll need to register separately.
> >
> > John
> >
> > On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org>
> wrote:
> >
> >> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> >>> Lots of things are just too complicated to discuss and comment on in an
> >> email thread.
> >>>
> >>>
> >>> E.g., code. E.g., design documents.
> >>>
> >>>
> >>> We have a big backlog of design notes/specs to create. My immediate
> task
> >> is to start writing these and getting them into review.
> >>>
> >>>
> >>> How should I be creating these? Where should I be putting these?
> >>>
> >>>
> >>> I looked at Apache Spark - their wiki has been deprecated in favor of
> >> markdown files that live in the docs tree of their git repo. However,
> those
> >> pages are also published in presentation form on a web site, and that's
> not
> >> a interactive environment for messing with them.
> >>>
> >>>
> >>> Suggestions?
> >>>
> >>
> >> I think confluence is probably the best place for storage of design
> >> documents. However, discussions and decisions related to the designs
> >> should be done on the mailing list, and if reasonable/possible, the
> >> design itself should be copied to the mailing list to start discussions.
> >>
> >> I've opened an INFRA bug to create a confluence wiki for us:
> >>
> >> https://issues.apache.org/jira/browse/INFRA-15263
> >>
> >> Related, we should all create both Confluence and JIRA accounts. The
> >> accounts are not linked to each other or to the apache id accounts, so
> >> you'll need to sign up separately for them. Sign up pages are here:
> >>
> >> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
> >> JIRA: https://cwiki.apache.org/confluence/signup.action
> >>
> >> - Steve
> >>
> >
>
>
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Steve Lawrence <sl...@apache.org>.
Tayor, Mike,
You should both have write access to the wiki now.
- Steve
On 10/12/2017 09:34 AM, Mike Beckerle wrote:
> mbeckerle in both JIRA and Confluence.
>
>
> I have no rights to create a page in Confluence currently.
>
>
> I can create a JIRA ticket.
>
> ________________________________
> From: Taylor Wise <tw...@gmail.com>
> Sent: Thursday, October 12, 2017 9:22:16 AM
> To: dev@daffodil.apache.org
> Subject: Re: When to discuss in email thread, when to use a document, or wiki page, or other?
>
> VTGuy08 in JIRA
> twise.vt in confluence
>
> On Thu, Oct 12, 2017 at 8:36 AM, Steve Lawrence <sl...@apache.org>
> wrote:
>
>> Thanks John. My confluence username is 'slawrence'.
>>
>> - Steve
>>
>> On 10/12/2017 08:14 AM, John D. Ament wrote:
>>> I've taken care of the wiki creation for you -
>>> https://cwiki.apache.org/confluence/display/DAFFODIL/Home
>>>
>>> I'll need a list of users to add as admins. Note that confluence isn't
>>> tied to your Apache accounts, so you'll need to register separately.
>>>
>>> John
>>>
>>> On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org>
>> wrote:
>>>
>>>> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
>>>>> Lots of things are just too complicated to discuss and comment on in an
>>>> email thread.
>>>>>
>>>>>
>>>>> E.g., code. E.g., design documents.
>>>>>
>>>>>
>>>>> We have a big backlog of design notes/specs to create. My immediate
>> task
>>>> is to start writing these and getting them into review.
>>>>>
>>>>>
>>>>> How should I be creating these? Where should I be putting these?
>>>>>
>>>>>
>>>>> I looked at Apache Spark - their wiki has been deprecated in favor of
>>>> markdown files that live in the docs tree of their git repo. However,
>> those
>>>> pages are also published in presentation form on a web site, and that's
>> not
>>>> a interactive environment for messing with them.
>>>>>
>>>>>
>>>>> Suggestions?
>>>>>
>>>>
>>>> I think confluence is probably the best place for storage of design
>>>> documents. However, discussions and decisions related to the designs
>>>> should be done on the mailing list, and if reasonable/possible, the
>>>> design itself should be copied to the mailing list to start discussions.
>>>>
>>>> I've opened an INFRA bug to create a confluence wiki for us:
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-15263
>>>>
>>>> Related, we should all create both Confluence and JIRA accounts. The
>>>> accounts are not linked to each other or to the apache id accounts, so
>>>> you'll need to sign up separately for them. Sign up pages are here:
>>>>
>>>> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
>>>> JIRA: https://cwiki.apache.org/confluence/signup.action
>>>>
>>>> - Steve
>>>>
>>>
>>
>>
>
>
> --
> -Taylor Wise
>
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Mike Beckerle <mb...@tresys.com>.
mbeckerle in both JIRA and Confluence.
I have no rights to create a page in Confluence currently.
I can create a JIRA ticket.
________________________________
From: Taylor Wise <tw...@gmail.com>
Sent: Thursday, October 12, 2017 9:22:16 AM
To: dev@daffodil.apache.org
Subject: Re: When to discuss in email thread, when to use a document, or wiki page, or other?
VTGuy08 in JIRA
twise.vt in confluence
On Thu, Oct 12, 2017 at 8:36 AM, Steve Lawrence <sl...@apache.org>
wrote:
> Thanks John. My confluence username is 'slawrence'.
>
> - Steve
>
> On 10/12/2017 08:14 AM, John D. Ament wrote:
> > I've taken care of the wiki creation for you -
> > https://cwiki.apache.org/confluence/display/DAFFODIL/Home
> >
> > I'll need a list of users to add as admins. Note that confluence isn't
> > tied to your Apache accounts, so you'll need to register separately.
> >
> > John
> >
> > On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org>
> wrote:
> >
> >> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> >>> Lots of things are just too complicated to discuss and comment on in an
> >> email thread.
> >>>
> >>>
> >>> E.g., code. E.g., design documents.
> >>>
> >>>
> >>> We have a big backlog of design notes/specs to create. My immediate
> task
> >> is to start writing these and getting them into review.
> >>>
> >>>
> >>> How should I be creating these? Where should I be putting these?
> >>>
> >>>
> >>> I looked at Apache Spark - their wiki has been deprecated in favor of
> >> markdown files that live in the docs tree of their git repo. However,
> those
> >> pages are also published in presentation form on a web site, and that's
> not
> >> a interactive environment for messing with them.
> >>>
> >>>
> >>> Suggestions?
> >>>
> >>
> >> I think confluence is probably the best place for storage of design
> >> documents. However, discussions and decisions related to the designs
> >> should be done on the mailing list, and if reasonable/possible, the
> >> design itself should be copied to the mailing list to start discussions.
> >>
> >> I've opened an INFRA bug to create a confluence wiki for us:
> >>
> >> https://issues.apache.org/jira/browse/INFRA-15263
> >>
> >> Related, we should all create both Confluence and JIRA accounts. The
> >> accounts are not linked to each other or to the apache id accounts, so
> >> you'll need to sign up separately for them. Sign up pages are here:
> >>
> >> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
> >> JIRA: https://cwiki.apache.org/confluence/signup.action
> >>
> >> - Steve
> >>
> >
>
>
--
-Taylor Wise
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Taylor Wise <tw...@gmail.com>.
VTGuy08 in JIRA
twise.vt in confluence
On Thu, Oct 12, 2017 at 8:36 AM, Steve Lawrence <sl...@apache.org>
wrote:
> Thanks John. My confluence username is 'slawrence'.
>
> - Steve
>
> On 10/12/2017 08:14 AM, John D. Ament wrote:
> > I've taken care of the wiki creation for you -
> > https://cwiki.apache.org/confluence/display/DAFFODIL/Home
> >
> > I'll need a list of users to add as admins. Note that confluence isn't
> > tied to your Apache accounts, so you'll need to register separately.
> >
> > John
> >
> > On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org>
> wrote:
> >
> >> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> >>> Lots of things are just too complicated to discuss and comment on in an
> >> email thread.
> >>>
> >>>
> >>> E.g., code. E.g., design documents.
> >>>
> >>>
> >>> We have a big backlog of design notes/specs to create. My immediate
> task
> >> is to start writing these and getting them into review.
> >>>
> >>>
> >>> How should I be creating these? Where should I be putting these?
> >>>
> >>>
> >>> I looked at Apache Spark - their wiki has been deprecated in favor of
> >> markdown files that live in the docs tree of their git repo. However,
> those
> >> pages are also published in presentation form on a web site, and that's
> not
> >> a interactive environment for messing with them.
> >>>
> >>>
> >>> Suggestions?
> >>>
> >>
> >> I think confluence is probably the best place for storage of design
> >> documents. However, discussions and decisions related to the designs
> >> should be done on the mailing list, and if reasonable/possible, the
> >> design itself should be copied to the mailing list to start discussions.
> >>
> >> I've opened an INFRA bug to create a confluence wiki for us:
> >>
> >> https://issues.apache.org/jira/browse/INFRA-15263
> >>
> >> Related, we should all create both Confluence and JIRA accounts. The
> >> accounts are not linked to each other or to the apache id accounts, so
> >> you'll need to sign up separately for them. Sign up pages are here:
> >>
> >> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
> >> JIRA: https://cwiki.apache.org/confluence/signup.action
> >>
> >> - Steve
> >>
> >
>
>
--
-Taylor Wise
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Steve Lawrence <sl...@apache.org>.
Thanks John. My confluence username is 'slawrence'.
- Steve
On 10/12/2017 08:14 AM, John D. Ament wrote:
> I've taken care of the wiki creation for you -
> https://cwiki.apache.org/confluence/display/DAFFODIL/Home
>
> I'll need a list of users to add as admins. Note that confluence isn't
> tied to your Apache accounts, so you'll need to register separately.
>
> John
>
> On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org> wrote:
>
>> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
>>> Lots of things are just too complicated to discuss and comment on in an
>> email thread.
>>>
>>>
>>> E.g., code. E.g., design documents.
>>>
>>>
>>> We have a big backlog of design notes/specs to create. My immediate task
>> is to start writing these and getting them into review.
>>>
>>>
>>> How should I be creating these? Where should I be putting these?
>>>
>>>
>>> I looked at Apache Spark - their wiki has been deprecated in favor of
>> markdown files that live in the docs tree of their git repo. However, those
>> pages are also published in presentation form on a web site, and that's not
>> a interactive environment for messing with them.
>>>
>>>
>>> Suggestions?
>>>
>>
>> I think confluence is probably the best place for storage of design
>> documents. However, discussions and decisions related to the designs
>> should be done on the mailing list, and if reasonable/possible, the
>> design itself should be copied to the mailing list to start discussions.
>>
>> I've opened an INFRA bug to create a confluence wiki for us:
>>
>> https://issues.apache.org/jira/browse/INFRA-15263
>>
>> Related, we should all create both Confluence and JIRA accounts. The
>> accounts are not linked to each other or to the apache id accounts, so
>> you'll need to sign up separately for them. Sign up pages are here:
>>
>> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
>> JIRA: https://cwiki.apache.org/confluence/signup.action
>>
>> - Steve
>>
>
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by "John D. Ament" <jo...@apache.org>.
I've taken care of the wiki creation for you -
https://cwiki.apache.org/confluence/display/DAFFODIL/Home
I'll need a list of users to add as admins. Note that confluence isn't
tied to your Apache accounts, so you'll need to register separately.
John
On Thu, Oct 12, 2017 at 7:59 AM Steve Lawrence <sl...@apache.org> wrote:
> On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> > Lots of things are just too complicated to discuss and comment on in an
> email thread.
> >
> >
> > E.g., code. E.g., design documents.
> >
> >
> > We have a big backlog of design notes/specs to create. My immediate task
> is to start writing these and getting them into review.
> >
> >
> > How should I be creating these? Where should I be putting these?
> >
> >
> > I looked at Apache Spark - their wiki has been deprecated in favor of
> markdown files that live in the docs tree of their git repo. However, those
> pages are also published in presentation form on a web site, and that's not
> a interactive environment for messing with them.
> >
> >
> > Suggestions?
> >
>
> I think confluence is probably the best place for storage of design
> documents. However, discussions and decisions related to the designs
> should be done on the mailing list, and if reasonable/possible, the
> design itself should be copied to the mailing list to start discussions.
>
> I've opened an INFRA bug to create a confluence wiki for us:
>
> https://issues.apache.org/jira/browse/INFRA-15263
>
> Related, we should all create both Confluence and JIRA accounts. The
> accounts are not linked to each other or to the apache id accounts, so
> you'll need to sign up separately for them. Sign up pages are here:
>
> Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
> JIRA: https://cwiki.apache.org/confluence/signup.action
>
> - Steve
>
RE: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Dave Thompson <dt...@tresys.com>.
Steve,
Signed up for Confluence and JIRA accounts with user name dfthompson for both.
Got confirmation email back for JIRA signup but not the Confluence.
Dave
-----Original Message-----
From: Steve Lawrence [mailto:slawrence@apache.org]
Sent: Thursday, October 12, 2017 7:59 AM
To: dev@daffodil.apache.org; Mike Beckerle <mb...@tresys.com>
Subject: Re: When to discuss in email thread, when to use a document, or wiki page, or other?
On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> Lots of things are just too complicated to discuss and comment on in an email thread.
>
>
> E.g., code. E.g., design documents.
>
>
> We have a big backlog of design notes/specs to create. My immediate task is to start writing these and getting them into review.
>
>
> How should I be creating these? Where should I be putting these?
>
>
> I looked at Apache Spark - their wiki has been deprecated in favor of markdown files that live in the docs tree of their git repo. However, those pages are also published in presentation form on a web site, and that's not a interactive environment for messing with them.
>
>
> Suggestions?
>
I think confluence is probably the best place for storage of design documents. However, discussions and decisions related to the designs should be done on the mailing list, and if reasonable/possible, the design itself should be copied to the mailing list to start discussions.
I've opened an INFRA bug to create a confluence wiki for us:
https://issues.apache.org/jira/browse/INFRA-15263
Related, we should all create both Confluence and JIRA accounts. The accounts are not linked to each other or to the apache id accounts, so you'll need to sign up separately for them. Sign up pages are here:
Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
JIRA: https://cwiki.apache.org/confluence/signup.action
- Steve
Re: When to discuss in email thread, when to use a document, or wiki
page, or other?
Posted by Steve Lawrence <sl...@apache.org>.
On 10/11/2017 01:58 PM, Mike Beckerle wrote:
> Lots of things are just too complicated to discuss and comment on in an email thread.
>
>
> E.g., code. E.g., design documents.
>
>
> We have a big backlog of design notes/specs to create. My immediate task is to start writing these and getting them into review.
>
>
> How should I be creating these? Where should I be putting these?
>
>
> I looked at Apache Spark - their wiki has been deprecated in favor of markdown files that live in the docs tree of their git repo. However, those pages are also published in presentation form on a web site, and that's not a interactive environment for messing with them.
>
>
> Suggestions?
>
I think confluence is probably the best place for storage of design
documents. However, discussions and decisions related to the designs
should be done on the mailing list, and if reasonable/possible, the
design itself should be copied to the mailing list to start discussions.
I've opened an INFRA bug to create a confluence wiki for us:
https://issues.apache.org/jira/browse/INFRA-15263
Related, we should all create both Confluence and JIRA accounts. The
accounts are not linked to each other or to the apache id accounts, so
you'll need to sign up separately for them. Sign up pages are here:
Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa
JIRA: https://cwiki.apache.org/confluence/signup.action
- Steve