I don't think this went to the list. It is my opinion that the git and svn repositories for our guides be included in the new requirements so that we make sure that contributions are properly licensed.
Thoughts?
--Eric
Toshio Kuratomi <a.badger@xxxxxxxxx> wrote:
>Greetings all,
>
>As you may have been made aware, the Fedora Project has recently
>switched
>From the Fedora Individual Contributor License Agreement (ICLA) to the
>Fedora Project Contributor Agreement (FPCA). We have reached the
>deadline
>for current contributors to have signed the new FPCA and are working to
>remove users who have signed the ICLA but not the FPCA from Fedora
>Groups
>where they must have signed the FPCA.
>
>In looking through the list of groups that are affected, we noticed
>that
>many of the affected groups are fedorahosted groups. Fedorahosted
>groups do
>not have a requirement to sign the FPCA from our side; the individual
>projects may make their contributors sign our contributor agreement,
>their
>own contributor agreement, or no contributor agreement at all. In most
>cases, we believe that these hosted groups were created with a default
>of
>signing our contributor agreement and then never changed.
>
>In order to minimize the disruption that Fedora switching from the ICLA
>to
>the FPCA will cause, we have removed the need for members of these
>groups to
>have signed the FPCA(list of groups attached). This will allow those
>members to remain in the hosted groups unless futher action is taken.
>
>If you do want to require all of your contributors to have a
>contributor
>agreement[1]_ with the Fedora Project, then you may follow these
>instructions
>for re-adding that as a requirement.
>
>== Requiring that a Fedora contributor agreement has been signed ==
>
>1) Make sure that you, at least, have signed the FPCA (or another valid
> contributor agreement) so there is at least one administrator in the
> group who has signed the FPCA.
>2) Go to https://fedorahosted.org/fedora-infrastructure/
>3) Click the login link and login using your fas username and password
>4) Click on the new ticket link
>5) Create a ticket of Type: change
>6) In the body of the ticket, state that you wish to have everyone who
>is
>not in the cla_done group removed from this group and have future group
> members sign the FPCA in order to be added.
>7) Set the Component to "Hosted Projects"
>8) Submit the ticket.
>
>A member of the infrastructure team will process the request.
>
>In the future these steps will likely be integrated into the Fedora
>Account
>System Web interface but currently the ticketing process is required as
>an
>infrastructure member has to do some steps manually.
>
>_[1]: Note that this includes the CLA's signed by certain corporations
>on
>behalf of their employees contributing to the Fedora Project as well as
>the
>FPCA.
>
>Thank you,
>Toshio Kuratomi
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
bzrpackagedb
bzrtest
designteam
fedora-emea-board
git-fedora-electronic-lab
git389
gitabrt
gitamber
gitanaconda
gitastronomy
gitaugeas
gitbeaker
gitbeakerlib
gitcdupgrader
gitcertmonger
gitchkconfig
gitcivx
gitcourses
gitcsi
gitdeployment-guide
gitdocbook-locales
gitdocsite-publican
giteclipse-fedorapackager
gitfas
gitfas-planet
gitfedora-cms
gitfedora-devshell
gitfedora-insight-theme
gitfedora-tour
gitfedora-zikula
gitfedora-zikula-theme
gitfedorabuzz
gitfldigi
gitfogmachine
gitfontpackages
gitfreeipa
gitfreeseer
gitgamesforscience
gitgbirthday
gitgenome
gitgfs2-utils
gitgroovyer
gitinitscripts
gitintelligentmirror
gitipadocs
gitkatello
gitlekhonee
gitliberation-fonts
gitlibvirt-qpid
gitliveusb-creator
gitlogrotate-syslog
gitmadhatter
gitmailcap
gitmatahari
gitmnm
gitmod_nss
gitmod_revocator
gitmoksha
gitmultiboot-media-creator
gitmultimedia-menus
gitnetbookdora
gitnewt
gitnitrate
gitoddjob
gitopenussd
gitopus
gitopyum
gitosutil
gitovirt
gitpam_krb5
gitpkinit-nss
gitplublican-genome
gitpublican-genome
gitpulp
gitpulsecaster
gitpyjigdo
gitpython-augeas
gitpython-meh
gitreflector
gitreport
gitrevisor
gitrevista-fedora-latam
gitrhel-comps
gitrhevm-api
gitrhgb
gitrhq
gitsamadhi
gitscap-workbench
gitsectool
gitsetroubleshoot
gitsetuptool
gitsimon
gitsnap
gitspectre
gitspins
gitsplatbind
gitsymbolic
gitsystem-config-boot
gitsystem-config-date
gitsystem-config-date-docs
gitsystem-config-display
gitsystem-config-firewall
gitsystem-config-lvm
gitsystem-config-network
gitsystem-config-nfs
gitsystem-config-nfs-docs
gitsystem-config-printer
gitsystem-config-samba
gitsystem-config-samba-docs
gitsystem-config-securitylevel
gitsystem-config-selinux
gitsystem-config-services
gitsystem-config-services-docs
gitsystem-config-users
gitsystem-config-users-docs
gitutrrs
gitvelo
gitvirt-v2v
gitvolume_key
gitwikirename
gityumex
hgauthconfig
hgfade
hgfedora-university
hgflies
hghwbrowser
hglibuser
hgmlocate
hgpam-po
hgpam-redhat
hgpasswd
hgpymail
hgpysqlface
hgpython-virtinst
hgsetroubleshoot
hgsmolt
hgsystem-config-audit
hgsystem-config-bind
hgsystem-config-httpd
hgtmpwatch
hgusermode
hgvirt-viewer
svnaspell-indic
svnbaraha-maps
svnclamsap
svncumin
svneclipse-wtp
svnendoculator
svnfirekit
svnfuel
svngforge-hindi
svngpstrekker
svnhandbook
svnidmcommon
svnim-chooser
svnindic-doc
svnindic-fonts
svnindic-locales
svnindic-ot
svnindic-sort
svnindlinux2
svniok
svnkf
svnkontrollbase
svnks-gnome-trans
svnlexwiki
svnligdesigner
svnmonksscripts
svnnevhma
svnnuxwdog
svnoo-enchant
svnpratilipi
svnpublican
svnrpmbuilder
svnsaleena
svnscribus-enchant
svnselinux-faq
svnshabdanjali
svnspellbind
svnsx
svnsystem-config-keyboard
svnsystem-config-language
svnsystem-config-netboot
svnsystem-config-printer
svnsystem-config-rootpassword
svntomcatjss
svnv7
svnvishwakarma
svnwebvirt
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
