Let me clarify what I think Bob is referring to about contributing to the Cincom Smalltalk code base in the VWDev program;
First, if you are testing a feature in development and discover issues with your valid use of it (and report it, code fix optional) that contributes by making sure our released code works with your (customer) needs.
Also we do "partnered development" on a case by case basis, with customers, for some features. For example, if three customers need the new "xyz" protocol available, and can commit to timely testing, we will work with those customers to make sure the protocol works for their needs (sometimes unique). This is a real win-win; the customer knows it will work for them when it is released, and Cincom knows it will work for our customers needs.
Both these scenarios could have parts of customer contributed code used, or the code can influence the solution, or be used as a starting point to contribute to the product level solution.
Regards
Arden
Arden Thomas
Cincom Smalltalk Product Manager
845 296 0686
Cincom Smalltalk - It makes hard things easier, the impossible, possible
"Simplicity is the Ultimate Sophistication" - Leonardo Da Vinci
On Feb 18, 2012, at 4:58 AM, Bob Calco wrote:
Or join their developer program, in which case you get all their products, including those in beta and early release, and are able to experience a feedback loop that gives you a more realistic taste of the rigors of their in-house development process. But, to be clear, they have that program specifically for people who wish to contribute potentially to the code base, to have their ideas affect CinCom's direction more directly. So if you're *really* serious about contributing to VW, and have the time, that is an alternative.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
