in reply to Open sourcing perlmonks
But, the accusation that *none* of the proposed features get implemented, is not true. Some do, occasionally, some pmdev will jump right on a feature, that they would also use/think is a great idea, and create a patch for it right away. Usually the suggesting node gets replied to with "I patched this, wait for someone to apply it", or even "Patched and applied".
Not every suggestion *can* get implemented. Some will just bring little gain while bogging down the server, some will wait on other changes which are still being tested, some will just not fit in to the site as a whole. Of the rest that can, and nobody jumps at, I would guess most of them are significantly complex that our volunteers need a bunch of time. Some of these get started on and not finished, which the person suggesting it will probably never find out about.
So, having said that, my suggestion to people suggesting site improvements: Help the pmdevs, break down your suggestion into small chunks which are easier/shorter to add, try and think up reasons for and against them before you post, be ready for someone to say "sorry, we just cant do that".
Ok, I will comment shortly on the other issue. Even if PMs code was available to all, we would keep pmdev group, the patch system and the gods-only-applying system, and thus a stable site. So the only gain you have is that people could try and figure out if their suggestions can be done, before posting them. The code is probably complex enough for that to take them a while, or disuade from even looking, though.
And no matter what you say about security and obscurity, although it should never be used as the only deterrent, hiding the code *does* give us the advantage that anyone wanting to misuse the site has to try things out, or mine the data that gets sent between their browser and the site, and not just search for the appropriate piece of code in the source.
C.
|
|---|