Using Jira for Issues

[Lewis John Mcgibbney]

Hi Folks,
One of the things about our Jira instance, is that it is hosted by and at
the ASF. Therefore all correspondence is always available to the ASF.
If Github were ever to vanish, we would essentially loose all of the
correspondence for all of the tickets issues created over there.
Typically what I, and every other Apache project I am aware of does, is to
first open a ticket in Jira, then just title your pull request commit
message after the Jira ticket.
This way we also have comprehensive release reports, assignees, road maps,
etc etc etc.
I would like to suggest that we start using Jira in this manner as recently
I've not really seen any tickets go in there.
What do you think about this?
Lewis


-- 
*Lewis*

Re: [GitHub] incubator-joshua pull request: More work on structuring translatio...

[Matt Post]

Sounds good.


> On Apr 29, 2016, at 1:50 AM, kellen sunderland  
> wrote:
> 
> Hey Matt.  I'd suggest we hook up the unit test runs in Vancouver (only a
> week away).  They should be runnable with junit.
> On Apr 28, 2016 9:55 PM, "mjpost"  wrote:
> 
>> Github user mjpost commented on the pull request:
>> 
>> 
>> https://github.com/apache/incubator-joshua/pull/9#issuecomment-215626822
>> 
>>Okay, this is merged. This is nice work. A few notes:
>> 
>>- Can you tell me how to run the unit tests? @KellenSunderland @fhieber
>> 
>>- The phrase-based decoder can use the exact same improvements you
>> pushed up, so I converted them over to this
>> 
>>- include_align_index is no longer used anywhere. I may add that back
>> to the phrase-based decoder if I need it, but am leaving it out for now (so
>> it will really just do nothing if you ask for it)
>> 
>> 
>> ---
>> If your project is set up for it, you can reply to this email and have your
>> reply appear on GitHub as well. If your project does not have this feature
>> enabled and wishes so, or if the feature is enabled but not working, please
>> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
>> 

Re: Using Jira for Issues

[Matt Post]

Lewis, this sounds good to me.

I'm in the process of moving the (hideous) Joshua web page over to Confluence, 
and created a Developer page, where I added this to the documentation.

https://cwiki.apache.org/confluence/display/JOSHUA/Development

Can you look this over and improve it (e.g., with links on the appropriate 
instruction points?)

matt



> On Apr 29, 2016, at 7:13 AM, Lewis John Mcgibbney  
> wrote:
> 
> Hi Folks,
> One of the things about our Jira instance, is that it is hosted by and at
> the ASF. Therefore all correspondence is always available to the ASF.
> If Github were ever to vanish, we would essentially loose all of the
> correspondence for all of the tickets issues created over there.
> Typically what I, and every other Apache project I am aware of does, is to
> first open a ticket in Jira, then just title your pull request commit
> message after the Jira ticket.
> This way we also have comprehensive release reports, assignees, road maps,
> etc etc etc.
> I would like to suggest that we start using Jira in this manner as recently
> I've not really seen any tickets go in there.
> What do you think about this?
> Lewis
> 
> 
> -- 
> *Lewis*

Re: Using Jira for Issues

[Lewis John Mcgibbney]

Hi Matt,
Dynamite. Thanks for taking notes action in the site. As you've seen I've
been hammering through the licensing issues and will continue to do so as I
look at more code in different languages.
I'll scope site throughout the next week or so.
Thanks

On Friday, April 29, 2016, Matt Post  wrote:

> Lewis, this sounds good to me.
>
> I'm in the process of moving the (hideous) Joshua web page over to
> Confluence, and created a Developer page, where I added this to the
> documentation.
>
> https://cwiki.apache.org/confluence/display/JOSHUA/Development
>
> Can you look this over and improve it (e.g., with links on the appropriate
> instruction points?)
>
> matt
>
>
>
> > On Apr 29, 2016, at 7:13 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com > wrote:
> >
> > Hi Folks,
> > One of the things about our Jira instance, is that it is hosted by and at
> > the ASF. Therefore all correspondence is always available to the ASF.
> > If Github were ever to vanish, we would essentially loose all of the
> > correspondence for all of the tickets issues created over there.
> > Typically what I, and every other Apache project I am aware of does, is
> to
> > first open a ticket in Jira, then just title your pull request commit
> > message after the Jira ticket.
> > This way we also have comprehensive release reports, assignees, road
> maps,
> > etc etc etc.
> > I would like to suggest that we start using Jira in this manner as
> recently
> > I've not really seen any tickets go in there.
> > What do you think about this?
> > Lewis
> >
> >
> > --
> > *Lewis*
>
>

-- 
*Lewis*

Re: Using Jira for Issues

[Lewis John Mcgibbney]

Boom
See you in Vancouver auld chap

On Friday, April 29, 2016, Tom Barber  wrote:

