Hi, On Wed, Jun 27, 2018 at 9:34 AM Luca Mambretti <[email protected]> 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: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
