Re: Github Issues

[Rohit Yadav]

Using Github issues is already a standard now, for reference this was the 
voting thread:

https://markmail.org/message/y5zgkssmwp4sh43t


I agree that Github milestone tagging on a pull request is limited to one per 
PR which I don't like as well. However, there is a workaround that may be used. 
A PR can be part of multiple projects that can have lists of 'todo', 'in 
progress', 'done' etc. I had experimented with them here: 
https://github.com/apache/cloudstack/projects


We can experiment if milestone can be used to map a PR towards a release 
(useful for RM-ing) and use Github projects towards tagging/mapping a PR 
towards multiple releases? The other way in-addition we can explore could be to 
use Github labels?


- Rohit

<https://cloudstack.apache.org>




From: Paul Angus 
Sent: Tuesday, July 17, 2018 2:23:10 PM
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Github Issues

Hi All,

We have been trialling replacing Jira with Github Issues.   I think that we 
should have a conversation about it before it become the new standard by 
default.

From my perspective, I don't like it.  Searching has become far more difficult, 
categorising has also. When there is a bug fix it can only be targeted for a 
single version, which makes them easy to lose track of, and when looking at 
milestones issues and PRs get jumbled up and people are commenting on issues 
when it should by the PR and vice-versa (yes I've done it too).
In summary, from an administrative point of view it causes a lot more problems 
than it solves.

I yield the floor to hear other people's opinions...


Kind regards,

Paul Angus


paul.an...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Github Issues

[Dingane Hlaluku]

+1 as a new developer for this community, I find Github much easier for me to 
create/track both issues and PRs.




From: Will Stevens 
Sent: Thursday, July 19, 2018 3:35:00 AM
To: dev@cloudstack.apache.org
Cc: users
Subject: Re: Github Issues

Github is the platform that is most comfortable for most users and
developers to collaborate.  Everyone knows it, regardless of their
background, so it opens our community to a wider group of people. Those are
my thoughts anyway...

Will

On Wed, Jul 18, 2018, 2:10 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> There is something else that might be worth mentioning.  Since we moved to
> Github, it seems that the project is attracting more people. I mean, it
> seems that there are new players coming and reporting issues and opening
> PRs.
>
> I might be totally mistaken though.
>
>
> On Wed, Jul 18, 2018 at 3:07 PM, Will Stevens 
> wrote:
>
> > +1 to access to better automation and integration.
> >
> > On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:
> >
> > > Hi
> > >
> > > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > > > Hi Paul,
> > > >
> > > > My 2 cents on the topic.
> > > >
> > > > people are commenting on issues when it should by the PR and
> vice-versa
> > > >>
> > > >
> > > > I think this is simply due to the fact that with one login you can do
> > > both,
> > > > versus before you had to have a JIRA login which people might have
> > tried
> > > to
> > > > avoid, preferring using github directly, ensuring the conversation
> will
> > > > only be on the PR. Most of the issues in Jira didn't have any
> > > conversation
> > > > at all.
> > > >
> > > > But I do feel also the pain of searching the issues on github as it's
> > > more
> > > > free-hand than a jira system. At the same time it's easier and
> quicker
> > to
> > > > navigate, so it ease the pain at the same time ;-)
> > > > I would say that the current labels isn't well organized to be able
> to
> > > > search like in jira but it could. For example any label has a prefix
> > > > describing the jira attribute type (component, version, ...) Then a
> bot
> > > > scanning the issue content could set some of them as other open
> source
> > > > project are doing. The bad thing here is that you might end up with
> too
> > > > many labels. Maybe @resmo can give his point of view on how things
> are
> > > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots
> of
> > > > labels, lots of issues and PRs). I don't know if that's a solution
> but
> > > > labels seem the only way to organize things.
> > >
> > > Personally, I don't care much if jira or github issues. Github issues
> > > worked pretty well for me so far.
> > >
> > > However, We don't use all the things that make the work easier with
> > > github issues. I assume we invested much more efforts in making "jira"
> > > the way we wanted, now we assume that github just works?
> > >
> > > The benefit about github issues is, that it has an extensive api which
> > > let you automate. There are many helpful tools making our life easier.
> > >
> > > Let a bot do the issue labeling, workflowing, and user guiding and even
> > > merging PR after ci passed when 2 comments have LGTM.
> > >
> > > Look at https://github.com/kubernetes/kubernetes e.g.
> > >
> > > Short: If we want to automate things and evolve, github may be the
> > > better platform, if we want to keep things manual, then jira is
> probably
> > > more suitable.
> > >
> > > Regards
> > > René
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

dingane.hlal...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

Re: Github Issues

[Will Stevens]

Github is the platform that is most comfortable for most users and
developers to collaborate.  Everyone knows it, regardless of their
background, so it opens our community to a wider group of people. Those are
my thoughts anyway...

Will

