Topics

[disscuss] github issue standardization

vinoyang
 

Hi guys:

I make a suggestion : shall we standardize the github issue's title and detail?

Some point : 

  • one PR one issue
  • mark some key info in issue title with tag, such as `[core] [task] xxxx` , `[support] [improvement] xxx` and so on... to let users see more valuable information without looking details
  • how to split a big task into some sub taks, it's useful for interacting or cooperating with others and reviewing PR.
  • the commit message contains the issue id , like this pattern '#123 xxxx' , if contributor sends this PR the commit will be linked to the issue with id 123
  • mark issue with labels
  • ...
just some opinion, if some rules be wrote into contribution guidance document, it looks good to the edgex community.

Actually, I really think the JIRA is a better choice.

Vino yang.
Thanks

vinoyang
 

Hi guys:

Anyone has more suggestions to continue this topic? How about using JIRA to manage the Edgex Project?

Vino yang
Thanks.

2018-03-16 10:15 GMT+08:00 vino yang <yanghua1127@...>:

Hi guys:

I make a suggestion : shall we standardize the github issue's title and detail?

Some point : 

  • one PR one issue
  • mark some key info in issue title with tag, such as `[core] [task] xxxx` , `[support] [improvement] xxx` and so on... to let users see more valuable information without looking details
  • how to split a big task into some sub taks, it's useful for interacting or cooperating with others and reviewing PR.
  • the commit message contains the issue id , like this pattern '#123 xxxx' , if contributor sends this PR the commit will be linked to the issue with id 123
  • mark issue with labels
  • ...
just some opinion, if some rules be wrote into contribution guidance document, it looks good to the edgex community.

Actually, I really think the JIRA is a better choice.

Vino yang.
Thanks

James.White2@...
 

Dell - Internal Use - Confidential

Hi Vino,

While I understand your sentiment, Jira would be an added expense to the project and given the number of potential users in the community, could be a rather hefty expense.  So at this time, the community is choosing to use tools more in line with project budgets.

Jim

 

From: edgex-golang-bounces@... [mailto:edgex-golang-bounces@...] On Behalf Of vino yang
Sent: Friday, March 23, 2018 12:02 AM
To: edgex-golang@...
Subject: Re: [Edgex-golang] [disscuss] github issue standardization

 

Hi guys:

 

Anyone has more suggestions to continue this topic? How about using JIRA to manage the Edgex Project?

 

Vino yang

Thanks.

 

2018-03-16 10:15 GMT+08:00 vino yang <yanghua1127@...>:

Hi guys:

 

I make a suggestion : shall we standardize the github issue's title and detail?

 

Some point : 

 

  • one PR one issue
  • mark some key info in issue title with tag, such as `[core] [task] xxxx` , `[support] [improvement] xxx` and so on... to let users see more valuable information without looking details
  • how to split a big task into some sub taks, it's useful for interacting or cooperating with others and reviewing PR.
  • the commit message contains the issue id , like this pattern '#123 xxxx' , if contributor sends this PR the commit will be linked to the issue with id 123
  • mark issue with labels
  • ...

just some opinion, if some rules be wrote into contribution guidance document, it looks good to the edgex community.

 

Actually, I really think the JIRA is a better choice.

 

Vino yang.

Thanks