Hi Kevin, On 3/20/13 3:53 PM, "Kevin Minder" <[email protected]> wrote:
>Hi Everyone, >Lets see, this is all just a symptom of me learning the ropes here and >transitioning into the open development mode. So let me address each >point I believed was raised so that I get concrete feedback about how to >improve and proceed. No worries. I'm just trying to help too, and it's a learning process for everyone. I'm a total fan of people trying to "do" around here; it's how things get done ^_^ > >1. Snapshot upload > >I certainly understand the "second class" citizen concern here and I was >concerned about it myself. At the time I thought my only option was a >private email about the upload. I thought that was worse that >discussing it publically. All discussion at Apache is done publicly. 99% of it. The 1% that's not is about people and sensitive issues (mostly having to do with people). We are measured (and we report out) on public mailing list activity, so when in doubt, be public :) > Ideally I would expect these type of frequent >snapshot distributions to be built via CI. We don't have that setup >yet. I will file a Jira for that but given the information I received >in the general@incubator thread this seemed like it could take awhile. Snapshot builds can be set up through repository.apache.org, since I believe Knox is a Java project and you really want to push out jars, correct? repository.apache.org is a Sonatype Nexus server, with full sync ability to the Central repository (even as an Incubator podling) on Apache release, and with snapshots provided as well (pre-release). >In the meantime I like Alan's suggestion of uploading to >apache.org/~kminder. I'll do that and send another email. You are talking about for the RCs, right? I'd imagine you'd use a combination of: 1. Uploading the signed, src release (with MD5 and SHA1) to people.a.o/~kminder 2. Use repository.apache.org to stage the binary jars and create a Maven staging repo See examples of this in Tika: http://s.apache.org/FT2 One social note: I would expect before a release that a [DISCUSS] thread occurs, so that everyone can get on the same page for what's in it, why it needs to be made, who the Release Manager is (e.g., in this case you), etc. > >2. Release vote > >We want to avoid co-development at all costs too but at the same time we >still need to make progresss, name and cut "unofficial releases" to >evaluate both at Hortonworks and also to court potential community >members. > What should we be calling these to stay within the rules? Understood. They aren't Apache releases, so you can't call them Apache Knox (Incubating). If you need to fork e.g., into a local Hortonworks repo, and release that, we don't/can't police that here at the ASF, so you have to wear both hats. Here at the ASF, it's not a big 'O' official release until it's VOTEd on, signed, and the processes of the org are followed. Internally I would encourage you and the Hortonworks crew to try and increase the speed of releases here at the ASF, and then mix that in with svn or git tagging/insulation of project critical things but those are internal insulation, and you aren't "distributing" those to anyone besides inside of your company, correct? If you are, then the name needs to change for those, etc etc. > I >specifically left the SNAPSHOT in everything as an attempt. I expect >that there is still significant work that needs to be done to create >something that will pass legal for an official Apache release. Why is that? These are the things that we want to discuss here. > I have >more work to do to understand exactly what needs to be in the LICENSE >and NOTICE files at a minimum. When that was done I was planning on >asking about calling for a vote. Gotcha. Well in the meanwhile, Hortonworks can do whatever it wants internally, but it's not Apache Knox (Incubating). That happens here at the ASF. > >3. v0.1.0 and v0.2.0-rc1 > >We had all of our history from the GitHub repository imported into the >Apache Git repo where we have continued working. Therefore there are >existing tags for the v0.1.0 and v0.2.0-rc1 so I thought it made the >most sense to continue on. I do acknowledge in hindsight that this is >something that should have been discussed. Yeah we should just have a [DISCUSS] thread on the Apache RC, whenever you (or any PPMC member) is ready to try and cut a release and be an Apache RM. Happy to discuss version #'ing then. > >3. Co-development > >There is no active private repository for this. Everything is being >committed to the Apache git repo at this point. Larry and I in >particular need to find the right balance between high bandwidth brain >storming (e.g. face:face, IM, phone) and email discussions on dev@knox. Well, that's fine, but Larry and you aren't the only devs on the project. There is a Podling Project Management Committee (PPMC) here at the ASF: http://incubator.apache.org/guides/ppmc.html They are basically like a PMC: http://www.apache.org/dev/pmc.html (just not officially endorsed by the ASF until graduation from the Incubator). That being said, you and Larry can discuss whatever you want at Hortonworks, but decisions (and *code*) happen here at the ASF for Apache Knox (Incubating). And those happen on the mailing lists. I would encourage you not to have lots of offline and off list discussions pertaining to Knox, and then to come here with a flush of what you guys decided. That's not the way it works and it will cause other folks here in the community (like me) to ask things like: 1. Please reference that discussion with a link to the email at mail-archives.apache.org 2. Please cite the VOTE thread(s) 3. Blah blah blah :) > >4. Jira > >Devarj filed INFRA-5922 on March 1st to have Jira setup. I would much >rather be using the Apache Jira so anything that can be done to speed >that up would be appreciated. I'll take the reference to the >Hortonworks Jira out of the docs and I guess we will just have to keep >track of any issues discovered in email. I'll come up with some email >subject convention (e.g. [BUG]) Better yet, jump on #asfinfra, and (cordially) ask infra peeps to speed things along. Anyone can do that. Mentors can help too. I've just asked politely in a comment on INFRA-5922 for some expeditious work on JIRA: http://s.apache.org/L6q > >Continued feedback appreciated. You are doing great. Keep it up. I'll keep trying to mentor where I can and where I think it's needed. Thanks for your hard work Kevin. Cheers, Chris >Kevin. > >On 3/20/13 5:49 PM, Mattmann, Chris A (388J) wrote: >> Hey Guys, >> >> RE: #3, after looking at it in more detail, we need to remove references >> to internal Hortonworks JIRA's in our Apache documentation. I realize >> Hortonworks >> people have their own company systems, etc. Those should not be confused >> with their Apache (!Hortonworks) counterparts. >> >> Do we have an Apache Knox JIRA? If not, I would be glad to request one. >> >> Cheers, >> Chris >> >> >> On 3/20/13 2:46 PM, "Mattmann, Chris A (388J)" >> <[email protected]> wrote: >> >>> Hi Kevin, >>> >>> I'm not sure what this email means, but I'm worried by its context. >>> >>> Are you suggesting that you have released a version of Apache Knox, >>>with >>> a version # 0.2.0? >>> >>> If so, then I have the following statements/questions: >>> >>> 1. Apache releases are VOTEd on by the Apache Knox PPMC and by the >>>Apache >>> Incubator PMC >>> (whose VOTEs are the binding ones in this process atm). Unless I missed >>> it, >>> I didn't see a VOTE thread, so I'm not sure how you released Apache >>>Knox. >>> See: http://incubator.apache.org/guides/releasemanagement.html >>> Small note: where is RC1? >>> >>> 2. It looks like there is development occurring internally at >>>Hortonworks >>> here. >>> Why? Co-developing wastes community resources. All of you guys here >>>that >>> are interested >>> in the project should be developing here. Of course there are naming >>> issues, etc., >>> associated with this, but more importantly there are community issues. >>>So >>> I request >>> clarification on this. >>> >>> 3. Great job on the documentation! >>> >>> Looking forward to the clarifications. >>> >>> Cheers, >>> Chris >>> >>> >>> On 3/20/13 2:35 PM, "Kevin Minder" <[email protected]> >>>wrote: >>> >>>> Hi Everyone, >>>> I decided to cut and share v0.2.0 RC2 of the gateway. I tagged the >>>>repo >>>> with v0.2.0-rc2. >>>> >>>> For those in Hortonworks I uploaded a ZIP here >>>> >>>>https://docs.google.com/a/hortonworks.com/file/d/0BzcmnaxIHtiAZkxhQWZCQ >>>>21 >>>> y >>>> WTA/edit >>>> >>>> Everyone else should be able to create their own following these >>>> instructions. >>>> http://knox.incubator.apache.org/release-process.html >>>> >>>> The Apache site is starting to come along. >>>> http://knox.incubator.apache.org/ >>>> >>>> Of particular interest are the links in the Documentation section of >>>>the >>>> left Nav bar. >>>> http://knox.incubator.apache.org/getting-started.html >>>> http://knox.incubator.apache.org/examples.html >>>> http://knox.incubator.apache.org/client.html >>>> http://knox.incubator.apache.org/sandbox.html >>>> >>>> I wrote and reorganized a bunch of documentation over the last few >>>>days >>>> and I haven't "tested" all of it yet. So there may need to be some >>>> tweaks there and an RC3. Functionally however the more eyes the >>>>better >>>> so give it a spin. We are especially interested in feedback. >>>> >>>> Kevin. >