On Wed, Jul 18, 2018, 2:10 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> There is something else that might be worth mentioning.  Since we moved to
> Github, it seems that the project is attracting more people. I mean, it
> seems that there are new players coming and reporting issues and opening
> PRs.
>
> I might be totally mistaken though.
>
>
> On Wed, Jul 18, 2018 at 3:07 PM, Will Stevens 
> wrote:
>
> > +1 to access to better automation and integration.
> >
> > On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:
> >
> > > Hi
> > >
> > > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > > > Hi Paul,
> > > >
> > > > My 2 cents on the topic.
> > > >
> > > > people are commenting on issues when it should by the PR and
> vice-versa
> > > >>
> > > >
> > > > I think this is simply due to the fact that with one login you can do
> > > both,
> > > > versus before you had to have a JIRA login which people might have
> > tried
> > > to
> > > > avoid, preferring using github directly, ensuring the conversation
> will
> > > > only be on the PR. Most of the issues in Jira didn't have any
> > > conversation
> > > > at all.
> > > >
> > > > But I do feel also the pain of searching the issues on github as it's
> > > more
> > > > free-hand than a jira system. At the same time it's easier and
> quicker
> > to
> > > > navigate, so it ease the pain at the same time ;-)
> > > > I would say that the current labels isn't well organized to be able
> to
> > > > search like in jira but it could. For example any label has a prefix
> > > > describing the jira attribute type (component, version, ...) Then a
> bot
> > > > scanning the issue content could set some of them as other open
> source
> > > > project are doing. The bad thing here is that you might end up with
> too
> > > > many labels. Maybe @resmo can give his point of view on how things
> are
> > > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots
> of
> > > > labels, lots of issues and PRs). I don't know if that's a solution
> but
> > > > labels seem the only way to organize things.
> > >
> > > Personally, I don't care much if jira or github issues. Github issues
> > > worked pretty well for me so far.
> > >
> > > However, We don't use all the things that make the work easier with
> > > github issues. I assume we invested much more efforts in making "jira"
> > > the way we wanted, now we assume that github just works?
> > >
> > > The benefit about github issues is, that it has an extensive api which
> > > let you automate. There are many helpful tools making our life easier.
> > >
> > > Let a bot do the issue labeling, workflowing, and user guiding and even
> > > merging PR after ci passed when 2 comments have LGTM.
> > >
> > > Look at https://github.com/kubernetes/kubernetes e.g.
> > >
> > > Short: If we want to automate things and evolve, github may be the
> > > better platform, if we want to keep things manual, then jira is
> probably
> > > more suitable.
> > >
> > > Regards
> > > René
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Github Issues

[Rafael Weingärtner]

There is something else that might be worth mentioning.  Since we moved to
Github, it seems that the project is attracting more people. I mean, it
seems that there are new players coming and reporting issues and opening
PRs.

I might be totally mistaken though.


On Wed, Jul 18, 2018 at 3:07 PM, Will Stevens  wrote:

> +1 to access to better automation and integration.
>
> On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:
>
> > Hi
> >
> > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > > Hi Paul,
> > >
> > > My 2 cents on the topic.
> > >
> > > people are commenting on issues when it should by the PR and vice-versa
> > >>
> > >
> > > I think this is simply due to the fact that with one login you can do
> > both,
> > > versus before you had to have a JIRA login which people might have
> tried
> > to
> > > avoid, preferring using github directly, ensuring the conversation will
> > > only be on the PR. Most of the issues in Jira didn't have any
> > conversation
> > > at all.
> > >
> > > But I do feel also the pain of searching the issues on github as it's
> > more
> > > free-hand than a jira system. At the same time it's easier and quicker
> to
> > > navigate, so it ease the pain at the same time ;-)
> > > I would say that the current labels isn't well organized to be able to
> > > search like in jira but it could. For example any label has a prefix
> > > describing the jira attribute type (component, version, ...) Then a bot
> > > scanning the issue content could set some of them as other open source
> > > project are doing. The bad thing here is that you might end up with too
> > > many labels. Maybe @resmo can give his point of view on how things are
> > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> > > labels, lots of issues and PRs). I don't know if that's a solution but
> > > labels seem the only way to organize things.
> >
> > Personally, I don't care much if jira or github issues. Github issues
> > worked pretty well for me so far.
> >
> > However, We don't use all the things that make the work easier with
> > github issues. I assume we invested much more efforts in making "jira"
> > the way we wanted, now we assume that github just works?
> >
> > The benefit about github issues is, that it has an extensive api which
> > let you automate. There are many helpful tools making our life easier.
> >
> > Let a bot do the issue labeling, workflowing, and user guiding and even
> > merging PR after ci passed when 2 comments have LGTM.
> >
> > Look at https://github.com/kubernetes/kubernetes e.g.
> >
> > Short: If we want to automate things and evolve, github may be the
> > better platform, if we want to keep things manual, then jira is probably
> > more suitable.
> >
> > Regards
> > René
> >
> >
> >
> >
> >
> >
>



-- 
Rafael Weingärtner

Re: Github Issues

[Will Stevens]

+1 to access to better automation and integration.

On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:

