rbowen / centos / board

Forked from centos/board 3 years ago
Clone

Blame meetings/2014/2014-03-26.md

7936f7
# Board minutes 2014-03-26
7936f7
7936f7
## Attendees
7936f7
* Mike
7936f7
* KB
7936f7
* Carl
7936f7
* Karsten
7936f7
* Fabian
7936f7
* Ralphp
7936f7
* Tru
7936f7
* Jim
7936f7
* Johnny
7936f7
7936f7
7936f7
## Agenda
7936f7
* Release naming
7936f7
* Export regulations verbage
7936f7
7936f7
7936f7
7936f7
7936f7
## Actions
7936f7
Jim to write up list of actions / content to address export control requirements
7936f7
7936f7
7936f7
## Notes
7936f7
### Naming
b1f77a
* Jim: need to sell the sanity aspect in light of new sigs
b1f77a
* Jim: not a fan of cute names
b1f77a
* Karsten: names are memorable
b1f77a
* Mike: the names don’t have to be cute
b1f77a
* Ralph: don’t want the name to be too long. dates are good/practical
b1f77a
* Carl: need to avoid fragmentation. no names per variants
b1f77a
* KB: Year and month is enough. It takes days to get content on the mirrors
b1f77a
* Mike: let’s enumerate the different classes of sigs/variants and think about how naming should work in each case
b1f77a
* Mike: we want to avoid giving the appearance of EUS-type support
b1f77a
* Fabian: consider chef/puppet variables
b1f77a
* could break various puppet modules/etc
b1f77a
* Karsten: can we provide major/minor number where necessary without using it at top level?
b1f77a
* Jim/KB: vendor validation
b1f77a
* Jim: too drastic a change too fast could cause a user revolt
b1f77a
* KB: just drop the subrelease altogether. E.g. centos-6-atomic
b1f77a
* Karsten: need to really think about how we will present this to the community
b1f77a
 * folks will point out holes in plan
b1f77a
 * we’ll have an iterative process
b1f77a
* KB: let’s take the rest of this offline/email
7936f7
### A wild Johnny appears!
7936f7
### Export stuff
b1f77a
* Karsten: the laws are complex, but we need a simple policy
b1f77a
* Karsten: software contributions imply access to software, which may be prohibited
b1f77a
* Karsten: we’re not here to take a political stance
b1f77a
 * let’s not let folks force us into taking one
b1f77a
 * people should not be using us to make a political statement
b1f77a
* Jim: some details about Fedora’s approach
b1f77a
* KB: a lot of people in Iran use Centos
b1f77a
 * users may be deliberately trying to push the boundaries
b1f77a
* Carl: we don’t have to be police, just state the facts (in a nice way)
b1f77a
* Jim: they can always get it from kernel.org
b1f77a
* Fabian: what / how do we communicate mirror requests
b1f77a
 * needs wording up
b1f77a
* ToDO: firewall off content from mirror-?.centos.org ( the ones hosted at redhat )
b1f77a
* desireable to have elsewhere, but not essential 
b1f77a
* ToDo: add notes to rsync header, mirrorlist node to say content is not acceptable for use in some areas
b1f77a
 * Jim to write up list of actions / content to address export control requirements
7936f7