Comments on Comments or Not? Public or Private? Relevant or Irrelevant?, page 3 of 3
· activism, community, enthusiasm, open source, python, support
As a programmer I hope someday I can do something ...
Kumo · 2009-12-01T18:14:19.814000
As a programmer I hope someday I can do something to give back to the community.
Maybe a lot of people has willingness to help, but how?
I think there should be an easier entrance for people to feel part of the Python community.
Greatfully, An insignificant Python user (that's not good at english)
A small cultural problem (in open source, and not ...
Anonymous · 2009-12-01T19:44:40.246000
A small cultural problem (in open source, and not at all specific to python) that I think would not be that difficult to fix is:
"if you don't like something, fix it" which @Titus mentioned.
What does this convey to the average user? Something like: 1. I am not going to fix your problem 2. I am not going to give you any pointers on how to fix it yourself 3. Go away
Open source projects are often staffed by volunteers and they certainly aren't *obligated* to do any work on behalf of users, but there are more diplomatic ways to say this.
Maybe: "Thanks for your feedback, but I'm not sure when I'll have time to look at this. If you do, the related source code is in this directory."
If you want people to get involved, then the tone of the community makes a lot of difference. Being helpful, even if that doesn't mean doing work for other people, goes a long way towards that.
To be fair, when I've interacted with the Python community I've actually had a good experience. I've even had small problems I reported almost immediately fixed. However, I've seen other projects where questions asked or problems reported on mailing lists routinely come back with RTFM, or "fix it yourself" in quite hostile sounding terms.
I have only been coding (in any form) for a couple...
kindly · 2009-12-01T21:46:26.840000
I have only been coding (in any form) for a couple of years and have found the python community very trustworthy, knowledgeable and safe (if a little set in their ways). I am not particularly young though, so I like the solidness.
The pypi stuff is very superficial to outsiders, especially as there are much much better ways of doing it i.e as Titus said a voting system for comments. Making pypi an api would do and let the web community make it (I am sure if you asked the django guys they would let you use their voice/pony). Documentation should have voted comments too which would sort out the documentation as user contributed stuff always ends up better. PHP does this and its the best thing about the language. They managed to do it well as they are a web community. Python should let their web community do the same for web related issues. I don't use django personally but its a very undervalued resource and I am sure any other framework would jump on the chance to have their name on python home stuff.
The community focus needs to be more based around, "making cool stuff with python", then "what shall we do to improve python". The Ruby community has more this attitude which does it favors. There is a moratorium on the language now too, so it seems there is not much a bystander can do. Issues with packaging aside, I think people think that python is stable and does what it says. There are worries about concurrency and speed but the community does seem to be working at that.
In conclusion, let the web people control the web and let them show off (let the ponies fly).
I think "kindly" hit the nail on the hea...
Anonymous · 2009-12-04T14:49:52.618000
I think "kindly" hit the nail on the head. Our current Web infrastructure seems handled by people like me (core developers) while it should be handled by people who are enthusiastic about Web stuff, and proactive in suggesting new functionalities/design/whatever.
I also hope you'll keep us updated about what you're planning to do to improve things, Steve :-) I think this is a very important issue (and I'd be glad to show moral support if needed!).
It's a flawed survey to be sure but given that...
Anonymous · 2009-12-04T16:15:12.619000
It's a flawed survey to be sure but given that the last four options all include giving the package owner the right to disallow comments that option really got 137+33+24+88=282 votes and seems to be the winning one.
Actually, why not just allow package owners to configure commenting and ratings so they can enable, disable, or make private either one independently?
You can't make everyone happy but that essentially provides all the options in the survey and some that weren't in the survey.
I realize it's probably easier said than done and have a lot of respect for the people that actually write the code.
As a programmer I hope someday I can do something ...
Kumo · 2009-12-01T18:14:19.814000
As a programmer I hope someday I can do something to give back to the community.Maybe a lot of people has willingness to help, but how?
I think there should be an easier entrance for people to feel part of the Python community.
Greatfully,
An insignificant Python user (that's not good at english)
A small cultural problem (in open source, and not ...
Anonymous · 2009-12-01T19:44:40.246000
A small cultural problem (in open source, and not at all specific to python) that I think would not be that difficult to fix is:"if you don't like something, fix it" which @Titus mentioned.
What does this convey to the average user? Something like:
1. I am not going to fix your problem
2. I am not going to give you any pointers on how to fix it yourself
3. Go away
Open source projects are often staffed by volunteers and they certainly aren't *obligated* to do any work on behalf of users, but there are more diplomatic ways to say this.
Maybe: "Thanks for your feedback, but I'm not sure when I'll have time to look at this. If you do, the related source code is in this directory."
If you want people to get involved, then the tone of the community makes a lot of difference. Being helpful, even if that doesn't mean doing work for other people, goes a long way towards that.
To be fair, when I've interacted with the Python community I've actually had a good experience. I've even had small problems I reported almost immediately fixed. However, I've seen other projects where questions asked or problems reported on mailing lists routinely come back with RTFM, or "fix it yourself" in quite hostile sounding terms.
I have only been coding (in any form) for a couple...
kindly · 2009-12-01T21:46:26.840000
I have only been coding (in any form) for a couple of years and have found the python community very trustworthy, knowledgeable and safe (if a little set in their ways). I am not particularly young though, so I like the solidness.The pypi stuff is very superficial to outsiders, especially as there are much much better ways of doing it i.e as Titus said a voting system for comments.
Making pypi an api would do and let the web community make it (I am sure if you asked the django guys they would let you use their voice/pony).
Documentation should have voted comments too which would sort out the documentation as user contributed stuff always ends up better.
PHP does this and its the best thing about the language. They managed to do it well as they are a web community. Python should let their web community do the same for web related issues. I don't use django personally but its a very undervalued resource and I am sure any other framework would jump on the chance to have their name on python home stuff.
The community focus needs to be more based around, "making cool stuff with python", then "what shall we do to improve python". The Ruby community has more this attitude which does it favors. There is a moratorium on the language now too, so it seems there is not much a bystander can do. Issues with packaging aside, I think people think that python is stable and does what it says. There are worries about concurrency and speed but the community does seem to be working at that.
In conclusion, let the web people control the web and let them show off (let the ponies fly).
I think "kindly" hit the nail on the hea...
Anonymous · 2009-12-04T14:49:52.618000
I think "kindly" hit the nail on the head. Our current Web infrastructure seems handled by people like me (core developers) while it should be handled by people who are enthusiastic about Web stuff, and proactive in suggesting new functionalities/design/whatever.I also hope you'll keep us updated about what you're planning to do to improve things, Steve :-) I think this is a very important issue (and I'd be glad to show moral support if needed!).
It's a flawed survey to be sure but given that...
Anonymous · 2009-12-04T16:15:12.619000
It's a flawed survey to be sure but given that the last four options all include giving the package owner the right to disallow comments that option really got 137+33+24+88=282 votes and seems to be the winning one.Actually, why not just allow package owners to configure commenting and ratings so they can enable, disable, or make private either one independently?
You can't make everyone happy but that essentially provides all the options in the survey and some that weren't in the survey.
I realize it's probably easier said than done and have a lot of respect for the people that actually write the code.
Older comments · Page 3 of 3
Back to post