> Hi
>
> On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > Hi Paul,
> >
> > My 2 cents on the topic.
> >
> > people are commenting on issues when it should by the PR and vice-versa
> >>
> >
> > I think this is simply due to the fact that with one login you can do
> both,
> > versus before you had to have a JIRA login which people might have tried
> to
> > avoid, preferring using github directly, ensuring the conversation will
> > only be on the PR. Most of the issues in Jira didn't have any
> conversation
> > at all.
> >
> > But I do feel also the pain of searching the issues on github as it's
> more
> > free-hand than a jira system. At the same time it's easier and quicker to
> > navigate, so it ease the pain at the same time ;-)
> > I would say that the current labels isn't well organized to be able to
> > search like in jira but it could. For example any label has a prefix
> > describing the jira attribute type (component, version, ...) Then a bot
> > scanning the issue content could set some of them as other open source
> > project are doing. The bad thing here is that you might end up with too
> > many labels. Maybe @resmo can give his point of view on how things are
> > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> > labels, lots of issues and PRs). I don't know if that's a solution but
> > labels seem the only way to organize things.
>
> Personally, I don't care much if jira or github issues. Github issues
> worked pretty well for me so far.
>
> However, We don't use all the things that make the work easier with
> github issues. I assume we invested much more efforts in making "jira"
> the way we wanted, now we assume that github just works?
>
> The benefit about github issues is, that it has an extensive api which
> let you automate. There are many helpful tools making our life easier.
>
> Let a bot do the issue labeling, workflowing, and user guiding and even
> merging PR after ci passed when 2 comments have LGTM.
>
> Look at https://github.com/kubernetes/kubernetes e.g.
>
> Short: If we want to automate things and evolve, github may be the
> better platform, if we want to keep things manual, then jira is probably
> more suitable.
>
> Regards
> René
>
>
>
>
>
>

Re: Github Issues

[Rene Moser]

Hi

On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> Hi Paul,
> 
> My 2 cents on the topic.
> 
> people are commenting on issues when it should by the PR and vice-versa
>>
> 
> I think this is simply due to the fact that with one login you can do both,
> versus before you had to have a JIRA login which people might have tried to
> avoid, preferring using github directly, ensuring the conversation will
> only be on the PR. Most of the issues in Jira didn't have any conversation
> at all.
> 
> But I do feel also the pain of searching the issues on github as it's more
> free-hand than a jira system. At the same time it's easier and quicker to
> navigate, so it ease the pain at the same time ;-)
> I would say that the current labels isn't well organized to be able to
> search like in jira but it could. For example any label has a prefix
> describing the jira attribute type (component, version, ...) Then a bot
> scanning the issue content could set some of them as other open source
> project are doing. The bad thing here is that you might end up with too
> many labels. Maybe @resmo can give his point of view on how things are
> managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> labels, lots of issues and PRs). I don't know if that's a solution but
> labels seem the only way to organize things.

Personally, I don't care much if jira or github issues. Github issues
worked pretty well for me so far.

However, We don't use all the things that make the work easier with
github issues. I assume we invested much more efforts in making "jira"
the way we wanted, now we assume that github just works?

The benefit about github issues is, that it has an extensive api which
let you automate. There are many helpful tools making our life easier.

Let a bot do the issue labeling, workflowing, and user guiding and even
merging PR after ci passed when 2 comments have LGTM.

Look at https://github.com/kubernetes/kubernetes e.g.

Short: If we want to automate things and evolve, github may be the
better platform, if we want to keep things manual, then jira is probably
more suitable.

Regards
René

Re: Github Issues

[Khosrow Moossavi]

I sort of agree with Marc-Aurèle and Will, and like github issues way
better than Jira.

It definitely is easier that both the issues and fix for those issues live
in the same place
and easily can be referenced from one another. The only thing is that we
need to come
up with good set of labels (for both issues and PRs) for tracking purpose.

Discussing the issue at hand under the issue itself can be even good, it
will leave a
trail of what has been discussed around the issue which led to the fix and
potentially
discussion can be continued under PR itself. Essentially they are targeting
the same
"problem".

As for the point Ron brought up, if one issue was that big that required
multiple PR for
it to be fixed, it only makes sens to me to create subset of issues all
referencing the
"parent" issue, and each individual PR fixes one of those smaller issue.

Khosrow


On Tue, Jul 17, 2018 at 11:08 AM Will Stevens  wrote:

> Ron, keep in mind that PRs on Github are different from Issues.  They are
> two different features.
>
> There will be a much cleaner, tighter integration between issues and the
> solution when everything is on Github.
>
> will
>
> On Tue, Jul 17, 2018, 9:33 AM Ron Wheeler 
> wrote:
>
> > I may have voiced my concerns earlier but as a user, I think that JIRA
> > issues are easier to follow than PRs.
> > - As Paul said an issue may affect more than one version.
> > - It may also require more than one PR to fully resolve the issue.
> > - Issues tend to be described in terms of a problem that the user would
> > recognize while PRs are most often described as what was done to fix the
> > problem. The JIRA could be much easier to relate to what the user is
> > seeing and more likely to show up in Google.
> >
> > Ron
> > On 17/07/2018 4:53 AM, Paul Angus wrote:
> > > Hi All,
> > >
> > > We have been trialling replacing Jira with Github Issues.   I think
> that
> > we should have a conversation about it before it become the new standard
> by
> > default.
> > >
> > >  From my perspective, I don't like it.  Searching has become far more
> > difficult, categorising has also. When there is a bug fix it can only be
> > targeted for a single version, which makes them easy to lose track of,
> and
> > when looking at milestones issues and PRs get jumbled up and people are
> > commenting on issues when it should by the PR and vice-versa (yes I've
> done
> > it too).
> > > In summary, from an administrative point of view it causes a lot more
> > problems than it solves.
> > >
> > > I yield the floor to hear other people's opinions...
> > >
> > >
> > > Kind regards,
> > >
> > > Paul Angus
> > >
> > >
> > > paul.an...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > Ron Wheeler
> > President
> > Artifact Software Inc
> > email: rwhee...@artifact-software.com
> > skype: ronaldmwheeler
> > phone: 866-970-2435, ext 102
> >
> >
>

