Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

AnnaLisik

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Inside composer.json there is dependency of satooshi/php-coveralls, whereis by Googling it one can find that this package is deprecated Proof here
  2. Is it even doable in Git (as a version system; not GitHub)? I think protocol prohibits this. But GitHub does not allow this for sure.
  3. @Chandra some food for thought. When Im presented with new things for me, first thing I do is to gather as much info as possible about new product. So I went straight to their web and few huge no-go popped up instantly: 1. SubPage Pricing. Standard/Pro/Self-hosted. Standard tactic = minimum amount of users while price per user is whats written in larger font, so to get your price, you need to multiply price/user * users count; 2. Self hosted plan. First bullet = Hosting included followed by barely visible question mark with hoover that says "managed hosting on our servers". So, self hosted or hosted by them (and surely paid extra)? Im more than sure there are many more no-go's, but above are major ones for me. Honestly, their product may be of outstanding quality, but the above disqualifies it for good in my case. I will not trust company that uses such tricks. Sorry. Edit: Just looked at thier repo on GitHub and guess what? their software does not even pass build step. Yeah, may happen, Worrisome, but still can happen. But, master branch was last updated (commited to) on 23th of July 2019. Want more? Here you go: 855 releases. Many, but ok, till you click on it: last release (12.7.1) was made 4 days ago, and - now grace yourself - 885 commits since than (since 4 day) : wow, they must be cyborgs that operate 24/7..... its around 2 commits per second....
  4. AnnaLisik

    Goodbye

    Sorry to see you go.
  5. AnnaLisik

    Goodbye

    As of @wakabayashi he is unbanned now; This was simple misunderstanding. Simple as this. No bad feelings involved. Sorry for this. As of @M4ketech sure, will send him an invite 🙂
  6. AnnaLisik

    Goodbye

    @Theo Aaa this one. Than Im also in. You are correct. OK will send the m an invite Sent 🙂
  7. AnnaLisik

    Goodbye

    @netamismb probably yes 🙂 @Theo I still have no idea which topic you are talking about?
  8. AnnaLisik

    Goodbye

    What private forum are you talking about? Can you PM me a link please? EDIT: @musicmaster just joined Discord 🙂
  9. AnnaLisik

    Goodbye

    @Theo Ive sent an invitation. Now its up to @musicmaster and @Occam to join or ignore it.
  10. AnnaLisik

    Goodbye

    How many of them is successful and can be recognized as a fully blown successor of TB? @dynambee I dont (fully?) agree with loosing things like forums/blog, website, knowledge, partners etc. Why did you say TB would loose it?
  11. AnnaLisik

    Goodbye

    Effort yes; lot of work: also yes. But its the same with every project that wants to be/is successful
  12. AnnaLisik

    Goodbye

    Now I get it :: in your concept fork = start over. But no. By fork, I understand taking the code as-is, just changing the owner of repo and push/pull paths. Thats it! No need for redoing anything. Just change owner, than change push/pull paths locally and off we go - the project is ready to accept contributions. As simple as this. There is absolutely no need to duplicate anything..... Thats exactly what I understand when talking about fork Yes, of course. But, only if new fork is going to be given new name. Thats a breeze. In most IDEs there is an option that will allow you to do this
  13. AnnaLisik

    Goodbye

    In this case the only (?) thing that would change is the owner, right? why? Oh, and forking does not need to mean rebranding; in this case rather save brand, but change owners.
×
×
  • Create New...