You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Robert Kowalski <ro...@kowalski.gd> on 2014/11/02 19:52:31 UTC
[DISCUSS] Fauxton: remove advice in docs to create a Jira ticket for
every PR
I just stumbled over a sentence in Fauxton's contributing.md (
https://github.com/apache/couchdb-fauxton/blob/master/CONTRIBUTING.md)
which made me curious:
(instructions to create a branch with the ticket-id in front of it):
followed by a: "If there is no Jira ticket for the issue you have, please
create one."
I would like to remove that sentence for several reasons:
- Summed up over a year it takes a lot of time to find each extra for a PR
created Jira ticket and close it, often people forget to close the ticket
after the PR is merged (or do not have the karma for it?).
- Another reason for removing this rule is that we do not act to this rule
in the project - the theory differs a lot from the practical day-to-day
business we are living.
- It also raises the entry barrier for folks which just want to fix a small
bug they found, but have to register an account on Jira first, then verify
their email, find out how to create a bug on Jira and then write it and
just after that are able to submit a patch for a bug which is probably my
main reason I would like to remove this advice.
I opened a PR on https://github.com/apache/couchdb-fauxton/pull/125 which
will be open until next week wednesday. There is no need to reply if you
are happy with this change.
Best,
Robert
Re: [DISCUSS] Fauxton: remove advice in docs to create a Jira ticket
for every PR
Posted by Noah Slater <ns...@apache.org>.
+1
On 2 November 2014 19:52, Robert Kowalski <ro...@kowalski.gd> wrote:
> I just stumbled over a sentence in Fauxton's contributing.md (
> https://github.com/apache/couchdb-fauxton/blob/master/CONTRIBUTING.md)
> which made me curious:
>
> (instructions to create a branch with the ticket-id in front of it):
>
> followed by a: "If there is no Jira ticket for the issue you have, please
> create one."
>
> I would like to remove that sentence for several reasons:
>
> - Summed up over a year it takes a lot of time to find each extra for a PR
> created Jira ticket and close it, often people forget to close the ticket
> after the PR is merged (or do not have the karma for it?).
>
> - Another reason for removing this rule is that we do not act to this rule
> in the project - the theory differs a lot from the practical day-to-day
> business we are living.
>
> - It also raises the entry barrier for folks which just want to fix a small
> bug they found, but have to register an account on Jira first, then verify
> their email, find out how to create a bug on Jira and then write it and
> just after that are able to submit a patch for a bug which is probably my
> main reason I would like to remove this advice.
>
> I opened a PR on https://github.com/apache/couchdb-fauxton/pull/125 which
> will be open until next week wednesday. There is no need to reply if you
> are happy with this change.
>
> Best,
>
> Robert
--
Noah Slater
https://twitter.com/nslater
Re: [DISCUSS] Fauxton: remove advice in docs to create a Jira ticket
for every PR
Posted by Andy Wenk <an...@apache.org>.
+1
On 3 November 2014 11:51, Klaus Trainer <kl...@posteo.de> wrote:
> +1
>
> Great suggestion.
>
>
> On 02.11.2014 19:52, Robert Kowalski wrote:
> > I just stumbled over a sentence in Fauxton's contributing.md (
> > https://github.com/apache/couchdb-fauxton/blob/master/CONTRIBUTING.md)
> > which made me curious:
> >
> > (instructions to create a branch with the ticket-id in front of it):
> >
> > followed by a: "If there is no Jira ticket for the issue you have, please
> > create one."
> >
> > I would like to remove that sentence for several reasons:
> >
> > - Summed up over a year it takes a lot of time to find each extra for a
> PR
> > created Jira ticket and close it, often people forget to close the ticket
> > after the PR is merged (or do not have the karma for it?).
> >
> > - Another reason for removing this rule is that we do not act to this
> rule
> > in the project - the theory differs a lot from the practical day-to-day
> > business we are living.
> >
> > - It also raises the entry barrier for folks which just want to fix a
> small
> > bug they found, but have to register an account on Jira first, then
> verify
> > their email, find out how to create a bug on Jira and then write it and
> > just after that are able to submit a patch for a bug which is probably my
> > main reason I would like to remove this advice.
> >
> > I opened a PR on https://github.com/apache/couchdb-fauxton/pull/125
> which
> > will be open until next week wednesday. There is no need to reply if you
> > are happy with this change.
> >
> > Best,
> >
> > Robert
> >
>
>
--
Andy Wenk
Hamburg - Germany
RockIt!
GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
https://people.apache.org/keys/committer/andywenk.asc
Re: [DISCUSS] Fauxton: remove advice in docs to create a Jira ticket
for every PR
Posted by Klaus Trainer <kl...@posteo.de>.
+1
Great suggestion.
On 02.11.2014 19:52, Robert Kowalski wrote:
> I just stumbled over a sentence in Fauxton's contributing.md (
> https://github.com/apache/couchdb-fauxton/blob/master/CONTRIBUTING.md)
> which made me curious:
>
> (instructions to create a branch with the ticket-id in front of it):
>
> followed by a: "If there is no Jira ticket for the issue you have, please
> create one."
>
> I would like to remove that sentence for several reasons:
>
> - Summed up over a year it takes a lot of time to find each extra for a PR
> created Jira ticket and close it, often people forget to close the ticket
> after the PR is merged (or do not have the karma for it?).
>
> - Another reason for removing this rule is that we do not act to this rule
> in the project - the theory differs a lot from the practical day-to-day
> business we are living.
>
> - It also raises the entry barrier for folks which just want to fix a small
> bug they found, but have to register an account on Jira first, then verify
> their email, find out how to create a bug on Jira and then write it and
> just after that are able to submit a patch for a bug which is probably my
> main reason I would like to remove this advice.
>
> I opened a PR on https://github.com/apache/couchdb-fauxton/pull/125 which
> will be open until next week wednesday. There is no need to reply if you
> are happy with this change.
>
> Best,
>
> Robert
>
Re: [DISCUSS] Fauxton: remove advice in docs to create a Jira ticket for every PR
Posted by Jan Lehnardt <ja...@apache.org>.
+1
> On 02 Nov 2014, at 19:52 , Robert Kowalski <ro...@kowalski.gd> wrote:
>
> I just stumbled over a sentence in Fauxton's contributing.md (
> https://github.com/apache/couchdb-fauxton/blob/master/CONTRIBUTING.md)
> which made me curious:
>
> (instructions to create a branch with the ticket-id in front of it):
>
> followed by a: "If there is no Jira ticket for the issue you have, please
> create one."
>
> I would like to remove that sentence for several reasons:
>
> - Summed up over a year it takes a lot of time to find each extra for a PR
> created Jira ticket and close it, often people forget to close the ticket
> after the PR is merged (or do not have the karma for it?).
>
> - Another reason for removing this rule is that we do not act to this rule
> in the project - the theory differs a lot from the practical day-to-day
> business we are living.
>
> - It also raises the entry barrier for folks which just want to fix a small
> bug they found, but have to register an account on Jira first, then verify
> their email, find out how to create a bug on Jira and then write it and
> just after that are able to submit a patch for a bug which is probably my
> main reason I would like to remove this advice.
>
> I opened a PR on https://github.com/apache/couchdb-fauxton/pull/125 which
> will be open until next week wednesday. There is no need to reply if you
> are happy with this change.
>
> Best,
>
> Robert