Alessandro On Thursday, June 5, 2014, Alessandro Sangiuliano <[email protected]> wrote:
> > Il giorno 04/giu/2014, alle ore 09:11, Gregory Casamento < > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> ha scritto: > > Would these companies and/or contributors be more inclined to contribute >> to the project if portions of it were GPLv2 over GPLv3? >> > Yes because there is apparently a no gplv3 policy in some conpanys due to > gplv3 patent restrictions. > >> Do they have a history our contributing to projects under GPLv2 over v3? >> Have these contributors submitted any patches to GPL projects? >> > Yes. > >> The reason I all these questions is because I do not see why a company or >> contributor would be so fervently again the GPLv3 but not v2. >> >> See again regarding patent restrictions in gplv3 > >> If it is am entity that has goaltending contributed to an educational >> license, such as BSD or MIT, be more inclined to contribute to a project >> licensed in such a manner? If so, relicensing to GPLv2 gains us nothing as >> the licensing objections would be still be present. >> > Gplv3 seems also to be hated by many developers including many of our own. > > > +1 > > This particular decision does not affect me any as my major contribution, >> CoreBase, is already LGPLv2.1. >> >> Over the decade that I've been involved with this project, beginning as a >> user and now as a contributor, I've read arguments about how a trivial >> solution, such as this one, would increase contribution. >> > No one is saying any one thing is a panacea.There are a myriad of issues > with gnustep only one of which is licensing. > > Also, I disagree that licensing is minor. Licensing affects how the > software can be used. So I would say it's very important. > > Other issues with gnustep are that there are many fundamental things which > currently don't work properly. Printing being one of them. Our default > look is unattractive, outdated and generally gives a poor impression, we do > not do a good job of inviting change and encouraging contribution. We do > not promote ourselves very well. The list continues. > > > For the look, I asked help in the past with the rick theme, because me and > Riccardo got busy, the theme is at a good point, I use it every days, it > needs some minor fixes, tabs implementation. > I asked help, saying that the code is on github, fork it and help please! > Gregory helped me a lot with advices in that period on the etoile IRC, but > as I said then I got busy, I had to work too. > > I link again: > > https://github.com/AlessandroSangiuliano/rik.theme > > There’s also an experimental dbuskit integration. > > > Thanks > >> Stefan >> > GC > > Thanks. I was just thinking of this theme the other day. > > If my opinion could count something, I think gnustep needs: > > All opinions count. > 1) Better quality code, I would propose a debugged release where features > implementation is frozen, focusing just on bugs fixing. > Indeed!!! > 2) A modern look & feel, without cutting out the old theme for NextStep > lovers; just give to people the possibility to choice. > Yes. There are a few candidates I would consider nominating for this including your theme. 3) Marketing. I mean: video, tutorials and so on to advertise gnustep > attracting developers. > An excellent idea. > > Alex. > > GC -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
