Page Time: 0.6267s

Memory: 10.6075 MB (Peak: 11.8828 MB)

Queries (13, time: 0.0977s, 15.6%)

  1. SELECT data_key, data_value
    FROM xf_data_registry
    WHERE data_key IN ('options', 'languages', 'contentTypes', 'codeEventListeners', 'deferredRun', 'simpleCache', 'addOns', 'defaultStyleProperties', 'routeFiltersIn', 'routeFiltersOut', 'routesPublic', 'nodeTypes', 'bannedIps', 'discouragedIps', 'styles', 'displayStyles', 'userBanners', 'smilies', 'bbCode', 'threadPrefixes', 'userTitleLadder', 'reportCounts', 'moderationCounts', 'userModerationCounts', 'notices', 'userFieldsInfo')
    Run Time: 0.006731
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLExf_data_registryrangePRIMARYPRIMARY27 26Using where
  2. SELECT data_key, data_value
    FROM xf_data_registry
    WHERE data_key IN ('brListenerClasses', 'brBriviumAddOns')
    Run Time: 0.007691
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLExf_data_registryrangePRIMARYPRIMARY27 2Using where
  3. SELECT *
    FROM xf_brivium_addon
    ORDER BY addon_id
    Run Time: 0.000266
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLExf_brivium_addonindex PRIMARY77 1 
  4. INSERT INTO xf_data_registry
    	(data_key, data_value)
    VALUES
    	(?, ?)
    ON DUPLICATE KEY UPDATE
    	data_value = VALUES(data_value)
    Params: brBriviumAddOns, a:0:{}
    Run Time: 0.000124
  5. SELECT session_data
    FROM xf_session
    WHERE session_id = ?
    	AND expiry_date >= ?
    Params: 90ccd07dfd8d681a6bea0b2288c03cc6, 1716146006
    Run Time: 0.000169
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLExf_sessionconstPRIMARY,expiry_datePRIMARY34const1 
  6. SELECT cache_value
    FROM xf_permission_combination
    WHERE permission_combination_id = ?
    Params: 1
    Run Time: 0.000219
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLExf_permission_combinationconstPRIMARYPRIMARY4const1 
  7. SELECT thread.*
    	,
    		user.gender, user.avatar_date, user.gravatar,
    		NULL AS thread_read_date,
    		0 AS thread_reply_banned,
    		0 AS thread_is_watched,
    		'' AS draft_message, NULL AS draft_extra
    FROM xf_thread AS thread
    
    		LEFT JOIN xf_user AS user ON
    			(user.user_id = thread.user_id)
    WHERE thread.thread_id = ?
    Params: 318254
    Run Time: 0.000447
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLEthreadconstPRIMARYPRIMARY4const1 
    SIMPLEuserconstPRIMARYPRIMARY4const1 
  8. SELECT node.*, forum.*
    	,
    	permission.cache_value AS node_permission_cache,
    		NULL AS forum_read_date
    FROM xf_forum AS forum
    INNER JOIN xf_node AS node ON (node.node_id = forum.node_id)
    
    	LEFT JOIN xf_permission_cache_content AS permission
    		ON (permission.permission_combination_id = 1
    			AND permission.content_type = 'node'
    			AND permission.content_id = forum.node_id)
    WHERE node.node_id = ?
    Params: 25
    Run Time: 0.004238
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLEforumconstPRIMARYPRIMARY4const1 
    SIMPLEnodeconstPRIMARYPRIMARY4const1 
    SIMPLEpermissionconstPRIMARYPRIMARY35const,const,const1 
  9. SELECT post.*
    	,
    		thread.*, thread.user_id AS thread_user_id, thread.username AS thread_username,
    		thread.post_date AS thread_post_date,
    		post.user_id, post.username, post.post_date,
    		bb_code_parse_cache.parse_tree AS message_parsed, bb_code_parse_cache.cache_version AS message_cache_version,
    		user.*, IF(user.username IS NULL, post.username, user.username) AS username,
    		user_profile.*,
    		user_privacy.*,
    		signature_parse_cache.parse_tree AS signature_parsed, bb_code_parse_cache.cache_version AS signature_cache_version,
    		session_activity.view_date AS last_view_date,
    		0 AS like_date
    FROM xf_post AS post
    
    		INNER JOIN xf_thread AS thread ON
    			(thread.thread_id = post.thread_id)
    		LEFT JOIN xf_bb_code_parse_cache AS bb_code_parse_cache ON
    			(bb_code_parse_cache.content_type = 'post' AND bb_code_parse_cache.content_id = post.post_id)
    		LEFT JOIN xf_user AS user ON
    			(user.user_id = post.user_id)
    		LEFT JOIN xf_user_profile AS user_profile ON
    			(user_profile.user_id = post.user_id)
    		LEFT JOIN xf_user_privacy AS user_privacy ON
    			(user_privacy.user_id = post.user_id)
    		LEFT JOIN xf_bb_code_parse_cache AS signature_parse_cache ON
    			(signature_parse_cache.content_type = 'signature' AND signature_parse_cache.content_id = post.user_id)
    		LEFT JOIN xf_session_activity AS session_activity ON
    			(post.user_id > 0 AND session_activity.user_id = post.user_id AND session_activity.unique_key = CAST(post.user_id AS BINARY))
    WHERE (
    		(post.thread_id = ?  AND (post.position >= 0 AND post.position < 10) )
    		
    		
    	)
    	AND (post.message_state IN ('visible'))
    ORDER BY post.position ASC, post.post_date ASC
    Params: 318254
    Run Time: 0.066673
    Select TypeTableTypePossible KeysKeyKey LenRefRowsExtra
    SIMPLEthreadconstPRIMARYPRIMARY4const1Using filesort
    SIMPLEpostrefthread_id_post_date,thread_id_positionthread_id_post_date4const1Using index condition; Using where
    SIMPLEbb_code_parse_cacheeq_refcontent_type_idcontent_type_id31const,xenforo.cc.post.post_id1Using where
    SIMPLEusereq_refPRIMARYPRIMARY4xenforo.cc.post.user_id1 
    SIMPLEuser_profileeq_refPRIMARYPRIMARY4xenforo.cc.post.user_id1 
    SIMPLEuser_privacyeq_refPRIMARYPRIMARY4xenforo.cc.post.user_id1 
    SIMPLEsignature_parse_cacheeq_refcontent_type_idcontent_type_id31const,xenforo.cc.post.user_id1Using where
    SIMPLEsession_activityeq_refPRIMARYPRIMARY22xenforo.cc.post.user_id,func1Using where
  10. INSERT  INTO xf_thread_view
    	(thread_id)
    VALUES
    	(?)
    Params: 318254
    Run Time: 0.000100
  11. UPDATE `xf_session` SET `expiry_date` = ? WHERE (session_id = '90ccd07dfd8d681a6bea0b2288c03cc6')
    Params: 1716149606
    Run Time: 0.005623
  12. INSERT INTO xf_session_activity
    	(user_id, unique_key, ip, controller_name, controller_action, view_state, params, view_date, robot_key)
    VALUES
    	(?, ?, ?, ?, ?, ?, ?, ?, ?)
    ON DUPLICATE KEY UPDATE
    	ip = VALUES(ip),
    	controller_name = VALUES(controller_name),
    	controller_action = VALUES(controller_action),
    	view_state = VALUES(view_state),
    	params = VALUES(params),
    	view_date = VALUES(view_date),
    	robot_key = VALUES(robot_key)
    Params: 0, , , XenForo_ControllerPublic_Thread, Index, valid, thread_id=318254, 1716146006,
    Run Time: 0.000228
  13. INSERT INTO xf_bb_code_parse_cache
    	(content_type, content_id, parse_tree, cache_version, cache_date)
    VALUES (?, ?, ?, ?, ?)
    ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
    	cache_version = VALUES(cache_version),
    	cache_date = VALUES(cache_date)
    Params: post, 324883, a:62:{i:0;s:123:"近日,开源项目 AppGet 作者 Keivan Beigi 与微软 WinGet 项目的“抄袭纠纷”事件迎来了最新进展。";i:1;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:130:"微软方面做出回应,坦承“辜负了 Keivan 和 AppGet”,并肯定了 Keivan 与 AppGet 对微软新项目的贡献。";}}i:2;s:2:" ";i:3;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:299:"今年 5 月,微软在 Build 2020 大会上发布了新的软件包管理工具 WinGet,并将其开源。 而就在 WinGet 发布之后不久,开源软件包管理工具 AppGet 项目作者 Keivan Beigi 发文宣布 AppGet 项目“死亡”,矛头直指微软的 WinGet 抄袭了 AppGet 。";}}i:4;s:2:" ";i:5;a:4:{s:3:"tag";s:6:"center";s:6:"option";N;s:8:"original";a:2:{i:0;s:8:"[CENTER]";i:1;s:9:"[/CENTER]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:76:"https://oscimg.oschina.net/oscnet/up-3553f453da6e9ec45bfdaf0224acda75067.png";}}}}i:6;s:2:" ";i:7;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:3:{i:0;s:25:"AppGet 是一款开源的";i:1;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:32:"https://microsoft.pvxt.net/x9Vg1";s:8:"original";a:2:{i:0;s:40:"[URL='https://microsoft.pvxt.net/x9Vg1']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:7:"Windows";}}i:2;s:626:"软件包管理工具,它可以在 Windows PC 上自动安装软件。作者 Keivan Beigi 是一名居住在加拿大温哥华的软件工程师。去年 7 月,微软 App 事业部产品经理 Andrew Clinick 开始主动接触 Keivan,表达了微软对于 AppGet 的兴趣,并表示可以给 Keivan 提供在微软的职位,共同开发 Windows 系统的软件包管理项目。期间,Andrew 多次与 Keivan 以交换意见为由进行面试沟通,获取了 AppGet 的开发思路。去年 12 月,Keivan 在微软位于西雅图的总部接受了一整天的采访,事情本来正向着好的方向发展。";}}i:8;s:2:" ";i:9;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:436:"然而此后的 6 个月里,微软没有再与 Keivan 联系。直到今年 5 月,Keivan 突然收到了一封来自微软的邮件:“我想花点时间告诉你,我们非常感谢你的投入和见解。我们一直在构建 windows 包管理器,第一个预览版将于明天在 Build 上线,我们的包管理器也将是开源的,我们欢迎您的任何贡献。”随后,微软就在 Build 上发布了 WinGet 。";}}i:10;s:2:" ";i:11;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:373:"Keivan 表示,当他看到公告和 WinGet 的代码时感到很震惊。Keivan 认为 WinGet 的核心机制、术语、manifest 格式和结构,甚至是包存储库的文件夹结构都有 AppGet 的影子。而微软在公告中对于 AppGet 的描述仅有一句 “ ……还有许多其他类似 AppGet、Npackd 和基于 PowerShell 的 OneGet 包管理器。”";}}i:12;s:2:" ";i:13;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:298:"Keivan 对微软的做法感到非常失望,他认为微软抄袭他的开源软件没有问题,但希望自己的工作获得适当的荣誉。为此他发表了“AppGet 之死”一文,宣布放弃 AppGet 项目的更新,因为与微软这种量级的开发者竞争没有任何意义。";}}i:14;s:2:" ";i:15;a:4:{s:3:"tag";s:6:"center";s:6:"option";N;s:8:"original";a:2:{i:0;s:8:"[CENTER]";i:1;s:9:"[/CENTER]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:76:"https://oscimg.oschina.net/oscnet/up-1afa0b85f3a593fb668cf64cdd6fbf1afc7.png";}}}}i:16;s:2:" ";i:17;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:356:"而对于微软面试官 Andrew 的做法,Keivan 在推特中表示:“我并不想站在 WinGet 的对立面,我也不希望任何人因这件事被解雇,我只是想分享我在这个故事中遭遇的一些不公平对待。”同时他也不想因为一些私人恩怨而毁掉一款好的产品,希望微软方面能给出适当的答复。";}}i:18;s:2:" ";i:19;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:740:"5 月 30 日,微软产品经理 Andrew 在微软官方发文回应称,“去年夏天,我们与 Keivan 进行了交谈,探讨了共同提供 Windows Package Manager 的潜在机会。AppGet 具有许多品质,确实可以帮助我们为 WinGet 找到更好的产品方向。” 承认了 Keivan 与 AppGet 对微软 WinGet 项目的贡献。“Windows Package Manger 的宗旨,是提供产品让社区和用户都能做出贡献并获得认可,这就是为什么我们要把它建立在 GitHub 上的原因;在过去的几天里,我们听取了社区的意见,并从中吸取了教训,显然我们有负于这个目标。更确切地说,我们辜负了 Keivan 和 AppGet 。这也是我们最不愿意看到的。”";}}i:20;s:2:" ";i:21;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:83:"Andrew 还明确列出了数个 AppGet “帮助 WinGet 变得更好”的贡献:";}}i:22;s:2:" ";i:23;a:4:{s:3:"tag";s:4:"list";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LIST]";i:1;s:7:"[/LIST]";}s:8:"children";a:9:{i:0;s:5:" [*] ";i:1;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:3:{i:0;s:86:"在安装过程中没有脚本 —— 这是我们完全同意的,但不允许使用";i:1;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:76:"https://c.duomai.com/track.php?site_id=242986&euid=&t=https://msi-pc.jd.com/";s:8:"original";a:2:{i:0;s:84:"[URL='https://c.duomai.com/track.php?site_id=242986&euid=&t=https://msi-pc.jd.com/']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:3:"MSI";}}i:2;s:1:"X";}}i:2;s:7:" [*] ";i:3;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:134:"GitHub 中丰富的清单定义—— 与应用程序的丰富声明性元数据相结合的开放能力对于实现目标非常重要";}}i:4;s:7:" [*] ";i:5;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:78:"支持所有类型的 Windows 应用程序安装程序(包括 Win32/Win64)";}}i:6;s:7:" [*] ";i:7;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:39:"存储库中应用程序的无缝更新";}}i:8;s:2:" ";}}i:24;s:2:" ";i:25;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:209:"Andrew 表示希望借此机会表达对 Keivan 提供的 AppGet 的开发思路,以及 Keivan 与微软合作的感谢。并希望未来能和 Keivan 以及其他开发者合作,把 WinGet 做得更好。";}}i:26;s:2:" ";i:27;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:140:"尽管微软承认了 AppGet 的贡献并表达了谢意,但仍然没有表达对整件事情的歉意,有网友对此表达了不满。";}}i:28;s:2:" ";i:29;a:4:{s:3:"tag";s:6:"center";s:6:"option";N;s:8:"original";a:2:{i:0;s:8:"[CENTER]";i:1;s:9:"[/CENTER]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:76:"https://oscimg.oschina.net/oscnet/up-4558d74c57e9227ba863789dd88af187d26.png";}}}}i:30;s:2:" ";i:31;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:3:{i:0;s:57:"甚至有网友表示“这下所有事情都明朗了,";i:1;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:87:"微软之所以开始向开源靠拢,是为了更方便窃取别人的劳动成果?";}}i:2;s:3:"”";}}i:32;s:2:" ";i:33;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:209:"其实网友的嘲讽并非心血来潮,早在 2018 年 6 月,微软就曝出过类似的抄袭事件。当时,开源的多包存储库管理工具 Lerna 作者 jamiebuilds 指责微软抄袭其代码。";}}i:34;s:2:" ";i:35;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:524:"jamiebuilds 表示,当自己在为 Babel 6 工作的过程中发现所有东西都拆分成漂亮的小插件包,但同时也就需要管理数十个软件包。因此,多包存储库管理工具 Lerna.js 应运而生。为让项目更好用,他对项目进行了 5 次重写,试图让架构更完善。之后某天,jamiebuilds 发现了微软推出了由许多小包组成的新的设计体系,本以为是微软在项目中使用了 Lerna ,结果发现他们使用的是一个名为 “Rush” 的东西。";}}i:36;s:2:" ";i:37;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:699:"Rush 或许是微软在 Lerna 的基础上开发的一个分支?抱着这样的想法,jamiebuilds 进一步查看了 Rush 的 Git 日志,结果发现该项目是在 Lerna 创建几天之后创建的,同时在文档中介绍了包括 Lerna 在内的其他类似工具,并称之为“不够好的产品”,俨然一副 “Rush 是比这些产品都要好的原创工具”的样子。为了解二者的区别,jamiebuilds 对两个项目进行了对比,结果发现 Rush 的文件和目录命名、核心功能的代码都与 Lerna 完全相同,甚至连提交记录都是一致的,也就是说 Rush 在不断复制 Lerna 的更改,然后声称其是微软开发的原创作品。";}}i:38;s:2:" ";i:39;a:4:{s:3:"tag";s:6:"center";s:6:"option";N;s:8:"original";a:2:{i:0;s:8:"[CENTER]";i:1;s:9:"[/CENTER]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:76:"https://oscimg.oschina.net/oscnet/up-f40b56679d1efccf070a36cb67d7cc4fed4.png";}}}}i:40;s:2:" ";i:41;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:341:"jamiebuilds 称自己主动与认识的微软员工联系说明此事后,对方感到震惊并道歉,但之后并没有任何来自官方的合理解释。Rush 项目也没有去更改许可证,或者添加补充说明,而是将提交记录进行了混淆,将代码位置进行移动,并重新编写或重命名了一些函数。";}}i:42;s:2:" ";i:43;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:207:"jamiebuilds 提到,如果是其他人做了这件事,他或许会有点不高兴但仍然把他忽略掉。但微软这样一个万亿市值的软件业巨头做这样的事情,这令他非常生气。";}}i:44;s:2:" ";i:45;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:298:"这件事最后不了了之。值得一提的是,这一次 Lerna 的开发者并没有选择向微软屈服。如今 Lerna 在 GitHub 上拥有 23k 的 Star ,成为名副其实的明星项目,以至于微软后来在自己的项目 Just 中也把多包存储管理工具改为使用 Lerna 。";}}i:46;s:2:" ";i:47;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:381:"尽管这些抄袭事件或许只是由微软个别员工的不当做法引起,但微软的一系列抄袭行为还是引发了开源界的担忧。事实上,在开源社区中 fork 或 copy 某人的代码并不是什么坏事。但微软这种将别人的劳动成果归功于己的行为,显然违反了开源社区应有的道德规范,当然也违反了开源协议。";}}i:48;s:2:" ";i:49;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:204:"目前,很多软件工程师普遍对于开源协议仍然不够了解。有人甚至认为:开源软件就是免费的软件,所以我可以不受限制地随意使用。这显然是一种误解。";}}i:50;s:2:" ";i:51;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:3:{i:0;s:581:"据业内律师介绍,开源软件与专有软件等闭源软件一样,都是受法律保护的。开源软件的著作权既没有放弃也没有过期,作者仍然是享有著作权的。除了著作权外,开源软件还可能被合同法、专利法、商标法等法律所规制。在著作权法的语境下,软件代码是类似于文字作品一样被保护的。在获得了一段源代码之后,默认情况下不能对该源代码进行改编或者再发行。而开源软件的特点在于,对于部分宽松开源协议(如 MIT、Apache 2.0)来说,";i:1;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:138:"在使用者承诺满足一定条件(通常包括给作者署名、附带许可证)的情况下,作者会放弃、让渡部分权利";}}i:2;s:57:",例如允许使用者将代码改编或者再发行。";}}i:52;s:2:" ";i:53;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:322:"律师介绍,使用者所承诺的条件以及作者所放弃的部分权利形成了一种合同关系,更具体来讲是许可合同,在开源软件的情况下该合同也就是我们常说的开源许可证(License)。许可证是一种无需磋商的、标准化的公共合同,降低了合同的成本。";}}i:54;s:2:" ";i:55;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:655:"理论上来说,使用 MIT、Apache 2.0 等宽松开源许可证的项目,源代码可以被任何人拿去修改、分发、甚至闭源商业化,但必须保留项目原作者的著作权,也就是在源代码引用的部分保留项目作者的版权声明。以 MIT 许可协议为例,该协议规定,被授权人要履行 “在软件和软件的所有副本中都必须包含版权声明和许可声明” 的义务。也就是说,微软采用开源项目源代码开发新项目本身并没有任何问题,但其拒绝履行开源协议规定的“保护软件原作者著作权”的义务,事实上是违反了开源协议的。";}}i:56;s:2:" ";i:57;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:1026:"尽管开源项目源代码受到开源协议的保护,但个人开发者维护的开源项目在面对微软这种级别的大型企业时,往往难以维护自己的合法权利。比较大型的开源项目通常会由专门成立的基金会来处理相关的法务问题,这些大型开源项目的版权属于中立的开源基金会,基金会享有处理项目授权、更改开源协议的权利,能够随时应对项目授权问题带来的法律纠纷。但个人开发的项目版权属于开发者自己,面对类似的侵权行为时,显然缺乏足够的人力和财力去处理这些法律纠纷,在大多数情况下只能闷声吃亏。因此,在个人开发者决定是否将自己的项目开源时,一定要衡量开源的利弊,充分理解各类开源许可证的各项条款,预测项目开源后可能带来的后果,三思而后行。同样的,当我们在使用开源项目的代码时,也要尊重原作者的劳动成果,自觉履行开源协议所要求的义务。";}}i:58;s:2:" ";i:59;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:75:"最后,以《是谁在阻碍我们创新》中的一句话作为结尾:";}}i:60;s:2:" ";i:61;a:4:{s:3:"tag";s:4:"left";s:6:"option";N;s:8:"original";a:2:{i:0;s:6:"[LEFT]";i:1;s:7:"[/LEFT]";}s:8:"children";a:1:{i:0;s:57:"“我们总是习惯去索取,而忘记了回馈。”";}}}, 1621686945, 1716146006
    Run Time: 0.005236

Included Files (107, XenForo Classes: 61)

  1. index.php
  2. library/XenForo/Autoloader.php
  3. library/XenForo/Application.php
  4. library/Zend/Registry.php
  5. library/Lgpl/utf8.php
  6. library/Zend/Config.php
  7. library/config.php
  8. library/XenForo/FrontController.php
  9. library/XenForo/Dependencies/Public.php
  10. library/XenForo/Dependencies/Abstract.php
  11. library/Zend/Controller/Request/Http.php
  12. library/Zend/Controller/Request/Abstract.php
  13. library/Zend/Uri.php
  14. library/Zend/Controller/Response/Http.php
  15. library/Zend/Controller/Response/Abstract.php
  16. library/XenForo/Model/DataRegistry.php
  17. library/XenForo/Model.php
  18. library/Zend/Db.php
  19. library/Zend/Db/Adapter/Mysqli.php
  20. library/Zend/Db/Adapter/Abstract.php
  21. library/Zend/Db/Select.php
  22. library/Zend/Db/Expr.php
  23. library/Zend/Db/Profiler.php
  24. library/Zend/Db/Statement/Mysqli.php
  25. library/Zend/Db/Statement.php
  26. library/Zend/Db/Statement/Interface.php
  27. library/Zend/Db/Profiler/Query.php
  28. library/XenForo/CodeEvent.php
  29. library/XenForo/Options.php
  30. library/XenForo/Link.php
  31. library/XenForo/Template/Helper/Core.php
  32. library/XenResource/Listener/Proxy.php
  33. library/XenGallery/Listener.php
  34. library/Brivium/BriviumHelper/EventListeners.php
  35. library/Brivium/BriviumHelper/1000271/EventListeners.php
  36. library/SV/RedisCache/Listener.php
  37. library/BestAnswer/Listener.php
  38. library/SV/RedisCache/XenForo/Model/DataRegistry.php
  39. library/Brivium/BriviumHelper/Model/ListenerClass.php
  40. library/Brivium/BriviumHelper/1000271/Model/ListenerClass.php
  41. library/XenForo/Router.php
  42. library/XenForo/Route/Filter.php
  43. library/XenForo/Route/Interface.php
  44. library/XenForo/Route/ResponseSuffix.php
  45. library/XenForo/Route/Prefix.php
  46. library/XenForo/Route/Prefix/Threads.php
  47. library/XenForo/RouteMatch.php
  48. library/XenForo/ControllerPublic/Thread.php
  49. library/XenForo/ControllerPublic/Abstract.php
  50. library/XenForo/Controller.php
  51. library/BestAnswer/ControllerPublic/Thread.php
  52. library/XenForo/Input.php
  53. library/XenForo/Session.php
  54. library/XenForo/Helper/Ip.php
  55. library/XenForo/Visitor.php
  56. library/XenForo/Model/User.php
  57. library/BestAnswer/Model/User.php
  58. library/XenResource/Listener/Proxy/ModelUser.php
  59. library/XenGallery/Model/User.php
  60. library/XenForo/Permission.php
  61. library/XenForo/Helper/Php.php
  62. library/XenForo/Phrase.php
  63. library/XenForo/Locale.php
  64. library/XenForo/ControllerHelper/ForumThreadPost.php
  65. library/XenForo/ControllerHelper/Abstract.php
  66. library/XenForo/Model/Thread.php
  67. library/SV/RedisCache/XenForo/Model/Thread.php
  68. library/BestAnswer/Model/Thread.php
  69. library/BestAnswer/Model/BestAnswer.php
  70. library/XenForo/Model/Forum.php
  71. library/XenForo/Helper/String.php
  72. library/XenForo/Model/Post.php
  73. library/FreddysHouse/SignatureOnce/Event/LoadClassModel.php
  74. library/BestAnswer/Model/Post.php
  75. library/FreddysHouse/SignatureOnce/Model/Post.php
  76. library/XenForo/Model/Attachment.php
  77. library/XenForo/Model/Node.php
  78. library/XenForo/Route/Prefix/Categories.php
  79. library/XenForo/Route/Prefix/Forums.php
  80. library/XenForo/ControllerResponse/View.php
  81. library/XenForo/ControllerResponse/Abstract.php
  82. library/XenResource/Listener/Template.php
  83. library/XenForo/ViewRenderer/HtmlPublic.php
  84. library/XenForo/ViewRenderer/Abstract.php
  85. library/XenForo/Template/Public.php
  86. library/XenForo/Template/Abstract.php
  87. library/XenForo/ViewPublic/Thread/View.php
  88. library/XenForo/ViewPublic/Base.php
  89. library/XenForo/View.php
  90. library/XenForo/BbCode/Parser.php
  91. library/XenForo/BbCode/Formatter/Base.php
  92. library/XenForo/ViewPublic/Helper/Message.php
  93. library/XenForo/BbCode/TextWrapper.php
  94. library/WhoHasVisited/Listener.php
  95. library/XenForo/Route/Prefix/Members.php
  96. library/XenForo/Template/FileHandler.php
  97. library/XenForo/Helper/File.php
  98. internal_data/templates/S.1,L.7,thread_view.php
  99. library/Brivium/RMDownloadTracker/EventListener/Listener.php
  100. library/XenForo/Route/Prefix/Posts.php
  101. library/XenForo/Model/Avatar.php
  102. library/XenForo/Helper/Criteria.php
  103. library/XenForo/Debug.php
  104. internal_data/templates/S.1,L.7,PAGE_CONTAINER.php
  105. internal_data/templates/S.1,L.7,xengallery_tab_links.php
  106. internal_data/templates/S.1,L.7,resources_tab_links.php
  107. library/XenForo/ViewRenderer/Json.php