On Wed, Apr 25, 2018, at 12:08 PM, Robert Story wrote: > On Thu, 12 Apr 2018 10:31:13 -0500 Ian wrote: > IB> This morning we (Keith, Ian) met with an assortment of the > IB> NET-SNMP developers / contributors (primarily Bart Van Assche) > IB> to discuss how we could best help the project. The meeting went > IB> well, at least form our perspective. > > I'm sorry I missed this meeting. I'm almost always on IRC, but > sometimes go a while without checking the mailing list. > > IB> The pain points we identified were: > IB> > IB> * bug mountain > IB> * help users on the mailing list > IB> * patch / MR handling process > > Yep, those are biggies. > > IB> * move out of SourceForge > > We've had recent discussions on this, and I think we'll be moving > the source to github in the near future.
I think it would be best to get full agreement from the team on this. I hear bits-and-pieces that there have been some move in that direction. However, I think there should be a separate discussion just on that topic and what it would entail to officially move the Net-SNMP project over. > > IB> * clean up headers in /include/net-snmp/system/ which are a > IB> mess and have import loops > IB> > IB> * #ifdef hell / too many supported configurations > > I'm a little nervous about these one, especially with folks that are > new to the code base. And as far as supported configurations, we're > very big on backwards compatibility. > > As 5.8 is getting really close to going out the door, this type of > cleanup likely won't make it into that release. Agree completely on both points. I feel that this project should be done by a group that's composed by those who know the code, and those new to the code. That way, we have assurance that things are not being dropped on the floor on accident and that a good knowledge transfer happens. I would go so far as to suggest that one member of this "team" should be tasked with documenting what's going on; essentially appoint a project librarian if you will. One conversation I was a part of regarding the configuration is to modularize things better and leverage the build system to decide what source files will be included in the build based on the target system/configuration. I personally would suggest holding this off until we've moved to github. > > > Got any cmake experts? One of the planned items for 5.9 is moving > to cmake. The bulk of the work is done (patches from VMware against > 5.7), but work will be needed to integrate to master and put on the > finishing touches. I have experience using cmake, and I'm sure I can tap other people if need be. I would suggest that we look into whether the cmake move should be part of the "#ifdef hell..." clean up. If you can point me to the branch where the CMake-related files are currently stored I'll do some research on it once 5.8 is released. As far as versioning is concerned; I personally feel if the build system is switched to cmake that it should be considered a major release. I feel that rolling it to 5.9 may give some package managers a nasty surprise when their packaging script suddenly starts breaking. > > Robert > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Net-snmp-coders mailing list > Net-snmp-coders@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders There are obviously a lot of irons that are suddenly being considered to be thrown in the fire. Would the Net-SNMP team be amenable to either a conference/meeting either on IRC, phone, or video chat to develop a long-term plan for the project? I have access to systems we can use for a phone or video conference. -- Thanks, Keith (pantherse) ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
