first of all +1 to the plan in general I like it. in specific: +1 for the release proposal by Toni;
@JIRA I think that at least "create issue" and "comment issue" are human interaction and no "spam". But as long as jira sends a direct reply to ppl watching/created/commented an issue I'm fine with sending those mails only to a notification list. Kind regards, Andreas On Sat, Dec 8, 2012 at 4:52 PM, Toni Menzel <toni.men...@rebaze.com> wrote: > Hi Harald, > > totally in your boat. > I checked the ops4j@google when posting this mail and i wanted to ask you > about why we send jira notifications to this list.. Something - when > setting this up - was not intended actually. > > Lets rethink this: > Clearly, we should separate jira "spam" from human communication. > Speaking of release announcements: my gut feeling is still this: just use > one list where communication AND release announcements take place. > For people who are not interested in general discussion but OPS4J > releases, well we have many options: > - [RELEASE] or [ANNOUNCE] tag in subject line (people can filter) > - Confluence has a blog feed, so people could subscribe there. > > I personally have a problem with having many public mailinglist for > seemingly cross cutting usergroups. Many don't know what they really want, > so don't confuse them. For the "inbox.count=0" type of users, we can offer > the aforementioned options. > Reason for this is that OPS4J is not a corporation selling software. > Instead we are a community where we should try to get people participating > instead of locking them into "read only" mailinglists. > > ANYWAY, if majority here thinks a dedicated List for announcements is > still required, no problem. Just wanted to share my thoughts on this while > we are at "it" ;) > > Toni Menzel | Founder | toni.men...@rebaze.com > *Rebaze GmbH | *www.rebaze.com | twitter > @rebazetech<https://twitter.com/rebazetech> > > *Rebaze Pass* - Tailored Services for Cross Cutting Concerns in > Enterprise IT > Rebaze Pass for DevOps <http://www.rebaze.com/pass4devops.html> > Rebaze Pass for Mobile <http://www.rebaze.com/pass4mobile.html> > Rebaze Pass for Runtimes <http://www.rebaze.com/pass4runtimes.html> > Rebaze Pass for Persistence <http://www.rebaze.com/pass4persistence.html> > > > > On Sat, Dec 8, 2012 at 4:20 PM, Harald Wellmann <hwellmann...@gmail.com>wrote: > >> Hi Toni, >> >> not sure if I'm repeating myself - I'm fine with moving this list to >> Google Groups, but o...@googlegroups.com is not new and currently >> carries mostly JIRA notifications and release announcements. I think >> we should keep automatic notifications and "real" messages separate. >> >> AFIAK, there are 3 OPS4J Google Groups: >> >> ops4j >> ops4j-announcement >> ops4j-notify >> >> JIRA notifications currently appear both on ops4j and ops4j-notify. We >> should make sure they only get sent to ops4j-notify and not to ops4j >> so that users can opt out of JIRA "spam". >> >> A minor question is whether or not we should continue to cross-post >> release announcements on ops4j-announcement and ops4j/general. I think >> the answer is no, and the current settings on ops4j-announcements >> (anyone can join, managers can post) is fine, as long as all OPS4J >> releaser are managers of this list. >> >> Cheers, >> Harald >> >> 2012/12/8 Toni Menzel <toni.men...@rebaze.com>: >> > Gang, >> > >> > For some time now we've partially transitioned OPS4J infrastructure to >> > detached hosting providers. Up until now this included: >> > >> > - Github for Code Hosting/SCM >> > >> > - Atlassian OnDemand for Confluence & Jira >> > >> > - Sonatype OSS Nexus for Artifact Repository and bridge to Maven Central >> > >> > We finalizing this transition by taking away srv07, which has now >> served the >> > OPS4J and Qi4j communities over the last 4 years. By end of December, >> the >> > server is shut down. >> > By finishing the transition we hope to have up-to-date, reliable >> > infrastructure for all OPS4J Community activities in-place, so members >> can >> > focus on code. >> > >> > Services will be migrated as follows: >> > - All subscribers to this list will get invites to the new Google >> Group: >> > op...@googlegroups.com. >> > - DNS records moved to new servers (invisible to community) >> > - Mailing list general@lists.ops4j.org (this one) will be shut down >> on >> > December 21. >> > - ci.ops4j.org (Hudson) will transition to a rebaze based server >> (detached >> > from srv07 already anyway) >> > >> > Unsolved issue; >> > - http://repository.ops4j.org doesn't have a new home yet. Working >> > with Qi4J to sort this out. >> > >> > I think that covers it. If there is anything I forgot - PLEASE BRING IT >> UP! >> > >> > (Thanks to Niclas for the nobelprize-lyrics) >> > >> > Toni >> > >> > Toni Menzel | Founder | toni.men...@rebaze.com >> > Rebaze GmbH | www.rebaze.com | twitter @rebazetech >> > >> > Rebaze Pass - Tailored Services for Cross Cutting Concerns in >> Enterprise IT >> > Rebaze Pass for DevOps >> > Rebaze Pass for Mobile >> > Rebaze Pass for Runtimes >> > Rebaze Pass for Persistence >> > >> > >> > _______________________________________________ >> > general mailing list >> > general@lists.ops4j.org >> > http://lists.ops4j.org/mailman/listinfo/general >> > >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
