Re: Giving credit for contributions through Github Pull Requests

[Doug Cutting <cu...@gmail.com>]

Maybe we should loosen the permissions on Avro's Jira so that any user can
assign an issue?  That would make things a bit simpler.  I doubt we'd see
much if any abuse.

Also, it's probably time to remove CHANGES.txt and just use Jira to
generate release notes.  Agreed?

Doug

On Thu, Apr 26, 2018 at 11:51 AM Sean Busbey <bu...@cloudera.com> wrote:

> On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting <cu...@gmail.com> wrote:
>
> > So I guess this would be easier if we also said that contributions would
> > only now be accepted via pull request.  Is that too onerous?  Instead of
> > requiring everyone to have an Apache Jira account we require them to
> have a
> > GitHub account.
> >
> >
> I take it the github contributor summary doesn't work for emails that
> aren't associated with a github id?
>
> What about jumping on the Apache Kibble train? They're trying to make
> similar "project observability" widgets as what github provides.
>
>
>
> > Moving issue tracking to GitHub seems unlikely, as it's lacking a lot of
> > features we depend on from Jira.
> >
> >
> I don't like the idea of moving from JIRA to GitHub issues, but I think GHI
> has all the features we'd need to do so, FYI. Or atleast, I can't think of
> any we use that don't have a mapping to something.
>
>
> --
> busbey
>

Re: Giving credit for contributions through Github Pull Requests

[Sean Busbey <bu...@cloudera.com>]

On Thu, May 3, 2018 at 4:18 PM, Doug Cutting <cu...@gmail.com> wrote:

> Maybe we should loosen the permissions on Avro's Jira so that any user can
> assign an issue?  That would make things a bit simpler.  I doubt we'd see
> much if any abuse.
>

locking down issue assigning happened ASF jira wide due to spammer abuse.
we could probably due with better documenting how folks gain the ability to
assign themselves issues.

I presume it's "email dev@avro and ask for the ability". At the very least
I've been granting it to anyone who asks.



>
> Also, it's probably time to remove CHANGES.txt and just use Jira to
> generate release notes.  Agreed?
>
>
Yeah that'd be great.  The Apache Yetus project makes a tool called Release
Doc Maker that will generate markdown for us.

http://yetus.apache.org/documentation/0.7.0/releasedocmaker/

It's  been working for the Hadoop project for ages. HBase has started
moving to it and it's gone well.

-- 
busbey

Re: Giving credit for contributions through Github Pull Requests

[Gabor Szadovszky <ga...@apache.org>]

+1 for both

On Fri, May 4, 2018 at 9:54 AM, Nandor Kollar <nk...@cloudera.com> wrote:

> +1 for both, especially for removing CHANGES.txt.
>
> On Thu, May 3, 2018 at 11:18 PM, Doug Cutting <cu...@gmail.com> wrote:
>
> > Maybe we should loosen the permissions on Avro's Jira so that any user
> can
> > assign an issue?  That would make things a bit simpler.  I doubt we'd see
> > much if any abuse.
> >
> > Also, it's probably time to remove CHANGES.txt and just use Jira to
> > generate release notes.  Agreed?
> >
> > Doug
> >
> > On Thu, Apr 26, 2018 at 11:51 AM Sean Busbey <bu...@cloudera.com>
> wrote:
> >
> > > On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting <cu...@gmail.com>
> wrote:
> > >
> > > > So I guess this would be easier if we also said that contributions
> > would
> > > > only now be accepted via pull request.  Is that too onerous?  Instead
> > of
> > > > requiring everyone to have an Apache Jira account we require them to
> > > have a
> > > > GitHub account.
> > > >
> > > >
> > > I take it the github contributor summary doesn't work for emails that
> > > aren't associated with a github id?
> > >
> > > What about jumping on the Apache Kibble train? They're trying to make
> > > similar "project observability" widgets as what github provides.
> > >
> > >
> > >
> > > > Moving issue tracking to GitHub seems unlikely, as it's lacking a lot
> > of
> > > > features we depend on from Jira.
> > > >
> > > >
> > > I don't like the idea of moving from JIRA to GitHub issues, but I think
> > GHI
> > > has all the features we'd need to do so, FYI. Or atleast, I can't think
> > of
> > > any we use that don't have a mapping to something.
> > >
> > >
> > > --
> > > busbey
> > >
> >
>

Re: Giving credit for contributions through Github Pull Requests

[Nandor Kollar <nk...@cloudera.com>]

+1 for both, especially for removing CHANGES.txt.

On Thu, May 3, 2018 at 11:18 PM, Doug Cutting <cu...@gmail.com> wrote:

> Maybe we should loosen the permissions on Avro's Jira so that any user can
> assign an issue?  That would make things a bit simpler.  I doubt we'd see
> much if any abuse.
>
> Also, it's probably time to remove CHANGES.txt and just use Jira to
> generate release notes.  Agreed?
>
> Doug
>
> On Thu, Apr 26, 2018 at 11:51 AM Sean Busbey <bu...@cloudera.com> wrote:
>
> > On Thu, Apr 26, 2018 at 1:43 PM, Doug Cutting <cu...@gmail.com> wrote:
> >
> > > So I guess this would be easier if we also said that contributions
> would
> > > only now be accepted via pull request.  Is that too onerous?  Instead
> of
> > > requiring everyone to have an Apache Jira account we require them to
> > have a
> > > GitHub account.
> > >
> > >
> > I take it the github contributor summary doesn't work for emails that
> > aren't associated with a github id?
> >
> > What about jumping on the Apache Kibble train? They're trying to make
> > similar "project observability" widgets as what github provides.
> >
> >
> >
> > > Moving issue tracking to GitHub seems unlikely, as it's lacking a lot
> of
> > > features we depend on from Jira.
> > >
> > >
> > I don't like the idea of moving from JIRA to GitHub issues, but I think
> GHI
> > has all the features we'd need to do so, FYI. Or atleast, I can't think
> of
> > any we use that don't have a mapping to something.
> >
> >
> > --
> > busbey
> >
>