Yunhong, Sorry for the delay. Please see my comments below....
Thanks, Ray On Tue, Aug 30, 2016 at 5:22 PM, yunhong jiang < [email protected]> wrote: > On Mon, 29 Aug 2016 09:41:46 -0700 > Raymond Paik <[email protected]> wrote: > > > All, > > > > One of the topics discussed at the Q3 Hackfest last week was OPNFV > > mailing lists. After ~2 years, I think most will agree that the > > opnfv-tech-discuss mailing list in particular has become difficult to > > digest. > > > > The consensus among attendees last week was to keep > > Such discussion has happened on almost each open source project, and > different project has diffrent conclusion. > > I'm not on the Hackfest and no idea of the exact meaning of "difficult > to digest". If you can provide more information of the "difficulty" of > the digest, it will be really good. > > Below is just my input. I'm against the spliting as: > > a) I think it's easy to filter the mail based on the subject. And till > now, I think the mailing list is quite well on the tag, of course we > can always do better on it. > > b) Keep all topic on the same mailing list make it easier to have a > quick look on the topic on the project. OPNFV includes a bunch of > projects and they are related to each other quite tightly. For example, > test projects are sure to be related to the test bed, i.e. the Pharos > project, which I think is part of the opnfv-infra. > > => Comments I heard from many community members is that even with tags, the tech-discuss mailing lists has become difficult to manage. Or with 40+ tags, tags themselves are not very useful or usable... > More inputs below. > > > opnfv-tech-discuss for general and project-related discussions (using > > tags), but it'd make sense to create additional mailing lists for > > other discussions. Below is the proposal that the attendees came up > > with and wanted to share this with the rest of the community for > > feedback and further discussions. > > > > > > > - Mailing list for Release discussions (e.g. opnfv-release) > > I'm not sure if we really need the release discussion mailing list. Per > my understanding and experience, the projects have more interactive > during the release time, and need more collaboration. Also every > projects would participate on the release discussion, why don't we do > that on the tech-discuss mailing list, which should involve everyone > already? > > But if you are talking about the discussion of stable release (like > B-release, or C-release after the C release date), I agree it make > sense. > > > - Mailing lists for OPNFV working groups: create separate lists > > for Test (opnfv-test-wg), Infra (opnfv-infra-wg), and MANO > > (opnfv-mano-wg) working groups > > As stated above, these work groups have very tight relationship. > > > - Create new mailing lists for upstream discussions with OpenStack > > (opnfv-openstack) and OpenDaylight (opnfv-odl) communities > > Most of the OPNFV projects have corresponding upstream project. Will we > create upstream discussion list for each one? And also what's > the benefit of this upstream mailing list? Is it to involve the upstream > community? If yes, I doubt if it will have any help. After all, the > involvement from upstream community depends more on our impact to > them :) > => Actually got requests from upstream community members (e.g. from OpenStack, ODL, etc.) that they would like an open mailing list that they can participate in without having to subscribe to it... > > Thanks > --jyh > > > - This will have the same set up as the mailing list already > > created for fd.io ([email protected]) > > > > Please jump in with your thoughts or other suggestions. We can have > > email discussions this week and try to come to a consensus during the > > TSC call next week (September 6th). > > > > Thanks, > > > > Ray > >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
