Meta tags:

Headings (most frequently used words):

to, other, models, description, and, examples, applicable, policy, license, who, consult, considerations, limitations, information, with, university, employee, of, unit, individual, student, use, resources, commercial, software, development, the, existing, open, or, contributing, project, independent, work, including, navigator, source, intent, is, collaborating, external, partner, for, an, developing, on, not, how, find, your, scenario, contributions, engaged, in, hybrid, model, collaboration, third, party, group, producing, free, shared, situations, their, own, without, sponsorship, guidance, employees, job, personal, interest, from, behalf, using, as, assignment, contact, service, desk, connect, tech, at, unc,

Text of the page (most frequently used words):
and (58), the (45), office (39), policy (33), #university (32), license (28), with (24), for (24), other (24), accessibility (21), information (20), unc (20), software (19), digital (19), technology (18), models (18), interest (16), project (16), use (16), who (15), commercial (15), work (14), commercialization (14), copyright (13), otc (13), applicable (13), research (12), external (12), limitations (12), considerations (12), consult (12), description (12), examples (12), resources (11), open (11), student (11), development (11), conflict (11), activities (11), existing (11), content (11), patent (11), help (10), epap (10), employee (10), libraries (10), its (9), you (9), dao (9), source (9), materials (9), standard (9), not (9), available (8), that (8), may (8), your (8), professional (8), supervisor (8), individual (8), policies (7), faculty (7), are (7), consider (7), using (7), services (6), staff (6), this (6), review (6), invention (6), sponsored (6), unit (6), internal (5), from (5), support (5), navigator (5), employees (5), must (5), contributing (5), coi (5), programs (5), commitment (5), institutional (5), model (5), distribution (5), partner (5), employment (4), students (4), via (4), pay (4), process (4), under (4), assignment (4), guidance (4), works (4), advice (4), structure (4), will (4), agreement (4), all (4), require (4), agreements (4), groups (4), party (4), trigger (4), obligations (4), tech (3), connect (3), email (3), monday (3), friday (3), when (3), understand (3), can (3), more (3), find (3), scenario (3), context (3), owned (3), depends (3), oss (3), including (3), subject (3), developed (3), developing (3), independent (3), conflicts (3), collaborating (3), personal (3), library (3), get (3), about (3), situation (3), collaboration (3), know (3), contributors (3), agree (3), contributor (3), exclusive (3), develop (3), compliance (3), department (3), leadership (3), application (3), third (3), intended (3), news (2), only (2), edu (2), service (2), desk (2), choose (2), contact (2), licensing (2), ownership (2), protect (2), yourself (2), doing (2), public (2), see (2), projects (2), own (2), time (2), app (2), others (2), should (2), any (2), their (2), before (2), specific (2), counsel (2), ouc (2), data (2), assistance (2), team (2), entrepreneurial (2), here (2), first (2), talk (2), osp (2), would (2), organizational (2), nonprofit (2), entity (2), inter (2), iia (2), free (2), avoid (2), granting (2), collaborate (2), new (2), crm (2), system (2), shared (2), linked (2), producing (2), getting (2), intent (2), created (2), purposes (2), benefit (2), sale (2), key (2), adherence (2), generally (2), doesn (2), but (2), carries (2), risks (2), warranties (2), 3rd (2), components (2), hybrid (2), different (2), carolina (2), search (2), skip (2), 2026, newsletter, commons, opportunities, accepted, accounts, tickets, confirmed, person, 1506, frank, porter, graham, union, call, 919, 962, 4357, live, agents, chat, centralized, need, method, best, creating, essential, potential, issues, well, impact, learn, matches, yours, one, fields, describe, role, what, trying, accomplish, includes, anyone, paid, unpaid, volunteers, collaborators, etc, offices, authority, useful, helpful, pages, include, supervisors, aware, direct, status, done, part, core, responsibilities, considered, used, departmental, noncommercial, hobby, publishing, self, github, behalf, secondary, approval, through, freelance, programming, modules, job, devices, resnet, network, affect, category, uses, them, regarding, class, becomes, released, without, sponsorship, check, expert, taking, irrevocable, steps, have, described, specifically, situations, non, royalty, nerf, ncsu, lab, study, memorandum, understanding, mou, educause, creates, multiple, universities, higher, ensure, attribution, notices, redistribution, requirements, large, long, term, teams, centers, labs, authorship, diffuse, unclear, such, cases, typically, manages, revenues, supporting, center, discuss, plans, early, nonexclusive, based, homegrown, parties, group, waivers, rights, inventor, engages, following, some, formally, purchased, licensed, outside, having, evaluate, contribute, copyrighted, industry, company, produce, both, terms, planned, limit, possible, purchasing, branching, engaged, firefox, contributions, myself, beneficiaries, making, openly, building, audiences, referenced, scholarly, communications, how, describes, ways, people, applications, units, researchers, important, things, while, depending, apply, facilitate, advise, meant, comprehensive, legal, just, place, start, home, tools, started, safe, computing, governance, quarterly, reports, standards, procedures, locations, divisions, senior, portfolio, toggle, navigation, submit, main, connectcarolina, departments, maps, events, north, chapel, hill, end, global, utility, bar, archive,

