From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
mNo edit summary
Line 24: Line 24:
Here is the updated schedule, reprinted below: <ref>https://fedoraproject.org/wiki/Summer_Coding_2010_schedule</ref>
Here is the updated schedule, reprinted below: <ref>https://fedoraproject.org/wiki/Summer_Coding_2010_schedule</ref>


<ref>‘’’Full schedule’’’
<ref>
'''Full schedule'''


April
'''April'''


      7 April - Students can begin submitting applications  
* 7 April - Students can begin submitting applications  


    * May
'''May'''


          Whole month - students, mentors, and sub-projects get to
* Whole month - students, mentors, and sub-projects get to know each other  
          know each other  
* 13 May - Mentors need to finish idea pages  
          13 May - Mentors need to finish idea pages  
* 20 May - Students applications + proposals need to be in  
          20 May - Students applications + proposals need to be in  
* 21 May - Sponsors must pledge funding by this point  
          21 May - Sponsors must pledge funding by this point  
* 24 May - Organizers finalize how many applications will be accepted  
          24 May - Organizers finalize how many applications will be
* 27 May - Mentors + admins finalize rank-ordered list  
          accepted  
* 28 May - Students informed yes/no about application  
          27 May - Mentors + admins finalize rank-ordered list  
          28 May - Students informed yes/no about application  


    * June
'''June'''


          Whole month - code, interact  
* Whole month - code, interact  
          01 June - Project begins (depending on proposal)  
* 01 June - Project begins (depending on proposal)  
  NOTE: Proposals may have a modified schedule included.
* NOTE: Proposals may have a modified schedule included.


    * July
'''July'''


          5 July - Midterm evaluations period begins  
* 5 July - Midterm evaluations period begins  
          12 July - Midterm evaluations due  
* 12 July - Midterm evaluations due  


    * August
'''August'''


          09 August - Project coding completes  
* 09 August - Project coding completes  
          16 August - Students final report, code snapshot, and
* 16 August - Students final report, code snapshot, and evaluations due  
          evaluations due  
* 20 August - Mentor evaluations due for students  
          20 August - Mentor evaluations due for students  
* 23 August - Final evaluations due back to students  
          23 August - Final evaluations due back to students  
* 25 August - Mentor, sub-project evaluations due  
          25 August - Mentor, sub-project evaluations due  


    * September
'''September'''


          01 September - Sponsors receive report from organizers  
* 01 September - Sponsors receive report from organizers  
          06 September - Sponsors release and deliver funds (proposed
* 06 September - Sponsors release and deliver funds (proposed date) </ref>
          date) </ref>


For more details:
For more details:
Line 79: Line 76:
====Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)====   
====Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)====   
[[User:Spot|Tom "spot" Callaway]]<ref> Tom "spot" Callaway</ref> from Fedora Legal announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002790.html</ref>”
[[User:Spot|Tom "spot" Callaway]]<ref> Tom "spot" Callaway</ref> from Fedora Legal announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002790.html</ref>”
Hello Fedora! (Is this thing on?)
Hello Fedora! (Is this thing on?)


