@tykus_ikus kinda, but Taylor isn't writing the code used to do the actual database management, I am writing my controller code, model code, and view code, the framework is merely a skeleton to get started. For example I used to use Visual FoxPro compare the Framework to Visual FoxPro. I did not have to write Visual FoxPro myself first to use it as a database management program.

Tomatos...

The point was made earlier that a good forum package would be a great addition to someone's project - but it's not the meat of their project, just something to enhance it. A framework is similar - we are leaning on the framework (code written by others) and instead writing what is unique (and interesting) about our project.

In any case, it's @JeffreyWay 's to do with as he pleases; he shouldn't be obliged to open-source this, and others shouldn't be pilloried for asking.

@tykus_ikus I will agree with that. I am one of those that doesn't use datatables, even if there was a package so easy, no thought was required to have paginated tables, I would still not use it I'd actually write my own html tables.
Put another way, if someone wanted a forum or datatables, fine, but I think they should know and have written their own first for the learning curve. Even if they did it just for learning and never used it. I think they would at least appreciate, and see the work that went into it.
We have become too much of a "I want it now", "One click fix all" society.

To add, you folks are right, Jeffrey can do what he wants with the code, I will not argue that point. But my opinion is that he has done too much work to just let it go that easy. Maybe he should open source parts, and leave it to the user to learn and fill in the missing code. That way someone might actually learn something.

@jlrdw

Let me make this clear first. I totally understand what you are trying to say. The value of self learning is very powerful. With this I totally agree with you. Yes, I also agree with your complaint about society.

However, what I disagree with is that using somebody else's package can save time, reduce mistakes, and possibly even improve the security of your code; even if it means that you loose the benefit of educational. This is what I mean by DRY. Another point to consider is what happens if you are building a proprietary software for a customer? Is your code completely documented and have easy to understand procedures in place so that the next developer will not have to spend time trying to catch up with your code compared to a well known and used library or package? What do you do when you have a paying customer that needs something done fast and say a "forum" needs to be included? Will you be able to put tested code into place within the time frame?

Please don't misunderstand me! I have never seen your code so I'm not saying your code is good or bad but rather just trying to say that their are times when a package is a choice that you will need to make.

Peace brother and I'm sorry that this simple topic turned into lots of extra posts.

@andy okie dokie all agreed on that then.

@JeffreyWay I'm topping up this question. Forum open sourcing would be great!

There's currently a "lets build a forum" series that is ongoing, if that isn't sufficient, there are also already a bunch of existing open source forum options. Not a lot that are laravel specific especially as a package, but even those exist, including this one that even looks a lot like the laracasts forum.