Re: Minutes from OpenAz call April 23, 2015

[Colm O hEigeartaigh <co...@apache.org>]

Hi Pam,

> Ok - so what I¹d like to do is create JIRA¹s for the items we discussed
at the status meeting.

+1. I believe the others have covered the issues surrounding
non-mailing-list discussions.

> Then call an official vote(s) via email for which JIRA's to take care for
the first release. As well as a vote for the release number.

Apache does not really work in such a formal way. Votes are really only
required for releases, voting in new commiters/PMC members, and possibly
for some major project decisions. Instead, you might create a mail with a
[DISCUSS] in the subject, and lay out what you feel to be a good versioning
system for the project, and a reasonable set of JIRAs to do for the first
release. People can then agree or disagree etc.

Colm.

On Thu, Apr 30, 2015 at 6:33 PM, DRAGOSH, PAMELA L (PAM) <
pdragosh@research.att.com> wrote:

> Ok - so what I¹d like to do is create JIRA¹s for the items we discussed at
> the status meeting.
>
> Then call an official vote(s) via email for which JIRA's to take care for
> the first release. As well as a vote for the release number.
>
> Is that the process that you want us to follow?
>
> Thanks,
>
> Pam
>
> On 4/24/15, 6:14 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
>
> >+1 to this.
> >
> >I suggest starting by taking each item from the call + discussing them on
> >the mailing list, so that other developers can see the rationale etc.
> >
> >Colm.
> >
> >On Fri, Apr 24, 2015 at 1:09 AM, Emmanuel Lécharny <el...@gmail.com>
> >wrote:
> >
> >> Hi guys,
> >>
> >> I understand that such meetings were most certainly the way the project
> >> used to communicate before being accepted at Apache, but this has to
> >>stop.
> >>
> >> At The ASF, if it's not on the mailing list, it does not exist. You have
> >> to understand that such calls are excluding any committers who are not
> >> on the same time zone, or at a convenient time zone. The very first day
> >> you'll have a committer in Australia, such calls will simply not be
> >> possible without excluding this comitter.
> >>
> >> Bottom line : if you are to decide somthing for the project, use the
> >> mailing list, nothing else. I know is less convenient, but this is The
> >> Apache way. And, no, pusing minutes on the mailing list is clearly not
> >> enough.
> >>
> >> Thanks !
> >>
> >>
> >> Le 23/04/15 19:54, Hal Lockhart a écrit :
> >> > Attendees
> >> >
> >> > Hal Lockhart
> >> > Rich Levinson
> >> > David Lawrence
> >> > Pam Dragosh
> >> > Ajith Nair
> >> >
> >> > Apache Migration
> >> >
> >> > Status
> >> >
> >> > Moved over PEPAPI code base. Combined with AT&T code. Put into GIT on
> >> Apache.
> >> >
> >> > Next Steps
> >> >
> >> > Need to rename packages to one uniform naming scheme. Need to decide
> >> what is needed for first release. Make sure everything works with one
> >> loader.
> >> >
> >> > Decided to create 0.9 release which contains PEPAPI over AT&T without
> >> significant additions or changes except for the following:
> >> >
> >> > Uniform package naming.
> >> > Remove developer names from source.
> >> > Single property loader.
> >> >
> >> > A list of items to be added for release 1.0  was started:
> >> >
> >> > Add bulk calls into AT&T API as in AzAPI.
> >> > Check with Oracle OES dev team whether "new" PEP is compatible with
> >> their use.
> >> > Integrate PIP code.
> >> >
> >> > Discussion about updating AMF design.
> >> >
> >> > Discussion about providing test attribute sources for testing PIPs.
> >> >
> >> > Discussion about doing single vs. multiple development items in a
> >>single
> >> checkout. Apache style seems to be one at a time.
> >> >
> >> > Pam is investigating the Sentry project to see if OpenAz could be
> >> integrated with it.
> >> >
> >> > Hal
> >>
> >>
> >
> >
> >--
> >Colm O hEigeartaigh
> >
> >Talend Community Coder
> >http://coders.talend.com
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Minutes from OpenAz call April 23, 2015

[Emmanuel Lécharny <el...@gmail.com>]

Le 01/05/15 15:56, Colm O hEigeartaigh a écrit :
> Hi Pam,
>
>> Ok - so what I¹d like to do is create JIRA¹s for the items we discussed
> at the status meeting.
>
> +1. I believe the others have covered the issues surrounding
> non-mailing-list discussions.
>
>> Then call an official vote(s) via email for which JIRA's to take care for
> the first release. As well as a vote for the release number.
>
> Apache does not really work in such a formal way. Votes are really only
> required for releases, voting in new commiters/PMC members, and possibly
> for some major project decisions. Instead, you might create a mail with a
> [DISCUSS] in the subject, and lay out what you feel to be a good versioning
> system for the project, and a reasonable set of JIRAs to do for the first
> release. People can then agree or disagree etc.

Colm is right here. We don't have a formal process, it' sup to this PMC
to define what fits your need.

If you prefer using a JIRA and vote it for each feature, it's up to you.
If you think it's a bit too rigid, you can adapt.

What is important is that every decision is made as a consensus, through
the mailing list.

At some point, you can also let one pick a feature, work on it, and
close it. If anyone part of the project does not feel that the
implementation is correct, or fits the project requirement,, then a
discussion can follow. Ultimately, one can always veto a commit (quite a
rare situation though).


The 'Apache Way' just try to make things done smoothly through consensus
building, that's the key point ! ANd consensus means every one is
included, in a way or another.

Hope it helps.