[Discuss] Request to the community

[Marcia K Wilbur]

Good one.

Actually, and going along with that, I would say that in the  
development cycle, there is a big difference.

I had never actually experienced a windows shop development  
environment until recently.
Since we are open, and share code, we don't really need to worry about  
things like proprietary files going along with our code to keep it  
"secret" or encrypted. Like for example .snk files.
I work on a fork of remastersys (linuxrespin now) and we are  
completely open with our code. We work together using GIT and share  
updates. We have a changelog and chat in IRC. Sometimes we use  
ventrillo to collaborate. We actually meet in person also.

 From what I've seen in a few meetings I attended for Windows devs...  
they have this thing called a Code Review. I like to call it "Show and  
tell for programmers".
Even if they just changed one thing from 10 to 21, they show it.
Their coding is inferior. I apologize, but it is in my experience.

Instead of functional requirements documents or business requirements  
documents, they call new "features" bugs or issues.
Maybe it's just the shop I have seen.

Open Source development teams are different. It gets really  
interesting when you have Free software people working with Open  
Source People. Then, it's a challenge. The Open people might want to  
use Google Hangouts and groups while the Free Software people would  
never and want to use Etherpad.

Anyway, if I could, I would always select in this order:

1. Free Software Project
2. Open Source Project
3. No Projects or the long sleep...


Check out Karl Fogel's book on projects:
http://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590



Quoting Jack Coats <jack at coats.org>:

> unless you are Ubiquiti evidently ... :-( ... bummer, I like their
> equipment. ... ubnt.com
>
> Their equipment is based on open source software, but they don't seem to
> think that they have to make available what they use, just some version.
>
> On Wed, Apr 8, 2015 at 6:03 PM, Dan Ritter <dsr at randomstring.org> wrote:
>
>> On Wed, Apr 08, 2015 at 04:26:14PM -0400, Bruce W wrote:
>> > Hello Boston Linux Community!
>> >
>> > I am looking for three software developers who would be willing to
>> discuss
>> > their experiences writing and developing open source software products.
>> > The conversation will take about 30 minutes and I will be asking about
>> the
>> > differences between open source and proprietary software development.
>> This
>> > is not a job interview nor is it a sales/marketing pitch.  I will not ask
>> > you to discuss anything that is proprietary or personal.
>>
>> It's really very simple.
>>
>> When you work in proprietary software, any time you buy somebody else's
>> product/library/application/service, you need to pay them and also follow
>> the terms of their proprietary license.
>>
>> When you work in open source software, you need to follow the
>> terms of their open source license.
>>
>> When you produce whatever product or service, you need to be in compliance
>> with the terms of the licenses of all the products you used, proprietary
>> and open source, or else you will be sued.
>>
>> See? Very simple.
>>
>> -dsr-
>> _______________________________________________
>> Discuss mailing list
>> Discuss at blu.org
>> http://lists.blu.org/mailman/listinfo/discuss
>>
>
>
>
> --
>> <> ... Jack
>
> "Whatever you do, work at it with all your heart"... Colossians 3:23
> "Anyone who has never made a mistake, has never tried anything new." -
> Albert Einstein
> "You don't manage people; you manage things. You lead people." - Admiral
> Grace Hopper, USN
> "Tell me and I forget. Teach me and I remember. Involve me and I learn." -
> Ben Franklin
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss