Beginning work on members submenu group on the site:
* wrote services page. * created template. * added submenu to CSS.
This commit is contained in:
		
							parent
							
								
									2e40f1981d
								
							
						
					
					
						commit
						8179150188
					
				
					 2 changed files with 112 additions and 0 deletions
				
			
		
							
								
								
									
										96
									
								
								www/conservancy/static/members/services/index.html
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										96
									
								
								www/conservancy/static/members/services/index.html
									
										
									
									
									
										Normal file
									
								
							|  | @ -0,0 +1,96 @@ | |||
| {% extends "base_members.html" %} | ||||
| {% block subtitle %}Member Project Services - {% endblock %} | ||||
| {% block category %}members{% endblock %} | ||||
| {% block content %} | ||||
| 
 | ||||
| <h1>Member Project Services</h1> | ||||
| 
 | ||||
| <p>Conservancy assists FLOSS project leaders by handling all matters other | ||||
|   than software development and documentation, so the developers can focus | ||||
|   on what they do best: improving the software for the public good.  The | ||||
|   following are the services and options that are available to FLOSS | ||||
|   projects that have joined Conservancy as a member project.</p> | ||||
| 
 | ||||
| <h2>Earmarked Donations</h2> | ||||
| 
 | ||||
| <p>Member projects can receive earmarked donations through Conservancy. | ||||
|   Donors can indicate that their donation should be used to advance a | ||||
|   specific member project, and those funds are kept in a separate account | ||||
|   by Conservancy.  The project leadership can then indicate to | ||||
|   Conservancy's leadership how the funds should be spent to advance the | ||||
|   project.  Generally, Conservancy permits these funds to be spent in any | ||||
|   way that is appropriate activity under Conservancy's 501(c)(3) | ||||
|   not-for-profit mission.  Some typical uses of earmarked donations by | ||||
|   Conservancy's member projects are: | ||||
| <ul> | ||||
| <li>funding travel expenses for project developers to attend relevant | ||||
|   conferences.</li>  | ||||
| 
 | ||||
| <li>domain name fees, bandwidth costs, and computer equipment | ||||
|   purchases.</li> | ||||
| 
 | ||||
| <li>purchasing media for distribution of project software at conferences | ||||
|   and events.</li> | ||||
| 
 | ||||
| <li>paying key developers on a contractual basis to improve the project's | ||||
|   software and its documentation.</li> | ||||
| 
 | ||||
| <li>sponsoring and organizing conferences for the project.</li> | ||||
|   | ||||
| <li>trademark registration and enforcement.</li> | ||||
| 
 | ||||
| <li>FLOSS license enforcement and compliance activity.</li> | ||||
| </p> | ||||
| 
 | ||||
| <h2>Asset Stewardship</h2> | ||||
| 
 | ||||
| <p>Conservancy can hold any assets for the project on its behalf.  This | ||||
|   includes copyrights, trademarks, domain names, physical computer | ||||
|   equipment or anything that should be officially held in the name of the | ||||
|   project.  Member projects are not required that Conservancy hold all | ||||
|   assets of a project. (For example, member projects are | ||||
|   not <em>required</em> to assign copyrights to the Conservancy.) | ||||
|   However, Conservancy can accommodate the needs of projects that want | ||||
|   their assets under the control of a not-for-profit entity and exercised | ||||
|   only for the public good.</p> | ||||
| 
 | ||||
| <h2>Contract Negotiation and Execution</h2> | ||||
| 
 | ||||
| <p>Projects sometimes need to negotiate and execute a contract with a | ||||
|   company.  For example, when a project wants to organize and run a | ||||
|   conference, the venue usually has a complicated contract for rental of | ||||
|   the space and services.  Conservancy assists projects in the negotiation | ||||
|   of such contracts, and can sign them on behalf of the project.</p> | ||||
| 
 | ||||
| <h2>FLOSS Copyright License Enforcement</h2> | ||||
| 
 | ||||
| <p>Complying with FLOSS licenses is easy, as they permit and encourage | ||||
|   both non-commercial and commercial distribution and improvements. | ||||
|   Nevertheless, violations of FLOSS licenses (in particular of | ||||
|   the <a href="http://www.gnu.org/licenses/gpl.html">GPL</a> | ||||
|   and <a href="http://www.gnu.org/licenses/lgpl.html">LGPL</a>) are all | ||||
|   too common.  At request of the project's leaders, Conservancy can carry | ||||
|   out license enforcement activity on behalf of the project's copyright | ||||
|   holders.</p> | ||||
| 
 | ||||
| <h2>Leadership Mentoring, Advice and Guidance</h2> | ||||
| 
 | ||||
| <p>Many of Conservancy's <a href="/about/directors">directors</a> are | ||||
|   experienced FLOSS project leaders.  They offer themselves as a resource | ||||
|   to member project leaders who need assistance or face challenges in | ||||
|   their work leading their projects.</p> | ||||
| 
 | ||||
| <h2>Some Personal Liability Protection</h2> | ||||
| 
 | ||||
| <p>When a project joins Conservancy, it formally becomes part of the | ||||
|   Conservancy. (The project is thus somewhat analogous to a division of a | ||||
|   company or a department in a large agency.)  As such, project leaders | ||||
|   benefit from some amount of protection from personal liability for their | ||||
|   work on the project.</p> | ||||
| 
 | ||||
| <hr/> | ||||
| 
 | ||||
| <p>Project | ||||
| leaders that believe their project might benefit from these services can | ||||
| <a href="/members/apply/">apply to become a member project</a>.</p> | ||||
| {% endblock %} | ||||
							
								
								
									
										16
									
								
								www/conservancy/templates/base_members.html
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										16
									
								
								www/conservancy/templates/base_members.html
									
										
									
									
									
										Normal file
									
								
							|  | @ -0,0 +1,16 @@ | |||
| {% extends "base_conservancy.html" %} | ||||
| {% block category %}Members{% endblock %} | ||||
| {% block outercontent %} | ||||
|     <div id="container"> | ||||
|          <div id="sidebar" class="{% block submenuselection %}other{% endblock %}"> | ||||
|             <h2>Membership & Services</h2> | ||||
|             <ul> | ||||
|             <li class="Current"><a href="/members/current/">Current Member Projects</a></li> | ||||
|             <li class="Services"><a href="/about/services/">Member Project Services</a></li> | ||||
|             <li class="Applying"><a href="/about/apply/">Applying</a></li> | ||||
|             </ul> | ||||
|          </div> | ||||
|                <div id="mainContent">{% block content %}{% endblock %} | ||||
|                </div> | ||||
|    </div> | ||||
| {% endblock %} | ||||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 Bradley M. Kuhn
						Bradley M. Kuhn