I've been thinking about my reply all day. Well, not so much my reply,
but some of the underlying concepts, assumptions, etc. that I believe
are really important.
On Oct 19, 2:12 pm, duncan.mcgreg...@gmail.com wrote:
> > Any status update would be great.
First of all, what got me started thinking along the "deep",
philosophical lines was the lateness of my reply to Dave. I have a poor
sense of time, but Dave emailed more than two weeks ago. For someone in
need, that's unkind and inconsiderate of me, no matter how busy things
have been.
> > I'm in the process of trying to find a good NetFlow data collection
> > tool and came across CoyoteMonitoring.
> > Everything on the site seems to indicate this is exactly what I
> > want/need.
This is great to hear, but even more so, it's special in this sense:
the CoyoteMonitoring corner of the Internet has addressed a certain
need. Many folks have that same need. That kind dynamic is the classic
one of the village and the blacksmith. The blacksmith can't eat iron,
and the miller can't shoe his horses with ground grain. Mutual benefit
is the kind of thing brings people and groups together, accomplishing
common good.
> Thanks for writing! I've been working with Zenoss and their monitoring
> software (free, open-source). You can check them out here:
>
http://zenoss.com/ > Lots of people in the community have started asking for NetFlow
> capability, something that I would like to build for them. I would
> encourage you to join the mail list and add your voice to the vote :-)
> I would be thrilled to work on NetFlow again.
If I would be so thrilled to work on NetFlow, howcome I'm not?
I asked myself that all day today. The answer is that there is no good
reason. There are people out there who could really benefit from the
stuff that I have written and the stuff that I am writing in my down
time. Likewise, if I am able to fulfill some need that people in the
community are having, my quality of life has just increase n-fold.
> You may have seen the posts I made to the list about refactoring the
> old code and rewriting the old, 3rd-party perl in modern, efficient
> python (CoyMon3). I've made some good progress, but now it just needs
> sponsorship to continue.
That's a pile of crap. There's no good reason why I can't start doing
this now. There's all kinds of stuff I do in my life that 1) has no
purpose and is a waste of time, or 2) goes unappreciated. If I can bend
some code-iron to the needs of users, then I am both fulfilling a
purpose and will most likely be greeted with appreciation. And let me
tell you, that appreciation is worth more than money.
So, here's the deal: as of right now, I'm working for the village
again. I'm heating the forge up now, and breaking out the tools.
Timeline:
* Within the next month, I will release CoyMon2, free of the
VA-specific code, even though the codebase is not up to my standards
and some of the third-party tools are difficult to work with
* I will do my best to support you all with answers to your CoyMon2
questions
* Within the next 2 months, I will resume work on CoyMon3, given the
interest of users on the list
As for that last bullet, you could really help me out by responding to
this email and letting me know what your Top 2, Top 5 and Top 10
feature requests/wishlists would be.
Time to get to work :-)
d