Re: Github Issues

[Will Stevens]

Ron, keep in mind that PRs on Github are different from Issues.  They are
two different features.

There will be a much cleaner, tighter integration between issues and the
solution when everything is on Github.

will

On Tue, Jul 17, 2018, 9:33 AM Ron Wheeler 
wrote:

> I may have voiced my concerns earlier but as a user, I think that JIRA
> issues are easier to follow than PRs.
> - As Paul said an issue may affect more than one version.
> - It may also require more than one PR to fully resolve the issue.
> - Issues tend to be described in terms of a problem that the user would
> recognize while PRs are most often described as what was done to fix the
> problem. The JIRA could be much easier to relate to what the user is
> seeing and more likely to show up in Google.
>
> Ron
> On 17/07/2018 4:53 AM, Paul Angus wrote:
> > Hi All,
> >
> > We have been trialling replacing Jira with Github Issues.   I think that
> we should have a conversation about it before it become the new standard by
> default.
> >
> >  From my perspective, I don't like it.  Searching has become far more
> difficult, categorising has also. When there is a bug fix it can only be
> targeted for a single version, which makes them easy to lose track of, and
> when looking at milestones issues and PRs get jumbled up and people are
> commenting on issues when it should by the PR and vice-versa (yes I've done
> it too).
> > In summary, from an administrative point of view it causes a lot more
> problems than it solves.
> >
> > I yield the floor to hear other people's opinions...
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>

Re: Github Issues

[Ron Wheeler]

I may have voiced my concerns earlier but as a user, I think that JIRA 
issues are easier to follow than PRs.

- As Paul said an issue may affect more than one version.
- It may also require more than one PR to fully resolve the issue.
- Issues tend to be described in terms of a problem that the user would 
recognize while PRs are most often described as what was done to fix the 
problem. The JIRA could be much easier to relate to what the user is 
seeing and more likely to show up in Google.


Ron
On 17/07/2018 4:53 AM, Paul Angus wrote:

Hi All,

We have been trialling replacing Jira with Github Issues.   I think that we 
should have a conversation about it before it become the new standard by 
default.

 From my perspective, I don't like it.  Searching has become far more 
difficult, categorising has also. When there is a bug fix it can only be 
targeted for a single version, which makes them easy to lose track of, and when 
looking at milestones issues and PRs get jumbled up and people are commenting 
on issues when it should by the PR and vice-versa (yes I've done it too).
In summary, from an administrative point of view it causes a lot more problems 
than it solves.

I yield the floor to hear other people's opinions...


Kind regards,

Paul Angus


paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
   
  



--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Re: Github Issues

[Marc-Aurèle Brothier]

Hi Paul,

My 2 cents on the topic.

people are commenting on issues when it should by the PR and vice-versa
>

I think this is simply due to the fact that with one login you can do both,
versus before you had to have a JIRA login which people might have tried to
avoid, preferring using github directly, ensuring the conversation will
only be on the PR. Most of the issues in Jira didn't have any conversation
at all.

But I do feel also the pain of searching the issues on github as it's more
free-hand than a jira system. At the same time it's easier and quicker to
navigate, so it ease the pain at the same time ;-)
I would say that the current labels isn't well organized to be able to
search like in jira but it could. For example any label has a prefix
describing the jira attribute type (component, version, ...) Then a bot
scanning the issue content could set some of them as other open source
project are doing. The bad thing here is that you might end up with too
many labels. Maybe @resmo can give his point of view on how things are
managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
labels, lots of issues and PRs). I don't know if that's a solution but
labels seem the only way to organize things.

Marc-Aurèle

On Tue, Jul 17, 2018 at 10:53 AM, Paul Angus 
wrote:

> Hi All,
>
> We have been trialling replacing Jira with Github Issues.   I think that
> we should have a conversation about it before it become the new standard by
> default.
>
> From my perspective, I don't like it.  Searching has become far more
> difficult, categorising has also. When there is a bug fix it can only be
> targeted for a single version, which makes them easy to lose track of, and
> when looking at milestones issues and PRs get jumbled up and people are
> commenting on issues when it should by the PR and vice-versa (yes I've done
> it too).
> In summary, from an administrative point of view it causes a lot more
> problems than it solves.
>
> I yield the floor to hear other people's opinions...
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Github Issues

[Paul Angus]

Hi All,

We have been trialling replacing Jira with Github Issues.   I think that we 
should have a conversation about it before it become the new standard by 
default.