> Hi guys
>
> Sorry I've not been of any use so far, day job(s) getting in the way and
> ApacheCon. Once I'm back from Vancouver I can certainly help out with
> licensing, docs and Jira org stuff.
>
> Keep it up Lewis I've seen all the commits streaming past!
>
> Tom
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> goal, but you can always help by sponsoring the project
> )
>
> On 29 April 2016 at 14:47, Lewis John Mcgibbney  >
> wrote:
>
> > Hi Matt,
> > Dynamite. Thanks for taking notes action in the site. As you've seen I've
> > been hammering through the licensing issues and will continue to do so
> as I
> > look at more code in different languages.
> > I'll scope site throughout the next week or so.
> > Thanks
> >
> > On Friday, April 29, 2016, Matt Post >
> wrote:
> >
> > > Lewis, this sounds good to me.
> > >
> > > I'm in the process of moving the (hideous) Joshua web page over to
> > > Confluence, and created a Developer page, where I added this to the
> > > documentation.
> > >
> > > https://cwiki.apache.org/confluence/display/JOSHUA/Development
> > >
> > > Can you look this over and improve it (e.g., with links on the
> > appropriate
> > > instruction points?)
> > >
> > > matt
> > >
> > >
> > >
> > > > On Apr 29, 2016, at 7:13 AM, Lewis John Mcgibbney <
> > > lewis.mcgibb...@gmail.com  > wrote:
> > > >
> > > > Hi Folks,
> > > > One of the things about our Jira instance, is that it is hosted by
> and
> > at
> > > > the ASF. Therefore all correspondence is always available to the ASF.
> > > > If Github were ever to vanish, we would essentially loose all of the
> > > > correspondence for all of the tickets issues created over there.
> > > > Typically what I, and every other Apache project I am aware of does,
> is
> > > to
> > > > first open a ticket in Jira, then just title your pull request commit
> > > > message after the Jira ticket.
> > > > This way we also have comprehensive release reports, assignees, road
> > > maps,
> > > > etc etc etc.
> > > > I would like to suggest that we start using Jira in this manner as
> > > recently
> > > > I've not really seen any tickets go in there.
> > > > What do you think about this?
> > > > Lewis
> > > >
> > > >
> > > > --
> > > > *Lewis*
> > >
> > >
> >
> > --
> > *Lewis*
> >
>


-- 
*Lewis*

Re: Using Jira for Issues

[Tom Barber]

Hi guys

Sorry I've not been of any use so far, day job(s) getting in the way and
ApacheCon. Once I'm back from Vancouver I can certainly help out with
licensing, docs and Jira org stuff.

Keep it up Lewis I've seen all the commits streaming past!

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 April 2016 at 14:47, Lewis John Mcgibbney 
wrote:

> Hi Matt,
> Dynamite. Thanks for taking notes action in the site. As you've seen I've
> been hammering through the licensing issues and will continue to do so as I
> look at more code in different languages.
> I'll scope site throughout the next week or so.
> Thanks
>
> On Friday, April 29, 2016, Matt Post  wrote:
>
> > Lewis, this sounds good to me.
> >
> > I'm in the process of moving the (hideous) Joshua web page over to
> > Confluence, and created a Developer page, where I added this to the
> > documentation.
> >
> > https://cwiki.apache.org/confluence/display/JOSHUA/Development
> >
> > Can you look this over and improve it (e.g., with links on the
> appropriate
> > instruction points?)
> >
> > matt
> >
> >
> >
> > > On Apr 29, 2016, at 7:13 AM, Lewis John Mcgibbney <
> > lewis.mcgibb...@gmail.com > wrote:
> > >
> > > Hi Folks,
> > > One of the things about our Jira instance, is that it is hosted by and
> at
> > > the ASF. Therefore all correspondence is always available to the ASF.
> > > If Github were ever to vanish, we would essentially loose all of the
> > > correspondence for all of the tickets issues created over there.
> > > Typically what I, and every other Apache project I am aware of does, is
> > to
> > > first open a ticket in Jira, then just title your pull request commit
> > > message after the Jira ticket.
> > > This way we also have comprehensive release reports, assignees, road
> > maps,
> > > etc etc etc.
> > > I would like to suggest that we start using Jira in this manner as
> > recently
> > > I've not really seen any tickets go in there.
> > > What do you think about this?
> > > Lewis
> > >
> > >
> > > --
> > > *Lewis*
> >
> >
>
> --
> *Lewis*
>

Re: Using Jira for Issues

[Sunderland, Kellen]

Sounds good to me Lewis.

-Kellen



On 4/29/16, 4:13 AM, "Lewis John Mcgibbney"  wrote:

>Hi Folks,
>One of the things about our Jira instance, is that it is hosted by and at
>the ASF. Therefore all correspondence is always available to the ASF.
>If Github were ever to vanish, we would essentially loose all of the
>correspondence for all of the tickets issues created over there.
>Typically what I, and every other Apache project I am aware of does, is to
>first open a ticket in Jira, then just title your pull request commit
>message after the Jira ticket.
>This way we also have comprehensive release reports, assignees, road maps,
>etc etc etc.
>I would like to suggest that we start using Jira in this manner as recently
>I've not really seen any tickets go in there.
>What do you think about this?
>Lewis
>
>
>-- 
>*Lewis*
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B