Open sourcing project

I designed and built several projects (50k lines of approximately 50 projects) around the JBoss Seam structure that I use when creating websites for clients. In fact, I developed a content management system in which various modules can be connected.

What will I get through an open search for projects and how much will I lose?

If I open the source code, the projects can be beneficial (reduced errors, more efficient code, etc.), but with the potential loss of third-party parties using the projects, not missing me to create a website.

It can be a good exposition so that my works and ideas are there.

Any thoughts?

You guys have a lot of good answers, it's so hard to choose one - I do it with the wiki community.

Walter

+3
source share
7 answers

It depends on how good / useful the project is and how much you buy for it.

At one end of the spectrum, you get a bunch of recognition, on the other - the code disappears into obscurity and you get nothing.

In general, although you will have to invest a lot in it as an OSS project in order to get something, and if you cannot or will not make this commitment, it is probably best not to go down this road.

In terms of what you gain / lose, essentially transferring your intellectual property, I would see that in this case, as a little secondary. Knowing the code is better than anyone else in the world (and most likely it will remain), you will always be able to use it better than your competitors.

, , , , , , "" , , .

+1

, , . , , - , . , - (AKA, ).

, - , , .

, , , .

: - , ... , (, GPL3), . , .

+2

-, . ?

0

. , , , , ... .

0

- , , . 30- . . QA. Ranorex . .

0

IHMO- # 1 . , , . , , , .

, ​​ GPL, ; , , .

0

. , .

, , . 1- ( - , , ) 2- ( / ​​ ..).

0

Source: https://habr.com/ru/post/1728633/


All Articles