485 reputation
1411
bio website
location
age
visits member for 3 years, 7 months
seen Feb 19 '13 at 16:32

Jun
17
comment Mix three different licenses for an open-source software
So now I am convinced: LGPL for the framework, GPL for the app, CC for the artwork. My problem is you and @ammoQ have the same answer, only one more concise (ammoQ) and one more detailed (@David Thornley). Which do I check as the right answer? Is there any SXchange policy on this?
Jun
17
comment Mix three different licenses for an open-source software
Meh...You are right. I guess that whole part was silly from start.
Jun
17
revised Mix three different licenses for an open-source software
Added some details that seemed to lack after reading the answers
Jun
17
comment Mix three different licenses for an open-source software
LGPL & CC for framework & artwork, ok. But I don't want to force people to release derivative works under an open-source license. If my framework is used in a larger app, I just need, for example, a link to the source in the "about" page, or in the footer. It doesn't make sense to force someone to release an app open-sourced if my framework contributes to 50% or less of the code.
Jun
17
awarded  Commentator
Jun
17
comment Mix three different licenses for an open-source software
Furthermore, I have a personal grudge against large companies and I would like to do my part in promoting freelancing and freelancers networks by allowing freelancers to use my code as much as they like to, but disallow large companies from doing the same. I guess if it gets too complex, I can forget about that too.
Jun
17
comment Mix three different licenses for an open-source software
Point taken. But I really don't want to see a lawyer, it's not that important. I mean it's a one-man job, it'll never compete with larger frameworks out there such as codeIgniter or cake, and I don't want to give it more time than necessary. As I commented to ammoQ's answer, I am trying to do a little self-promotion along releasing a framework that I deem useful (and simpler than the examples cited), so I would like to protect my own framework as the main reference for projects that stem from it. But that goal is less important than just releasing the framework and allow people to use it.
Jun
17
comment Mix three different licenses for an open-source software
I guess so...I have never released anything public so maybe I am being too cautious. I am doing this as a payback for the open-source community that has given me so much over the years, but also for personal promotion. Although the personal promotion part is less important so if it gets too complex, I can just release under a regular open license and forget about worries.
Jun
17
comment Mix three different licenses for an open-source software
I am doing this to make sure there can't be two exact same versions of the framework, with two different names. What I want is to forbid people from selling the framework as-is. If they add anything to it, the littlest thing, or fork it, then why not. Would this be against FOSS principles?
Jun
15
asked Mix three different licenses for an open-source software
May
15
awarded  Teacher
May
15
answered How to apply one of the OOP concepts (Closed for Modification and Open for extension)?
May
15
comment database schema with unlimited hierarchical data that is modified a lot
the read about couchDB was very interesting and I see what you mean. It is a viable solution (probably, I haven't looked into it extensively), but I would like my app to be portable and flexible, so I'd rather not be tied to a particular technology. I'll still read further before deciding
May
14
awarded  Editor
May
14
revised database schema with unlimited hierarchical data that is modified a lot
edited to explain the concept further
May
14
comment database schema with unlimited hierarchical data that is modified a lot
It's not a single linked list...In fact, my bad, this is not clear in my original post. I am looking for a mixup of forum/mindmap, so any node can have an unlimited amount of siblings/parents/childs.
May
14
comment database schema with unlimited hierarchical data that is modified a lot
I am indeed in a situation needing many insertions. But I am also in a situation where a node can have an unlimited amount of parents. So I would need a table to store relationships. I don't see anything particularly difficult or weird there; I am just wondering if there isn't anything better, specially to retrieve large amounts of relations, and be able to stop loading of nodes after a certain level of recursion.
May
14
awarded  Supporter
May
14
comment database schema with unlimited hierarchical data that is modified a lot
It is worth considering, but my main problem is, even at the stage of POC, I'd like to provide a working theory, even though the DB calls could be unoptimized. I'd rather have a good theoretical backbone with slow calls and iterate optimizations. And frankly I can't really see a file structure that would be actually efficient. If you have anything to propose I am open to all sorts of suggestions
May
14
comment database schema with unlimited hierarchical data that is modified a lot
This is very interesting. If anyone's still following, I found info on materialized paths (had never heard of them) and more here: communities.bmc.com/communities/docs/DOC-9902. However, I am really having trouble wrapping my head around this. It still seems the easiest way to go for now though