在开源许可证的发布ASP.NET MVC 3的OpenID入门套件 [英] Releasing an ASP.NET MVC 3 OpenId StarterKit under Open Source License

查看:139
本文介绍了在开源许可证的发布ASP.NET MVC 3的OpenID入门套件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经建立使用OpenID登录系统ASP.NET MVC 3(RC目前)的网站。我还在学习的OpenID,同时实施这让我评论了code严重。其结果是,它可以让用户登陆/注册使用OpenID,添加其他的OpenID他们的帐户,并删除他们的站点。这个小项目可以再用来作为起点的任何新项目将使用OpenID登录系统。它也可以用来作为资源为人们了解使用OpenID

I've build a ASP.NET MVC 3 (RC at the moment) site that uses OpenID login system. I was still learning about OpenID while implementing this so I commented the code heavily. The result is a site that let's users login/register with OpenID, add other OpenIDs to their account and also remove them. This little project can be then used as a starting point for any new project that would use OpenID login system. It can also be used as a resource for people to learn OpenID with.

我决定发布这个项目作为开源。这将是我的第一个开源项目,我需要决定使用什么许可证。我希望人们能够使用此为他们希望的任何目的。他们可以从中吸取教训,将其用于商业或非商业项目,并做出自己的code的叉子。这也将是不错的其他人能够像GitHub的场所的东西贡献回到项目类似的错误修复。不过,我想是code那是我控制下的版权拥有者。例如,code,它是我的GitHub库(我会打电话给这主要code库)。我听说,为了这个,我需要让每一个贡献者,,增加了code将该code碱基,给我的版权所作出的贡献。究竟是如何工作的呢?

I decided to release this project as open source. This will be my first open source project and I need to decided what license to use. I want people to be able to use this for any purpose they wish for. They can learn from it, use it for commercial or non-commercial projects and make their own forks of the code. It would also be nice for others to be able to contribute back to the project with stuff like bug fixes on sites like GitHub. But I'd like to be the copyright owner of the code that is under my control. For example the code that is in my GitHub repository (I'll call this the main code base). I've heard that for this I need to get every contributor, that adds code to this code base, to give me the copyright for their contribution. How exactly does this work?

我也使用其他许可(主要是开源的)资源在我的项目。这里是他们的名单和他们的许可证:

I also use other licensed (mostly open source) resources in my projects. Here's their list and their licenses:


  • DotNetOpenAuth(MS-PL)

  • T4MVC(这是使用Apache许可证2.0 licesned MvcContrib的一部分)

  • ASP.NET MVC(MS-PL)

  • ADO.NET实体框架CTP4(我无法找到一个执照)

我想使用的主code基地的任何类型的我想要的项目。商业,非商业,开源,...

I of course want to use the main code base for any type of projects I want. Commercial, non-commercial, open source, ...

所以我有一些非常重要的问题在这里:

So I have some very important questions here:


  1. 我应该使用哪种许可证?我认为GPL或LGPL不适合这里。我一直在寻找的Apache 2,新的BSD,MIT及Ms-PL。 MS-PL似乎是一个不错的选择的,但我不知道。

  2. 什么限制和/或义务做我对我在这个项目中使用的资源?我觉得我读的地方,我要补充-LICENSE.txt为MS-PL资源。真的吗?这是如何工作的Apache 2和其他许可证?我有什么,如果我修改任何这些资源'code,然后用在我的项目?做

  3. 我倒也真的像一个原样许可条款,因此人们不能起诉我,如果东西,而他们使用我的code出错。

  4. 请我需要什么添加到我的文件,明确什么许可证?如果是这样,我怎么格式化?

还有最后一件事。如果我决定做一个Visual Studio模板出这个样本的我怎么许可证?

Also one last thing. If I decide to make a Visual Studio template out of this samples how do I license that?

推荐答案

我听说过一份报告(从别人谁也不能对其进行备份)的女士-PL限制其他许可证的其他开源软件的使用。我不同意他们,但我们俩都不是律师。

I've heard one report (from someone who couldn't back it up) that Ms-PL restricts use by other open source software of other licenses. I disagree with them, but neither of us were lawyers.

大多数开源许可证,包括为Ms-PL 包括原样条款。

Most open source licenses including Ms-PL include as-is clauses.

我完全支持的的使用GPL或LGPL去,因为这严重限制你的自由做任何你想要的软件。它的高度朝着永续自由软件并没有那么多的自由宗教片面的。不是要flamebait,但它是一个真正的问题。

I totally support not going with GPL or LGPL because that severely restricts your "freedom" to do with the software whatever you want. It's highly sided toward the "religion" of perpetual "free software" and not so much freedom. Not trying to flamebait, but it's a genuine concern.

我个人选择为Ms-PL,因为我分享你的问题建议你有相同的目标,我觉得为Ms-PL适合该法案。我不是在一个位置,以保证正确的法律间pretation,但它是我不专业的意见。

Personally I chose Ms-PL because I share the same goals your question suggests you have and I felt Ms-PL fit the bill. I'm not in a position to promise correct legal interpretation, but it's my unprofessional opinion.

我相信您需要包括基于MS-PL反正在自己的软件redists许可/版权声明,但你不必的添加的这些新的许可证引用我相信。所以我认为这是不够的,如果您的许可文件包括自己的许可证,以及其他软件的REDIST包含的许可证,更不用说哪些文件每个许可证适用。再不用重新编译任何你的依赖,以除去可能已经包含在编译软件的版权声明。

I do believe you are required to include the licenses/copyright notices in your own software redists based on the Ms-PL anyway, but you don't have to add new references to these licenses I believe. So I'd consider it enough if your LICENSE file included your own license, and the licenses of the other software your redist includes, mention to which files each license applies. And then don't recompile any of your dependencies to remove the copyright notices that may have been included in the compiled software.

这篇关于在开源许可证的发布ASP.NET MVC 3的OpenID入门套件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