hi all, im planning to release some code into open source, and am wondering what would be the best approach. Im using fuelphp, and right now it's just using the standard models/controllers etc.
I would like for people to be able to clone this project from git so people are ready to go immediately.
Would the best way for this to be to just fetch/merge upstream fuelphp into my own project whenever necessary and maintain my own git repo for this project? Or would it be better to have people clone fuelphp, and then clone my project as a module? Im a little worried about versioning issues then. How do others do this?
the answer is "it depends". You have two system to extend a fuelphp application:
Modules, they are application extension. An example are a blog, a forum, a gallery
Packages, thery are functionality extension. An example are captcha, a library, an authentication. Usually something that doesn't have a front-end part
It's a little like yousendit but due to security concerns we cant have the data in the cloud. My company needed some specific functionality, and since we prefer open source and couldnt find something that fit well, we're just building it ourselves. We plan to put it on git for anyone to play with. It's built around fuel and im just not sure what would be the best thing to do. Include fuel into our git repo or not.
I think the best thing is to link fuel, not to update it: if you want an example to understand how it works, you can check scrapyrd on GitHub: if you try to download it you won't find Fuel or other packages, but onlye the source code of the application.
By the way if you navigate on github you can find every link in the proper section, so you can recreate the entire application, but each part is stand-alone.
Harro sorry, can you send me to a good tutorial for composer package? I know fuel is moving to that direction, but I didn't find some useful tutorial...
Donate
