Closed CleanCut closed 8 years ago
I only came across green recently, and I can't remember how, unfortunately. Turn the origin section of your readme into an article (it wouldn't take much work because it's well written), post it on your blog, on medium, then link it on reddit (/r/python), twitter and other social network platforms. I think content is received better in that form than a simple advertisement.
edit: Quick look through my history, I think your medium post about python 3.5 compatibility was suggested to me, or I was looking for unit test modules with python 3.5 support.
I'm not sure you have enough lines of code, but you could enter this comptetion for the publicity, money and free feedback. I found the blog posts pretty interesting as well, if a little vehement!
@Ogaday That competition looks awesome. Unfortunately, I'm not even halfway to the 10,000 lines of code minimum.
Thanks for the suggestion about medium and reddit. That's what I've been doing for major/minor releases (not dot releases). But going back and turning the origin story into a medium post is a good idea. I wasn't on medium at the time I originally wrote that.
@CleanCut Good job on the getting the pull request accepted. You should look to get on the unittest documentation page. Pytest and nose are there. Also linked are the testing page on the python wiki and the Testing in Python Mailing List. I don't know how you'd get on those different pages, but it's a start.
@CleanCut Have you come across the Anaconda distribution and specifically the environment/package manager Conda? Not entirely sure what it entails, but distributing green via conda/binstar might make it more accessible to scientific users in particular.
@Ogaday Thanks! I added those all to the list.
Pytontesting.net who delivered a fantastic article would look like a good place to get coverage. Perhaps ask for a review, in the same way the author has reviewed nose and pytest.
I actually contacted the guy behind pythontesting.net last August. Here's a snippet from his reply email where he declined to look at green :-(
Those features might be awesome, but they aren't useful to me.
I can't run tests concurrently against one system anyway.
And I don't actually watch the test run, I parse the report and push it to a web site that graphs the results for each test run.
There's a podcast I like, talkpythontome, the author may be happy to interview you ?
My publicity ambitions have been sufficiently satisfied.
Green should be listed next to py.test in public lists of python test frameworks!
If people have a hard time finding out about green, they won't use green! Life will be so much slower and less colorful for them. Don't let that happen!
LET ME KNOW about other places that ought to link to green: