Pam, Emmanuel, Colm, I would definitely want to see OpenAz successful and be adopted widely. I haven’t been able to stay engaged as much as I would like to, in the last couple of months or so. I do intent to contribute to this effort going forward.
As Pam mentioned, we have a potential release candidate. Ideally, it would be nice to add a couple of tests that demonstrate the use/configuration of PIPs, with the PepAPI in action. I can take this up and add it in the next few days. Ajith > On Jul 2, 2015, at 3:28 PM, DRAGOSH, PAMELA L (PAM) > <[email protected]> wrote: > > Emmanuel, > > I can¹t answer for other folks, I know that myself and my company are > committed to seeing OpenAZ be successful. I would ask those folks to > please indicate if they are still committed. I know that my management > team will get involved and pull in help from our vendors/partners who will > be utilizing this software in their platforms. I will raise this issue > with them. > > Pam > > On 6/30/15, 7:05 PM, "Emmanuel Lécharny" <[email protected]> wrote: > >> Le 30/06/15 17:13, DRAGOSH, PAMELA L (PAM) a écrit : >>> Colm, >>> >>> This code when it was first put into Github was already fully >>> functioning. In fact, its in production at AT&T. >>> >>> There was a list of items that were done to get it ³Apache-ready², that >>> included all the package renaming, and all the formatting that you did. >>> I believe there might be a few more items that folks want done before >>> the release, we¹ll flesh that out soon enough. >> >> Pamela, >> >> I think you don't get it. >> >> What Colm point out, and I would have done the same thing, would have I >> posted a response faster, is that this podling has little to no >> activity, beside what you and Colm has done in the last few weeks. This >> is not good. >> >> We do expect that projects accepted into the incubator start getting >> some traction, some new commers to see what's going on, using the >> existing code, pointing to errors or proposing patches. So far, none of >> that happened, yet. All what we have seen since january is some code >> being injected into an Apache repository, some package renaming, and >> that's pretty much it. >> >> What we need is not -only- a release, but a full status : >> - who is *really* working on the project ? >> - what's the roadmap, where is it being discussed ? >> - do we have potential new committers, or at least some potential ? >> - what is the effort done to expose the project to the world ? (website, >> etc) ? >> >> Everything that would make OpenAZ a candidate for a promotion to a TLP, >> in other words. >> >> I do understand that OpenAZ is used in production, but this is >> irrelevant : what is is how do we build a community around the project, >> to maintain it if you have to quite the project. Atm, you are the only >> one with Colm who have shawn some involvement into it, and we need at >> least 3 person to vote a release. This is not going to fly... >> >> I do think this project is important and deserves a better exposition, >> and more effort to make it a vibrant community, beside the original >> committers. I don't see that happening, as of today, and I'd like to >> know what is going to be done to fix this issue. >> >> Many thanks ! >> Emmanuel >> >
