On Tue, Apr 19, 2016 at 3:57 PM, David Ash <[email protected]> wrote:
> Maybe my hands aren't tied. Here's what I'm looking for, maybe you can > tell me I've already got what I need: > > 1) Username / password to a system where I can make arbitrary updates to > the website. > After looking, this just requires committer status. > 2) Ability to grant that power to others. > There's kind of a community approach for this, although I'm not sure what our process is (officially, we should have this kind of figured out as a podling, there's no set method). So how do we decide on this? > 3) Be able to merge pull requests to the git website. > We can just fork it and own a new official base as far as github is concerned. Nothing needed here. > 4) Be able to grant that power to others. > That's a github thing. No need to discuss it here. > 5) Be able to pull any git updates into the official repository. > Committer status (same as 1) > 6) Have access to top-level management information, like URLs and access > info for all Apache OpenAZ resources. > Not sure this even exists. But if it does, access to it would be nice. Ideally, it would just be on the website we don't have yet, which would publish that information to anyone that visited our site. > 7) Be able to change that top-level management information. > Committer status. So I guess what I have realized is: I just need committer status. > That would be enough as a start. > > We need some movement, which requires just those things for now. Then > when there's movement, I've got at least 3 more people I could bring on to > make little tweaks (which is all we really need for a first release). > > I also know how to use twitter well enough to drum up more hands and > feet. But without the power to make things happen (not just commit code to > a fork on github, but actually make those merges happen), I'm not getting > more people involved. > > So, do I have this power already and don't know it, or what? > > On Tue, Apr 19, 2016 at 3:46 PM, John D. Ament <[email protected]> > wrote: > >> On Tue, Apr 19, 2016 at 4:45 PM David Ash <[email protected]> wrote: >> >> > I've been ignoring this because my hands are tied for trying to help it. >> > But can we try moving to new management? Can I be put in charge? >> > >> >> I'm a bit confused by your statements. Who is management in this case? >> Your employer? The ASF? Why are your hands tied for trying to help? >> >> ASF projects have no one in charge of them. TLPs get a VP, whose main >> responsibility is keeping the project running. >> >> >> > >> > Send me links to the right resources and give me the credentials to make >> > things happen, and I might be able to recover it. >> > >> >> I'm not sure what recover it means. A community of 1 isn't a community. >> >> >> > >> > On Mon, Apr 18, 2016, 3:25 PM Farasath Ahamed <[email protected]> >> > wrote: >> > >> > > +1 >> > > On Apr 19, 2016 2:41 AM, "Hadrian Zbarcea" <[email protected]> >> wrote: >> > > >> > > > +1 >> > > > >> > > > Hadrian >> > > > >> > > > On 04/17/2016 11:40 AM, John D. Ament wrote: >> > > > >> > > >> All, >> > > >> >> > > >> This is a formal vote to retire the OpenAz podling. This vote is >> the >> > > >> second step in the retirement process and is used as an indicator >> to >> > the >> > > >> IPMC about whether to retire the podling, as the final decision >> lies >> > > with >> > > >> the Incubator. >> > > >> >> > > >> Unless one of the mentors wants to take it on, if the vote passes >> here >> > > and >> > > >> on the IPMC list, I can take care of the retirement process (as >> > > described >> > > >> at http://incubator.apache.org/guides/retirement.html ). >> > > >> >> > > >> This vote will be open for 72 hours via lazy consensus. >> > > >> >> > > >> Thanks, >> > > >> >> > > >> John >> > > >> >> > > >> >> > > >> > >> > >
