Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


The learning curve for developers to become valid for a large open source
project is particularly steep (git, java,perl, python, c ++, c #, project
architecture, project philosophy, .  many, too many technologies, to learn
in a short time).
Who, like me, every day develops Windows desktop applications (. NET)
without a strong source control system in considerable difficulty.
I use only some basic functions of svn.

Probably the biggest problem is the development philosophy that is radically
different.
Windows developers who use only the tools found in the MSDN think in a way
totally different from those who develop an open source project with open
technologies.
I have a long past of system administrator and I know very well Unix shell /
awk, but I'm not developing Linux applications.
I believe that in addition to the information in the wiki is interesting to
provide some simple scripts that allow you to quickly start the initial
work.

I think it is necessary to find a way to reduce the gap between these two
environments in order to facilitate the windows developers to enter the
world of open source technologies.
In http://pastebin.com/u/walterLO I will upload some simple scripts that
might be of interest to developers who are in my same position.
can you check their validity?
If you think that these simple scripts are useful feel free to post them in
the wiki.

 

Regards

walter


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.