Jump to content
thirty bees forum

AnnaLisik

Members
  • Posts

    23
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by AnnaLisik

  1. On 4/28/2020 at 1:11 AM, Traumflug said:

    They apparently release from more than one branch

    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.

  2. @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....

  3. 1 minute ago, toplakd said:

    I left that server, as in my opinion that discussion is not going into any usable direction.

    There are better ways spending time than reading a debate that leads nowhere 🙂

    Sorry to see you go.

  4. 2 minutes ago, Theo said:

    Thanks. I believe he should also be added to the private Forum thread that Lesley created. So he can get a background of some of the ideas that was discussed. @lesley

    What private forum are you talking about? Can you PM me a link please?

    EDIT: @musicmaster just joined Discord 🙂

  5. 2 minutes ago, datakick said:

    hat also means that thirtybees has already over 200 forks, so no need to worry 🙂

    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?

     

  6. 5 minutes ago, Briljander said:

    I agree that there is a lot of work and effort

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

  7. 34 minutes ago, dynambee said:

    Correct.
     

    I'm sorry, but did you read my previous post at all? There is a huge amount of work that would need to be redone from scratch if the project is forked. Website, SEO, blog (all existing posts & knowledge gone), forums (all existing knowledge, discussions, & users lost), social media, module shop, existing supporters platform, etc. If it is absolutely necessary to redo all that work then fine, it has to be redone. I'm curious though, are you volunteering to pay someone to do it? I expect it will be quite expensive to duplicate the level of branding & design that already exists, and yes, branding and design are important if one wants to be taken seriously as a business, project, & platform.

    Personally I don't think it is a good idea to reinvent the wheel unless there is no way forward that can save all the existing work.

    Edit: I'll also add, a fork would mean needing to redo the existing core themes and edit the codebase to change everywhere the TB name appears to be the new name. This may sound trivial but it took ages for TB to get that right. I think even now there are times that PS pops up where TB should be instead. It's just more work that needs to be redone, duplicated effort. Starting with a completely existing platform means all effort can be spent on pushing the project forward. Forking means a huge amount of effort has to be wasted to redo work that has already been done once.

    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.

     

    Quote

    duplicate the level of branding & design that already exists

    There is absolutely no need to duplicate anything.....

     

    Quote

    Starting with a completely existing platform means all effort can be spent on pushing the project forward.

    Thats exactly what I understand when talking about fork

     

    Quote

    edit the codebase to change everywhere the TB name appears to be the new name.

    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

  8. 38 minutes ago, dynambee said:

    It would be better to keep the existing brand, website, forums, repos, module shop, supporter payment system, (and more) in place.

    In this case the only (?) thing that would change is the owner, right?

    38 minutes ago, dynambee said:

    Forking would be a last resort, IMO.

    why?

    Oh, and forking does not need to mean rebranding; in this case rather save brand, but change owners.

  9. 1 hour ago, toplakd said:

    I was wondering how come you have not registered before, as being heavy user you've most likely have had some issues or suggestions regarding the modification.

    Let me answer you: I did not register as Im self learner, and, if/when problem arises, I like to solve it myself.

    • Like 1
  10. 1 minute ago, zen said:

    That is true.. who are you thinking about for taking the ownership of the repo ?

    Someone who has managerial skills probably, who is with the project from start, who has the most accepted PRs, whatever.... criteria is one thing that needs to be established.......

    It would be nice if owner of the repo = project leader.

  11. 1 minute ago, Theo said:

    @AnnaLisik same reason as @zen with the addition of existing revenue from Supporter base + Partners. If we can help it. 

    Im affraid Im not following what you were trying to communicate here?

  12. Just now, zen said:

    it's still possible to not break TB reputation (even if it's small) if it's not forked, and keep on increasing it while keeping brand, logo, forum, community etc..

    I agree, but on the other hand, reputation follows the project, and - correct me if Im wrong - the only person that will change is the repo owner. Correct?

    All I want to establish is that if people ( = potential devs) would come to the repo, they will see known (and well-established) nicknames so they will instantly catch.

  13. 4 hours ago, Theo said:

    @datakick @lesley @everybody concerned. Is it not time that we have meeting to discuss this??
    Can the community not create some sort of "TB Foundation" / Committee and nominate a leader + we all figure out the rest together?

    Hey everyone, I can create fork of TB as Im heavy-user as well as customizer (my customization are internal only) so I know codebase quite-well and thus I can lead a fork. But Im not going to take-over company.

×
×
  • Create New...