Differentiate this fork from its parent

[amoghe]

I've written a pkg to interact with upstart using this. My initial search led me to the guelfey/dbus pkg using which I implemented my pkg. I'm considering moving to using this one (it seems more actively maintained?) but I'm not sure what the plans are for this repo (eventually contribute back to the parent repo?).

I assume other developers might follow this path as well (because google prefers to display the parent repo over this one). There is nothing in the README that differentiates this fork from its parent, especially in terms of planned work/roadmap or even why the fork was created and is maintained separately.

[philips]

The author of guelfey/dbus is a maintainer of this package. This is upstream. See guelfey/go.dbus#51

[amoghe]

Interesting! (unfortunately, thats not obvious unless one goes searching for that bug).

Github displays forked from guelfey/go.dbus right under the godbus/dbus repo name. This is the source of confusion in this case. Maybe an update to one (or both) READMEs might help?

[philips]

@amoghe I contacted github support to remove the forked from thing.

[philips]

Fixed.