From my perspective, I don't like it.  Searching has become far more difficult, 
categorising has also. When there is a bug fix it can only be targeted for a 
single version, which makes them easy to lose track of, and when looking at 
milestones issues and PRs get jumbled up and people are commenting on issues 
when it should by the PR and vice-versa (yes I've done it too).
In summary, from an administrative point of view it causes a lot more problems 
than it solves.

I yield the floor to hear other people's opinions...


Kind regards,

Paul Angus


paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Request to enable Github issues, wiki for apache/cloudstack* repos

[Daniel Pono Takamori]

Enabled for your repos: https://issues.apache.org/jira/browse/INFRA-16186

Cheers

On Mon, Apr 2, 2018 at 1:23 PM, Rohit Yadav  wrote:
> Ping infra?
>
> - Rohit
>
> On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav  wrote:
>>
>> All,
>>
>> Based on a vote [1] on Apache CloudStack MLs, I would like to request
>> infra to enable Github issue and wiki features for all cloudstack
>> repositories:
>>
>> https://github.com/apache?q=cloudstack+
>>
>> [1] https://markmail.org/message/y5zgkssmwp4sh43t
>>
>> Regards,
>> Rohit Yadav
>> PMC member and committer,
>> Apache CloudStack
>
>

Re: Request to enable Github issues, wiki for apache/cloudstack* repos

[Rohit Yadav]

Ping infra?

- Rohit

On Fri, Mar 30, 2018 at 1:51 PM, Rohit Yadav  wrote:

> All,
>
> Based on a vote [1] on Apache CloudStack MLs, I would like to request
> infra to enable Github issue and wiki features for all cloudstack
> repositories:
>
> https://github.com/apache?q=cloudstack+
>
> [1] https://markmail.org/message/y5zgkssmwp4sh43t
>
> Regards,
> Rohit Yadav
> PMC member and committer,
> Apache CloudStack
>

Re: [VOTE] Move to Github issues

[Rafael Weingärtner]

My bad, I just saw the e-mail to infra after replying to this one :(

Thanks for taking the lead on this matter.

On Fri, Mar 30, 2018 at 11:30 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
wrote:

> Rafael, yes I did see the other email to infra cc-ed to dev@. I've also
> reopened a ticket.
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> 
> From: Rafael Weingärtner <rafaelweingart...@gmail.com>
> Sent: Friday, March 30, 2018 4:53:57 PM
> To: dev
> Subject: Re: [VOTE] Move to Github issues
>
> Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already
> experiment using it.
>
> On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
> wrote:
>
> > Thanks all, after 5days the vote *passes* with all in favour of the
> > proposal.
> >
> > I'll request infra immediately to enable the Github features for us, and
> > update the website/docs over the next few days.
> >
> > After issues is available, users should use Github issues for logging
> > bugs/features etc. Developers who have submitted PRs without a jira id
> may
> > be accepted now provided their PRs have a milestone and qualify merge
> > guidelines (2 lgtms, test results etc).
> >
> > PS. Happy Easter!
> >
> > Regards.
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> >
> > 
> > From: Tutkowski, Mike <mike.tutkow...@netapp.com>
> > Sent: Thursday, March 29, 2018 11:08:36 PM
> > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote:
> >
> > All,
> >
> > Based on the discussion last week [1], I would like to start a vote
> to
> > put
> > the proposal into effect:
> >
> > - Enable Github issues, wiki features in CloudStack repositories.
> > - Both user and developers can use Github issues for tracking issues.
> > - Developers can use #id references while fixing an existing/open
> > issue in
> > a PR [2]. PRs can be sent without requiring to open/create an issue.
> > - Use Github milestone to track both issues and pull requests
> towards a
> > CloudStack release, and generate release notes.
> > - Relax requirement for JIRA IDs, JIRA still to be used for
> historical
> > reference and security issues. Use of JIRA will be discouraged.
> > - The current requirement of two(+) non-author LGTMs will continue
> for
> > PR
> > acceptance. The two(+) PR non-authors can advise resolution to any
> > issue
> > that we've not already discussed/agreed upon.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Vote will be open for 120 hours. If the vote passes the following
> > actions
> > will be taken:
> > - Get Github features enabled from ASF INFRA
> > - Update CONTRIBUTING.md and other relevant cwiki pages.
> > - Update project website
> >
> > [1] https://markmail.org/message/llodbwsmzgx5hod6
> > [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-
> > requests/
> >
> > Regards,
> > Rohit Yadav
> >
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
>
> --
> Rafael Weingärtner
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Rafael Weingärtner

Re: [VOTE] Move to Github issues

[Rohit Yadav]

Rafael, yes I did see the other email to infra cc-ed to dev@. I've also 
reopened a ticket.

Get Outlook for Android<https://aka.ms/ghei36>


From: Rafael Weingärtner <rafaelweingart...@gmail.com>
Sent: Friday, March 30, 2018 4:53:57 PM
To: dev
Subject: Re: [VOTE] Move to Github issues

Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already
experiment using it.

On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
wrote:

> Thanks all, after 5days the vote *passes* with all in favour of the
> proposal.
>
> I'll request infra immediately to enable the Github features for us, and
> update the website/docs over the next few days.
>
> After issues is available, users should use Github issues for logging
> bugs/features etc. Developers who have submitted PRs without a jira id may
> be accepted now provided their PRs have a milestone and qualify merge
> guidelines (2 lgtms, test results etc).
>
> PS. Happy Easter!
>
> Regards.
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> 
> From: Tutkowski, Mike <mike.tutkow...@netapp.com>
> Sent: Thursday, March 29, 2018 11:08:36 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
>     Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-
> requests/
>
> Regards,
> Rohit Yadav
>
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


--
Rafael Weingärtner

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [VOTE] Move to Github issues

[Rafael Weingärtner]

Awesome Rohit.Can you also ask Infra to enable Wiki? Then, we could already
experiment using it.

On Fri, Mar 30, 2018 at 5:13 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
wrote:

> Thanks all, after 5days the vote *passes* with all in favour of the
> proposal.
>
> I'll request infra immediately to enable the Github features for us, and
> update the website/docs over the next few days.
>
> After issues is available, users should use Github issues for logging
> bugs/features etc. Developers who have submitted PRs without a jira id may
> be accepted now provided their PRs have a milestone and qualify merge
> guidelines (2 lgtms, test results etc).
>
> PS. Happy Easter!
>
> Regards.
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> 
> From: Tutkowski, Mike <mike.tutkow...@netapp.com>
> Sent: Thursday, March 29, 2018 11:08:36 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-
> requests/
>
> Regards,
> Rohit Yadav
>
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Rafael Weingärtner

Request to enable Github issues, wiki for apache/cloudstack* repos

[Rohit Yadav]

All,

Based on a vote [1] on Apache CloudStack MLs, I would like to request infra
to enable Github issue and wiki features for all cloudstack repositories:

https://github.com/apache?q=cloudstack+

[1] https://markmail.org/message/y5zgkssmwp4sh43t

Regards,
Rohit Yadav
PMC member and committer,
Apache CloudStack

Re: [VOTE] Move to Github issues

[Rohit Yadav]

Thanks all, after 5days the vote *passes* with all in favour of the proposal.

I'll request infra immediately to enable the Github features for us, and update 
the website/docs over the next few days.

After issues is available, users should use Github issues for logging 
bugs/features etc. Developers who have submitted PRs without a jira id may be 
accepted now provided their PRs have a milestone and qualify merge guidelines 
(2 lgtms, test results etc).

PS. Happy Easter!

Regards.

Get Outlook for Android<https://aka.ms/ghei36>


From: Tutkowski, Mike <mike.tutkow...@netapp.com>
Sent: Thursday, March 29, 2018 11:08:36 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Move to Github issues

+1

On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote:

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:

- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav



rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [VOTE] Move to Github issues

[Tutkowski, Mike]

+1

On 3/26/18, 12:33 AM, "Rohit Yadav" <ro...@apache.org> wrote:

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:
    
    - Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav

Re: [VOTE] Move to Github issues

[Parth Patel]

+1

On Mon, 26 Mar 2018 at 21:25 Glenn Wagner <glenn.wag...@shapeblue.com>
wrote:

> +1
>
> glenn.wag...@shapeblue.com
> www.shapeblue.com
> Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape
> Town  7129South Africa
> @shapeblue
>
>
>
>
> -Original Message-
> From: David Mabry <dma...@ena.com.INVALID>
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users <us...@cloudstack.apache.org>
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 8:05 AM, "Will Stevens" <wstev...@cloudops.com> wrote:
>
> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > +1
> >
> > 
> > From: Dag Sonstebo <dag.sonst...@shapeblue.com>
>     > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
> >
> > All,
> >
> > Based on the discussion last week [1], I would like to start a
> vote to
> > put
> > the proposal into effect:
> >
> > - Enable Github issues, wiki features in CloudStack repositories.
> > - Both user and developers can use Github issues for tracking
> issues.
> > - Developers can use #id references while fixing an existing/open
> > issue in
> > a PR [2]. PRs can be sent without requiring to open/create an
> issue.
> > - Use Github milestone to track both issues and pull requests
> towards a
> > CloudStack release, and generate release notes.
> > - Relax requirement for JIRA IDs, JIRA still to be used for
> historical
> > reference and security issues. Use of JIRA will be discouraged.
> > - The current requirement of two(+) non-author LGTMs will
> continue for
> > PR
> > acceptance. The two(+) PR non-authors can advise resolution to
> any
> > issue
> > that we've not already discussed/agreed upon.
> >
> > For sanity in tallying the vote, can PMC members please be sure
> to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Vote will be open for 120 hours. If the vote passes the following
> > actions
> > will be taken:
> > - Get Github features enabled from ASF INFRA
> > - Update CONTRIBUTING.md and other relevant cwik
> <https://maps.google.com/?q=pdate+CONTRIBUTING.md+and+other+relevant+cwik=gmail=g>i
> pages.
> > - Update project website
> >
> > [1] https://markmail.org/message/llodbwsmzgx5hod6
> > [2]
> > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> >
> > Regards,
> > Rohit Yadav
> >
> >
> >
> > dag.sonst...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > nicolas.vazq...@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>
>
>

RE: [VOTE] Move to Github issues

[Glenn Wagner]

+1 

glenn.wag...@shapeblue.com 
www.shapeblue.com
Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town  
7129South Africa
@shapeblue
  
 


-Original Message-
From: David Mabry <dma...@ena.com.INVALID> 
Sent: Monday, 26 March 2018 4:51 PM
To: dev@cloudstack.apache.org
Cc: users <us...@cloudstack.apache.org>
Subject: Re: [VOTE] Move to Github issues

+1

On 3/26/18, 8:05 AM, "Will Stevens" <wstev...@cloudops.com> wrote:

+1

On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
nicolas.vazq...@shapeblue.com> wrote:

> +1
>
> 
> From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
    > - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards 
a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2]
> https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
>
> Regards,
> Rohit Yadav
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>

Re: [VOTE] Move to Github issues

[David Mabry]

+1

On 3/26/18, 8:05 AM, "Will Stevens" <wstev...@cloudops.com> wrote:

+1

On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
nicolas.vazq...@shapeblue.com> wrote:

> +1
>
> 
> From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
    > Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards 
a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2]
> https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
>
> Regards,
> Rohit Yadav
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>

Re: [VOTE] Move to Github issues

[Khosrow Moossavi]

+1


On Mon, Mar 26, 2018 at 9:05 AM, Will Stevens <wstev...@cloudops.com> wrote:

> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > +1
> >
> > 
> > From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
> >
> > All,
> >
> > Based on the discussion last week [1], I would like to start a vote
> to
> > put
> > the proposal into effect:
> >
> > - Enable Github issues, wiki features in CloudStack repositories.
> > - Both user and developers can use Github issues for tracking issues.
> > - Developers can use #id references while fixing an existing/open
> > issue in
> > a PR [2]. PRs can be sent without requiring to open/create an issue.
> > - Use Github milestone to track both issues and pull requests
> towards a
> > CloudStack release, and generate release notes.
> > - Relax requirement for JIRA IDs, JIRA still to be used for
> historical
> > reference and security issues. Use of JIRA will be discouraged.
> > - The current requirement of two(+) non-author LGTMs will continue
> for
> > PR
> > acceptance. The two(+) PR non-authors can advise resolution to any
> > issue
> > that we've not already discussed/agreed upon.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Vote will be open for 120 hours. If the vote passes the following
> > actions
> > will be taken:
> > - Get Github features enabled from ASF INFRA
> > - Update CONTRIBUTING.md and other relevant cwiki pages.
> > - Update project website
> >
> > [1] https://markmail.org/message/llodbwsmzgx5hod6
> > [2]
> > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> >
> > Regards,
> > Rohit Yadav
> >
> >
> >
> > dag.sonst...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > nicolas.vazq...@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>

Re: [VOTE] Move to Github issues

[Marc-Aurèle Brothier]

+1

On Mon, Mar 26, 2018 at 3:05 PM, Will Stevens <wstev...@cloudops.com> wrote:

> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > +1
> >
> > 
> > From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
> >
> > All,
> >
> > Based on the discussion last week [1], I would like to start a vote
> to
> > put
> > the proposal into effect:
> >
> > - Enable Github issues, wiki features in CloudStack repositories.
> > - Both user and developers can use Github issues for tracking issues.
> > - Developers can use #id references while fixing an existing/open
> > issue in
> > a PR [2]. PRs can be sent without requiring to open/create an issue.
> > - Use Github milestone to track both issues and pull requests
> towards a
> > CloudStack release, and generate release notes.
> > - Relax requirement for JIRA IDs, JIRA still to be used for
> historical
> > reference and security issues. Use of JIRA will be discouraged.
> > - The current requirement of two(+) non-author LGTMs will continue
> for
> > PR
> > acceptance. The two(+) PR non-authors can advise resolution to any
> > issue
> > that we've not already discussed/agreed upon.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Vote will be open for 120 hours. If the vote passes the following
> > actions
> > will be taken:
> > - Get Github features enabled from ASF INFRA
> > - Update CONTRIBUTING.md and other relevant cwiki pages.
> > - Update project website
> >
> > [1] https://markmail.org/message/llodbwsmzgx5hod6
> > [2]
> > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> >
> > Regards,
> > Rohit Yadav
> >
> >
> >
> > dag.sonst...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > nicolas.vazq...@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>

Re: [VOTE] Move to Github issues

[Simon Weller]

+1 (binding).



From: Rohit Yadav <ro...@apache.org>
Sent: Monday, March 26, 2018 1:33 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Move to Github issues

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:

- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav

Re: [VOTE] Move to Github issues

[Syed Ahmed]

+1
On Mon, Mar 26, 2018 at 6:05 AM Will Stevens <wstev...@cloudops.com> wrote:

> +1
>
> On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > +1
> >
> > 
> > From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> > Sent: Monday, March 26, 2018 5:06:29 AM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Move to Github issues
> >
> > +1
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
> >
> > All,
> >
> > Based on the discussion last week [1], I would like to start a vote
> to
> > put
> > the proposal into effect:
> >
> > - Enable Github issues, wiki features in CloudStack repositories.
> > - Both user and developers can use Github issues for tracking issues.
> > - Developers can use #id references while fixing an existing/open
> > issue in
> > a PR [2]. PRs can be sent without requiring to open/create an issue.
> > - Use Github milestone to track both issues and pull requests
> towards a
> > CloudStack release, and generate release notes.
> > - Relax requirement for JIRA IDs, JIRA still to be used for
> historical
> > reference and security issues. Use of JIRA will be discouraged.
> > - The current requirement of two(+) non-author LGTMs will continue
> for
> > PR
> > acceptance. The two(+) PR non-authors can advise resolution to any
> > issue
> > that we've not already discussed/agreed upon.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Vote will be open for 120 hours. If the vote passes the following
> > actions
> > will be taken:
> > - Get Github features enabled from ASF INFRA
> > - Update CONTRIBUTING.md and other relevant cwiki pages.
> > - Update project website
> >
> > [1] https://markmail.org/message/llodbwsmzgx5hod6
> > [2]
> > https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> >
> > Regards,
> > Rohit Yadav
> >
> >
> >
> > dag.sonst...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > nicolas.vazq...@shapeblue.com
> > www.shapeblue.com
> > ,
> > @shapeblue
> >
> >
> >
> >
>

Re: [VOTE] Move to Github issues

[Will Stevens]

+1

On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
nicolas.vazq...@shapeblue.com> wrote:

> +1
>
> 
> From: Dag Sonstebo <dag.sonst...@shapeblue.com>
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2]
> https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
>
> Regards,
> Rohit Yadav
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>

Re: [VOTE] Move to Github issues

[Nicolas Vazquez]

+1


From: Dag Sonstebo <dag.sonst...@shapeblue.com>
Sent: Monday, March 26, 2018 5:06:29 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Move to Github issues

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:

- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav



dag.sonst...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




nicolas.vazq...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

Re: [VOTE] Move to Github issues

[Rafael Weingärtner]

+1

On Mon, Mar 26, 2018 at 5:06 AM, Dag Sonstebo <dag.sonst...@shapeblue.com>
wrote:

> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-
> requests/
>
> Regards,
> Rohit Yadav
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Rafael Weingärtner

Re: [VOTE] Move to Github issues

[Dag Sonstebo]

+1 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 26/03/2018, 07:33, "Rohit Yadav" <ro...@apache.org> wrote:

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:
    
    - Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [VOTE] Move to Github issues

[Boris Stoyanov]

+1

> On 26 Mar 2018, at 10:21, Nux! <n...@li.nux.ro> wrote:
> 
> +1
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> 
boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

- Original Message -
>> From: "Rohit Yadav" <ro...@apache.org>
>> To: "dev" <dev@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
>> Sent: Monday, 26 March, 2018 07:33:08
>> Subject: [VOTE] Move to Github issues
> 
>> All,
>> 
>> Based on the discussion last week [1], I would like to start a vote to put
>> the proposal into effect:
>> 
>> - Enable Github issues, wiki features in CloudStack repositories.
>> - Both user and developers can use Github issues for tracking issues.
>> - Developers can use #id references while fixing an existing/open issue in
>> a PR [2]. PRs can be sent without requiring to open/create an issue.
>> - Use Github milestone to track both issues and pull requests towards a
>> CloudStack release, and generate release notes.
>> - Relax requirement for JIRA IDs, JIRA still to be used for historical
>> reference and security issues. Use of JIRA will be discouraged.
>> - The current requirement of two(+) non-author LGTMs will continue for PR
>> acceptance. The two(+) PR non-authors can advise resolution to any issue
>> that we've not already discussed/agreed upon.
>> 
>> For sanity in tallying the vote, can PMC members please be sure to indicate
>> "(binding)" with their vote?
>> 
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> Vote will be open for 120 hours. If the vote passes the following actions
>> will be taken:
>> - Get Github features enabled from ASF INFRA
>> - Update CONTRIBUTING.md and other relevant cwiki pages.
>> - Update project website
>> 
>> [1] https://markmail.org/message/llodbwsmzgx5hod6
>> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
>> 
>> Regards,
>> Rohit Yadav

