+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 <[email protected]> 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
