[Dev] POLL: Spatial4j list traffic

[dsmiley]

I'm soliciting the opinion of what this mailing list should receive outside of directly emailing the list:

* Travis CI build fail or recovery.  This happens now and I think it makes good sense.

* Commits:  This happens now and it generates a lot of email.  Is it desirable or too much?  If there was a way to only limit it to commits to the master branch then this would be good motivation for me to use feature-branches, but I'm not aware of that.  If it's just too much noise then I might even volunteer to email progress summaries from time to time.

* GitHub Issue emails:  This doesn't get sent to the list.  Arguably I think the messages there are even more worthwhile than the commits.

Opinions?

~ David

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com

[Chris Male]

Bring it all in.  We can filter as needed.

On Mon, Jan 27, 2014 at 10:02 AM, [hidden email] <[hidden email]> wrote:

I'm soliciting the opinion of what this mailing list should receive outside of directly emailing the list:

* Travis CI build fail or recovery.  This happens now and I think it makes good sense.

* Commits:  This happens now and it generates a lot of email.  Is it desirable or too much?  If there was a way to only limit it to commits to the master branch then this would be good motivation for me to use feature-branches, but I'm not aware of that.  If it's just too much noise then I might even volunteer to email progress summaries from time to time.

* GitHub Issue emails:  This doesn't get sent to the list.  Arguably I think the messages there are even more worthwhile than the commits.

Opinions?

~ David

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com

[dsmiley]

Ok, though ya know... if people want to see each commit and issue activity then couldn't they just "Watch" the project using GitHub's tools like we can do for any GitHub project?  And GH makes it easy to browse the activity even if you don't wan't to "Watch" it for immediate notification.

On Tue, Jan 28, 2014 at 5:36 PM, Chris Male <[hidden email]> wrote:

Bring it all in.  We can filter as needed.

On Mon, Jan 27, 2014 at 10:02 AM, [hidden email] <[hidden email]> wrote:

I'm soliciting the opinion of what this mailing list should receive outside of directly emailing the list:

* Travis CI build fail or recovery.  This happens now and I think it makes good sense.

* Commits:  This happens now and it generates a lot of email.  Is it desirable or too much?  If there was a way to only limit it to commits to the master branch then this would be good motivation for me to use feature-branches, but I'm not aware of that.  If it's just too much noise then I might even volunteer to email progress summaries from time to time.

* GitHub Issue emails:  This doesn't get sent to the list.  Arguably I think the messages there are even more worthwhile than the commits.

Opinions?

~ David

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com

_______________________________________________
dev mailing list
[hidden email]
http://lists.spatial4j.com/listinfo.cgi/dev-spatial4j.com