Minutes from Rya Working Group

[Puja Valiyil <pu...@gmail.com>]

Aaron and Caleb talked about the status of the release.  They described the
remaining steps and outlined what they are planning to do this week to for
creating the release.  Aaron had a question about gpg maven tools.

We spent some time talking through Jira and how as a community we need to
document and conform to standard definitions about jira states.  We decided
to increase community involvement by:
1.  Establishing WIP pull requests: If a developer has started work, they
should not wait until the work has finished to submit the pull request.
Instead they can submit WIP pull requests and receive feedback as they
develop the feature.
2.  Moving more design discussions to confluence and the dev list:  Rather
than having discussions over email (which may happen outside of the dev
list), we should move more discussions related to design to confluence,
jira, and the dev list

We also decided to make the Rya working group alternate between
prioritizing bugs in jira and community outreach.

The next working group will be in two weeks and will focus on prioritizing
tasks in jira and putting together a road map for the project.  The working
group after that will discuss how to add a new backend persistence to Rya.

Thanks,
Puja

Re: Minutes from Rya Working Group

[Josh Elser <jo...@gmail.com>]

Great, thanks for the clarification, Puja!

Puja Valiyil wrote:
> I think what Josh said is in line with what we were thinking.  The thought
> would be that if any design work is done before starting a feature, that
> design work would be posted to confluence or the dev list so that the
> entire community has an opportunity to comment on it.  There isn't an
> expectation that one would wait for comments prior to starting work, but at
> the same time it provides more insight into things that are being actively
> worked than just jira might.  Significant decisions should be proposed and
> debated on the dev list.
>
> On Thu, Aug 11, 2016 at 11:36 AM, Josh Elser<jo...@gmail.com>  wrote:
>
>>
>> Josh Elser wrote:
>>
>>> We spent some time talking through Jira and how as a community we need to
>>>> document and conform to standard definitions about jira states.  We
>>>> decided
>>>> to increase community involvement by:
>>>> 1.  Establishing WIP pull requests: If a developer has started work, they
>>>> should not wait until the work has finished to submit the pull request.
>>>> Instead they can submit WIP pull requests and receive feedback as they
>>>> develop the feature.
>>>> 2.  Moving more design discussions to confluence and the dev list:
>>>> Rather
>>>> than having discussions over email (which may happen outside of the dev
>>>> list), we should move more discussions related to design to confluence,
>>>> jira, and the dev list
>>>>
>>> Err, hold up. Discussions *must* happen on email. Are discussions
>>> happening outside of the dev list now? The in-person meetings are OK to
>>> talk about ideas, but just reporting minutes and decisions agreed upon
>>> by the IRL attendees is not OK.
>>>
>> Realized that I didn't do a good job clarifying this late last night.
>>
>> Discussions can (and do) happen offline. The Apache Way isn't trying to
>> assert that this cannot happen. The distinction is that project _decisions_
>> should not be made in these offline discussions. Ideas/proposals can be
>> thought up offline, but the community at large must still have the ability
>> to participate in discussion.
>>
>>
>> IMO, email is still the best way to have interactive discussion, but
>>> recording design decisions and architectures on Confluence as reference
>>> material sounds like a good idea to me.
>>>
>

Re: Minutes from Rya Working Group

[Puja Valiyil <pu...@gmail.com>]

I think what Josh said is in line with what we were thinking.  The thought
would be that if any design work is done before starting a feature, that
design work would be posted to confluence or the dev list so that the
entire community has an opportunity to comment on it.  There isn't an
expectation that one would wait for comments prior to starting work, but at
the same time it provides more insight into things that are being actively
worked than just jira might.  Significant decisions should be proposed and
debated on the dev list.

On Thu, Aug 11, 2016 at 11:36 AM, Josh Elser <jo...@gmail.com> wrote:

