2015-03-21 10:51 GMT+04:00 Loganaden Velvindron <loganaden_at_gmail.com>:
>
> That would be a contractual agreement. Once I'm done writing the
> plugin, I would move to another project. You can't expect a contractor
> to be held responsible once the product is shipped, because of some
> bug that later turned out to be a security vulnerability. If such is
> the case, and at the same time, I'm getting a better contract with
> another client, then, I would go work where there is more money, and
> choose the other contract.
>
Not a bug, let's say a backdoor as you mentioned previously. What will be
your stand then?
> However, when a person is an employee, he will have to answer later
> on. That's what we are looking for here: a structure put in place
> where the employee(s) work full-time, drive the project, and maintain
> it. We don't want changing sub-contractors after each feature
> request/major rewrite, and be left with legacy code, and layers and
> layers of code added on by later developers who have no clue what the
> previous developer did.
>
Wait. You have been mentioning the word "employee" several times while I
offered SM my "help" to write a proposal and clarified I am not available
to "work" for free however. SM in an earlier email expressed that he
understood what I meant by the words "help" and "work".
Did you understand the use of those words?
> For the new .mu to be successful in the long term, we need employees
> who will commit themselves in the long term, and lay down a strong
> foundation and a well-executed growth plan.
>
Can you force your employees to be dedicated and committed? How do you
ensure they will be?
Do you propose SM to be an employee? Employed by whom?
Regards,
Ish Sookun
*- Geek by birth, Linux by choice.*
* +-+-+-+-+-+-+-+-+-+-+*
* |H|A|C|K|L|O|G|.|i|n|*
* +-+-+-+-+-+-+-+-+-+-+ *
*
https://twitter.com/IshSookun <
https://twitter.com/IshSookun> ^^ Do you
tweet?*
Received on Sat Mar 21 2015 - 07:00:26 PST