Publishing ideas on ActiveState recipe site
On Tue, Nov 6, 2012 at 1:22 AM, Steven D'Aprano <steve@pearwood.info> wrote:
On 05/11/12 23:52, Ned Batchelder wrote:
Get everything the way you want it, and then propose it.
+1
Also consider publishing it as a recipe on ActiveState, where many people will view it, use it, and offer feedback. This has many benefits:
* You will gauge community interest;
* Many eyeballs make bugs shallow;
* You are providing a useful recipe that others can use, even if it doesn't get included in the std lib.
Some of the most useful parts of the std lib, like namedtuple, started life on ActiveState.
Why I don't use ActiveState: 1. StackOverflow is much easier to access - just one click to login with Google Account versus several clicks, data entry and copy/paste operations to remind the password on ActiveState - I want to login there with Python account 2. StackOverflow is problem search oriented - not recipe catalog oriented, which makes it better for solving problems, which I do more often than reading the recipe book (although I must admin when I was starting Python - the Cookbook from O'Reilly in CHM format was mega awesome) 3. I post the code as gists as it includes the notion of history, unlike ActiveState, which interface looks a little outdated - it was not obvious for me that recipes have history until today 4. Recipes are licensed, which is a too much of a burden for a snippet 5. ActiveState site makes it clear that it is ActiveState site - the 20% of my screen is taken by ActiveState header, so it looks like company site - not a site for community Otherwise the idea of community recipe site is very nice.
On Wed, Nov 7, 2012 at 8:46 AM, anatoly techtonik <techtonik@gmail.com>wrote:
On Tue, Nov 6, 2012 at 1:22 AM, Steven D'Aprano <steve@pearwood.info> wrote:
On 05/11/12 23:52, Ned Batchelder wrote:
Get everything the way you want it, and then propose it.
+1
Also consider publishing it as a recipe on ActiveState, where many people will view it, use it, and offer feedback. This has many benefits:
* You will gauge community interest;
* Many eyeballs make bugs shallow;
* You are providing a useful recipe that others can use, even if it doesn't get included in the std lib.
Some of the most useful parts of the std lib, like namedtuple, started life on ActiveState.
Why I don't use ActiveState:
1. StackOverflow is much easier to access - just one click to login with Google Account versus several clicks, data entry and copy/paste operations to remind the password on ActiveState - I want to login there with Python account 2. StackOverflow is problem search oriented - not recipe catalog oriented, which makes it better for solving problems, which I do more often than reading the recipe book (although I must admin when I was starting Python - the Cookbook from O'Reilly in CHM format was mega awesome) 3. I post the code as gists as it includes the notion of history, unlike ActiveState, which interface looks a little outdated - it was not obvious for me that recipes have history until today 4. Recipes are licensed, which is a too much of a burden for a snippet 5. ActiveState site makes it clear that it is ActiveState site - the 20% of my screen is taken by ActiveState header, so it looks like company site - not a site for community
Otherwise the idea of community recipe site is very nice.
https://gist.github.com/ works great too. But I believe we are a bit OT.
On Wed, Nov 7, 2012 at 11:03 AM, Yuval Greenfield <ubershmekel@gmail.com>wrote:
On Wed, Nov 7, 2012 at 8:46 AM, anatoly techtonik <techtonik@gmail.com>wrote:
On Tue, Nov 6, 2012 at 1:22 AM, Steven D'Aprano <steve@pearwood.info> wrote:
On 05/11/12 23:52, Ned Batchelder wrote:
Get everything the way you want it, and then propose it.
+1
Also consider publishing it as a recipe on ActiveState, where many people will view it, use it, and offer feedback. This has many benefits:
* You will gauge community interest;
* Many eyeballs make bugs shallow;
* You are providing a useful recipe that others can use, even if it doesn't get included in the std lib.
Some of the most useful parts of the std lib, like namedtuple, started life on ActiveState.
Why I don't use ActiveState:
1. StackOverflow is much easier to access - just one click to login with Google Account versus several clicks, data entry and copy/paste operations to remind the password on ActiveState - I want to login there with Python account 2. StackOverflow is problem search oriented - not recipe catalog oriented, which makes it better for solving problems, which I do more often than reading the recipe book (although I must admin when I was starting Python - the Cookbook from O'Reilly in CHM format was mega awesome) 3. I post the code as gists as it includes the notion of history, unlike ActiveState, which interface looks a little outdated - it was not obvious for me that recipes have history until today 4. Recipes are licensed, which is a too much of a burden for a snippet 5. ActiveState site makes it clear that it is ActiveState site - the 20% of my screen is taken by ActiveState header, so it looks like company site - not a site for community
Otherwise the idea of community recipe site is very nice.
https://gist.github.com/ works great too. But I believe we are a bit OT.
Yea. That's point no.3 We're not offtopic, because people are proposing to post ideas on ActiveState first. I also found that ActiveState site doesn't allow to release recipes into Public Domain.
anatoly techtonik, 07.11.2012 09:19:
4. Recipes are licensed, which is a too much of a burden for a snippet
I also found that ActiveState site doesn't allow to release recipes into Public Domain.
Which is ok because "Public Domain" is not a universal concept. It won't work in all countries where your recipes will be read and where people want to use them. Better use a suitable license. Stefan
On Wed, Nov 7, 2012 at 11:29 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
anatoly techtonik, 07.11.2012 09:19:
4. Recipes are licensed, which is a too much of a burden for a snippet
I also found that ActiveState site doesn't allow to release recipes into Public Domain.
Which is ok because "Public Domain" is not a universal concept. It won't work in all countries where your recipes will be read and where people want to use them. Better use a suitable license.
MIT license or GPL license is not a universal concept either and wont work outside of U.S. universally. In court it will come down as a special case of personal copyright agreement between user and author. In this respect it is absolutely no different from the public domain notice.
On Nov 7, 2012, at 3:29 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
anatoly techtonik, 07.11.2012 09:19:
4. Recipes are licensed, which is a too much of a burden for a snippet
I also found that ActiveState site doesn't allow to release recipes into Public Domain.
Which is ok because "Public Domain" is not a universal concept. It won't work in all countries where your recipes will be read and where people want to use them. Better use a suitable license.
Creative Commons did a lot of work on making CC0 a universal "Public Domain". While other CC licenses are not suitable for code, CC0 does make sense when you want to release code as what some of us know as "Public Domain". https://creativecommons.org/publicdomain/zero/1.0/ As for ActiveState not allowing it, StackOverflow might confuse things as well since all contributions on StackExchange sites are licensed under CC-BY-SA. It may be difficult to put a CC0 license along side each post in StackOverflow. https://stackexchange.com/legal/terms-of-service -- Jay R. Wren
On Wed, Nov 7, 2012 at 6:18 PM, Jay Wren <jrwren@xmtp.net> wrote:
On Nov 7, 2012, at 3:29 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
anatoly techtonik, 07.11.2012 09:19:
4. Recipes are licensed, which is a too much of a burden for a snippet
I also found that ActiveState site doesn't allow to release recipes into Public Domain.
Which is ok because "Public Domain" is not a universal concept. It won't work in all countries where your recipes will be read and where people want to use them. Better use a suitable license.
Creative Commons did a lot of work on making CC0 a universal "Public Domain". While other CC licenses are not suitable for code, CC0 does make sense when you want to release code as what some of us know as "Public Domain".
https://creativecommons.org/publicdomain/zero/1.0/
As for ActiveState not allowing it, StackOverflow might confuse things as well since all contributions on StackExchange sites are licensed under CC-BY-SA. It may be difficult to put a CC0 license along side each post in StackOverflow.
Wow. I didn't know that - it looks like all code on SO is copylefted and can not be used in commercial products without giving up the rest of your commercial code - http://meta.stackoverflow.com/questions/18883/what-license-should-be-on-samp... -- anatoly t.
participants (4)
-
anatoly techtonik -
Jay Wren -
Stefan Behnel -
Yuval Greenfield