Update Microsoft.AspNet.WebApi Nuget package from 5.2.2 to 5.2.3 on ByodService

[Steven Borg (StevenBorg)]

This allows for successful build on Visual Studio 2015.

Also resolves Issue #17

[Steven Borg (StevenBorg)]

Just seeing if this Repo is dead. Not seeing any changes to it, or contributions. I've noticed a large move away from Azure ML to other Azure data tools. Wanted to see if this is something people are still working on, or not.

[smcinerney]

Hi Steven,

My understanding is this would be for Data Science APIs, contributions incl. recipes.
i.e. people like me, in future. (Gopi, if you're reading that please confirm if this is correct?)
But yeah, the operational volume will be v. low compared to other repos.

Regards,
Stephen

Date: Mon, 14 Mar 2016 16:14:29 -0700
From: notifications@github.com
To: Azure-MachineLearning-DataScience@noreply.github.com
Subject: Re: [Azure-MachineLearning-DataScience] Update Microsoft.AspNet.WebApi Nuget package from 5.2.2 to 5.2.3 on ByodService (#18)

Just seeing if this Repo is dead. Not seeing any changes to it, or contributions. I've noticed a large move away from Azure ML to other Azure data tools. Wanted to see if this is something people are still working on, or not.

—
Reply to this email directly or view it on GitHub.

[zenlytix (gopitk)]

Yes. That is right Stephen and Steven. This repo is active and contains data science examples, APIs, demos. Volume of contributions / commits has been a little low of late though and a few examples go beyond Azure machine learning. What suggestions do you have for new content on this repo?

[smcinerney]

I don't really have strong opinions on which repo(s) we use.
If there is a case here for a separate repo so we can potentially give commit privilege
to a different of people, possibly MSFT partners?
Otherwise maybe there's a case for folding the less-used repo into the more-common one.

Stephen

Date: Tue, 15 Mar 2016 13:41:01 -0700
From: notifications@github.com
To: Azure-MachineLearning-DataScience@noreply.github.com
CC: spmcinerney@hotmail.com
Subject: Re: [Azure-MachineLearning-DataScience] Update Microsoft.AspNet.WebApi Nuget package from 5.2.2 to 5.2.3 on ByodService (#18)

Yes. That is right Stephen and Steven. This repo is active and contains data science examples, APIs, demos. Volume of contributions / commits has been a little low of late though and a few examples go beyond Azure machine learning. What suggestions do you have for new content on this repo?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

[Steven Borg (StevenBorg)]

Hmm… I don’t mind my pull request not being accepted, but there should be a reason.

If you’re building a place to share Microsoft code, then maybe consider using a different location, or being clearer. But other teams are engaging with the community, accepting pull requests (especially trivial ones) and bringing partners in. I don’t need commit rights, but don’t leave contributors out in the cold for too long. It’s been three months since the last update, and my pull request has sat there that long.

Feel free to deny it, or otherwise act on it. But ignoring it has caused me to stop contributing to the Microsoft repos in general. I don’t want to take the time and effort to help improve other people’s overall experience with the product if I can’t actually get something through. :-)

:-)
Steve

From: Gopi Kumar [mailto:notifications@github.com]
Sent: Tuesday, March 15, 2016 1:41 PM
To: Azure/Azure-MachineLearning-DataScience Azure-MachineLearning-DataScience@noreply.github.com
Cc: Steven Borg steven.borg@nwcadence.com
Subject: Re: [Azure-MachineLearning-DataScience] Update Microsoft.AspNet.WebApi Nuget package from 5.2.2 to 5.2.3 on ByodService (#18)

Yes. That is right Stephen and Steven. This repo is active and contains data science examples, APIs, demos. Volume of contributions / commits has been a little low of late though and a few examples go beyond Azure machine learning. What suggestions do you have for new content on this repo?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-197011310