oak-issues@ list

[Jukka Zitting <ju...@gmail.com>]

Hi,

When talking with people interested in Oak, a common complaint (I've
heard it now from three different sources) is that trying to follow
the broader design discussions on oak-dev@ is a bit difficult with the
often lower-level issue tracker traffic that also hits this list.
There are some issues (like recently OAK-169) where broader topics are
discussed, but in general it's preferable to have such discussions on
the dev list and just use the issue tracker for the concrete action
items that may result from such discussions (OAK-181 and -182 being
good examples).

One could of course say that filtering out anything from jira@ should
be an easy enough solution to people who experience oak-dev@
information overload, but who has time to maintain such filter
settings? (I know I don't.) A simpler alternative could be to direct
the issue tracker updates to oak-commits@ or (better) a separate
oak-issues@ list where everyone who wants to track day-to-day
development can get all the updates. Both oak-commits@ and oak-issues@
should have Reply-To pointing to oak-dev@ to bring any followup
discussions back to here.

WDYT?

BR,

Jukka Zitting

Re: oak-issues@ list

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Sun, Aug 5, 2012 at 12:04 PM, Jukka Zitting <ju...@gmail.com> wrote:
> The list is now finally in place. To subscribe, send a message to
>
>     oak-issues-subscribe@jackrabbit.apache.org
>
> I'll redirect the Jira notifications from oak-dev@ to oak-issues@ in a
> few days once everyone has had a chance to subscribe.

It took a few more days than expected, but Jira notifications are now
finally going to oak-issues@.

BR,

Jukka Zitting

Re: oak-issues@ list

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Fri, Jul 20, 2012 at 10:13 AM, Jukka Zitting <ju...@gmail.com> wrote:
> With no objections and some explicit support, I'm assuming lazy
> consensus and moving forward on this. See
> https://issues.apache.org/jira/browse/INFRA-5068.

The list is now finally in place. To subscribe, send a message to

    oak-issues-subscribe@jackrabbit.apache.org

I'll redirect the Jira notifications from oak-dev@ to oak-issues@ in a
few days once everyone has had a chance to subscribe.

BR,

Jukka Zitting

Re: oak-issues@ list

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Jul 12, 2012 at 9:01 PM, Jukka Zitting <ju...@gmail.com> wrote:
> WDYT?

With no objections and some explicit support, I'm assuming lazy
consensus and moving forward on this. See
https://issues.apache.org/jira/browse/INFRA-5068.

BR,

Jukka Zitting

Re: oak-issues@ list

[Alexander Klimetschek <ak...@adobe.com>]

+1 !!!

Cheers,
Alex

On 12.07.2012, at 21:01, Jukka Zitting wrote:

> Hi,
> 
> When talking with people interested in Oak, a common complaint (I've
> heard it now from three different sources) is that trying to follow
> the broader design discussions on oak-dev@ is a bit difficult with the
> often lower-level issue tracker traffic that also hits this list.
> There are some issues (like recently OAK-169) where broader topics are
> discussed, but in general it's preferable to have such discussions on
> the dev list and just use the issue tracker for the concrete action
> items that may result from such discussions (OAK-181 and -182 being
> good examples).
> 
> One could of course say that filtering out anything from jira@ should
> be an easy enough solution to people who experience oak-dev@
> information overload, but who has time to maintain such filter
> settings? (I know I don't.) A simpler alternative could be to direct
> the issue tracker updates to oak-commits@ or (better) a separate
> oak-issues@ list where everyone who wants to track day-to-day
> development can get all the updates. Both oak-commits@ and oak-issues@
> should have Reply-To pointing to oak-dev@ to bring any followup
> discussions back to here.
> 
> WDYT?
> 
> BR,
> 
> Jukka Zitting