-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mailinglist #38
Comments
Other mailing list that I know seems to be on googlegroups:
The mailing list is not that pretty active, so we may be bike-shedding here.
|
a side question: I see about 15% of linux downloads on Germany. Is it real users ? does WinPython works on "Wine" ? Does some users need that ? |
Sorry, but this is not an argument.
I do receive support requests via mail. This is an indicator, that we are doing something wrong.
No idea. We could add a link to Anaconda for Linux users. Winpython does have more recent software than distributions, but compiling yourself is also much much easier (just with pip install). |
Why would we be doing anything more wrong than others on mailing list ? there is maybe just better alternatives than mailing list nowodays:
When all is normal, WinPython may only be rarely the direct concern of its users, |
stackoverflow is an excellent resource. I suggest adding a link to http://stackoverflow.com/questions/tagged/python on https://winpython.github.io/ I notice that stackoverflow has no tag for WinPython. Is it possible to add this? You could encourage users to use the WinPython tag for questions specific to WinPython. Today, I rely on the googlegroups release announcement for the SHA1 hash of the release downloads. Could release announcements be put somewhere else so that googlegroups can be retired for WinPython? |
You need 1000 points to be able to suggest a new "tag", I'm 531. Then you need to prove the "tag" is usefull, and in pure truth there are not so much issues on Winpython:
|
I already thought about adding a tag for winpython some time ago. Currently there are 428 questions on stackoverflow containing 'winpython', definitely more than when I thought about it last time. So it may be reasonable.
It requires 1500 reputation points. |
I looked again at https://winpython.github.io/ and I see that the MD5 and SHA1 hash of releases is there already. Sorry for not paying attention. The main reason for me to use the googlegroups now is for WinPython announcements. I like the highlights and summary of these. But wouldn't a WinPython blog be better for announcements? For me to post to googlegroups, I need to allow Google cookies and scripts. If I allow these for all my web browsing, which is the most convenient, then Google tracks my browsing habits and sells my personal info. Lately, when I try to log into my Google account to post on the WinPython group, Google accuses me of being a robot and asks for my landline or cellphone number to prove I am not a robot. If I comply, I have given Google yet more personal info, and I have no control over to whom they sell this info. Instead, I choose not to post on the WinPython googlegroup any more. This means that WinPython users who ask for help there are not getting any help from me. I notice that questions on the WinPython googlegroup sometimes don't get any answer, or a suggestion takes many days to arrive. If I wanted a quick answer, I would go to stackoverflow or github instead. New WinPython users may not know the options and feel frustrated with no response or a slow response on the googlegroup. Some users are aware of how unpopular the WinPython googlegroup is, so they ask on stackoverflow too. If their question is answered on stackoverflow, then answering on the googlegroup is a waste of time. |
Using googlegroups without a google account is actually possible (that's what I did), but the function is very well hidden. I agree with you @hiccup7 |
It is nearly impossible to find out how to subscribe to our mailinglist at googlegroups for non-gmail users. Therefore I would prefer to move the list to another provider, e.g. librelist.com
The text was updated successfully, but these errors were encountered: