Hi Chris, Sounds pretty neat.
Until we have package manager, the general protocol is as follows: If the module is generally useful to other Chapel users, we ask that you open a PR for submission into module/packages. Once your code / documentation meets the reviewer¹s demands, it will be merged in and available for use by any Chapel user working out of master. If you think the audience for the module is fairly narrow, you can keep it hosted on a git repository, and have users check out your repo / modify their MODULE_PATH to use it. Best, Ben On 6/13/16, 3:13 PM, "ct clmsn" <[email protected]> wrote: >I've a small module of chapel code containing the following types: Option, >Some, None, Try, Result, Error. > >The chapel code is modeled after the Mesos project's stout library. > > >The Mesos C++ API, with code samples, is available here: >https://mesos.apache.org/api/latest/c++/md_3rdparty_libprocess_3rdparty_stout_README.html > ><https://mesos.apache.org/api/latest/c++/md_3rdparty_libprocess_3rdparty_stout_README.html> > > >The module has been pretty helpful implementing some of my current projects. >It's helped make bugs a little easier to identify and fix. I think other users >might like it. > > >Is there a process for submitting a 3rd party module as a package? > > >ct > > > > > > > > > > > > > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
