It's typical to use the project's main JIRA project to track documentation and website enhancements, not a separate JIRA project. You could consider using the Component field, set to something like "documentation", for further refinement. That would then allow you to query JIRA for all documentation requests.
--Chris Nauroth On 9/21/15, 12:59 PM, "Andy Perlitch" <[email protected]> wrote: >Certainly on board for using JIRA to track website issues, however does >that mean we have to create a new JIRA project? > >-Andy > >On Fri, Sep 18, 2015 at 2:45 PM, York, Brennon ><[email protected]> >wrote: > >> Andy, that’s awesome. I figure, to your earlier point on tracking >>website >> issues, I figure we can just make more JIRAs and track there. That was >>we >> at least have a reference. Thanks for this! >> >> On 9/18/15, 10:16 AM, "Andy Perlitch" <[email protected]> wrote: >> >> >Brennon, >> > >> >I have added this page >> ><http://apex.incubator.apache.org/github-mirror-pull-requests.html> to >> the >> >site. It's basically just what thomas mentioned earlier in this email, >>and >> >could probably use a little more love. Also, once we get our new docs >> >worked out, we'll formalize this doc and put it there. >> > >> >Best, >> >Andy >> > >> >On Wed, Sep 16, 2015 at 2:28 PM, Andy Perlitch <[email protected]> >> >wrote: >> > >> >> Hey Brennon, >> >> >> >> The website is backed by an apache git repository ( >> >> https://git-wip-us.apache.org/repos/asf/incubator-apex-site.git). The >> >> github mirror is here: >>https://github.com/apache/incubator-apex-site. I >> >> made a first pass at the README when creating it for the first time >>but >> >>I >> >> assume there are some things missing from it (specifically, I see >>that >> >> there is no "contributing" section). >> >> >> >> Take a look and please reply here with questions. I suppose best way >>to >> >> allow for contributing to the site is to open pull requests against >>the >> >> github mirror. Let me know what you think. >> >> >> >> -Andy >> >> >> >> >> >> >> >> On Wed, Sep 16, 2015 at 10:25 AM, York, Brennon < >> >> [email protected]> wrote: >> >> >> >>> Nailed it! Thanks @Thomas for this. >> >>> >> >>> @Andy, could you help me understand how to update the incubator site >> >>> (apex.incubator.apache.org)? I’d like to take a stab at either >> updating >> >>> the docs there (if you haven’t) or know how to do it :) >> >>> >> >>> On 9/16/15, 9:28 AM, "Andy Perlitch" <[email protected]> wrote: >> >>> >> >>> >I'll be sure and add these instructions to the website. >> >>> > >> >>> >Andy >> >>> > >> >>> >> On Sep 16, 2015, at 8:47 AM, Thomas Weise >><[email protected]> >> >>> >>wrote: >> >>> >> >> >>> >> Brennon, >> >>> >> >> >>> >> See below. What you are looking for is mentioned under committer. >> >>> >> >> >>> >> We should probably add this to our web site. >> >>> >> >> >>> >> Thanks >> >>> >> >> >>> >> >> >>> >> *As contributor:* >> >>> >> >> >>> >> Fork the ASF github mirror: >> >>> >> >> >>> >> https://github.com/apache/incubator-apex-core/ >> >>> >> >> >>> >> You can then update your local repository to add the new fork as >> >>> >>remote. No >> >>> >> need for another clone or to recreate your workspace. >> >>> >> >> >>> >> Once your feature is complete, submit the pull request. Ensure >>that >> >>>the >> >>> >> Apex JIRA numbers are part of the commit message (we have not >> >>>migrated >> >>> >>to >> >>> >> ASF JIRA yet). >> >>> >> >> >>> >> *As committer:* >> >>> >> >> >>> >> The ASF master repository is: >> >>> >> >> >>> >> https://git-wip-us.apache.org/repos/asf/incubator-apex-core.git >> >>> >> >> >>> >> Access: https://git-wip-us.apache.org/#committers-getting-started >> >>> >> >> >>> >> Use the command line to pull in the changes from the pull >>requests. >> >>> >>Since >> >>> >> the github mirror is readonly, you will not be shown the >>convenient >> >>> >>command >> >>> >> line instructions :-( Good opportunity to remember the git >>commands! >> >>> >> >> >>> >> Once done with verification, push the changes to the master. >>Within >> >>>a >> >>> >>few >> >>> >> seconds, the changes will propagate back to the github mirror and >> >>>the >> >>> >>pull >> >>> >> requests be closed and marked merged. >> >>> >> >> >>> >> Note: since none of us has write access to the mirror, only the >> >>>author >> >>> >>of a >> >>> >> pull request can close it. >> >>> >> >> >>> >> >> >>> >> On Wed, Sep 16, 2015 at 8:37 AM, York, Brennon >> >>> >><[email protected]> >> >>> >> wrote: >> >>> >> >> >>> >>> All, can someone provide a succinct guide on how to merge in a >>PR >> >>>from >> >>> >>>the >> >>> >>> Github mirror (at github.com/apache/incubator-apex-core) into >>the >> >>> >>>Apache >> >>> >>> github repo (at >> >>> >>> >>https://git-wip-us.apache.org/repos/asf/incubator-apex-core.git). >> >>>I¹m >> >>> >>> trying to test my commit access by merging in Thomas¹ PR (#53 to >> >>>add a >> >>> >>> LICENSE file) and I¹ve followed the links below (plus the other >> >>> >>>thread) to >> >>> >>> set everything up although I can¹t figure out how to explicitly >> >>>merge >> >>> >>>code >> >>> >>> into the upstream repo. Any help here would be really helpful! >> >>> >>> >> >>> >>>> On 8/27/15, 1:12 PM, "Hitesh Shah" <[email protected]> wrote: >> >>> >>>> >> >>> >>>> Hi folks >> >>> >>>> >> >>> >>>> For all the folks who recently got accounts created, here are a >> >>>set >> >>> of >> >>> >>>> useful links to help get you started: >> >>> >>>> >> >>> >>>> A general good-to-read guide about the ASF: >> >>> >>>> http://incubator.apache.org/learn/theapacheway.html >> >>> >>>> >> >>> >>>> New Committer Guide: >> >>> >>>>http://www.apache.org/dev/new-committers-guide.html >> >>> >>>> >> >>> >>>> Using Git at the ASF: https://git-wip-us.apache.org/ >> >>> >>>> >> >>> >>>> Incubator related guides for committers and podling PMC: >> >>> >>>> http://incubator.apache.org/guides/participation.html >> >>> >>>> http://incubator.apache.org/guides/committer.html >> >>> >>>> http://incubator.apache.org/guides/ppmc.html >> >>> >>>> >> >>> >>>> thanks >> >>> >>>> ‹ Hitesh >> >>> >>> >> >>> >>> ________________________________________________________ >> >>> >>> >> >>> >>> The information contained in this e-mail is confidential and/or >> >>> >>> proprietary to Capital One and/or its affiliates and may only be >> >>>used >> >>> >>> solely in performance of work or services for Capital One. The >> >>> >>>information >> >>> >>> transmitted herewith is intended only for use by the individual >>or >> >>> >>>entity >> >>> >>> to which it is addressed. If the reader of this message is not >>the >> >>> >>>intended >> >>> >>> recipient, you are hereby notified that any review, >>retransmission, >> >>> >>> dissemination, distribution, copying or other use of, or taking >>of >> >>>any >> >>> >>> action in reliance upon this information is strictly >>prohibited. If >> >>> you >> >>> >>> have received this communication in error, please contact the >> >>>sender >> >>> >>>and >> >>> >>> delete the material from your computer. >> >>> >>> >> >>> >>> >> >>> >> >>> ________________________________________________________ >> >>> >> >>> The information contained in this e-mail is confidential and/or >> >>> proprietary to Capital One and/or its affiliates and may only be >>used >> >>> solely in performance of work or services for Capital One. The >> >>>information >> >>> transmitted herewith is intended only for use by the individual or >> >>>entity >> >>> to which it is addressed. If the reader of this message is not the >> >>>intended >> >>> recipient, you are hereby notified that any review, retransmission, >> >>> dissemination, distribution, copying or other use of, or taking of >>any >> >>> action in reliance upon this information is strictly prohibited. If >>you >> >>> have received this communication in error, please contact the sender >> >>>and >> >>> delete the material from your computer. >> >>> >> >> >> >> >> >> >> >> -- >> >> Regards, >> >> Andy Perlitch >> >> Software Engineer >> >> DataTorrent Inc >> >> (408)829-9319 >> >> >> > >> > >> > >> >-- >> >Regards, >> >Andy Perlitch >> >Software Engineer >> >DataTorrent Inc >> >(408)829-9319 >> >> ________________________________________________________ >> >> The information contained in this e-mail is confidential and/or >> proprietary to Capital One and/or its affiliates and may only be used >> solely in performance of work or services for Capital One. The >>information >> transmitted herewith is intended only for use by the individual or >>entity >> to which it is addressed. If the reader of this message is not the >>intended >> recipient, you are hereby notified that any review, retransmission, >> dissemination, distribution, copying or other use of, or taking of any >> action in reliance upon this information is strictly prohibited. If you >> have received this communication in error, please contact the sender and >> delete the material from your computer. >> ________________________________________________________ >> >> The information contained in this e-mail is confidential and/or >> proprietary to Capital One and/or its affiliates and may only be used >> solely in performance of work or services for Capital One. The >>information >> transmitted herewith is intended only for use by the individual or >>entity >> to which it is addressed. If the reader of this message is not the >>intended >> recipient, you are hereby notified that any review, retransmission, >> dissemination, distribution, copying or other use of, or taking of any >> action in reliance upon this information is strictly prohibited. If you >> have received this communication in error, please contact the sender and >> delete the material from your computer. >> > > > >-- >Regards, >Andy Perlitch >Software Engineer >DataTorrent Inc >(408)829-9319
