-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdescribed.js
54 lines (49 loc) · 1.86 KB
/
described.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
#!/usr/bin/env node
'use strict';
const inquirer = require('inquirer')
const generator = require('./generator');
const detailedMenu = [
{
key: 'apache',
name:'Apache requires Apache License 2.0'
},
{
key:'apache',
name:'Cloud Native Computing Foundation dictates Apache License 2.0 by default'
},
{
key:'gnu',
name:'GNU recommends GNU GPLv3 for most programs'
},
{
key:'mit',
name:'NPM packages overwhelmingly use the MIT'
},
{
key:'isc',
name:'OpenBSD prefers the ISC License'
},
{
key:'apache',
name:'Rust crates are overwhelmingly licensed under both MIT and Apache License 2.0'
},
{
key:'gnu',
name:'WordPress plugins and themes must be GNU GPLv2 (or later)'
}
]
module.exports.default = () => {
console.clear()
console.log('Which of the following best describes your situation?\n');
console.log('If you’re contributing to or extending an existing project, it’s almost always easiest to continue using that project’s license. To find its license, look for a file called LICENSE or COPYING, and skim the project’s README. If you can’t find a license, ask the maintainers.\n');
console.log('Depending on the original project’s license, using the same license might be a requirement, not just the easiest thing to do.\n');
console.log('Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use their preferred license, even if you’re starting a brand new project with no existing dependencies. Some examples include:\n');
inquirer.prompt({
type: 'list',
name: 'license',
key: 'key',
choices: detailedMenu,
}).then(answers => {
generator.default(answers["license"])
})
}