On Tue, 2008-08-12 at 17:59 +1000, Brett Porter wrote:
> Any other opinions?
>
> On 08/08/2008, at 6:26 PM, Mark Hobson wrote:
>
> > 2008/8/8 Brett Porter <[EMAIL PROTECTED]>:
> >> I was poking back through the archives for a couple of things
> >> related to
> >> Maven core and was having trouble since it was drowned out in plugin
> >> development discussion and votes.
> >>
> >> Considering plugin dev occurs on more on the stable basis of previous
> >> versions of Maven it seemed to make some sense to use separate
> >> lists, even
> >> if the audience is largely similar. For commits I already filter
> >> the various
> >> pieces into separate folders, but that isn't as easy with dev
> >> traffic.
> >>
> >> This isn't a huge urge, I just wanted to see if it was something
> >> others had
> >> already been thinking was a good idea?
Speaking as a user and lurker, not having contributed any official
plugins or core code: I wonder if the mixed lists enable
cross-pollination of ideas and best practises and improves the
quality/usability of plugins .
I think my concern is that if the lists are split the core developers
isolate themselves from the plugin developers and vice versa. The
plugin developers are then left to sort out issues on their own, without
input from the core team who may be able to provide valuable direction.
As well there may be some plugin code that jumps through hoops to
achieve a task, but a core dev may see this and realize that adding some
convenience methods to the core would be beneficial to more than just
one plugin.
I don't know if this would really be an issue, but thought I'd chime in.
I know I'd subscribe to both lists still and may just use the separation
as a filter.
Jamie,
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is authorized. Any
liability arising from any party acting, or refraining from acting, on any
information contained in this e-mail is hereby excluded. If you are not the
intended recipient, please notify the sender immediately, destroy the original
transmission and its attachments and do not disclose the contents to any other
person, use it for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or
its affiliated entities.
