Jump to content
thirty bees forum

doclucas

Members
  • Posts

    162
  • Joined

  • Last visited

Everything posted by doclucas

  1. @MockoB Prestashop was just an example of a project that I know you are familiar with, which I listed because you wrote "I can’t imagine open source project with CEO, I think that both are completely incompatible conceptions." Not to vouch for their CEO's performance (which may or may not be good, I don't form opinions based on your forum or Safari experiences :rollingonthefloorlaughing: ) . Seems like most people don't know much about large & successful open-source projects and how they are being managed, so I will skip further public discussion about these matters as they seem to lead nowhere productive. If anyone really wants to learn more , I suggest you google projects like: OpenCog, Kubernetes, Magento, Red Hat, Ubuntu, Wordpress and many many more.
  2. @MockoB There are practically zillion open source projects with CEOs/CTOs etc. (some are/were doing amazing job and some not so, but I digress). Here is one project you probably know: https://www.prestashop.com/en/press-releases/2018/03/08/prestashop-appoints-alexandre-eruimy-as-its-new-ceo-and-launches-prestatrust-a-traceability-system-based-on-blockchain-innovation
  3. @lesley I don't know where the statistic is from, but I sure hope your software will be the #1 ecommerce platform on the market. I will do what I can to help. :)
  4. @vincentdenkspel Isn't that book about getting to have great leadership (for example, a great CEO) that inspire people?
  5. @traumflug (Before I start, I have a lot of respect to all the people involved in this project, I am here voicing my own opinion and only trying to help.) Plenty of examples in history that completely contradict these claims. Of course people who are not convinced of something and/or not enthusiastic about their work should simply not be there, IMHO. Plenty of talented programmers, QC and other personnel are available on the market to take their place. A proper hierarchy and smart & experienced people in charge to direct the project can take it to amazing heights. I don't want to hurt anybody's feeling, but a project that is on the market for over 1.5 years with such a small adoption rate and backers isn't really a great progress. I have some great ideas (IMHO) and I would be happy to invest nice money in the project, if the founders are interested in a brighter future. @lesley We both know that the release doesn't have only a couple of bugs, but I generally agree that a few bugs are not enough to pull a release, yet it depends on which bugs. If we are talking about so obvious bugs like the AJAX "add to cart" not working at all, that's a major and obvious bug that doesn't reflect well at all on the development team, the software and the project as a whole. 2 users installing betas brings me back to the small adoption rate discussed above. If the software gained a lot more popularity (as it deserves and able to, I believe) - then betas could have been tested by far more people...chicken and egg, again. :)
  6. By the way, I said crowd funding is failing because of the apparent failure of Patreon. I didn't see any other campaign.
  7. @lesley said in Say hello to release 1.0.5!: I wouldn't say the crowd funding is failing, we have met all of the goals in so far as our indiegogo campaigns. 1.0.5 was less stable than expected, but really there are only 2 version specific bugs in it. One is where we have changed a huge part of the software, because the original developers were lazy and wrote it insecure. The other was a front end bug I introduced. Some of the bug reports you see are not 1.0.5 specific, they are just discovered old bugs showing their faces from the core. When you say "less stable than expected" and" 2 version specific bugs", could you kindly elaborate? And which front end bug did you introduce? (a bit confused) Thanks
  8. @vincentdenkspel said in Say hello to release 1.0.5!: @doclucas said in Say hello to release 1.0.5!: The intentions are (IMHO) good. The same goes for the developers. So even if this release should not have been released (i don't have an opinion about it because i have not enough knowledge about coding) there is no need to be aggressive. Saying the software shouldn't have been released with such obvious bugs in basic functionality isn't being aggressive, it's the truth, especially for a project that promotes itself as being the project that cleans up PS 1.6 bugs. I have no doubt the developers (and founders) have good intentions, but there is a proper release cycle that a good software should go through before being introduced to the public as a final build. For example, I don't see any kind of beta builds listed or changelog (although I may have missed them, so feel free to point me to the right direction). If there were betas, nightlies etc., these kind of bugs wouldn't be introduced in a final release in the first place. Yes, there are always bugs in every software, but shouldn't be so obvious and basic ones. If it was me, and I care about my project, I'd pull the release, revert to publish the last known stable release, fix the new release and launch it again. That would create much more confidence in the software and the team.
  9. @MockoB Frankly, I am not into one-man-show projects. I have seen many open-source projects go down hill just because of that reason. No offence to anyone specific. Such a project must be a team work (or at least a work of several highly skilled and experienced developers) and properly managed by a serious CEO. It is clear the crowd funding is failing at the moment, thus another approach must be taken or the project will eventually die. I am open for business discussions, if the founders wish to talk. My contact details are registered on the site.
  10. @pelnykoszyk_pl I have added a code change here: https://github.com/thirtybees/thirtybees/issues/551 You may try it and let us know if it works.
  11. @piet said in Say hello to release 1.0.5!: @testtb4store there is a lot of negative vibes in your posts, I wonder why is that? Maybe because reporting bugs can not have a positive vibe to it? Look at github and see all the bugs that this version has and you will come to the same conclusion that this release should have gone through some additional QC before getting launched. If basic things like full page caching and AJAX add to cart are broken on a vanilla installation, then this must not have been released. period. https://github.com/thirtybees/thirtybees/issues Some people have the money to back the project with that. Other contribute with bug reports, others with bug reports and fixes etc. etc. Each person does what he can do to contribute and there is no reason to bash someone for saying that, even if it done aggressively. The intentions are (IMHO) good. I am here for a totally different reason, tho. I am a programmer and an investor and was looking into this promising project in order to invest greatly in it. I am saying promising because I have read the great posts by the founder and was led to believe that this project is going to be managed much better than Prestashop. Seeing buggy releases such as 1.0.5 (the first I ever tried unfortunately) and the very slow development progress, don't make me very hopeful. I realize that it's chicken and egg, you gotta have money to be able to work on the project, but I think that at least for the beginning, some major compromises must be done on the part of the founders to make this a very high quality product to begin with, as nobody is going to invest on an e-commerce system that is very buggy still, while there are so many great, popular alternatives out there. I am still interested in making very nice investments and becoming part of this company, but major changes will have to happen. Contact me if you want to discuss.
×
×
  • Create New...