Text of the page (random words):
software development models archive information technology services skip to the end of the global utility bar the university of north carolina at chapel hill accessibility events libraries maps departments connectcarolina unc search skip to main content information technology services submit search toggle navigation information technology services services project portfolio its news about senior leadership its divisions its locations its policies standards and procedures quarterly reports it governance groups student employment connect with its safe computing getting started employees students ai tools at carolina software development navigator home software development models software development models software development navigator when creating software it s essential to understand potential copyright licensing and ownership accessibility and other issues as well as the policies that may impact your work the software development navigator can help you learn more and protect yourself and the university the navigator describes ways that people at the university develop software and applications employees students groups and units of the university researchers and others can find guidance and important things to know while developing software depending on your situation different policies may apply and different groups at the university can help facilitate advise or review the project this information is meant to help you protect yourself and the university it is not comprehensive and is not legal advice this is just a place to start to get more information how to use the navigator to find a scenario that matches yours choose one or more of the fields to describe your role or what you are trying to accomplish employees in this context includes student employees and anyone doing paid or unpaid work for the university i e volunteers research collaborators etc other resources offices of the university with authority and useful information and helpful pages include library copyright and the scholarly communications office library copyright ownership office of technology commercialization guidance on software and other works of copyright office of digital accessibility policies referenced here are available at policies unc edu find your scenario audiences i am a all employee other student purposes i am building software for making available openly other personal use sale university use beneficiaries i am doing this work for myself other the university university use of existing open source software with employee contributions description and examples firefox development applicable policy unc copyright policy patent invention policy institutional conflict of interest and commitment accessibility of digital content and materials standard license models depends on existing license oss available under who to consult libraries office of technology commercialization otc digital accessibility office dao considerations intended use and compliance with open source license limitations consider benefit to the university from contributing to oss project other information distribution is the key trigger for adherence to license obligations internal use generally doesn t trigger license obligations but carries other risks e g no warranties university unit engaged in hybrid model of development description and examples new development using existing 3rd party components branching an existing open source project other hybrid model intended only for university internal use applicable policy unc copyright policy patent invention policy institutional conflict of interest and commitment use of university resources in support of entrepreneurial activities policy accessibility of digital content and materials standard license models depends on existing license the open source software is available under who to consult supervisor libraries office of sponsored programs office of the vs for research office of technology commercialization otc information technology services university data assistance team unc purchasing office of university counsel ouc digital accessibility office dao considerations intended use and compliance with open source license of 3rd party components limitations license terms for existing or planned projects will limit their possible use other information distribution is the key trigger for adherence to license obligations internal use generally doesn t trigger license obligations but carries other risks e g no warranties university unit collaboration with third party with commercial intent description and examples university and software company collaborate to produce an application that both will benefit from the sale of applicable policy patent invention policy accessibility of digital content and materials standard license models exclusive or patent linked commercial industry sponsored research or commercial agreements who to consult office of technology commercialization otc conflicts of interest office coi digital accessibility office dao considerations before inventor engages in the following activities should contact cm and department leadership some may require conflict of interest coi review using third party software or content not formally purchased or licensed using your unc created work for commercial purposes using work created outside unc at unc having students evaluate or contribute to your copyrighted work limitations all contributors must agree to model of distribution may require waivers assignment of rights or contributor agreements other information university group or unit producing with commercial intent description and examples pi producing an application based on research work it unit with homegrown application is getting interest from other third parties applicable policy patent invention policy individual conflict of interest and commitment accessibility of digital content and materials standard license models nonexclusive commercial exclusive or patent linked commercial who to consult libraries office of sponsored programs office of the vs for research office of technology commercialization otc conflicts of interest office coi digital accessibility office dao considerations when works are developed by large or long term teams e g centers labs authorship may be diffuse or unclear in such cases unc typically manages the copyright licensing revenues are shared with the supporting department or center discuss commercialization plans with department leadership and otc early limitations ensure compliance with license attribution notices redistribution requirements and unc internal policies other information when to consider a software patent unit is collaborating with external partner for open free use description and examples educause creates project for multiple universities to develop a crm system for higher ed applicable policy unc copyright policy accessibility of digital content and materials standard license models inter institutional agreement iia memorandum of understanding mou avoid patent granting open source license models who to consult supervisor libraries office of sponsored programs office of the vs for research office of technology commercialization otc digital accessibility office dao considerations organizational structure of external partner e g nonprofit commercial entity limitations all contributors must agree to model of distribution may require assignment or contributor agreements other information understand the structure of the collaboration first that will help you know who to talk with e g if you are in a research context osp would help with the agreement unit is collaborating with an external partner for shared use description and examples unc and ncsu collaborate on a new crm system research lab works with partner research groups to develop app for use in a study applicable policy unc copyright policy accessibility of digital content and materials standard license models inter institutional agreement iia non exclusive royalty free license nerf avoid patent granting open source license models who to consult supervisor libraries office of sponsored programs office of the vs for research office of technology commercialization otc digital accessibility office dao considerations organizational structure of external partner e g nonprofit commercial entity limitations all contributors must agree to model of distribution may require assignment or contributor agreements other information understand the structure of the collaboration first that will help you know who to talk with e g if you are in a research context osp would help with the agreement other situations description and examples you have a software development scenario not described specifically here applicable policy unc copyright policy external professional activities of faculty and staff policy epap patent invention policy institutional conflict of interest and commitment individual conflict of interest and commitment use of university resources in support of entrepreneurial activities policy accessibility of digital content and materials standard license models any who to consult supervisor libraries office of sponsored programs office of the vs for research office of technology commercialization otc university data assistance team office of university counsel ouc digital accessibility office dao considerations get advice about your specific situation limitations get advice about your specific situation other information advice is available check with an expert before taking irrevocable steps individual student developing on their own without university resources sponsorship or guidance description and examples class project that becomes released software individual development applicable policy unc copyright policy license models any who to consult office of technology commercialization otc considerations student owned limitations see copyright policy regarding support of a faculty project other information university library resnet and other network resources are not resources that affect this category if the student uses them individual employee or student contributing to an existing open source project independent of work description and examples public project not on work time or using university devices applicable policy external professional activities of faculty and staff policy epap license models consider the existing license the project is under who to consult supervisor libraries office of technology commercialization otc considerations should not use university resources or university developed works limitations subject to review other information consider conflict of interest via external professional activities for pay epap process individual employee including student employees contributing to commercial project independent of job with personal commercial interest description and examples freelance programming work collaborating with others on a personal commercial project contributing modules to an existing commercial project for pay applicable policy external professional activities of faculty and staff policy epap accessibility of digital content and materials standard license models commercial license models who to consult supervisor libraries office of technology commercialization otc conflicts of interest office coi digital accessibility office dao considerations must go through conflict of interest coi review limitations subject to review secondary employment external professional activities for pay epap approval other information consider conflict of interest via epap process individual employee including student employee developing independent from work not on behalf of the university not using university resources description and examples hobby project on own time publishing a self developed app on github applicable policy unc copyright policy external professional activities of faculty and staff policy epap patent invention policy license models noncommercial who to consult supervisor office of technology commercialization otc considerations employee owned subject to departmental review limitations no university resources may be used see guidance on commercial projects if applicable other information consider conflict of interest via epap process individual employee including student employee contributing to existing project as work assignment description and examples public project using university resources applicable policy external professional activities of faculty and staff policy epap accessibility of digital content and materials standard license models depends on existing license the open source software oss is available under who to consult supervisor libraries office of technology commercialization otc digital accessibility office dao considerations employment status of employee work done as part of core responsibilities considered unc owned limitations supervisors must be aware of and direct this work other information consider conflict of interest via external professional activities for pay epap process 1 2 contact the service desk the its service desk is centralized support for students faculty and staff who need tech help choose the method best for you chat with us live agents available 8 a m 5 p m monday friday call 919 962 help 4357 available 7 a m 7 p m monday friday in person 1506 frank porter graham student union open 8 a m 5 p m monday friday email support help unc edu accepted only from unc email accounts tickets confirmed by email resources policies its employment opportunities its commons internal connect with tech at unc its news tech connect newsletter 2026 information technology services