Re: [VOTE] Move to Github issues

[Nux!]

+1

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" <ro...@apache.org>
> To: "dev" <dev@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> Sent: Monday, 26 March, 2018 07:33:08
> Subject: [VOTE] Move to Github issues

> All,
> 
> Based on the discussion last week [1], I would like to start a vote to put
> the proposal into effect:
> 
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for PR
> acceptance. The two(+) PR non-authors can advise resolution to any issue
> that we've not already discussed/agreed upon.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Vote will be open for 120 hours. If the vote passes the following actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
> 
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> 
> Regards,
> Rohit Yadav

Re: [VOTE] Move to Github issues

[Rene Moser]

+1

Re: [VOTE] Move to Github issues

[Wido den Hollander]

+1

On 03/26/2018 08:33 AM, Rohit Yadav wrote:
> All,
> 
> Based on the discussion last week [1], I would like to start a vote to put
> the proposal into effect:
> 
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for PR
> acceptance. The two(+) PR non-authors can advise resolution to any issue
> that we've not already discussed/agreed upon.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Vote will be open for 120 hours. If the vote passes the following actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
> 
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
> 
> Regards,
> Rohit Yadav
> 

[VOTE] Move to Github issues

[Rohit Yadav]

All,

Based on the discussion last week [1], I would like to start a vote to put
the proposal into effect:

- Enable Github issues, wiki features in CloudStack repositories.
- Both user and developers can use Github issues for tracking issues.
- Developers can use #id references while fixing an existing/open issue in
a PR [2]. PRs can be sent without requiring to open/create an issue.
- Use Github milestone to track both issues and pull requests towards a
CloudStack release, and generate release notes.
- Relax requirement for JIRA IDs, JIRA still to be used for historical
reference and security issues. Use of JIRA will be discouraged.
- The current requirement of two(+) non-author LGTMs will continue for PR
acceptance. The two(+) PR non-authors can advise resolution to any issue
that we've not already discussed/agreed upon.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Vote will be open for 120 hours. If the vote passes the following actions
will be taken:
- Get Github features enabled from ASF INFRA
- Update CONTRIBUTING.md and other relevant cwiki pages.
- Update project website

[1] https://markmail.org/message/llodbwsmzgx5hod6
[2] https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

Regards,
Rohit Yadav