>
>
> Josh Elser wrote:
>
>> We spent some time talking through Jira and how as a community we need to
>>> document and conform to standard definitions about jira states.  We
>>> decided
>>> to increase community involvement by:
>>> 1.  Establishing WIP pull requests: If a developer has started work, they
>>> should not wait until the work has finished to submit the pull request.
>>> Instead they can submit WIP pull requests and receive feedback as they
>>> develop the feature.
>>> 2.  Moving more design discussions to confluence and the dev list:
>>> Rather
>>> than having discussions over email (which may happen outside of the dev
>>> list), we should move more discussions related to design to confluence,
>>> jira, and the dev list
>>>
>>
>> Err, hold up. Discussions *must* happen on email. Are discussions
>> happening outside of the dev list now? The in-person meetings are OK to
>> talk about ideas, but just reporting minutes and decisions agreed upon
>> by the IRL attendees is not OK.
>>
>
> Realized that I didn't do a good job clarifying this late last night.
>
> Discussions can (and do) happen offline. The Apache Way isn't trying to
> assert that this cannot happen. The distinction is that project _decisions_
> should not be made in these offline discussions. Ideas/proposals can be
> thought up offline, but the community at large must still have the ability
> to participate in discussion.
>
>
> IMO, email is still the best way to have interactive discussion, but
>> recording design decisions and architectures on Confluence as reference
>> material sounds like a good idea to me.
>>
>

Re: Minutes from Rya Working Group

[Josh Elser <jo...@gmail.com>]

Josh Elser wrote:
>> We spent some time talking through Jira and how as a community we need to
>> document and conform to standard definitions about jira states.  We
>> decided
>> to increase community involvement by:
>> 1.  Establishing WIP pull requests: If a developer has started work, they
>> should not wait until the work has finished to submit the pull request.
>> Instead they can submit WIP pull requests and receive feedback as they
>> develop the feature.
>> 2.  Moving more design discussions to confluence and the dev list:
>> Rather
>> than having discussions over email (which may happen outside of the dev
>> list), we should move more discussions related to design to confluence,
>> jira, and the dev list
>
> Err, hold up. Discussions *must* happen on email. Are discussions
> happening outside of the dev list now? The in-person meetings are OK to
> talk about ideas, but just reporting minutes and decisions agreed upon
> by the IRL attendees is not OK.

Realized that I didn't do a good job clarifying this late last night.

Discussions can (and do) happen offline. The Apache Way isn't trying to 
assert that this cannot happen. The distinction is that project 
_decisions_ should not be made in these offline discussions. 
Ideas/proposals can be thought up offline, but the community at large 
must still have the ability to participate in discussion.

> IMO, email is still the best way to have interactive discussion, but
> recording design decisions and architectures on Confluence as reference
> material sounds like a good idea to me.

Re: Minutes from Rya Working Group

[Josh Elser <jo...@gmail.com>]

Puja Valiyil wrote:
> Aaron and Caleb talked about the status of the release.  They described the
> remaining steps and outlined what they are planning to do this week to for
> creating the release.  Aaron had a question about gpg maven tools.

Were these left outstanding? I have a little bit of experience here.

> We spent some time talking through Jira and how as a community we need to
> document and conform to standard definitions about jira states.  We decided
> to increase community involvement by:
> 1.  Establishing WIP pull requests: If a developer has started work, they
> should not wait until the work has finished to submit the pull request.
> Instead they can submit WIP pull requests and receive feedback as they
> develop the feature.
> 2.  Moving more design discussions to confluence and the dev list:  Rather
> than having discussions over email (which may happen outside of the dev
> list), we should move more discussions related to design to confluence,
> jira, and the dev list

Err, hold up. Discussions *must* happen on email. Are discussions 
happening outside of the dev list now? The in-person meetings are OK to 
talk about ideas, but just reporting minutes and decisions agreed upon 
by the IRL attendees is not OK.

IMO, email is still the best way to have interactive discussion, but 
recording design decisions and architectures on Confluence as reference 
material sounds like a good idea to me.

> We also decided to make the Rya working group alternate between
> prioritizing bugs in jira and community outreach.
>
> The next working group will be in two weeks and will focus on prioritizing
> tasks in jira and putting together a road map for the project.  The working
> group after that will discuss how to add a new backend persistence to Rya.
>
> Thanks,
> Puja
>