Working with upstream

[Jc2k]

Hi!

It looks like this is a fork of my fork of hpfeeds. I don't think we've spoken before and didn't know about this fork until hpfeeds/hpfeeds#61. I'd very much like to build more community around hpfeeds upstream, so I thought i'd say hello!

I'd also like to let you know that my fork was actually merged upstream here and will be completely archived soon. It took a bit longer than expected because someone not part of hpfeeds projects had registered the pypi project. This should be resolved now, and we are able to turn round releases upstream pretty quickly if they are needed.

I've become an upstream maintainer myself and I wanted to say that I encourage contributions upstream. Indeed, the mongo implementation itself was a contribution. (I don't use mongo myself). I don't see anything in here that couldn't potentially go upstream (although it's hard to be sure because its a fresh repo and didn't preserve this history).

If there is something I or the project have done that makes you feel like it's impossible to contribute or work upstream please do let me know and maybe I can do something about it. Hopefully it was just that you didn't know I existed 😄

If you are really committed to running as a downstream fork please consider rebasing on the upstream repository so that it's at least easier for us to share changes. If you want I might be able to do a no-op no-shared-parent pull request so that both our existing histories are preserved but git is able to do PR's between our projects.

Also it would be really nice if you could make it clear in your README that upstream is at github.com/hpfeeds/hpfeeds, and if you can I think it would be helpful to spell out the key differences between your fork and upstream for anyone that finds it on google.

Thanks for you work on and around hpfeeds and i hope we can work together upstrem soon!