3 ms·

> I agree with you, but open source software is given as-is, in any context, But if you are calling somebody or something "professional" what you are saying is

> I agree with you, but open source software is given as-is, in any context, But if you are calling somebody or something "professional" what you are saying is they act as if they were doing it in a certain way. If they don't follow the practices it does not matter if they are doing it for free. It is like saying a kid is doing something professionally (even if he is not) and argumenting that it is because he isn't paid for it.

lnxg33k1 5y ago
I think symfony developers are still good professionals, given the size of the project and the amount of contributors, having an error or not having a test case for something specific could be forgiven, I would reply that errors and bugs can slip in a codebase, I guess it's more important to create a test case to double check that a bug doesn't re-appear in the future after it has been fixed? I mean I fail to understand what are you trying to say, someone stops being a professional as soon as it hasn't covered a test case? Or are they kids just for having slipped a bug? Despite their work powers a lot of companies software (including the ones I work for) Are you just trolling?
- lmilcin 5y ago
  The statement was that they acted professionally. I don't know if they are or are not professionals. It is just my opinion that being nice and prompt about removing cause of the damage after they have caused damage through recklessly ignoring industry standards cannot be reason to call their entire set of actions around this particular issue as "professional".
  - jasonshaev 5y ago
    FYI, the GP comment said "The issue was resolved/disclosed very quickly, and in a professional manor." So they didn't say their "entire set of actions" was "professional" just that it was disclosed and resolved professionally.
  - 420official 5y ago
    It shows lack of experience to suggest having a gap in testing is somehow "recklessly ignoring industry standards". If you look at Symfony's test suite it's clear that they take testing extremely seriously and keep their tests up to date in a way that's far superior to my experience with "industry standard". If you look at the fix for this issue which is linked from the OP you'd see that the first thing they did is add a unit test to prevent this kind of issue from happening again. If you consider that kind of behavior recklessly unprofessional I'd be amazed to see the kind of tests you write for your code.

lnxg33k1 5y ago

I think symfony developers are still good professionals, given the size of the project and the amount of contributors, having an error or not having a test case for something specific could be forgiven, I would reply that errors and bugs can slip in a codebase, I guess it's more important to create a test case to double check that a bug doesn't re-appear in the future after it has been fixed? I mean I fail to understand what are you trying to say, someone stops being a professional as soon as it hasn't covered a test case? Or are they kids just for having slipped a bug? Despite their work powers a lot of companies software (including the ones I work for) Are you just trolling?

lmilcin 5y ago
The statement was that they acted professionally. I don't know if they are or are not professionals. It is just my opinion that being nice and prompt about removing cause of the damage after they have caused damage through recklessly ignoring industry standards cannot be reason to call their entire set of actions around this particular issue as "professional".
- jasonshaev 5y ago
  FYI, the GP comment said "The issue was resolved/disclosed very quickly, and in a professional manor." So they didn't say their "entire set of actions" was "professional" just that it was disclosed and resolved professionally.
- 420official 5y ago
  It shows lack of experience to suggest having a gap in testing is somehow "recklessly ignoring industry standards". If you look at Symfony's test suite it's clear that they take testing extremely seriously and keep their tests up to date in a way that's far superior to my experience with "industry standard". If you look at the fix for this issue which is linked from the OP you'd see that the first thing they did is add a unit test to prevent this kind of issue from happening again. If you consider that kind of behavior recklessly unprofessional I'd be amazed to see the kind of tests you write for your code.