netbeans-netcat mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geertjan Wielenga <geertjan.wiele...@googlemail.com.INVALID>
Subject Re: [DISCUSS] Merging back netcat@ into the dev@ mailing list
Date Wed, 27 Jun 2018 16:01:06 GMT
On Wed, Jun 27, 2018 at 4:44 PM, Brett Ryan <brett.ryan@gmail.com> wrote:


> My plan is for a lot of my devs and test teams to come join NetCAT, most
> of my QA team do not have an engineering background and for them they
> wouldn’t want to see dev related topics.
>


Now that's an awesome plan!

Gj





>
> You’re all doing great work here.
>
> > On 27 Jun 2018, at 22:03, Geertjan Wielenga
> <geertjan.wielenga@googlemail.com.INVALID> wrote:
> >
> > Whatever keeps Luca and all other NetCAT people inspired and on board is
> > what we should do.
> >
> > I frankly don’t understand what the problem is that we’re trying to fix
> > here. If we’re saying that we’re not able to communicate with the whole
> > community because we have NetCAT separated from dev, then we should use
> the
> > same argument consistently and merge the users mailing list into dev as
> > well and I’m sure no one is suggesting that. :-)
> >
> > Apache NetBeans has a community of users, developers, and testers.
> That's a
> > value add, if anything.
> >
> > Gj
> >
> >
> >
> > On Wednesday, June 27, 2018, Bertrand Delacretaz <bdelacretaz@apache.org
> >
> > wrote:
> >
> >> Hi,
> >>
> >> On Wed, Jun 27, 2018 at 9:34 AM Luca Mambretti
> >> <luca.mambretti@bizeta.net> wrote:
> >>> ...During the previous programs there were weekly reports on
> activities,
> >> measurement on traffic
> >>> on the mailing list and various surveys to check the status of the
> >> release train in the allotted
> >>> time-frame; ...
> >>
> >> I know little about how NetCAT works but from an Apache perspective of
> >> asynchronous collaboration, jira tickets might be a good way to
> >> coordinate the NetCAT reviews: create a ticket for each main part of
> >> the review (per-tribe?), people can create sub-tickets for more fine
> >> grained coordination and it's easy to get an overview on activity and
> >> status via jira queries. And NetCAT jira tickets can be linked to
> >> development tickets which can help make both teams feel more united.
> >>
> >> Apache projects rarely have set deadlines for releases, as those can
> >> go against quality and people usually work on their own schedule as
> >> opposed to being paid to do things on time. Such loose but efficient
> >> coordination mechanisms work very well for that and quality as opposed
> >> to artificial deadlines then drive the releases.
> >>
> >> This is just my 2 cents, as mentioned I know little about NetCAT, but
> >> I do know a bit about how things work in loosely coupled Apache
> >> projects, and I feel that Apache NetBeans is getting more loosely
> >> coupled - which does have advantages but might require some
> >> adjustments.
> >>
> >> -Bertrand (NetBeans incubation mentor)
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: netcat-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: netcat-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: netcat-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: netcat-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message