Line 103: Line 101:
====F14 Naming====
====F14 Naming====
=====F14 Naming: Constaine -> Goddard -> ???=====
=====F14 Naming: Constaine -> Goddard -> ???=====
[[User:Pfrields|Paul W. Frields]]<ref> Paul W. Frields</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002791.html</ref>,
[[User:Pfrields|Paul W. Frields]] <ref> Paul W. Frields</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002791.html</ref>,
“Fedora 13 is just around the corner, so it's time for us to kick off the naming process for the next Fedora release.  You can make a suggestion for the name for Fedora 14 here:
“Fedora 13 is just around the corner, so it's time for us to kick off the naming process for the next Fedora release.  You can make a suggestion for the name for Fedora 14 here:
<ref>https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_13</ref>
<ref>https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_13</ref>
Line 115: Line 113:
=====F14 Naming: Constantine -> Goddard -> ??? =====   
=====F14 Naming: Constantine -> Goddard -> ??? =====   
[[User:Pfrields|Paul W. Frields]]<ref>Paul W. Frields</ref> on another announcement<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002792.html</ref> mentioned, “
[[User:Pfrields|Paul W. Frields]]<ref>Paul W. Frields</ref> on another announcement<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002792.html</ref> mentioned, “
On Tue, Apr 20, 2010 at 09:32:18PM -0400, Paul W. Frields wrote:
On Tue, Apr 20, 2010 at 09:32:18PM -0400, Paul W. Frields wrote:
> Fedora 13 is just around the corner, so it's time for us to kick off
> Fedora 13 is just around the corner, so it's time for us to kick off
> the naming process for the next Fedora release.  You can make a
> the naming process for the next Fedora release.  You can make a
> suggestion for the name for Fedora 14 here:
> suggestion for the name for Fedora 14 here:
>  
>  
And of course, this link should really be:
And of course, this link should really be:
Line 125: Line 127:


> Remember that there are *instructions and guidelines* at the page that
> Remember that there are *instructions and guidelines* at the page that
> you must follow if you want your name to be considered.  For instance,
> you must follow if you want your name to be considered.  For instance,
> there must be an "is-a" link between the name Constantine and the name
> there must be an "is-a" link between the name Constantine and the name
> you suggest.  That link must be different than previous links for
> you suggest.  That link must be different than previous links for
> Fedora release names.  Please be sure to conduct the required searches
> Fedora release names.  Please be sure to conduct the required searches
> for brand and trademark names that might cause us problems.
> for brand and trademark names that might cause us problems.
>  
>  
> Read the full guidelines at that page, where you can also find full
> Read the full guidelines at that page, where you can also find full
> schedule details for the release naming process.  Suggestions will be
> schedule details for the release naming process.  Suggestions will be
> collected until Tuesday, April 27, and voting will happen starting
> collected until Tuesday, April 27, and voting will happen starting
> Tuesday, May 4!
> Tuesday, May 4!



Revision as of 17:53, 21 April 2010

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Rashadul Islam

Fedora Announcement News

Summer Coding 2010 - now with more time!

Karsten Wade [1] - Senior Community Gardener of Red Hat Community Architecture announced[2], “We have pushed back the first part of the Summer Coding 2010 schedule. There wasn't enough time to find sponsors. Now there is more time for mentors and students to generate ideas and write up good proposals, while people like you and me look for more sponsors.

Highlights - note all due items now have an entire month more:

  • Ideas page closes 13 May
  • Proposals are due 20 May
  • Sponsors must pledge by 21 May

Projects are set to start on 01 June, which is only a week after the original start date. Our goal is to be as flexible as we can be after that, contact us if you have any questions about how to make the schedule work for you: [3]

Here is the updated schedule, reprinted below: [4]

[5]

For more details: [6]

Thanks,

- Summer Coding SIG

  1. Karsten Wade
  2. http://lists.fedoraproject.org/pipermail/announce/2010-April/002789.html
  3. https://fedoraproject.org/wiki/Communication_for_Summer_Coding_2010
  4. https://fedoraproject.org/wiki/Summer_Coding_2010_schedule
  5. Full schedule April
    • 7 April - Students can begin submitting applications
    May
    • Whole month - students, mentors, and sub-projects get to know each other
    • 13 May - Mentors need to finish idea pages
    • 20 May - Students applications + proposals need to be in
    • 21 May - Sponsors must pledge funding by this point
    • 24 May - Organizers finalize how many applications will be accepted
    • 27 May - Mentors + admins finalize rank-ordered list
    • 28 May - Students informed yes/no about application
    June
    • Whole month - code, interact
    • 01 June - Project begins (depending on proposal)
    • NOTE: Proposals may have a modified schedule included.
    July
    • 5 July - Midterm evaluations period begins
    • 12 July - Midterm evaluations due
    August
    • 09 August - Project coding completes
    • 16 August - Students final report, code snapshot, and evaluations due
    • 20 August - Mentor evaluations due for students
    • 23 August - Final evaluations due back to students
    • 25 August - Mentor, sub-project evaluations due
    September
    • 01 September - Sponsors receive report from organizers
    • 06 September - Sponsors release and deliver funds (proposed date)
  6. http://iquaid.org/2010/04/14/more-time-for-fedora-summer-coding-schedule-moved-back-a-month/

Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)

Tom "spot" Callaway[1] from Fedora Legal announced[2]

Hello Fedora! (Is this thing on?)

Sorry for the very wide net, but we wanted to make sure as many members of our community could see this as possible.

For some time now, Fedora has been working with Red Hat Legal to come up with a replacement for the Fedora Individual Contributor License Agreement (aka, the Fedora ICLA). As a result, the Fedora Project Contributor Agreement (FPCA) has been approved by Red Hat Legal, and is now being presented to the Fedora Community for comments and discussion.

The full text of the FPCA, along with a FAQ, can be found here: [3]

Please, take a moment and read the FPCA and the FAQ. It is not a long, or overly complicated document, as legal documents go, but it is important that all Fedora Contributors read it over and make sure they understand it and like it (or can at least agree to it).

Fedora Legal wishes to give the Fedora community a window of time for discussion and review of the FPCA. This window is open until May 18, 2010 (2010-05-18). After that point, either a revised FPCA will be released for review, or we will begin the process of phasing in the FPCA and phasing out the Fedora ICLA.

Thanks in advance,

Tom "spot" Callaway, Fedora Legal

P.S. Fedora Legal would like to give a huge thank you to the people involved behind the scenes to make the FPCA possible. The primary author was Richard Fontana, with feedback from Tom Callaway, Pamela Chestek, Paul Frields, and Robert Tiller. Feel free to give them gifts (for example, drinks or tasty snacks) as thank yous, although, this is not a requirement (legal or otherwise). ;)

F14 Naming

F14 Naming: Constaine -> Goddard -> ???

Paul W. Frields [1] announced[2], “Fedora 13 is just around the corner, so it's time for us to kick off the naming process for the next Fedora release. You can make a suggestion for the name for Fedora 14 here: [3]

Remember that there are *instructions and guidelines* at the page that you must follow if you want your name to be considered. For instance, there must be an "is-a" link between the name Constantine and the name you suggest. That link must be different than previous links for Fedora release names. Please be sure to conduct the required searches for brand and trademark names that might cause us problems.

Read the full guidelines at that page, where you can also find full schedule details for the release naming process. Suggestions will be collected until Tuesday, April 27, and voting will happen starting Tuesday, May 4!”

F14 Naming: Constantine -> Goddard -> ???

Paul W. Frields[1] on another announcement[2] mentioned, “

On Tue, Apr 20, 2010 at 09:32:18PM -0400, Paul W. Frields wrote: > Fedora 13 is just around the corner, so it's time for us to kick off

> the naming process for the next Fedora release. You can make a

> suggestion for the name for Fedora 14 here:

> And of course, this link should really be:

[3]

> Remember that there are *instructions and guidelines* at the page that

> you must follow if you want your name to be considered. For instance,

> there must be an "is-a" link between the name Constantine and the name

> you suggest. That link must be different than previous links for

> Fedora release names. Please be sure to conduct the required searches

> for brand and trademark names that might cause us problems. > > Read the full guidelines at that page, where you can also find full

> schedule details for the release naming process. Suggestions will be

> collected until Tuesday, April 27, and voting will happen starting

> Tuesday, May 4!

Apologies for the error.”

Fedora Development News

Fedora Events

Fedora events are the source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (March 2010 to May 2010)

  • North America (NA)[1]
  • Central & South America (LATAM) [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Past Events

Archive of Past Fedora Events[1]

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.