> I think the thing to do is to contact the author and ask if you can
> help, or, if s/he is not planning on updating the package, whether
> s/he would mind if you released a modified version of the package.
Thanks guys, I'll contact the original dev and take things from there.
Shalom,
Jordan
Jay McCarthy wrote at 08/24/2011 08:55 PM:
The best think is to just upload a new package with the same name and
not the provenance in the docs. This has happened before (sxml2)
We actually talked with Oleg Kiselyov (original developer) and the other
developers before doing that, and got th
One thing to keep in mind: the bug reports on the PLaneT site are not
necessarily the de facto way to submit bug reports for the package. The
author of the package might not even be aware of them, or may have
forgotten.
I think the thing to do is to contact the author and ask if you can
help
On Wed, Aug 24, 2011 at 6:16 PM, Jordan Schatz wrote:
> There is a planet package that looks like it's author is too busy to
> maintain (it has open bugs, and some with unmerged patches, and they are
> many months old) that I plan on fixing for my own needs... What is the
> proper etiquette for ge
There is a planet package that looks like it's author is too busy to
maintain (it has open bugs, and some with unmerged patches, and they are
many months old) that I plan on fixing for my own needs... What is the
proper etiquette for getting a version with my updates into planet?
On github I would
5 matches
Mail list logo
