On Fri, Jun 17, 2011 at 12:44:17PM -0700, Toshio Kuratomi 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 ==
- 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.
- Go to https://fedorahosted.org/fedora-infrastructure/
- Click the login link and login using your fas username and password
- Click on the new ticket link
- Create a ticket of Type: change
- 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.
- Set the Component to "Hosted Projects"
- 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.
[...snip...]
gitfedora-insight-theme
Given this project is by Fedora/for Fedora, it's probably a good idea for us to require FPCA for contributions. Thoughts on that?
gitfedora-zikula gitfedora-zikula-theme
These are actually deprecated, so I'm not really concerned about them. Perhaps these should be retired as dead projects though?
Hi!
I agree with Paul, so +1 to require FPCA for contributions into Insight theme. -- Peter
On Fri, Jun 17, 2011 at 10:24 PM, Paul W. Frields stickster@gmail.com wrote:
On Fri, Jun 17, 2011 at 12:44:17PM -0700, Toshio Kuratomi 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 ==
- 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.
[...snip...]
gitfedora-insight-theme
Given this project is by Fedora/for Fedora, it's probably a good idea for us to require FPCA for contributions. Thoughts on that?
gitfedora-zikula gitfedora-zikula-theme
These are actually deprecated, so I'm not really concerned about them. Perhaps these should be retired as dead projects though?
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ logistics mailing list logistics@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/logistics
logistics@lists.fedoraproject.org