Re: [pypy-dev] Forwarding...
Thanks for answer Maciej! I'm glad that this is in progress. It isn't possible to make some image about the situation from what I have found on the web. You response clarifies that a bit. I understand how difficult it can be. But I disagree with you regarding kickstarter. Pypy is connected to user experience. E.g. I am working as datascientists and pypy is running about 3 times faster on the code I am able to use it on (which is, unfortunately, minority - most of it is of course in those 4 libraries which shines red on the library support wall - numpy, scipy, pandas, scikit-learn). Similar with (py)Spark. I would say there are more data scientists using Python than those who likes to use "MicroPython on the ESP8266". The gain this field can get from Pypy is quite substantial, even with that conservative estimate about 3 times as fast compared to cPython. And that is just one example. Of course, I cannot ensure that you might get reasonably funded on kickstarter-like sites. But, what can you lose by making a campaign? It would be definitely much more visible than on your website, which, to be honest, could be a bit modernized as well. And even if it wouldn't be a success, you still get PR basically for free. I, unfortunately, don't have any insights or recommendation, it just scratched my mind. Thanks for your awesome work, Daniel čt 19. 5. 2016 v 18:12 odesílatel Maciej Fijalkowski napsal: > Hi Daniel. > > We've done all of the proposed scenarios. We had some success talking > to companies, but there is a lot of resistance for various reasons > (and the successful proposals I can't talk about), including the > inability to pay open source from the engineering budget and instead > doing it via the marketing budget (which is orders of magnitude > slower). In short - you need to offer them something in exchange, > which usually means you need to do a good job, but not good enough (so > you can fix it for money). This is a very perverse incentive, btu this > is how it goes. > > As for kickstarter - that targets primarily end-user experience and > not infrastructure. As such, it's hard to find money from users for > infrastructure, because it has relatively few direct users - mostly > large companies. > > As for who is working on this subject - I am. Feel free to get in > touch with me via other channels (private mail, gchat, IRC) if you > have deeper insights > > Best regards, > Maciej Fijalkowski > > On Thu, May 19, 2016 at 5:11 PM, Armin Rigo wrote: > > On 19 May 2016 at 14:58, wrote: > >> -- Forwarded message -- > >> From: Daniel Hnyk > >> To: pypy-dev@python.org > >> Cc: > >> Date: Thu, 19 May 2016 12:58:36 + > >> Subject: Question about funding, again > >> Hello, > >> > >> my question is simple. It strikes me why you don't have more financial > support, since PyPy might save quite a lot of resources compared to > CPython. When we witness that e.g. microsoft is able to donate $100k to > Jupyter (https://ipython.org/microsoft-donation-2013.html), why PyPy, > being even more generic then Jupyter, has problem to raise few tenths of > thousands. > >> > >> I can find few mentions about this on the internet, but no serious > article or summary is out there. > >> > >> Have you tried any of the following? > >> > >> 1. Trying to get some funding from big companies and organizations such > as Google, Microsoft, RedHat or some other like Free Software Foundation? > If not, why not? > >> 2. Crowd founding websites such as Kickstarter or Indiegogo get quite a > big attention nowadays even for similar projects. There were successful > campaigns for projects with even smaller target group, such as designers ( > https://krita.org/) or video editors (openshot 2). Why haven't you > created a campaign there? Micropython, again, with much smaller target > group of users had got funded as well. > >> > >> Is someone working on this subject? Or is there a general lack of man > power in PyPy's team? Couldn't be someone hired from money already > collected? > >> > >> Thanks for an answer, > >> Daniel > > ___ > > pypy-dev mailing list > > pypy-dev@python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Forwarding...
Hey, thanks for your answers. I know you are working on numpy and similar libraries, as well about the fundraisers on your site. I am glad there is something happening around this. Thank you for your work and information, Daniel čt 19. 5. 2016 v 23:53 odesílatel Armin Rigo napsal: > Hi, > > On 19 May 2016 at 21:29, Kotrfa wrote: > > Of course, I cannot ensure that you might get reasonably funded on > > kickstarter-like sites. But, what can you lose by making a campaign? It > > would be definitely much more visible than on your website > > I should add that we did that already: we have three fundraisers > linked from the website---or maybe *had,* given that we launced them > long ago already. It was reasonably successful. We're now thinking > about what we'll do next. > > > A bientôt, > > Armin. > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] Pypy's facelift and certificate issues
Hi, thank you for all your hard work, I really appreciate it. Firstly, it seems that the website SSL certificate expired or something. At my latest Chromium reports "Not secure". Secondly, I totally understand that there are more pressing issues than cool website, but the current design and functionality is IMO really putting people off. So I am going to through away some things which seems weird to ME (and I understand it's subjective - please take it as a friendly feedback). The jQuery versions suggests November 2012, the design idea seems even older... There are old information such as "*We are soon releasing a beta supporting Python 3.3." *or the fact that the donations bars are still present even though they are closed (and hence could be moved into some blog post). Blog is also terrible, this is how it renders on my laptop (the same with the external display): https://imgur.com/a/qkjEa . The logo could be surely polished as well (I like the idea, but it seems a bit childish). Even though I am not professional front end developer, I am quite confident this feedback is not far from what a professional would say. It's also not about having "cool" website for itself, but that a nice projects attracts good people. I myself am questioning how good, from technical point of view, Pypy's project can be if the site looks like like it does and the most convenient way how to reach the devs is through mailing list... Best, Daniel ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Pypy's facelift and certificate issues
Hey, as I said, I am not a professional, but I would be willing to help with the site. I have built couple of websites in Django/Wagtail (or plain HTML), have some basic knowledge about design (+ frontend CSS/JS/HTML). The site seems quite simple, so if we just did a revamp, it shouldn't take a long. Also, if we went with Wagtail, adding blog capabilities would be also trivial. Best, Daniel so 30. 12. 2017 v 10:02 odesílatel Maciej Fijalkowski napsal: > Hi Kortrfa > > I've even paid for a design of new pypy logo that we can use on the > new website :-) Maybe it's a good time I spend some effort upgrading > it. Thanks for the reminder, it's something that's on our heads, but > it's not like we can just hire someone to do it for us. > > Cheers, > fijal > > On Wed, Dec 27, 2017 at 9:35 PM, Kotrfa wrote: > > Hi, > > > > thank you for all your hard work, I really appreciate it. > > > > Firstly, it seems that the website SSL certificate expired or something. > At > > my latest Chromium reports "Not secure". > > > > Secondly, I totally understand that there are more pressing issues than > cool > > website, but the current design and functionality is IMO really putting > > people off. So I am going to through away some things which seems weird > to > > ME (and I understand it's subjective - please take it as a friendly > > feedback). > > > > The jQuery versions suggests November 2012, the design idea seems even > > older... There are old information such as "We are soon releasing a beta > > supporting Python 3.3." or the fact that the donations bars are still > > present even though they are closed (and hence could be moved into some > blog > > post). Blog is also terrible, this is how it renders on my laptop (the > same > > with the external display): https://imgur.com/a/qkjEa . The logo could > be > > surely polished as well (I like the idea, but it seems a bit childish). > Even > > though I am not professional front end developer, I am quite confident > this > > feedback is not far from what a professional would say. It's also not > about > > having "cool" website for itself, but that a nice projects attracts good > > people. I myself am questioning how good, from technical point of view, > > Pypy's project can be if the site looks like like it does and the most > > convenient way how to reach the devs is through mailing list... > > > > Best, > > Daniel > > > > ___ > > pypy-dev mailing list > > pypy-dev@python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > > > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Pypy's facelift and certificate issues
Hi, I am based in Prague (UTC+2), but during January, I am travelling and hence I am not very available. It should get better during February, so could we schedule a Hangout/Skype call or something then? Also, depending on the volume of the work on the site, I may not be able to work on it before July. But have no problem if someone else want start on it themselves and I can join :-) ... But I believe I could find some time before then for simple redesign. Best, Daniel so 30. 12. 2017 v 11:49 odesílatel Maciej Fijalkowski napsal: > Hi Kotrfa. > > Great, we would definitely appreciate some help. I have very sketchy > internet till next week, maybe we can coordinate something next week > on IRC? What timezone are you in? > > Best regards, > Maciej Fijalkowski > > On Sat, Dec 30, 2017 at 9:41 AM, Kotrfa wrote: > > Hey, > > > > as I said, I am not a professional, but I would be willing to help with > the > > site. I have built couple of websites in Django/Wagtail (or plain HTML), > > have some basic knowledge about design (+ frontend CSS/JS/HTML). The site > > seems quite simple, so if we just did a revamp, it shouldn't take a long. > > Also, if we went with Wagtail, adding blog capabilities would be also > > trivial. > > > > Best, > > Daniel > > > > so 30. 12. 2017 v 10:02 odesílatel Maciej Fijalkowski > > napsal: > >> > >> Hi Kortrfa > >> > >> I've even paid for a design of new pypy logo that we can use on the > >> new website :-) Maybe it's a good time I spend some effort upgrading > >> it. Thanks for the reminder, it's something that's on our heads, but > >> it's not like we can just hire someone to do it for us. > >> > >> Cheers, > >> fijal > >> > >> On Wed, Dec 27, 2017 at 9:35 PM, Kotrfa wrote: > >> > Hi, > >> > > >> > thank you for all your hard work, I really appreciate it. > >> > > >> > Firstly, it seems that the website SSL certificate expired or > something. > >> > At > >> > my latest Chromium reports "Not secure". > >> > > >> > Secondly, I totally understand that there are more pressing issues > than > >> > cool > >> > website, but the current design and functionality is IMO really > putting > >> > people off. So I am going to through away some things which seems > weird > >> > to > >> > ME (and I understand it's subjective - please take it as a friendly > >> > feedback). > >> > > >> > The jQuery versions suggests November 2012, the design idea seems even > >> > older... There are old information such as "We are soon releasing a > beta > >> > supporting Python 3.3." or the fact that the donations bars are still > >> > present even though they are closed (and hence could be moved into > some > >> > blog > >> > post). Blog is also terrible, this is how it renders on my laptop (the > >> > same > >> > with the external display): https://imgur.com/a/qkjEa . The logo > could > >> > be > >> > surely polished as well (I like the idea, but it seems a bit > childish). > >> > Even > >> > though I am not professional front end developer, I am quite confident > >> > this > >> > feedback is not far from what a professional would say. It's also not > >> > about > >> > having "cool" website for itself, but that a nice projects attracts > good > >> > people. I myself am questioning how good, from technical point of > view, > >> > Pypy's project can be if the site looks like like it does and the most > >> > convenient way how to reach the devs is through mailing list... > >> > > >> > Best, > >> > Daniel > >> > > >> > ___ > >> > pypy-dev mailing list > >> > pypy-dev@python.org > >> > https://mail.python.org/mailman/listinfo/pypy-dev > >> > > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Pypy's facelift and certificate issues
Yeah, that's a very good point worth mentioning. I am not against an idea going just with a static version. po 1. 1. 2018 v 18:05 odesílatel anatoly techtonik napsal: > On Sat, Dec 30, 2017 at 12:41 PM, Kotrfa wrote: > > Hey, > > > > as I said, I am not a professional, but I would be willing to help with > the > > site. I have built couple of websites in Django/Wagtail (or plain HTML), > > have some basic knowledge about design (+ frontend CSS/JS/HTML). The site > > seems quite simple, so if we just did a revamp, it shouldn't take a long. > > Also, if we went with Wagtail, adding blog capabilities would be also > > trivial. > > Just want to warn that Wagtail and Django means database, which adds > maintenance overhead compared to current static version. Logins, spam > and all that stuff.. I don't mind against custom blog engine, but > putting all static content from version control into Wagtail/Django > database doesn't seem a good solution to me. When site gets hacked, > for example to change donation credentials, there is no trace who did > what. So going with simple static site solution is probably a better > way. It also doesn't require permission or privilege to send a pull > request, and content previews can be made with Netlify. > > Happy New Year. =) > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Pypy's facelift and certificate issues
Do you mean http://packages.pypy.org/ ? st 3. 1. 2018 v 0:22 odesílatel Barry Hart napsal: > Question about the web site -- does PyPy currently have anything similar > to this page for Python 3? > > http://py3readiness.org/ > > I think a page like this, showing which major libraries are compatible > with PyPy, could really help drive adoption of PyPy. I know for our team, > the Python 3 page was a strong reason we felt "safe" starting to make the > switch to Python 3. > > I'm not sure how we'd get this information about PyPy library > compatibility. One idea would be to install each library on PyPy, run the > automated tests, and compare the results against those for CPython. > > Barry > > > On Tuesday, January 2, 2018 5:31 PM, Kotrfa wrote: > > > Yeah, that's a very good point worth mentioning. I am not against an idea > going just with a static version. > > po 1. 1. 2018 v 18:05 odesílatel anatoly techtonik > napsal: > > On Sat, Dec 30, 2017 at 12:41 PM, Kotrfa wrote: > > Hey, > > > > as I said, I am not a professional, but I would be willing to help with > the > > site. I have built couple of websites in Django/Wagtail (or plain HTML), > > have some basic knowledge about design (+ frontend CSS/JS/HTML). The site > > seems quite simple, so if we just did a revamp, it shouldn't take a long. > > Also, if we went with Wagtail, adding blog capabilities would be also > > trivial. > > Just want to warn that Wagtail and Django means database, which adds > maintenance overhead compared to current static version. Logins, spam > and all that stuff.. I don't mind against custom blog engine, but > putting all static content from version control into Wagtail/Django > database doesn't seem a good solution to me. When site gets hacked, > for example to change donation credentials, there is no trace who did > what. So going with simple static site solution is probably a better > way. It also doesn't require permission or privilege to send a pull > request, and content previews can be made with Netlify. > > Happy New Year. =) > > ___ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > > ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
