Timeline for Should SE partly open source their code?
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 5 at 8:30 | comment | added | B-Tech | @CPlus Downvoting is the default action on meta no matter the actual content. | |
| Mar 5 at 8:28 | comment | added | NoDataDumpNoContribution | @CPlus It doesn't but people vote like this almost forever and everywhere. Just look at all the negatively received company posts. They aren't feature requests either, and aren't written so badly as to warrant hundreds of downvotes. | |
| Mar 5 at 8:23 | history | edited | NoDataDumpNoContribution | CC BY-SA 4.0 | streamlined |
| Mar 4 at 19:13 | comment | added | CPlus | Why was this downvoted? This is not a feature request, but rather a discussion, so I do not see how 'downvotes indicate disagreement' applies here. | |
| Mar 4 at 18:37 | comment | added | Karl Knechtel | Or you could just use an alternative (for example) that already is open source and also shows much greater respect for its community, etc. | |
| Mar 4 at 17:18 | comment | added | Journeyman Geek | I don't think SE has 'hundreds' of developers. Maybe dozens at best. | |
| Mar 4 at 16:42 | comment | added | Starship | @A-Tech I do support SE code being open source in theory, but practically...there is a reason SE has hundreds of developers and "some random dude on the internet" modifying code is likely to cause more harm than good (in terms of bugs and time wasted) | |
| Mar 4 at 15:28 | comment | added | B-Tech | a backlog with the magnitude of thousands of feature request is still way too big | |
| Mar 4 at 14:16 | comment | added | Laurel | A lot of what's in that "enormous backlog" is stuff that the community has indicated it doesn't want (or is a duplicate). Adding score:3.. is:q closed:no to the searches cuts both of them down by more than half. | |
| Mar 4 at 11:53 | comment | added | B-Tech | @RobertLongson Maybe, but we can say that we offered a solution. | |
| Mar 4 at 10:59 | answer | added | Journeyman Geek | timeline score: 13 | |
| Mar 4 at 10:44 | comment | added | Robert Longson | Let's say this question gets lots of upvotes. Stack Exchange's response (if they give one at all) is, no. We're no further forward than the previous question are we? | |
| Mar 4 at 10:17 | comment | added | B-Tech | @security_paranoid as of know we can only suggest ideas. If the code is open source one could make suggest an idea alongside with complete implementation. You would lessen the workload on SEs side massively from implementing an entire bug-fix/feature to reviewing the code. Meaning that in theory more features/ bug fixes can be implemented. | |
| Mar 4 at 10:00 | comment | added | Meta Andrew T. | I believe the first and biggest hurdle is to separate the code from anything sensitive, similar to Make the mobile apps open source! | |
| Mar 4 at 9:59 | comment | added | security_paranoid | Open source their code and then… what? Let anyone modify it? Let people suggest modifications? I fail to understand what solely open sourcing SE's code will achieve. | |
| S Mar 4 at 9:56 | history | edited | B-Tech | CC BY-SA 4.0 | recject-edit as suggest-edit conflicted with another edit |
| Mar 4 at 9:49 | review | Suggested edits | |||
| S Mar 4 at 9:56 | |||||
| Mar 4 at 9:49 | history | edited | B-Tech | CC BY-SA 4.0 | added refernce to post itself |
| Mar 4 at 9:31 | history | asked | B-Tech | CC BY-SA 4.0 |