Search results for "contribute to wiki"

[Ambassadors] Re: [fedora-india] Re: Re: Need your help in organizing a Fedora Women Day event at Pune

by Amita

On 06/29/2016 03:05 PM, Priyanka Nag wrote: > Hey all, > > A few of the local Fedora ambassadors and event organizers for FWD > Pune event met this morning for a quick discussion on the proposed > event and here we have the meeting notes for everyone: > > [1] Apologies that this part wasn't well explained previously but the > list of talks that you see on the pirate pad, mainly under the > '*Getting Started with your Fedora contribution' *section are > going**to be flash talks for 5 mins each. Since we couldn't find > existing female contributors in all of these different contribution > pathways, to share their experience with us; a group of volunteers > decided to try finding out details about these different contribution > pathways, how to get started, the related IRC channels and mailing > lists for each and finally give a 5 min presentation about their > findings. This can save the rest of the audience's effort to do a > complete research on the different contribution pathways (which is > often the first barrier in contribution) and they should have most of > the data at hand to now go back and start contributing. The FWD event > was also thought of as a first step to initiating a consistent women > contributor community, where each month we could take up one of these > contribution pathways and make it as the flavor of the month...doing > some actual hands-on contribution together for that chosen project or > pathway. This can probably even be clubbed with the monthly Fedora > meetups that we have in Pune. That ofcourse can be discussed in more > details with the local ambassadors. > > [2] The new speakers can try and do some actual contributions before > the FWD event so that they can also share their experience (and > blockers) at the event. They could also join the upcoming Fedora > monthly meetup and release party, planned on 9th July, at Pune. > > [3] The organizers are suggested to try reach out to college students > (not just via emails or messages, but by physically going down to > colleges) since this event can be a good place for new contributors to > know how to get started with their contribution as well as meet other > existing and experienced community members. > > [4] The organizers are also suggested to do more social media posts > about the event, so as to create more awareness around this event. > > [5] The new contributors and speakers can also join the Fedora > telegram group, since not all of us are big IRC fans. > > [6] The speaker and attendee list to be moved to Wiki from the etherpad. Thanks, updated https://fedoraproject.org/wiki/FWD_Pune . Regards, Amita > > I hope I have covered all the points that was discussed in today's > meeting. If not, today's meeting attendees, please add those points to > the thread here. > > If anyone has any further questions on any of the above points or any > suggestions for the event in general, please do feel free to shoot a > response to this thread. > > > > > _______________________________________________ > india mailing list > india(a)lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/india@lists.fedoraproject.org

7 years, 10 months

Fedora Weekly News 265

by Pascal Calarco

* 1 Fedora Weekly News Issue 265 o 1.1 Announcements + 1.1.1 Fedora Announcement News # 1.1.1.1 Infrastructure Outage Notification: 2011-03-02 1200 UTC -> 1500 UTC # 1.1.1.2 Updated: Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC * 1.1.1.2.1 Reason for outage * 1.1.1.2.2 Contact Information + 1.1.2 Fedora Events # 1.1.2.1 Upcoming Events (Dec 2010 - Feb 2011) # 1.1.2.2 Past Events # 1.1.2.3 Additional information o 1.2 Fedora In the News + 1.2.1 Who Contributes the Most to LibreOffice? (Linux Journal) + 1.2.2 Fedora 15 alpha delayed - Btrfs may be default in 16 (H Online) + 1.2.3 Beyond FUDCon with Robyn Bergeron, Fedora Program Manager (Linux Magazine) o 1.3 Ambassadors + 1.3.1 Welcome New Ambassadors + 1.3.2 Summary of traffic on Ambassadors mailing list + 1.3.3 Summary of events reported on Ambassadors mailing list + 1.3.4 Summary of traffic on FAmSCo mailing list o 1.4 QualityAssurance + 1.4.1 Test Days + 1.4.2 Fedora 15 Alpha preparation + 1.4.3 Bodhi improvements + 1.4.4 FreeIPA Test Day problems and proposals + 1.4.5 Complications for Delta ISO users + 1.4.6 IPv6 testing + 1.4.7 Using abrt during Test Days o 1.5 Security Advisories + 1.5.1 Fedora 14 Security Advisories + 1.5.2 Fedora 13 Security Advisories o 1.6 LATAM Fedora! + 1.6.1 Ruby Capítulo 1: El primer contacto # 1.6.1.1 Aprovechando el espacio # 1.6.1.2 Los "Hola mundo" * 1.6.1.2.1 holamundo.rb * 1.6.1.2.2 holamundo.rb # 1.6.1.3 Ruby es un lenguaje de programación orientado a objetos # 1.6.1.4 Pero no necesito clases # 1.6.1.5 Clases base * 1.6.1.5.1 Cadenas de caracteres, String * 1.6.1.5.2 Arreglos, Array * 1.6.1.5.3 Arreglos indexados arbitrariamente, Hash * 1.6.1.5.4 Recapitulación rápida, los objetos y sus métodos, ¿documentación? # 1.6.1.6 Ruby es dinámico ¿ 2 + 2 = 4 ? * 1.6.1.6.1 fixnum_mod.rb * 1.6.1.6.2 Y ahora ejecutamos nuestro programa: # 1.6.1.7 Estructuras de control # 1.6.1.8 Lazos e iteradores * 1.6.1.8.1 Lazo con for y loop: - Fedora Weekly News Issue 265 - Welcome to Fedora Weekly News Issue 265[1] for the week ending March 2, 2011. What follows are some highlights from this issue. Our issue kicks off with a couple outage announcements from this past week, followed by three articles 'In the News', including an interview with Fedora Program Manager, Robyn Bergeron. In Ambassador news, summaries of traffic on the Ambassador and FAmSCo lists, and QA brings us a whole slew of Test Day details over the next few weeks, Fedora 15 prep and bodhi improvements. Security Advisories keeps us updated with security-related patches released this past week. We're also very pleased this week to kick off our foreign language content initiative, which developed out of FUDCon Tempe, with a new Latin American beat, all in Spanish. To start off, we have part one of a Ruby on Fedora primer, contributed by Guillermo Gómez, a Fedora Ambassador in Venezuela. If you would like to contribute Fedora-related content in your language, please send a note to the editors! An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news(a)lists.fedoraproject.org FWN Editorial Team: Pascal Calarco, Adam Williamson 1. http://fedoraproject.org/wiki/FWN/Issue265 2. http://www.archive.org/search.php?query=subject%3A%22FWN%22 3. http://fedoraproject.org/wiki/NewsProject/Join -- 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 1. http://lists.fedoraproject.org/pipermail/announce/ 2. http://lists.fedoraproject.org/pipermail/devel-announce/ 3. http://fedoraproject.org/wiki/Events --- Fedora Announcement News --- The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1] 1. https://admin.fedoraproject.org/mailman/listinfo/announce ---- Infrastructure Outage Notification: 2011-03-02 1200 UTC -> 1500 UTC ---- Stephen John Smoogen on Tue Mar 1 20:13:07 UTC 2011 announced[1], "Tomorrow the services at ibiblio will be moved to a new physical location * ibiblio01.fedoraproject.org * app05 * backup02 * ns02 * proxy04 * smtp-mm03 * torrent01" 1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002928.html ---- Updated: Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC ---- Stephen John Smoogen on Tue Mar 1 22:09:31 UTC 2011 announced[1], "Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC There will be an outage starting at UTC, 2011-03-02 14:00 which will last approximately 4 hours. To convert UTC to your local time, take a look at[2] or run: date -d '2011-03-02 14:00 UTC' ----- Reason for outage ----- metalabs is moving facilities and needs for our collocated server to move with them. Systems will be down and getting new IP addresses with the move. [3] ----- Contact Information ----- Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage." 1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002929.html 2. http://fedoraproject.org/wiki/Infrastructure/UTCHowto 3. https://fedorahosted.org/fedora-infrastructure/ticket/2651 --- Fedora Events --- The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and 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 (Dec 2010 - Feb 2011) ---- * North America (NA)[1] * Central & South America (LATAM): [2] * Europe, Middle East, and Africa (EMEA)[3] * India, Asia, Australia (India/APJ)[4] 1. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29 2. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2 3. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3 4. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4 ---- Past Events ---- Archive of Past Fedora Events[1] 1. http://fedoraproject.org/wiki/FedoraEvents/PastEvents ---- 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. -- Fedora In the News -- In this section, we cover news from the trade press and elsewhere that is re-posted to the Fedora Marketing list[1]. http://fedoraproject.org/wiki/Marketing Contributing Writer: Pascal Calarco 1. http://lists.fedoraproject.org/pipermail/marketing/ --- Who Contributes the Most to LibreOffice? (Linux Journal) --- Rahul Sundaram forwarded[1] an article from Linux Journal noting contributions to LibreOffice: "Bosdonnat began tracking line contributions in the middle of September 2010 with the original 14 contributions being made by Oracle. Oracle actually contributes code to OpenOffice.org, and then LibreOffice merges those changes, thus resulting in Oracle's contributions to the new fork. These 112 contributions have continued throughout development, but are dwarfed by the contributions of new developers." These contributions make up well over half of the total new changes found in LibreOffice as of mid-February. Weekly contributions in this area have averaged between 20 and 30 with a total number of 517 line contributions. Red Hat, who also contributed to OpenOffice.org, has chipped in as well. With usually two contributions per week, Red Hat developers have provided 39 patches since the fork." The full article is available[2]. 1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013722.html 2. http://www.linuxjournal.com/content/who-contributes-most-libreoffice --- Fedora 15 alpha delayed - Btrfs may be default in 16 (H Online) --- Rahul Sundaram forwarded[1] an an article in The H Online about the decision to push back Fedora 15 alpha: "The Fedora project has postponed the release of the first and only alpha version of Fedora 15, originally scheduled for 1 March, by a week. This was due, at least in part, to a bug in X Server that occurred in connection with keyboard layouts for such languages as German or French and prevented users from successfully logging into GDM. Subsequent milestones in the release schedule for Fedora 15 remain unaffected at present, and the final release is still scheduled for 10 May. The fifteenth Fedora release is currently planned to be the first version that won't require a special boot parameter to be submitted to the installer in order to format a storage device with the experimental Btrfs file system. Red Hat employee Josef Bacik, who is heavily involved in the development of Btrfs, has now proposed on the project's most important developer mailing list that Btrfs should be made the default file system in Fedora 16, which is expected in late October or early November" The full post is available[2]. 1. http://lists.fedoraproject.org/pipermail/marketing/2011-February/013713.html 2. http://www.h-online.com/open/news/item/Fedora-15-alpha-delayed-Btrfs-may-... --- Beyond FUDCon with Robyn Bergeron, Fedora Program Manager (Linux Magazine) --- Rahul Sundaram forwarded[1] another article highlighting Fedora community leaders, this with Robyn Bergeron, who remarked: "I personally would love to see more folks getting involved in areas that don't necessarily require coding skills. I think that there is enormous room for growth and contribution in these areas, and there are plenty of Linux enthusiasts out there who have the skills and imagination to make great contributions in these places." The full article is available[2] -- Ambassadors -- This section covers the news surrounding the Fedora Ambassadors Project[3]. Contributing Writer: Sankarshan Mukhopadhyay 1. http://lists.fedoraproject.org/pipermail/marketing/2011-February/013714.html 2. http://www.linux-magazine.com/Online/News/Beyond-FUDCon-with-Robyn-Berger... 3. http://fedoraproject.org/wiki/Ambassadors --- Welcome New Ambassadors --- This week the Fedora Ambassadors Project had no new members joining. --- Summary of traffic on Ambassadors mailing list --- Pierros Papadeas posted [1] about Ambassador SOPs [2] on which FAmSCo has been working. Clint Savage suggested [3] attending the FAD at SCaLE this year specifically mentioning the Sysadmin Study Group Buddhika Kurera informed [4] that the order for the FAm T-shirts [5] had been placed and expected delivery is around end of March (impacted by the orders around the ICC Cricket World Cup) Neville A. Cross asked [6] if any other Fedora Project participants would be attending PyCon from 2011-03-08 till 2011-03-13. Mark McIntyre responded [7] and provided his plans. Max Spevack suggested [8] creating an Event page and also posting to devel at lists.fedoraproject.org. The page [9] was created by Mark McIntyre Pierre-Yves Chibon posted [10] the translated annual report [11] for Fedora-Fr, the French speaking NPO. David Ramsey provided prior notice [12] about Fedora 15 Test Days [13] coming up David Ramsey posted [14] the draft Agenda [15] of the APAC meeting on 2011-03-05 Caius Chance informed [16] about having around 700 F14 LiveCDs with him at Brisbane and wanted to get them to Fedora Ambassadors in APAC soonest. The thread [17] had requests from Ambassadors who wanted the CDs. Christoph Wickert announced [18] that the Trac instance used by the Fedora Board [19] was open for ticket submissions by all FAS account holders. Christoph Wickert provided an update [20] on the Fedora 14 media for EMEA Max Spevack posted [21] an initial announcement of the Finance SIG [22] David Ramsey posted [23] about Summer Coding Ideas for 2011 [24] Larry Cafiero posted [25] Meeting Minutes from FAmNA meeting on 2011-03-01[26] 1. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017066... 2. https://fedoraproject.org/wiki/Ambassadors_SOPs 3. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017071... 4. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017073... 5. https://fedoraproject.org/wiki/User:Bckurera/APAC-shirts 6. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017077... 7. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017090... 8. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017099.html 9. https://fedoraproject.org/wiki/FedoraEvents/PyCon_2011 10. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017078... 11. https://fedoraproject.org/wiki/Fedora-Fr_annual_report_2010 12. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017079... 13. https://fedoraproject.org/wiki/Category:Fedora_15_Test_Days 14. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017081... 15. https://fedoraproject.org/wiki/Meeting:APAC_Ambassadors_2011-03-05#Agenda 16. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017083... 17. http://lists.fedoraproject.org/pipermail/famsco/2011-February/thread.html... 18. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017094... 19. https://fedorahosted.org/board/newticket 20. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017095... 21. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017098.html 22. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010523... 23. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017102.html 24. https://fedoraproject.org/wiki/Summer_coding_ideas_for_2011 25. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017105.html 26. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora-meeting... --- Summary of events reported on Ambassadors mailing list --- No event reports were posted to the Ambassadors mailing list. --- Summary of traffic on FAmSCo mailing list --- Caius Chance informed [1] about having around 700 F14 LiveCDs with him at Brisbane and wanted to get them to Fedora Ambassadors in APAC soonest. Max Spevack posted [2] an initial announcement of the Finance SIG [3] 1. http://lists.fedoraproject.org/pipermail/famsco/2011-February/000687.html 2. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000688.html 3. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010523... -- Quality Assurance -- In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2]. Contributing Writer: Adam Williamson 1. http://fedoraproject.org/wiki/QA 2. http://fedoraproject.org/wiki/QA/Join --- Test Days --- Thursday 2011-02-17 was Xfce 4.8[1] Test Day[2]. The event was well organized by the Xfce team, and a dedicated group of testers was able to expose some important bugs to be fixed. The week of 2011-02-21 saw the traditional Graphics Test Week. Adam Williamson posted a full recap of the event to the mailing list[3]. He noted that participation was up again compared to the Fedora 14 events and that some important testing had been carried out, but also noted a worrying trend in status of bugs from previous events, with many bugs reported during the Fedora 13 and 14 events remaining unfixed. He promised to investigate the causes of this. This week (and next Tuesday!) is internationalization and localization Test Week, and Adam Williamson put up a blog post[4] explaining the three Test Days this includes: the Anaconda i18n and l10n Test Day on 2011-03-01[5], the desktop i18n Test Day on 2011-03-03[6] and the desktop l10n Test Day on 2011-03-08[7]. All these events are very important to ensure that non-US-English-speaking users of Fedora get a great experience with Fedora 15. Thursday 2011-03-10 will be the second of three planned GNOME 3 Test Days[8], where we'll continue to work with the GNOME team to test GNOME 3.0 and its integration with Fedora 15 as rigorously as we can before the final release of both. We'll be repeating the tests from the previous event to see how things have progressed, and also running some new tests which have been added for this event. As before, this is a very important event for both Fedora and GNOME and affects most Fedora users, so if you have a few minutes to spare, please come along and help testing. Once again, live images will be available to make it easier to test, and we'll have a new process in place for reporting crasher bugs without the trouble of trying to install debuginfo packages on a live image! 1. http://fedoraproject.org/wiki/Features/Xfce48 2. http://fedoraproject.org/wiki/Test_Day:2011-02-17_Xfce 3. http://lists.fedoraproject.org/pipermail/test-announce/2011-March/000200.... 4. http://www.happyassassin.net/2011/02/28/internationalization-and-localiza... 5. http://fedoraproject.org/wiki/Test_Day:2011-03-01_L10n_i18n_Installation 6. http://fedoraproject.org/wiki/Test_Day:2011-03-03_I18n_Desktop 7. http://fedoraproject.org/wiki/Test_Day:2011-03-08_L10n_Desktop 8. http://fedoraproject.org/wiki/Test_Day:2011-03-10_GNOME3_Beta --- Fedora 15 Alpha preparation --- The QA team has been busy over the last two weeks validating the Fedora 15 Alpha release, with TC2[1], RC1[2], and RC2[3] candidate builds being posted and tested. As always, the whole team chipped in with the all-important testing. In the end the RC1 image was not accepted and the release delayed for a week[4] due to a significant bug with many non-English keyboard layouts which was exposed during the testing. With this bug fixed, the RC2 image was accepted as gold at the go/no-go meeting of 2011-03-02[5]. --- Bodhi improvements --- At the weekly meeting of 2011-02-28[6], Luke Macken announced that package-specific test case integration into Bodhi is now live, meaning that packages which have test cases associated with them according to the package test plan SOP[7] will now have the test cases displayed in Bodhi when an update for the package is under review. Also going live in the new Bodhi release are the improvements to the automated messages Bodhi sends to Bugzilla when an update's status changes, improvements discussed in previous issues of this newsletter. 1. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 2. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 3. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 4. http://lists.fedoraproject.org/pipermail/devel-announce/2011-February/000... 5. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora_15_alph... 6. http://fedoraproject.org/wiki/QA/Meetings/20110228 7. http://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation --- FreeIPA Test Day problems and proposals --- Dmitri Pal posted a comment to the FreeIPA Test Day trac ticket[1] noting that he was unhappy with the way the event had turned out. Adam Williamson, James Laska and Jóhann Guðmundsson joined in with suggestions to try and learn from this experience. Dmitri is considering re-running the event with some tweaks. 1. http://fedorahosted.org/fedora-qa/ticket/163#comment:10 --- Complications for Delta ISO users --- Andre Robatino provided some detailed information[1] on what a change to the xz compression scheme would mean for users of DeltaISOs. In a nutshell, users trying to use Fedora 14 -> Fedora 15 DeltaISOs will need to use a workaround, detailed in the post, if applying the ISO on a Fedora 14 system. Andre followed up later with a refinement of the workaround[2]. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097009.html 2. http://lists.fedoraproject.org/pipermail/test/2011-February/097284.html --- IPv6 testing --- A.J. Werkman provided a recap of some very solid testing he had performed on Fedora's out-of-the-box IPv6 capabilities[1]. He identified some significant problems and reported them as bugs, including anaconda refusing to work without an IPv4 DHCP lease, and Fedora's Bugzilla not being available in the IPv6 domain. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097153.html --- Using abrt during Test Days --- A thread[1] started by Mike Cloaked highlighted the issue of abrt being difficult or impossible to use successfully from live images (such as during Test Days), in large part due to the size of debuginfo packages. Adam Williamson pointed out[2] that the abrt team's retrace server project[3] would be a perfect solution for this, but noted that he had not yet tested using it. When he did, it seemed not yet to be ready for Fedora 15[4]. Jiri Moskovc said that the Fedora 15 support would soon be available[5]. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097271.html 2. http://lists.fedoraproject.org/pipermail/test/2011-February/097289.html 3. http://fedoraproject.org/wiki/Features/RetraceServer 4. http://lists.fedoraproject.org/pipermail/test/2011-February/097299.html 5. http://lists.fedoraproject.org/pipermail/test/2011-February/097314.html -- Security Advisories -- In this section, we cover Security Advisories from fedora-package-announce from the past week. http://lists.fedoraproject.org/pipermail/package-announce Contributing Writer: Pascal Calarco --- Fedora 14 Security Advisories --- none --- Fedora 13 Security Advisories --- * ruby-1.8.6.420-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * abcm2ps-5.9.21-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * telepathy-glib-0.11.16-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * telepathy-gabble-0.10.5-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... -- LATAM Fedora! -- LATAM Fedora is a regular column of Spanish language contributions around open source software. It is our first expansion into incorporating foreign language content into FWN. This week's contribution is from Guillermo Gómez, a primer on Ruby. Enjoy! --- Ruby Capítulo 1: El primer contacto --- "Yo quería un lenguaje de programación más poderoso que Perl y más orientado a objetos que Python. Entonces me acordé de mi viejo sueño y decidí diseñar mi propio lenguaje. Al principio estuve jugando con él en el trabajo. Gradualmente creció lo suficiente como para remplazar a Perl. Lo llamé Ruby en honor a esa piedra preciosa roja y lo liberé al público en 1995." Yukihiro Matsumoto, a.k.a. ``Matz Japan, October 2000 ---- Aprovechando el espacio ---- Para comenzar en Fedora con Ruby vamos instalar lo mínimo necesario y sin perder mucho espacio dando vueltas con teoría y opiniones, directo al grano. Abra una sesión de emulación de terminal preferida y siga las siguientes instrucciones para instalar. En la medida que desarrollemos esta columna dedicada a Ruby, entonces iremos descubriendo el poder y flexibilidad de Ruby. $ su - <contraseña de root> # yum install ruby ruby-rdoc ruby-ri Para el editor, hay muchas opciones, mi editor de preferencia es Vim , pero puede usar el de su preferencia, intente usar alguno que pueda resaltar sintaxis Ruby como mínimo. Puede escoger desde entornos tan complejos y completos como Eclipse, hasta editores de escritorio GUI como Gedit, o simples en consola como nano o complejos y sofisticados como Vim y Emacs. ---- Los "Hola mundo" ---- La primera forma interactiva simple de ejecutar comandos Ruby es simplemente usar el intérprete, simplemente ejecute el intérprete, ingrese los comandos y termine presionando Ctrl-D para indicarle al intérprete que la entrada de comandos ha finalizado: $ ruby puts "Hola Mundo" <Ctrl-D> Hola Mundo La segunda forma interactiva es con irb. irb es el acrónimo para Interactive Ruby. irb es un shell Ruby, es decir, es un espacio donde puede evaluar su código al instante. En próximas ediciones iremos desarrollando más el tema de irb, por ahora simplemente invoque a irb e intente: $ irb irb(main):001:0> puts "Hola Mundo" Hola Mundo => nil irb(main):002:0>exit $ Si lo que quiere es crear un programa Ruby que nos imprima "Hola Mundo" en la salida del monitor, lance su editor e incluya el siguiente código fuente en un archivo denominado holamundo.rb., guarde y salga de su editor. ----- holamundo.rb ----- 1 puts "Hola Mundo" Para ejecutar simplemente pásale al intérprete Ruby el archivo como argumento. [gomix@fricky capitulo_1]$ ruby holamundo.rb Hola Mundo También puede usar el método "shebang" y convertir el archivo fuente Ruby en ejecutable del sistema, edite su holamundo.rb para que luzca como se muestra en el listado a continuación. ----- holamundo.rb ----- 1 #!/usr/bin/ruby 2 3 puts "Hola Mundo" [gomix@fricky capitulo_1]$ chmod +x holamundo.rb [gomix@fricky capitulo_1]$ ./holamundo.rb Hola Mundo Existe la forma de pasarle directamente código Ruby al intérprete sin apoyo de archivos o programas adicionales y sin entrar en modo interactivo. $ ruby -e 'puts "Hola Mundo"' Hola Mundo ---- Ruby es un lenguaje de programación orientado a objetos ---- Todo lo que usted manipula en Ruby es un objeto, y los resultados de dichas manipulaciones a su vez, también son objetos. Cuando usted escribe código orientado a objetos normalmente está modelando conceptos del mundo real en su código. Típicamente durante este proceso de modelado usted descubrirá categorías de cosas que necesitan ser representadas en código. En un reproductor de música el concepto de "canción" puede ser una de esas categorías. En Ruby usted define una clase para representar cada una de esas entidades. Una clase es una combinación de estado, por ejemplo el nombre de la canción, y métodos que usan dicho estado, por ejemplo para reproducir la canción. Una vez que tiene dichas clases usted creará instancias de dicha clase. Para el reproductor de música que contiene la clase Cancion usted terminará teniendo instancias separadas independientes para canciones populares como "Todo o nada", "Canción para un amigo", "Amanecer llanero", y por el estilo. La palabra objeto e instancia son intercambiables. En Ruby para crear dichas instancias u objetos, se debe llamar a un método constructor de la clase, el método constructor estandar se llama new. 1 cancion1 = Cancion.new("Amanecer llanero") 2 cancion2 = Cancion.new("Todo o nada") Estas instancias son derivadas de la misma clase pero tienen características únicas. Primero, cada objeto tiene un object_id único. Segundo, usted puede definir variables de instancia, variables con valor que son únicos para cada instancia. Estas variables de instancia mantienen el estado del objeto. Igualmente puede definir métodos de instancia para acceder y/o alterar el estado del objeto, es decir, acceder y/o alterar las variables de instancia. Rápidamente definamos nuestra clase Cancion. Ruby se puede leer fácilmente. 1 class Cancion 2 def titulo 3 @titulo 4 end 5 6 def titulo=(titulo_de_la_cancion) 7 @titulo = titulo_de_la_cancion.to_s 8 end 9 end Claramente podemos ver y leer que hemos definido la clase de nombre Cancion con dos métodos de instancia, titulo y titulo=. La variable de instancia se representa en @titulo , con la notación de nombre de variable en minúscula precedida del símbolo @ . Note la indentación que hemos implementado para representar la estructura, dos espacios es cómun entre los Rubyeros (me gusta llamarlos así). Es evidente que la plabra clave class establece el inicio de un bloque que se cierra con end para definir una clase con nombre, en este ejemplo Cancion. Dentro de dicha estructura también podemos identificar claramente la palabra clave def que igualmente define bloques que se cierran también con la palabra clave end. def define dos métodos de instancia en este ejemplo. Hablaremos más de def de forma recurrente en muchas ediciones de esta columna. Podemos probar nuestra clase en irb fácilmente, por ahora tipee con cuidado para no equivocarse, luego le ofreceré más técnicas irb. 1 $ irb 2 >> class Cancion 3 >> def titulo 4 >> @titulo 5 >> end 6 >> def titulo=(titulo_de_la_cancion) 7 >> @titulo = titulo_de_la_cancion.to_s 8 >> end 9 >> end 10 => nil 11 >> cancion1 = Cancion.new 12 => #<Cancion:0xb76e25c8> 13 >> cancion1.titulo="Alma llanera" 14 => "Alma llanera" 15 >> cancion1.titulo 16 => "Alma llanera" ---- Pero no necesito clases ---- También se puede usar Ruby del modo procedimental, funcional, sin necesidad de crear (explícitamente) clases y objetos. 1 $ irb 2 >> 2 + 2 3 => 4 Pero igual note que estamos trabajando con objetos de alguna clase, en nuestro ejemplo Fixnum. 1 >> 2.class 2 => Fixnum Puede definir métodos y llamarlos: 1 >> def saludo 2 >> puts "Hola Mundo" 3 >> end 4 => nil 5 >> saludo 6 Hola Mundo 7 => nil ---- Clases base ---- Ya que "todo" son objetos de alguna clase, más vale que comencemos por aprender las más fundamentales del lenguaje, Fixnum, Bignum, Float, String, Array y Hash. Números... Fixnum, Bignum, Float Enteros, dejemos que nuestro código Ruby hable. 1 >> num = 8 2 => 8 3 >> 7.times do 4 ?> print num.class, " ", num, "\n" 5 >> num *= num 6 >> end 7 Fixnum 8 8 Fixnum 64 9 Fixnum 4096 10 Fixnum 16777216 11 Bignum 281474976710656 12 Bignum 79228162514264337593543950336 13 Bignum 6277101735386680763835789423207666416102355444464034512896 14 => 7 15 >> num = 3.14 16 => 3.14 17 >> 8.times do 18 ?> print num.class, " ", num, "\n" 19 >> num *= num 20 >> end 21 Float 3.14 22 Float 9.8596 23 Float 97.21171216 24 Float 9450.11698107869 25 Float 89304710.9560719 26 Float 7.97533139894754e+15 27 Float 6.36059109230385e+31 28 Float 4.04571190434951e+63 ---- Cadenas de caracteres, String ---- 1 >> "Hola Mundo".class 2 => String 3 >> "987".class 4 => String < ---- Arreglos, Array ---- 1 >> arreglo = ["a",1,"b",2] 2 => ["a", 1, "b", 2] 3 >> arreglo.class 4 => Array 5 >> arreglo[0] 6 => "a" 7 >> arreglo[1] 8 => 1 < ---- Arreglos indexados arbitrariamente, Hash ---- 1 >> hash = { "color" => "rojo", "temperatura" => 75, 1 => "hoy"} 2 => {1=>"hoy", "temperatura"=>75, "color"=>"rojo"} 3 >> hash.class 4 => Hash 5 >> hash["color"] 6 => "rojo" 7 >> hash["temperatura"] 8 => 75 9 >> hash[1] 10 => "hoy" ---- Recapitulación rápida, los objetos y sus métodos, ¿documentación? ---- Teniendo cualquier objeto de cualquier clase a la mano, para acceder a su métodos podemos usar la sintaxis objeto.método. En el ejemplo abajo llamamos al popular método to_s que nos ofrece una representación en String del objeto en cuestión. 1 >> hash.to_s 2 => "1hoytemperatura75colorrojo" 3 >> arreglo.to_s 4 => "a1b2" 5 >> 8.to_s 6 => "8" Ahora bien, ¿dónde consigo la documentación de dichas clases y métodos? Demos la bienvenida a ri para ayuda local en línea de comandos, y por supuesto, en la web a http://www.ruby-doc.org/ . Francamente, en nuestros días la primera fuente de información es la Web, y en segundo lugar, nuestros recursos locales como ri. Entonces, y para efectos de esta serie de artículos, vamos a usar inicialmente Ruby 1.8.7. * http://www.ruby-doc.org/core-1.8.7/ * http://www.ruby-doc.org/stdlib-1.8.7/ Ejemplo de salida ri (extracto). $ ri Fixnum ------------------------------------------------ Class: Fixnum < Integer A +Fixnum+ holds +Integer+ values that can be represented in a native machine word (minus 1 bit). If any operation on a +Fixnum+ exceeds this range, the value is automatically converted to a +Bignum+. ... Instance methods: ----------------- %, &, *, **, +, -, -@, /, <, <<, <=, <=>, ==, >, >=, >>, [], ^, __serialize__, abs, dclone, div, divmod, html_safe?, id2name, modulo, power!, quo, rdiv, rpower, size, to_f, to_s, to_sym, xchr, zero?, |, ~ ---- Ruby es dinámico ¿ 2 + 2 = 4 ? ---- Uno de los aspectos notables de Ruby es su dinamismo, una forma de visualizarlo es hacer uso del hecho que todas las clases están "abiertas" y es posible redefinir sus métodos, por ejemplo: ----- fixnum_mod.rb ----- #!/usr/bin/ruby # class Fixnum def +(otro) 100 end end puts (2+2).to_s ----- Y ahora ejecutamos nuestro programa: ----- $ ruby fixnum_mod.rb 100 Horror, hemos echado a perder el método sumar de Fixnum, por ello algunos consideran peligroso los lenguajes dinámicos, sin embargo existe la forma de protegernos de este tipo de modificaciones en el caso de que ello no sea deseable. El ejemplo sin embargo demuestra que toda clase puede redefinir cualquiera de sus métodos en tiempo de ejecución, en cualquier momento, este dinamismo le da gran poder a Ruby, piense en una clase u objeto que evoluciona y gana funcionalidad en el tiempo de existencia del programa, o que la pierde, su funcionalidad puede mutar, cambiar. No puede devolver el cambio, no sin que le enseñe cómo preservar el código sobrescrito, probablemente en la próxima edición de esta columna. ---- Estructuras de control ---- Por supuesto que ningún lenguaje está completo si no tiene la capacidad de ejecución de código condicionada, es decir, evaluar alguna condición o estado, y proceder en consecuencia de distintas maneras. Abajo le resumimos las estructuras más comunes. 1 # Evaluacion máxima 20 2 if evaluacion < 10 3 puts "Usted reprobó la asignatura." 4 elsif evaluacion > 16 5 puts "Usted obtuvo un grado sobresaliente." 6 else 7 puts "Usted aprobó la materia." 8 end 1 unless unaCancion.duracion > 180 then 2 costo = .25 3 else 4 costo = .35 5 end 1 case forma 2 when Cuadrado, Rectangulo 3 # ... 4 when Circulo 5 # ... 6 when Triangulo 7 # ... 8 else 9 # ... 10 end ---- Lazos e iteradores ---- Un iterador en Ruby es simplemente un método que puede invocar un bloque de código. Note como se pasa la referencia del bloque de código y este a su vez ejecutado por medio de la llamada yield. Ruby Salida 1 def tres_veces Hola mundo 2 yield Hola mundo 3 yield Hola mundo 4 yield 5 end 6 7 tres_veces { puts "Hola Mundo" } Algunos iteradores son muy comunes en muchas clases Ruby para representar colecciones, por ejemplo each en un arreglo simple. Note que each además de iterar por cada uno de los elementos del arreglo, pasa un argumento al bloque de código ha ser ejecutado, en este caso pasa el contenido correspondiente en el arreglo. Ruby Salida i| puts i } 1 3 5 7 9 Lazos con while y until. Ruby Salida 1 peso = 5 10 2 while peso < 100 20 3 peso = peso * 2 40 4 puts peso 80 5 end 160 Ruby Salida 1 peso = 5 10 2 until peso > 100 20 3 peso = peso * 2 40 4 puts peso 80 5 end 160 ---- Lazo con for y loop: ---- Ruby Salida 1 for i in 1..8 do 1 2 puts i 2 3 end 3 4 5 6 7 8 Ruby Salida 1 num = 0 En el lazo por 0 vez 2 loop do En el lazo por 2 vez 3 puts "En el lazo por #{num} vez" En el lazo por 2 vez 4 num += 1 En el lazo por 3 vez 5 break unless num < 5 En el lazo por 4 vez 6 end De salida, por supuesto hay mucho más acerca de Ruby y su mundo, usted podrá hacer desde pequeños guiones (scripts) hasta poderosas aplicaciones de escritorio o su último desarrollo web, no se detenga aquí y espero que nos leamos en la próxima entrega de esta publicación, envíeme sus comentarios a <gomix(a)fedoraproject.org>. Nuestro trabajo es resolver problemas concretos, no alimentar al compilador con cucharilla, nos gustan los lenguajes dinámicos que se adapten a nosotros sin reglas rígidas que seguir. Gomix_ - end FWN 265 - --- Pascal Calarco, Fedora Ambassador, Indiana, USA

13 years, 2 months

Fedora Weekly News 265

by Pascal Calarco

* 1 Fedora Weekly News Issue 265 o 1.1 Announcements + 1.1.1 Fedora Announcement News # 1.1.1.1 Infrastructure Outage Notification: 2011-03-02 1200 UTC -> 1500 UTC # 1.1.1.2 Updated: Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC * 1.1.1.2.1 Reason for outage * 1.1.1.2.2 Contact Information + 1.1.2 Fedora Events # 1.1.2.1 Upcoming Events (Dec 2010 - Feb 2011) # 1.1.2.2 Past Events # 1.1.2.3 Additional information o 1.2 Fedora In the News + 1.2.1 Who Contributes the Most to LibreOffice? (Linux Journal) + 1.2.2 Fedora 15 alpha delayed - Btrfs may be default in 16 (H Online) + 1.2.3 Beyond FUDCon with Robyn Bergeron, Fedora Program Manager (Linux Magazine) o 1.3 Ambassadors + 1.3.1 Welcome New Ambassadors + 1.3.2 Summary of traffic on Ambassadors mailing list + 1.3.3 Summary of events reported on Ambassadors mailing list + 1.3.4 Summary of traffic on FAmSCo mailing list o 1.4 QualityAssurance + 1.4.1 Test Days + 1.4.2 Fedora 15 Alpha preparation + 1.4.3 Bodhi improvements + 1.4.4 FreeIPA Test Day problems and proposals + 1.4.5 Complications for Delta ISO users + 1.4.6 IPv6 testing + 1.4.7 Using abrt during Test Days o 1.5 Security Advisories + 1.5.1 Fedora 14 Security Advisories + 1.5.2 Fedora 13 Security Advisories o 1.6 LATAM Fedora! + 1.6.1 Ruby Capítulo 1: El primer contacto # 1.6.1.1 Aprovechando el espacio # 1.6.1.2 Los "Hola mundo" * 1.6.1.2.1 holamundo.rb * 1.6.1.2.2 holamundo.rb # 1.6.1.3 Ruby es un lenguaje de programación orientado a objetos # 1.6.1.4 Pero no necesito clases # 1.6.1.5 Clases base * 1.6.1.5.1 Cadenas de caracteres, String * 1.6.1.5.2 Arreglos, Array * 1.6.1.5.3 Arreglos indexados arbitrariamente, Hash * 1.6.1.5.4 Recapitulación rápida, los objetos y sus métodos, ¿documentación? # 1.6.1.6 Ruby es dinámico ¿ 2 + 2 = 4 ? * 1.6.1.6.1 fixnum_mod.rb * 1.6.1.6.2 Y ahora ejecutamos nuestro programa: # 1.6.1.7 Estructuras de control # 1.6.1.8 Lazos e iteradores * 1.6.1.8.1 Lazo con for y loop: - Fedora Weekly News Issue 265 - Welcome to Fedora Weekly News Issue 265[1] for the week ending March 2, 2011. What follows are some highlights from this issue. Our issue kicks off with a couple outage announcements from this past week, followed by three articles 'In the News', including an interview with Fedora Program Manager, Robyn Bergeron. In Ambassador news, summaries of traffic on the Ambassador and FAmSCo lists, and QA brings us a whole slew of Test Day details over the next few weeks, Fedora 15 prep and bodhi improvements. Security Advisories keeps us updated with security-related patches released this past week. We're also very pleased this week to kick off our foreign language content initiative, which developed out of FUDCon Tempe, with a new Latin American beat, all in Spanish. To start off, we have part one of a Ruby on Fedora primer, contributed by Guillermo Gómez, a Fedora Ambassador in Venezuela. If you would like to contribute Fedora-related content in your language, please send a note to the editors! An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us! If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news(a)lists.fedoraproject.org FWN Editorial Team: Pascal Calarco, Adam Williamson 1. http://fedoraproject.org/wiki/FWN/Issue265 2. http://www.archive.org/search.php?query=subject%3A%22FWN%22 3. http://fedoraproject.org/wiki/NewsProject/Join -- 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 1. http://lists.fedoraproject.org/pipermail/announce/ 2. http://lists.fedoraproject.org/pipermail/devel-announce/ 3. http://fedoraproject.org/wiki/Events --- Fedora Announcement News --- The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1] 1. https://admin.fedoraproject.org/mailman/listinfo/announce ---- Infrastructure Outage Notification: 2011-03-02 1200 UTC -> 1500 UTC ---- Stephen John Smoogen on Tue Mar 1 20:13:07 UTC 2011 announced[1], "Tomorrow the services at ibiblio will be moved to a new physical location * ibiblio01.fedoraproject.org * app05 * backup02 * ns02 * proxy04 * smtp-mm03 * torrent01" 1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002928.html ---- Updated: Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC ---- Stephen John Smoogen on Tue Mar 1 22:09:31 UTC 2011 announced[1], "Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC There will be an outage starting at UTC, 2011-03-02 14:00 which will last approximately 4 hours. To convert UTC to your local time, take a look at[2] or run: date -d '2011-03-02 14:00 UTC' ----- Reason for outage ----- metalabs is moving facilities and needs for our collocated server to move with them. Systems will be down and getting new IP addresses with the move. [3] ----- Contact Information ----- Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage." 1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002929.html 2. http://fedoraproject.org/wiki/Infrastructure/UTCHowto 3. https://fedorahosted.org/fedora-infrastructure/ticket/2651 --- Fedora Events --- The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and 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 (Dec 2010 - Feb 2011) ---- * North America (NA)[1] * Central & South America (LATAM): [2] * Europe, Middle East, and Africa (EMEA)[3] * India, Asia, Australia (India/APJ)[4] 1. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29 2. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2 3. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3 4. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4 ---- Past Events ---- Archive of Past Fedora Events[1] 1. http://fedoraproject.org/wiki/FedoraEvents/PastEvents ---- 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. -- Fedora In the News -- In this section, we cover news from the trade press and elsewhere that is re-posted to the Fedora Marketing list[1]. http://fedoraproject.org/wiki/Marketing Contributing Writer: Pascal Calarco 1. http://lists.fedoraproject.org/pipermail/marketing/ --- Who Contributes the Most to LibreOffice? (Linux Journal) --- Rahul Sundaram forwarded[1] an article from Linux Journal noting contributions to LibreOffice: "Bosdonnat began tracking line contributions in the middle of September 2010 with the original 14 contributions being made by Oracle. Oracle actually contributes code to OpenOffice.org, and then LibreOffice merges those changes, thus resulting in Oracle's contributions to the new fork. These 112 contributions have continued throughout development, but are dwarfed by the contributions of new developers." These contributions make up well over half of the total new changes found in LibreOffice as of mid-February. Weekly contributions in this area have averaged between 20 and 30 with a total number of 517 line contributions. Red Hat, who also contributed to OpenOffice.org, has chipped in as well. With usually two contributions per week, Red Hat developers have provided 39 patches since the fork." The full article is available[2]. 1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013722.html 2. http://www.linuxjournal.com/content/who-contributes-most-libreoffice --- Fedora 15 alpha delayed - Btrfs may be default in 16 (H Online) --- Rahul Sundaram forwarded[1] an an article in The H Online about the decision to push back Fedora 15 alpha: "The Fedora project has postponed the release of the first and only alpha version of Fedora 15, originally scheduled for 1 March, by a week. This was due, at least in part, to a bug in X Server that occurred in connection with keyboard layouts for such languages as German or French and prevented users from successfully logging into GDM. Subsequent milestones in the release schedule for Fedora 15 remain unaffected at present, and the final release is still scheduled for 10 May. The fifteenth Fedora release is currently planned to be the first version that won't require a special boot parameter to be submitted to the installer in order to format a storage device with the experimental Btrfs file system. Red Hat employee Josef Bacik, who is heavily involved in the development of Btrfs, has now proposed on the project's most important developer mailing list that Btrfs should be made the default file system in Fedora 16, which is expected in late October or early November" The full post is available[2]. 1. http://lists.fedoraproject.org/pipermail/marketing/2011-February/013713.html 2. http://www.h-online.com/open/news/item/Fedora-15-alpha-delayed-Btrfs-may-... --- Beyond FUDCon with Robyn Bergeron, Fedora Program Manager (Linux Magazine) --- Rahul Sundaram forwarded[1] another article highlighting Fedora community leaders, this with Robyn Bergeron, who remarked: "I personally would love to see more folks getting involved in areas that don't necessarily require coding skills. I think that there is enormous room for growth and contribution in these areas, and there are plenty of Linux enthusiasts out there who have the skills and imagination to make great contributions in these places." The full article is available[2] -- Ambassadors -- This section covers the news surrounding the Fedora Ambassadors Project[3]. Contributing Writer: Sankarshan Mukhopadhyay 1. http://lists.fedoraproject.org/pipermail/marketing/2011-February/013714.html 2. http://www.linux-magazine.com/Online/News/Beyond-FUDCon-with-Robyn-Berger... 3. http://fedoraproject.org/wiki/Ambassadors --- Welcome New Ambassadors --- This week the Fedora Ambassadors Project had no new members joining. --- Summary of traffic on Ambassadors mailing list --- Pierros Papadeas posted [1] about Ambassador SOPs [2] on which FAmSCo has been working. Clint Savage suggested [3] attending the FAD at SCaLE this year specifically mentioning the Sysadmin Study Group Buddhika Kurera informed [4] that the order for the FAm T-shirts [5] had been placed and expected delivery is around end of March (impacted by the orders around the ICC Cricket World Cup) Neville A. Cross asked [6] if any other Fedora Project participants would be attending PyCon from 2011-03-08 till 2011-03-13. Mark McIntyre responded [7] and provided his plans. Max Spevack suggested [8] creating an Event page and also posting to devel at lists.fedoraproject.org. The page [9] was created by Mark McIntyre Pierre-Yves Chibon posted [10] the translated annual report [11] for Fedora-Fr, the French speaking NPO. David Ramsey provided prior notice [12] about Fedora 15 Test Days [13] coming up David Ramsey posted [14] the draft Agenda [15] of the APAC meeting on 2011-03-05 Caius Chance informed [16] about having around 700 F14 LiveCDs with him at Brisbane and wanted to get them to Fedora Ambassadors in APAC soonest. The thread [17] had requests from Ambassadors who wanted the CDs. Christoph Wickert announced [18] that the Trac instance used by the Fedora Board [19] was open for ticket submissions by all FAS account holders. Christoph Wickert provided an update [20] on the Fedora 14 media for EMEA Max Spevack posted [21] an initial announcement of the Finance SIG [22] David Ramsey posted [23] about Summer Coding Ideas for 2011 [24] Larry Cafiero posted [25] Meeting Minutes from FAmNA meeting on 2011-03-01[26] 1. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017066... 2. https://fedoraproject.org/wiki/Ambassadors_SOPs 3. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017071... 4. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017073... 5. https://fedoraproject.org/wiki/User:Bckurera/APAC-shirts 6. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017077... 7. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017090... 8. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017099.html 9. https://fedoraproject.org/wiki/FedoraEvents/PyCon_2011 10. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017078... 11. https://fedoraproject.org/wiki/Fedora-Fr_annual_report_2010 12. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017079... 13. https://fedoraproject.org/wiki/Category:Fedora_15_Test_Days 14. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017081... 15. https://fedoraproject.org/wiki/Meeting:APAC_Ambassadors_2011-03-05#Agenda 16. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017083... 17. http://lists.fedoraproject.org/pipermail/famsco/2011-February/thread.html... 18. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017094... 19. https://fedorahosted.org/board/newticket 20. http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017095... 21. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017098.html 22. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010523... 23. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017102.html 24. https://fedoraproject.org/wiki/Summer_coding_ideas_for_2011 25. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017105.html 26. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora-meeting... --- Summary of events reported on Ambassadors mailing list --- No event reports were posted to the Ambassadors mailing list. --- Summary of traffic on FAmSCo mailing list --- Caius Chance informed [1] about having around 700 F14 LiveCDs with him at Brisbane and wanted to get them to Fedora Ambassadors in APAC soonest. Max Spevack posted [2] an initial announcement of the Finance SIG [3] 1. http://lists.fedoraproject.org/pipermail/famsco/2011-February/000687.html 2. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000688.html 3. http://lists.fedoraproject.org/pipermail/advisory-board/2011-March/010523... -- Quality Assurance -- In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2]. Contributing Writer: Adam Williamson 1. http://fedoraproject.org/wiki/QA 2. http://fedoraproject.org/wiki/QA/Join --- Test Days --- Thursday 2011-02-17 was Xfce 4.8[1] Test Day[2]. The event was well organized by the Xfce team, and a dedicated group of testers was able to expose some important bugs to be fixed. The week of 2011-02-21 saw the traditional Graphics Test Week. Adam Williamson posted a full recap of the event to the mailing list[3]. He noted that participation was up again compared to the Fedora 14 events and that some important testing had been carried out, but also noted a worrying trend in status of bugs from previous events, with many bugs reported during the Fedora 13 and 14 events remaining unfixed. He promised to investigate the causes of this. This week (and next Tuesday!) is internationalization and localization Test Week, and Adam Williamson put up a blog post[4] explaining the three Test Days this includes: the Anaconda i18n and l10n Test Day on 2011-03-01[5], the desktop i18n Test Day on 2011-03-03[6] and the desktop l10n Test Day on 2011-03-08[7]. All these events are very important to ensure that non-US-English-speaking users of Fedora get a great experience with Fedora 15. Thursday 2011-03-10 will be the second of three planned GNOME 3 Test Days[8], where we'll continue to work with the GNOME team to test GNOME 3.0 and its integration with Fedora 15 as rigorously as we can before the final release of both. We'll be repeating the tests from the previous event to see how things have progressed, and also running some new tests which have been added for this event. As before, this is a very important event for both Fedora and GNOME and affects most Fedora users, so if you have a few minutes to spare, please come along and help testing. Once again, live images will be available to make it easier to test, and we'll have a new process in place for reporting crasher bugs without the trouble of trying to install debuginfo packages on a live image! 1. http://fedoraproject.org/wiki/Features/Xfce48 2. http://fedoraproject.org/wiki/Test_Day:2011-02-17_Xfce 3. http://lists.fedoraproject.org/pipermail/test-announce/2011-March/000200.... 4. http://www.happyassassin.net/2011/02/28/internationalization-and-localiza... 5. http://fedoraproject.org/wiki/Test_Day:2011-03-01_L10n_i18n_Installation 6. http://fedoraproject.org/wiki/Test_Day:2011-03-03_I18n_Desktop 7. http://fedoraproject.org/wiki/Test_Day:2011-03-08_L10n_Desktop 8. http://fedoraproject.org/wiki/Test_Day:2011-03-10_GNOME3_Beta --- Fedora 15 Alpha preparation --- The QA team has been busy over the last two weeks validating the Fedora 15 Alpha release, with TC2[1], RC1[2], and RC2[3] candidate builds being posted and tested. As always, the whole team chipped in with the all-important testing. In the end the RC1 image was not accepted and the release delayed for a week[4] due to a significant bug with many non-English keyboard layouts which was exposed during the testing. With this bug fixed, the RC2 image was accepted as gold at the go/no-go meeting of 2011-03-02[5]. --- Bodhi improvements --- At the weekly meeting of 2011-02-28[6], Luke Macken announced that package-specific test case integration into Bodhi is now live, meaning that packages which have test cases associated with them according to the package test plan SOP[7] will now have the test cases displayed in Bodhi when an update for the package is under review. Also going live in the new Bodhi release are the improvements to the automated messages Bodhi sends to Bugzilla when an update's status changes, improvements discussed in previous issues of this newsletter. 1. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 2. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 3. http://lists.fedoraproject.org/pipermail/test-announce/2011-February/0001... 4. http://lists.fedoraproject.org/pipermail/devel-announce/2011-February/000... 5. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora_15_alph... 6. http://fedoraproject.org/wiki/QA/Meetings/20110228 7. http://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation --- FreeIPA Test Day problems and proposals --- Dmitri Pal posted a comment to the FreeIPA Test Day trac ticket[1] noting that he was unhappy with the way the event had turned out. Adam Williamson, James Laska and Jóhann Guðmundsson joined in with suggestions to try and learn from this experience. Dmitri is considering re-running the event with some tweaks. 1. http://fedorahosted.org/fedora-qa/ticket/163#comment:10 --- Complications for Delta ISO users --- Andre Robatino provided some detailed information[1] on what a change to the xz compression scheme would mean for users of DeltaISOs. In a nutshell, users trying to use Fedora 14 -> Fedora 15 DeltaISOs will need to use a workaround, detailed in the post, if applying the ISO on a Fedora 14 system. Andre followed up later with a refinement of the workaround[2]. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097009.html 2. http://lists.fedoraproject.org/pipermail/test/2011-February/097284.html --- IPv6 testing --- A.J. Werkman provided a recap of some very solid testing he had performed on Fedora's out-of-the-box IPv6 capabilities[1]. He identified some significant problems and reported them as bugs, including anaconda refusing to work without an IPv4 DHCP lease, and Fedora's Bugzilla not being available in the IPv6 domain. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097153.html --- Using abrt during Test Days --- A thread[1] started by Mike Cloaked highlighted the issue of abrt being difficult or impossible to use successfully from live images (such as during Test Days), in large part due to the size of debuginfo packages. Adam Williamson pointed out[2] that the abrt team's retrace server project[3] would be a perfect solution for this, but noted that he had not yet tested using it. When he did, it seemed not yet to be ready for Fedora 15[4]. Jiri Moskovc said that the Fedora 15 support would soon be available[5]. 1. http://lists.fedoraproject.org/pipermail/test/2011-February/097271.html 2. http://lists.fedoraproject.org/pipermail/test/2011-February/097289.html 3. http://fedoraproject.org/wiki/Features/RetraceServer 4. http://lists.fedoraproject.org/pipermail/test/2011-February/097299.html 5. http://lists.fedoraproject.org/pipermail/test/2011-February/097314.html -- Security Advisories -- In this section, we cover Security Advisories from fedora-package-announce from the past week. http://lists.fedoraproject.org/pipermail/package-announce Contributing Writer: Pascal Calarco --- Fedora 14 Security Advisories --- none --- Fedora 13 Security Advisories --- * ruby-1.8.6.420-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * abcm2ps-5.9.21-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * telepathy-glib-0.11.16-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... * telepathy-gabble-0.10.5-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0544... -- LATAM Fedora! -- LATAM Fedora is a regular column of Spanish language contributions around open source software. It is our first expansion into incorporating foreign language content into FWN. This week's contribution is from Guillermo Gómez, a primer on Ruby. Enjoy! --- Ruby Capítulo 1: El primer contacto --- "Yo quería un lenguaje de programación más poderoso que Perl y más orientado a objetos que Python. Entonces me acordé de mi viejo sueño y decidí diseñar mi propio lenguaje. Al principio estuve jugando con él en el trabajo. Gradualmente creció lo suficiente como para remplazar a Perl. Lo llamé Ruby en honor a esa piedra preciosa roja y lo liberé al público en 1995." Yukihiro Matsumoto, a.k.a. ``Matz Japan, October 2000 ---- Aprovechando el espacio ---- Para comenzar en Fedora con Ruby vamos instalar lo mínimo necesario y sin perder mucho espacio dando vueltas con teoría y opiniones, directo al grano. Abra una sesión de emulación de terminal preferida y siga las siguientes instrucciones para instalar. En la medida que desarrollemos esta columna dedicada a Ruby, entonces iremos descubriendo el poder y flexibilidad de Ruby. $ su - <contraseña de root> # yum install ruby ruby-rdoc ruby-ri Para el editor, hay muchas opciones, mi editor de preferencia es Vim , pero puede usar el de su preferencia, intente usar alguno que pueda resaltar sintaxis Ruby como mínimo. Puede escoger desde entornos tan complejos y completos como Eclipse, hasta editores de escritorio GUI como Gedit, o simples en consola como nano o complejos y sofisticados como Vim y Emacs. ---- Los "Hola mundo" ---- La primera forma interactiva simple de ejecutar comandos Ruby es simplemente usar el intérprete, simplemente ejecute el intérprete, ingrese los comandos y termine presionando Ctrl-D para indicarle al intérprete que la entrada de comandos ha finalizado: $ ruby puts "Hola Mundo" <Ctrl-D> Hola Mundo La segunda forma interactiva es con irb. irb es el acrónimo para Interactive Ruby. irb es un shell Ruby, es decir, es un espacio donde puede evaluar su código al instante. En próximas ediciones iremos desarrollando más el tema de irb, por ahora simplemente invoque a irb e intente: $ irb irb(main):001:0> puts "Hola Mundo" Hola Mundo => nil irb(main):002:0>exit $ Si lo que quiere es crear un programa Ruby que nos imprima "Hola Mundo" en la salida del monitor, lance su editor e incluya el siguiente código fuente en un archivo denominado holamundo.rb., guarde y salga de su editor. ----- holamundo.rb ----- 1 puts "Hola Mundo" Para ejecutar simplemente pásale al intérprete Ruby el archivo como argumento. [gomix@fricky capitulo_1]$ ruby holamundo.rb Hola Mundo También puede usar el método "shebang" y convertir el archivo fuente Ruby en ejecutable del sistema, edite su holamundo.rb para que luzca como se muestra en el listado a continuación. ----- holamundo.rb ----- 1 #!/usr/bin/ruby 2 3 puts "Hola Mundo" [gomix@fricky capitulo_1]$ chmod +x holamundo.rb [gomix@fricky capitulo_1]$ ./holamundo.rb Hola Mundo Existe la forma de pasarle directamente código Ruby al intérprete sin apoyo de archivos o programas adicionales y sin entrar en modo interactivo. $ ruby -e 'puts "Hola Mundo"' Hola Mundo ---- Ruby es un lenguaje de programación orientado a objetos ---- Todo lo que usted manipula en Ruby es un objeto, y los resultados de dichas manipulaciones a su vez, también son objetos. Cuando usted escribe código orientado a objetos normalmente está modelando conceptos del mundo real en su código. Típicamente durante este proceso de modelado usted descubrirá categorías de cosas que necesitan ser representadas en código. En un reproductor de música el concepto de "canción" puede ser una de esas categorías. En Ruby usted define una clase para representar cada una de esas entidades. Una clase es una combinación de estado, por ejemplo el nombre de la canción, y métodos que usan dicho estado, por ejemplo para reproducir la canción. Una vez que tiene dichas clases usted creará instancias de dicha clase. Para el reproductor de música que contiene la clase Cancion usted terminará teniendo instancias separadas independientes para canciones populares como "Todo o nada", "Canción para un amigo", "Amanecer llanero", y por el estilo. La palabra objeto e instancia son intercambiables. En Ruby para crear dichas instancias u objetos, se debe llamar a un método constructor de la clase, el método constructor estandar se llama new. 1 cancion1 = Cancion.new("Amanecer llanero") 2 cancion2 = Cancion.new("Todo o nada") Estas instancias son derivadas de la misma clase pero tienen características únicas. Primero, cada objeto tiene un object_id único. Segundo, usted puede definir variables de instancia, variables con valor que son únicos para cada instancia. Estas variables de instancia mantienen el estado del objeto. Igualmente puede definir métodos de instancia para acceder y/o alterar el estado del objeto, es decir, acceder y/o alterar las variables de instancia. Rápidamente definamos nuestra clase Cancion. Ruby se puede leer fácilmente. 1 class Cancion 2 def titulo 3 @titulo 4 end 5 6 def titulo=(titulo_de_la_cancion) 7 @titulo = titulo_de_la_cancion.to_s 8 end 9 end Claramente podemos ver y leer que hemos definido la clase de nombre Cancion con dos métodos de instancia, titulo y titulo=. La variable de instancia se representa en @titulo , con la notación de nombre de variable en minúscula precedida del símbolo @ . Note la indentación que hemos implementado para representar la estructura, dos espacios es cómun entre los Rubyeros (me gusta llamarlos así). Es evidente que la plabra clave class establece el inicio de un bloque que se cierra con end para definir una clase con nombre, en este ejemplo Cancion. Dentro de dicha estructura también podemos identificar claramente la palabra clave def que igualmente define bloques que se cierran también con la palabra clave end. def define dos métodos de instancia en este ejemplo. Hablaremos más de def de forma recurrente en muchas ediciones de esta columna. Podemos probar nuestra clase en irb fácilmente, por ahora tipee con cuidado para no equivocarse, luego le ofreceré más técnicas irb. 1 $ irb 2 >> class Cancion 3 >> def titulo 4 >> @titulo 5 >> end 6 >> def titulo=(titulo_de_la_cancion) 7 >> @titulo = titulo_de_la_cancion.to_s 8 >> end 9 >> end 10 => nil 11 >> cancion1 = Cancion.new 12 => #<Cancion:0xb76e25c8> 13 >> cancion1.titulo="Alma llanera" 14 => "Alma llanera" 15 >> cancion1.titulo 16 => "Alma llanera" ---- Pero no necesito clases ---- También se puede usar Ruby del modo procedimental, funcional, sin necesidad de crear (explícitamente) clases y objetos. 1 $ irb 2 >> 2 + 2 3 => 4 Pero igual note que estamos trabajando con objetos de alguna clase, en nuestro ejemplo Fixnum. 1 >> 2.class 2 => Fixnum Puede definir métodos y llamarlos: 1 >> def saludo 2 >> puts "Hola Mundo" 3 >> end 4 => nil 5 >> saludo 6 Hola Mundo 7 => nil ---- Clases base ---- Ya que "todo" son objetos de alguna clase, más vale que comencemos por aprender las más fundamentales del lenguaje, Fixnum, Bignum, Float, String, Array y Hash. Números... Fixnum, Bignum, Float Enteros, dejemos que nuestro código Ruby hable. 1 >> num = 8 2 => 8 3 >> 7.times do 4 ?> print num.class, " ", num, "\n" 5 >> num *= num 6 >> end 7 Fixnum 8 8 Fixnum 64 9 Fixnum 4096 10 Fixnum 16777216 11 Bignum 281474976710656 12 Bignum 79228162514264337593543950336 13 Bignum 6277101735386680763835789423207666416102355444464034512896 14 => 7 15 >> num = 3.14 16 => 3.14 17 >> 8.times do 18 ?> print num.class, " ", num, "\n" 19 >> num *= num 20 >> end 21 Float 3.14 22 Float 9.8596 23 Float 97.21171216 24 Float 9450.11698107869 25 Float 89304710.9560719 26 Float 7.97533139894754e+15 27 Float 6.36059109230385e+31 28 Float 4.04571190434951e+63 ---- Cadenas de caracteres, String ---- 1 >> "Hola Mundo".class 2 => String 3 >> "987".class 4 => String < ---- Arreglos, Array ---- 1 >> arreglo = ["a",1,"b",2] 2 => ["a", 1, "b", 2] 3 >> arreglo.class 4 => Array 5 >> arreglo[0] 6 => "a" 7 >> arreglo[1] 8 => 1 < ---- Arreglos indexados arbitrariamente, Hash ---- 1 >> hash = { "color" => "rojo", "temperatura" => 75, 1 => "hoy"} 2 => {1=>"hoy", "temperatura"=>75, "color"=>"rojo"} 3 >> hash.class 4 => Hash 5 >> hash["color"] 6 => "rojo" 7 >> hash["temperatura"] 8 => 75 9 >> hash[1] 10 => "hoy" ---- Recapitulación rápida, los objetos y sus métodos, ¿documentación? ---- Teniendo cualquier objeto de cualquier clase a la mano, para acceder a su métodos podemos usar la sintaxis objeto.método. En el ejemplo abajo llamamos al popular método to_s que nos ofrece una representación en String del objeto en cuestión. 1 >> hash.to_s 2 => "1hoytemperatura75colorrojo" 3 >> arreglo.to_s 4 => "a1b2" 5 >> 8.to_s 6 => "8" Ahora bien, ¿dónde consigo la documentación de dichas clases y métodos? Demos la bienvenida a ri para ayuda local en línea de comandos, y por supuesto, en la web a http://www.ruby-doc.org/ . Francamente, en nuestros días la primera fuente de información es la Web, y en segundo lugar, nuestros recursos locales como ri. Entonces, y para efectos de esta serie de artículos, vamos a usar inicialmente Ruby 1.8.7. * http://www.ruby-doc.org/core-1.8.7/ * http://www.ruby-doc.org/stdlib-1.8.7/ Ejemplo de salida ri (extracto). $ ri Fixnum ------------------------------------------------ Class: Fixnum < Integer A +Fixnum+ holds +Integer+ values that can be represented in a native machine word (minus 1 bit). If any operation on a +Fixnum+ exceeds this range, the value is automatically converted to a +Bignum+. ... Instance methods: ----------------- %, &, *, **, +, -, -@, /, <, <<, <=, <=>, ==, >, >=, >>, [], ^, __serialize__, abs, dclone, div, divmod, html_safe?, id2name, modulo, power!, quo, rdiv, rpower, size, to_f, to_s, to_sym, xchr, zero?, |, ~ ---- Ruby es dinámico ¿ 2 + 2 = 4 ? ---- Uno de los aspectos notables de Ruby es su dinamismo, una forma de visualizarlo es hacer uso del hecho que todas las clases están "abiertas" y es posible redefinir sus métodos, por ejemplo: ----- fixnum_mod.rb ----- #!/usr/bin/ruby # class Fixnum def +(otro) 100 end end puts (2+2).to_s ----- Y ahora ejecutamos nuestro programa: ----- $ ruby fixnum_mod.rb 100 Horror, hemos echado a perder el método sumar de Fixnum, por ello algunos consideran peligroso los lenguajes dinámicos, sin embargo existe la forma de protegernos de este tipo de modificaciones en el caso de que ello no sea deseable. El ejemplo sin embargo demuestra que toda clase puede redefinir cualquiera de sus métodos en tiempo de ejecución, en cualquier momento, este dinamismo le da gran poder a Ruby, piense en una clase u objeto que evoluciona y gana funcionalidad en el tiempo de existencia del programa, o que la pierde, su funcionalidad puede mutar, cambiar. No puede devolver el cambio, no sin que le enseñe cómo preservar el código sobrescrito, probablemente en la próxima edición de esta columna. ---- Estructuras de control ---- Por supuesto que ningún lenguaje está completo si no tiene la capacidad de ejecución de código condicionada, es decir, evaluar alguna condición o estado, y proceder en consecuencia de distintas maneras. Abajo le resumimos las estructuras más comunes. 1 # Evaluacion máxima 20 2 if evaluacion < 10 3 puts "Usted reprobó la asignatura." 4 elsif evaluacion > 16 5 puts "Usted obtuvo un grado sobresaliente." 6 else 7 puts "Usted aprobó la materia." 8 end 1 unless unaCancion.duracion > 180 then 2 costo = .25 3 else 4 costo = .35 5 end 1 case forma 2 when Cuadrado, Rectangulo 3 # ... 4 when Circulo 5 # ... 6 when Triangulo 7 # ... 8 else 9 # ... 10 end ---- Lazos e iteradores ---- Un iterador en Ruby es simplemente un método que puede invocar un bloque de código. Note como se pasa la referencia del bloque de código y este a su vez ejecutado por medio de la llamada yield. Ruby Salida 1 def tres_veces Hola mundo 2 yield Hola mundo 3 yield Hola mundo 4 yield 5 end 6 7 tres_veces { puts "Hola Mundo" } Algunos iteradores son muy comunes en muchas clases Ruby para representar colecciones, por ejemplo each en un arreglo simple. Note que each además de iterar por cada uno de los elementos del arreglo, pasa un argumento al bloque de código ha ser ejecutado, en este caso pasa el contenido correspondiente en el arreglo. Ruby Salida i| puts i } 1 3 5 7 9 Lazos con while y until. Ruby Salida 1 peso = 5 10 2 while peso < 100 20 3 peso = peso * 2 40 4 puts peso 80 5 end 160 Ruby Salida 1 peso = 5 10 2 until peso > 100 20 3 peso = peso * 2 40 4 puts peso 80 5 end 160 ---- Lazo con for y loop: ---- Ruby Salida 1 for i in 1..8 do 1 2 puts i 2 3 end 3 4 5 6 7 8 Ruby Salida 1 num = 0 En el lazo por 0 vez 2 loop do En el lazo por 2 vez 3 puts "En el lazo por #{num} vez" En el lazo por 2 vez 4 num += 1 En el lazo por 3 vez 5 break unless num < 5 En el lazo por 4 vez 6 end De salida, por supuesto hay mucho más acerca de Ruby y su mundo, usted podrá hacer desde pequeños guiones (scripts) hasta poderosas aplicaciones de escritorio o su último desarrollo web, no se detenga aquí y espero que nos leamos en la próxima entrega de esta publicación, envíeme sus comentarios a <gomix(a)fedoraproject.org>. Nuestro trabajo es resolver problemas concretos, no alimentar al compilador con cucharilla, nos gustan los lenguajes dinámicos que se adapten a nosotros sin reglas rígidas que seguir. Gomix_ - end FWN 265 - --- Pascal Calarco, Fedora Ambassador, Indiana, USA

13 years, 2 months

Fedora EPEL 8 Update: koji-osbuild-11-1.el8

by updates＠fedoraproject.org

-------------------------------------------------------------------------------- Fedora EPEL Update Notification FEDORA-EPEL-2023-a89d8f6a76 2023-02-09 00:55:30.902084 -------------------------------------------------------------------------------- Name : koji-osbuild Product : Fedora EPEL 8 Version : 11 Release : 1.el8 URL : https://github.com/osbuild/koji-osbuild Summary : Koji integration for osbuild composer Description : Koji integration for osbuild composer. -------------------------------------------------------------------------------- Update Information: This project provides osbuild integration with Koji. It makes it possible to build images and other OS artifacts via osbuild-composer through koji, -------------------------------------------------------------------------------- ChangeLog: * Mon Nov 21 2022 Packit <hello(a)packit.dev> - 11-1 Changes with 11 ---------------- * Print more log messages to enable tracking of SLIs (#110) * Various fixes (#108) Contributions from: Simon Steinbeiss, Thomas Lavocat, Tom�� Hozza �� Somewhere on the Internet, 2022-11-21 * Fri Sep 2 2022 Packit <hello(a)packit.dev> - 10-1 Changes with 10 ---------------- * Hub: support `image_type` being an array for backwards compatibility (#107) * packit: Enable Bodhi updates workflow (#106) Contributions from: Tomas Hozza �� Somewhere on the Internet, 2022-09-02 * Wed Aug 31 2022 Packit <hello(a)packit.dev> - 9-1 Changes with 9 ---------------- * Support specifying upload options for image builds (#104) * Various enhancements (#105) * builder: add retries to composer API calls (#103) Contributions from: Ond��ej Budai, Tomas Hozza �� Somewhere on the Internet, 2022-08-31 * Thu Jul 21 2022 Fedora Release Engineering <releng(a)fedoraproject.org> - 8-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Thu Jun 30 2022 Packit <hello(a)packit.dev> - 8-1 Changes with 8 ---------------- * builder: always refresh OAuth token after getting 401 (#102) Contributions from: Ond��ej Budai �� Somewhere on the Internet, 2022-06-30 * Wed Jun 29 2022 Packit <hello(a)packit.dev> - 7-1 Changes with 7 ---------------- * builder: set OAuth token creation time before we fetch it (#101) * packit: Enable Koji build integration (#99) * spec: set the default release to 1 (#98) Contributions from: Jakub Rusz, Ond��ej Budai, Simon Steinbeiss �� Somewhere on the Internet, 2022-06-29 * Mon Jun 13 2022 Python Maint <python-maint(a)redhat.com> - 6-1 - Rebuilt for Python 3.11 * Tue May 3 2022 Packit <hello(a)packit.dev> - 6-0 Changes with 6 ---------------- * builder: add support for proxying requests to composer (#96) * devcontainer: remove trailing comma from JSON (#95) * plugins: add support for customizations (#97) * workflows/trigger-gitlab: run Gitlab CI in new image-builder project (#94) Contributions from: Christian Kellner, Jakub Rusz, Ond��ej Budai �� Somewhere on the Internet, 2022-05-03 * Mon Mar 28 2022 Packit Service <user-cont-team+packit-service(a)redhat.com> - 5-0 CHANGES WITH 5: ---------------- * builder: rename gpg_key field to gpgkey for repos (#91) * builder: fix type annotations (#92) * Add GitHub Action to create upstream tag (#90) * docs: fix error in hacking.md (#85) * build(deps): bump actions/checkout from 2 to 3 (#86) * spec: don't push tests into Fedora (#89) * test/builder: drop misleading quotes from config (#88) * builder: use correct secret when fetching token (#87) * packit: Push directly to dist-git (#84) Contributions from: Christian Kellner, Ond��ej Budai, Simon Steinbeiss, Stephen Coady, dependabot[bot] �� Somewhere on the Internet, 2022-03-28 * Tue Feb 15 2022 Packit Service <user-cont-team+packit-service(a)redhat.com> - 4-0 CHANGES WITH 4: ---------------- * plugins: support for repo package sets (#82) * Lower task weight (#60) * Add upstream release bot and enable packit (#81) * plugins: support for ostree specific options (#80) * builder: use cloud api (#73) * README: contributing (#74) * README.md,HACKING.md: update for SSO/OAuth2 (#79) * Support for oauth2 authentication (#69) * ci: switch from rhel 8.4 to 8.5 (#78) * ci: integration tests now adapt to the host (#77) * schutzbot: update osbuild to 46 (#75) * cli: do not use translation helper (#72) * `builder`: fixes for the command line argument parsing (#71) * Fix command line argument names (#70) * devcontainer: add initial support (#68) * schutzbot: remove ssh keys of team member that left us (#67) * CI: Fix failure in Coverity Scan (#66) * ci: Enable Coverity Scan (#65) * Adjust variable names (#64) * build(deps): bump ludeeus/action-shellcheck from 0.5.0 to 1.1.0 (#63) * test: use importlib instead of imp (#62) * Enable Dependabot (#61) * plugin/cli: remove type annotation (#59) * Migrate to GitLab CI (#58) * Test and CI maintenance (#57) * Fetch and attach the manifests (#56) * Test housekeeping (#55) * assorted CI fixes/improvements (#54) * Add Fedora 33 to Schutzbot & fix the name of repo (#52) * test/integration.sh: bump nightly (#53) * test: replace docker.io with fedora's registry (#50) * mockbuild: make more consistent with other osbuild projects (#49) * Update osbuild-composer dependency to 25 (#48) Contributions from: Alexander Todorov, Chloe Kaubisch, Christian Kellner, Lars Karlitski, Ond��ej Budai, Simon Steinbeiss, Tomas Kopecek �� V��cklabruck, 2022-02-15 * Thu Jan 20 2022 Fedora Release Engineering <releng(a)fedoraproject.org> - 2-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Thu Jul 22 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Fri Jun 4 2021 Python Maint <python-maint(a)redhat.com> - 2-2 - Rebuilt for Python 3.10 * Tue Jan 26 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2-1 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Tue Nov 3 2020 Christian Kellner <ckellner(a)redhat.com> - 2-0 - Upstream release 2 - Add python3-jsonschema dependency for builder sub-package. * Wed Sep 30 2020 Christian Kellner <ckellner(a)redhat.com> - 1-0 - Initial import. -------------------------------------------------------------------------------- This update can be installed with the "yum" update programs. Use su -c 'yum update koji-osbuild' at the command line. For more information, refer to "YUM", available at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7\ /html/System_Administrators_Guide/ch-yum.html All packages are signed with the Fedora EPEL GPG key. More details on the GPG keys used by the Fedora Project can be found at https://fedoraproject.org/keys --------------------------------------------------------------------------------

1 year, 2 months

Re: Proposal: end Gilligan's Island copyright notices in Fedora docs

by Eric Christensen

On Fri, Jun 24, 2011 at 12:46, David Nalley <david.nalley(a)fedoraproject.org> wrote: >>> >>> That is only a valid objection if the suggestion was (c) Fedora Project >>> but (c) Fedora Project contributors says something different. It means >>> *individual* Fedora project contributors hold the copyright to their >>> contributions which is certainly possible and is the case here. >> >> Correct. But if we do that then we should just list *who* holds the copyrights. > > > I personally think that's unmaintainable. And here's why: > First, with some of our guides that have seen organic growth over > releases there are scores of people with copyright claims. Who is > going to ensure that it's right, up to date, and who is going to want > to page through it? Secondly, we have translators who don't get > attribution until the next release for their work. IRT translators and their work: This is another reason why translators should own their work instead of handing it back to us for publication. The translators do put their copyright information on their PO files so it's there in the source but their name should appear with the copyright notice on the *translated* document. Since they didn't contribute to the English version, unless they contribute outside of their translation duties, then they don't hold any copyright to that version. > > Do we really want this kind of copyright notice: > > (c) Copyright 200x-2011 Fabian Affolter, Amanpreet Singh Alam, ... > Zacarão, Izaac Zavaleta, Red Hat Inc, and others. That might be a bit extreme... :) > > That's the list of contributors on the F15 Install Guide. The above > list (since it doesn't have all of the translators) isn't complete, > and it has some errant contributions (assuming that RHT employees who > contribute work don't retain copyright, and then we have people like > Paul Frields who have contributed as employee and non-employee). Add > to that that we have a good chunk of information on the wiki and no > good way to list who the contributors there are. When we take information from the wiki and move it into a guide we are really not attributing the work back to the original author which is in violation of the CC-BY-SA license. > So I am going to say something that is likely to be unpopular. I think > we should go with (c) Copyright 2011 Fedora Project Contributors as > that would cover both RHT contributions and individual contributors, > or perhaps as Richard suggested, no explicit copyright notice. It's > less effort to maintain, it scales to other places like the wiki, and > our websites. Yes, it scales well but doesn't provide information to someone that may want to use our information and needs to know who to attribute it to. > That said, I am currently doing precious little of the > work in Docs, so my opinion may hold little weight. You have licensed your works, that we still use, to us (Fedora) so your opinion holds as much weight as the rest of us that have contributed. > I am also somewhat worried that we really aren't talking about > copyright notices, and if that's the case we should discuss the real > issue. To me this is a multi-faceted discussion of both copyright, licensing, and the associated attribution. Now if there are other issues afoot then we should be made aware of that sooner than later. --Eric

12 years, 10 months

Re: [SSSD] [WIKI] Contribute and DevelTips are duplicate

by Petr Cech

On 09/02/2015 05:47 PM, Jakub Hrozek wrote: > On Wed, Sep 02, 2015 at 05:18:24PM +0200, Michal Židek wrote: >> On 08/17/2015 02:21 PM, Petr Cech wrote: >>> On 07/17/2015 01:26 PM, Petr Cech wrote: >>>> Hi, >>>> >>>> I have read the wiki pages. And I have the edited version. It would be >>>> difficult to send the diff, so I started a new pages where you can >>>> view the result. >>>> >>>> Original pages: >>>> [ 1] https://fedorahosted.org/sssd/wiki/Contribute >>>> [ 2] https://fedorahosted.org/sssd/wiki/DevelTips >>>> [ 3] https://fedorahosted.org/sssd/wiki/DevelTutorials >>>> [ 4] https://fedorahosted.org/sssd/wiki/Reporting_sssd_bugs >>>> [ 5] https://fedorahosted.org/sssd/wiki/BugLifecycle >>>> [ 6] https://fedorahosted.org/sssd/wiki/Repositories >>>> >>>> Content of [3] has been divided between [1] and [3], content of [5] >>>> has been divided between [1] and [4]. Then [3,5,6] will be deleted. >>>> >>>> Test of new pages: >>>> [ 7] https://fedorahosted.org/sssd/wiki/pcech_test_contribute >>>> [ 8] https://fedorahosted.org/sssd/wiki/pcech_test_devel_tips >>>> [ 9] https://fedorahosted.org/sssd/wiki/pcech_test_reporting_sssd_bugs >>>> >>>> Note that the links lead to the original pages. >>>> At [7] you can find "COPR Repository" section, but I am not sure with >>>> text here. Please look at it. >>>> I did not pass the whole wiki. I think there might be a link from [8] >>>> (perhaps [9]) on Troubleshooting. >>>> >>>> I look forward to your comments, I need the opinions of another persons. >>>> >>>> Petr >>> >>> Hi, >>> >>> a did some little edits according to talk with Jakub: >>> * deleting Code Submission Process in Contribute >>> * simplifying the structure of the headings in Contribute >>> * adding link to tevent documentation in Devel tips >>> * merging SSSD bug report >>> and we would like to move link to COPR repo to the homepage (and add >>> note about Ubuntu package, is it right?) >>> >>> So new version (without homepage and link to Ubuntu repo) is on the same >>> place: >>> [ 7] https://fedorahosted.org/sssd/wiki/pcech_test_contribute >>> [ 8] https://fedorahosted.org/sssd/wiki/pcech_test_devel_tips >>> [ 9] https://fedorahosted.org/sssd/wiki/pcech_test_reporting_sssd_bugs >>> >>> Petr >> >> Hi! >> >> I think that Petr's changes to Wiki are improvement over the >> current state. He removes a lot of duplicated and outdated >> info. So if nobody objects I would like Petr to go ahead >> and replace the current pages with the new ones. > > Thank you very much for review, they looked good to me as well when we > discussed the changes in person last time. > > Petr, please move the pages and then send a mail to the list about the > update, we can always change more stuff or even roll back. I just updated the wiki pages. I will send another mail for it. But in this thread, I would like to note, what is exactly done. Original pages: [ 1] https://fedorahosted.org/sssd/wiki/Contribute [ 2] https://fedorahosted.org/sssd/wiki/DevelTips [ 3] https://fedorahosted.org/sssd/wiki/DevelTutorials [ 4] https://fedorahosted.org/sssd/wiki/Reporting_sssd_bugs [ 5] https://fedorahosted.org/sssd/wiki/BugLifecycle [ 6] https://fedorahosted.org/sssd/wiki/Repositories Content of [3] has been divided between [1] and [3], content of [5] has been divided between [1] and [4]. Then [3,5,6] will be deleted. Test of new pages: [ 7] https://fedorahosted.org/sssd/wiki/pcech_test_contribute [ 8] https://fedorahosted.org/sssd/wiki/pcech_test_devel_tips [ 9] https://fedorahosted.org/sssd/wiki/pcech_test_reporting_sssd_bugs UPDATE: [ 7] --> [ 1] [ 8] --> [ 2] [ 9] --> [ 4] Pages [7,8,9] exist still, but we could remove it. Pages [3,5,6] exist too, but I hope, no links target them. We could remove it too. I am sorry, but after this ticket I am blind on wiki. Could somebody check, that I did update properly? Thanks. Petr > >> >> I have one comment: Does somebody know how to move the >> table of contents to the left? Currently it is in the upper >> right corner and I think (especially on bigger monitors) >> it is really not easy to spot. The table is IMO very important >> and gives good outline of what to expect from the page >> so I would really like to have it on the left nice and >> visible. > > I only found http://trac.edgewall.org/wiki/PageOutline about the macro. > >> >> Also I like the idea of revisiting the wiki pages regularly >> in order to further improve them and keep them up-to-date. >> I think the overall navigation on our wiki has room for >> improvement, but we do not need to do everything at once. > > > Hmm I guess I missed that how exactly are we going to update them > regularly? (I agree we should, I'm just interested in the mechanics) > _______________________________________________ > sssd-devel mailing list > sssd-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/sssd-devel >

8 years, 8 months

Re: [Ambassadors] During some of my review of the Fedora 12 "Constantine, " Fedora 12 Talking Points. :)

by Chitlesh GOORAH

On Wed, Dec 23, 2009 at 10:28 PM, Mel Chua wrote: > Almost - there's a subtle but important difference I think we (Marketing) > may have been unclear about when making and talking about our talking > points, and for that I apologize. Hello Mel, You don't need to apologize as a "person" since this is the responsibility of almost anyone actively contributing (community and redhat). > The F12 talking points are to briefly introduce the major work done by > Fedora contributors *for the F12 Desktop Spin release.* That means that > talking points for other Spins should go elsewhere - the question is where. If it is *for the F12 Desktop Spin release.* as you say : please _remove_ contents ---- # 2 For administrators * 2.1 libguestfs * 2.2 Virtualization improvements # 3 For developers * 3.1 SystemTap Eclipse integration and tracing improvements * 3.2 NetBeans 6.7.1 ---- from the wiki page https://fedoraproject.org/wiki/Fedora_12_Talking_Points . In accordance to you, they should be irrelevant for the desktop spin, hence perfectly natural for their instant removal. This is not the Fedora Desktop 12 spin but might be for RHEL 6, I don't know. We should stress on Fedora Project here. > Chitlesh pointed out (rightfully so!) that there wasn't a place for > release-specific items for each Spin. I didn't specify "spin specific", but stressed on "contribution-specific". > That means we should create one! I'm trying to restructure the Marketing > wiki pages to carve out space for this - in particular, see: > > https://fedoraproject.org/wiki/Marketing#Release_deliverables > > You'll notice that the page is still extremely messy, Actually, I would say focus on what matters and what is being claimed. We(fedora) claim that https://fedoraproject.org/wiki/Fedora_12_Talking_Points is the talking points about F-12. We know Fedora (unlike RHEL) doesn't have a specific targeted userbase. That above wiki page was suppose to give : * _fedora_ contributors * _fedora_ users * _non-fedora_ users a brief introduction what Fedora is providing for release N and what they can expect. Thereby, it is fully acceptable to have one small paragraph that points to the workdone during the development cycle of F-N, by any SIG. Please don't create other secondary pages for the same purpose, which are meant for spins/SIG. ^^ This would be considered by uninformed press as an example where RedHat is advertising its products first before community's contributions. We(fedora) don't want bad publicity, don't we ? People in the past has worked hard to convince public that Fedora is not a beta of RHEL. I thank RahulSundaram for taking the initiative at that time. (That said, in the past during Max Spevack's reign, the Fedora Marketing was contacting News websites that reflects Fedora as "Red Hat's Fedora" to recommend them to opt for "Fedora Project" instead. This should be continued. ) Coming back to the Talking Points wiki page, what should be focussed on are "Fedora release N specific details". Unlike any of other distributions, I think Fedora contributors are intelligent and mature (another reason why I contribute to Fedora, if not I would not spend my time for nothing) , so they should be able to summarize their main contributions for Fedora N release into two/three lines and giving a link to a detailed page. RexDieter, Sebastian & Kevin(kde spin), Sebastian(of education spin), Christopher(of LXDE spin), JoergSimon (of Security Spin) are all wise men and if time permits they would be able to summarise their contribution into 2/3 lines (perfect of a centralized wiki page for F-N talking points). (Surprisingly, a lot of european contributors concentrate on spins.) This is Fedora, an intelligent community, which strives to give an example for others to follow in terms of opensource movement. Hence it is assumed that Fedora users would be glad to hear and able to point to anyone a single location of what Fedora Project has done for them, for their children, their spouse, their friends and their colleagues. This would initiate person-to-person marketing strategy, the ground idea of the Fedora Ambassador Project. The basic definition of the existence of the wiki page : https://fedoraproject.org/wiki/Fedora_12_Talking_Points Kind regards, Chitlesh Goorah

14 years, 4 months

Re: Introductory mail

by Sumantro Mukherjee

----- Original Message ----- > From: "Aravind Elamurugan" <aravind2898(a)gmail.com> > To: test(a)lists.fedoraproject.org > Sent: Saturday, July 15, 2017 1:32:26 PM > Subject: Introductory mail > > Hello Friends, > > My name is Aravind Elamurugan. I am from Coimbatore, Tamil Nadu. And I am > studying in KGiSL Institute of Technology. I have just started with my > Fedora contribution under the guidance of Vipul Siddharth and Prakash > Mishra. And I am eager to contribute to fedora QA. I am more passionate > towards contributing fedora QA. I also did some projects in > Web-Technologies(HTML and CSS). I have also developed an App. And so I am > more passionate in knowing many programming languages and developing it. So, > under the instructions of Mr.Vipul Sidharth and Prakash Mishra, I am ready > to contribute to Fedora QA. And I am really interested in contributing to > Fedora QA. I am happy to be a part of your community. > > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-leave(a)lists.fedoraproject.org > Hey Aravind, First of all, Welcome and thanks for showing your interest in Fedora QA.Please create a FAS account and send a QA group request. You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , Fedora 25 and Fedora 26. Update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you can sort the packages with Fedora Releases and tags viz "pending" & "testing" . You can read much about update testing here [1]. You can also, use fedora-easy-karma for giving out feedbacks. We just had a release but you can still test rawhide. In between the release cycle , you can start with Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest alpha (Fedora 26 Branched 20170513), you can run test cases which are mentioned [2] and submit your results in the test matrix. Note that each of the test cases[3] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|<fas_username>}} . Always make sure to check for "Associated release criterion" which can be found on the top of test case page , if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|<fas_username>}} and file a bug at RHBZ [4] under Fedora. You can always find the ‘current’ validation pages using these addresses: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Server_Test https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test For Automation, you can start looking at Taskotron [https://fedoraproject.org/wiki/Taskotron] and Open QA[https://fedoraproject.org/wiki/OpenQA]. [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513... [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ PS we have a on-boarding call happening very soon , stay tuned to this mailing list as I will be sending an Poll very soon. Thanks //sumantrom

6 years, 9 months

churchyard pushed to aspectjweaver (master). "Orphaned for 6+ weeks"

by notifications＠fedoraproject.org

Notification time stamped 2019-09-11 09:35:10 UTC From f61564ef66104ade170fb6ac9602ae700a194bc6 Mon Sep 17 00:00:00 2001 From: Miro Hrončok <miro(a)hroncok.cz> Date: Sep 11 2019 09:35:03 +0000 Subject: Orphaned for 6+ weeks --- diff --git a/.gitignore b/.gitignore deleted file mode 100644 index b5abce1..0000000 --- a/.gitignore +++ /dev/null @@ -1,4 +0,0 @@ -/aspectjweaver1.6.12-src.jar -/aspectjweaver-1.8.4-sources.jar -/aspectjweaver-1.8.9-sources.jar -/aspectjweaver-1.8.9.pom diff --git a/aspectjweaver-build.xml b/aspectjweaver-build.xml deleted file mode 100644 index a1b79d5..0000000 --- a/aspectjweaver-build.xml +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<project name="aspectjweaver" default="jar" basedir="."> - <property name="src.dir" value="."/> - <property name="build.dir" value="./build"/> - <property name="build.classes" value="${build.dir}/classes"/> - <property name="doc.api.dir" value="javadoc"/> - <target name="compile"> - <mkdir dir="${build.dir}"/> - <mkdir dir="${build.classes}"/> - <javac srcdir="${src.dir}" destdir="${build.classes}"> - <include name="**/*.java"/> - </javac> - <copy todir="${build.classes}"> - <fileset dir="${src.dir}" includes="**/*.properties,**/*.xsl"/> - </copy> - </target> - <target name="jar" depends="compile"> - <jar jarfile="${build.dir}/aspectjweaver.jar"> - <fileset dir="${build.classes}"> - <include name="org/**"/> - </fileset> - </jar> - </target> - <target name="javadoc" description="Generated Java API documentation"> - <delete dir="${doc.api.dir}" quiet="true"></delete> - <javadoc destdir="${doc.api.dir}" windowtitle="aspectjweaver API" sourcepath="${src.dir}" linksource="no" encoding="ISO8859-1" additionalparam="-Xdoclint:none"/> - </target> - <target name="clean"> - <delete dir="${build.dir}"/> - </target> -</project> - diff --git a/aspectjweaver.spec b/aspectjweaver.spec deleted file mode 100644 index 8f2eb37..0000000 --- a/aspectjweaver.spec +++ /dev/null @@ -1,146 +0,0 @@ -Name: aspectjweaver -Version: 1.8.9 -Release: 9%{?dist} -Summary: Java byte-code weaving library -License: EPL -URL: http://eclipse.org/aspectj/ -Source0: http://repo1.maven.org/maven2/org/aspectj/%{name}/%{version}/%{name}-%{ve... -# This build.xml file was adapted from the Ubuntu package. The src jar has no build scripts. -Source1: aspectjweaver-build.xml -Source2: http://repo1.maven.org/maven2/org/aspectj/%{name}/%{version}/%{name}-%{ve... -Source3: epl-v10.txt - -BuildRequires: ant -BuildRequires: apache-commons-logging -BuildRequires: javapackages-local -BuildRequires: objectweb-asm -BuildRequires: glibc-langpack-en - -BuildArch: noarch - -%description -The AspectJ Weaver supports byte-code weaving for aspect-oriented -programming (AOP) in java. - -%package javadoc -Summary: Javadoc for %{name} - -%description javadoc -API documentation for %{summary}. - -%prep -%setup -q -c -sed -i.objectweb-asm "s|import aj.|import |" \ - org/aspectj/weaver/bcel/asm/StackMapAdder.java - -cp %{SOURCE1} build.xml - -# JRockit is not open source, so we cannot build against it -rm org/aspectj/weaver/loadtime/JRockitAgent.java - -cp %{SOURCE2} pom.xml -%pom_xpath_inject "pom:project" " - <dependencies> - <dependency> - <groupId>org.ow2.asm</groupId> - <artifactId>asm</artifactId> - <version>5.0.3</version> - </dependency> - </dependencies>" - -cp %{SOURCE3} . - -%build - -%mvn_file org.aspectj:%{name} %{name} -%mvn_alias org.aspectj:%{name} "org.aspectj:aspectjrt" "aspectj:aspectjrt" -LANG=en_US.ISO8859-1 CLASSPATH=$( build-classpath objectweb-asm/asm commons-logging ) ant -LANG=en_US.ISO8859-1 CLASSPATH=$( build-classpath objectweb-asm/asm commons-logging ) ant javadoc -%mvn_artifact pom.xml build/%{name}.jar - -%install -%mvn_install -J javadoc - -%files -f .mfiles -%license epl-v10.txt - -%files javadoc -f .mfiles-javadoc -%license epl-v10.txt - -%changelog -* Wed Jul 24 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-9 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild - -* Thu Jan 31 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-8 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild - -* Mon Nov 19 2018 Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> - 1.8.9-7 -- Add BR:glibc-langpack-en - See https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_bu... - -* Thu Jul 12 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-6 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild - -* Wed Feb 07 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-5 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild - -* Wed Jul 26 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-4 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild - -* Fri Feb 10 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.9-3 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild - -* Mon Dec 12 2016 gil cattaneo <puntogil(a)libero.it> 1.8.9-2 -- fix FTBFS - -* Sat Oct 29 2016 gil cattaneo <puntogil(a)libero.it> 1.8.9-1 -- update to 1.8.9 - -* Wed Feb 03 2016 Fedora Release Engineering <releng(a)fedoraproject.org> - 1.8.4-4 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild - -* Wed Jun 17 2015 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 1.8.4-3 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild - -* Thu Jan 29 2015 gil cattaneo <puntogil(a)libero.it> 1.8.4-2 -- introduce license macro - -* Tue Dec 09 2014 gil cattaneo <puntogil(a)libero.it> 1.8.4-1 -- update to 1.8.4 - -* Sat Jun 07 2014 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 1.6.12-12 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild - -* Fri Mar 28 2014 Michael Simacek <msimacek(a)redhat.com> - 1.6.12-11 -- Use Requires: java-headless rebuild (#1067528) - -* Mon Mar 24 2014 Michal Srb <msrb(a)redhat.com> - 1.6.12-10 -- Add alias aspectj:aspectjrt - -* Thu Nov 14 2013 gil cattaneo <puntogil(a)libero.it> 1.6.12-9 -- use objectweb-asm3 - -* Tue Oct 15 2013 Michal Srb <msrb(a)redhat.com> - 1.6.12-8 -- Add alias org.aspectj:aspectjr - -* Sat Aug 03 2013 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 1.6.12-7 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild - -* Wed Feb 13 2013 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 1.6.12-6 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild - -* Wed Jul 18 2012 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 1.6.12-5 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild - -* Wed Feb 15 2012 Andy Grimm <agrimm(a)gmail.com> 1.6.12-4 -- Add better comments, reference POM source URL - -* Wed Feb 15 2012 Andy Grimm <agrimm(a)gmail.com> 1.6.12-3 -- add commons-logging buildreq - -* Tue Feb 14 2012 Andy Grimm <agrimm(a)gmail.com> 1.6.12-2 -- Add javadoc -- Fix description - -* Tue Dec 20 2011 Andy Grimm <agrimm(a)gmail.com> 1.6.12-1 -- Initial Package diff --git a/dead.package b/dead.package new file mode 100644 index 0000000..5204a84 --- /dev/null +++ b/dead.package @@ -0,0 +1 @@ +Orphaned for 6+ weeks diff --git a/epl-v10.txt b/epl-v10.txt deleted file mode 100644 index 0d347ab..0000000 --- a/epl-v10.txt +++ /dev/null @@ -1,224 +0,0 @@ - - Eclipse Public License - v 1.0 - -THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE -PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF -THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. - -*1. DEFINITIONS* - -"Contribution" means: - -a) in the case of the initial Contributor, the initial code and -documentation distributed under this Agreement, and - -b) in the case of each subsequent Contributor: - -i) changes to the Program, and - -ii) additions to the Program; - -where such changes and/or additions to the Program originate from and -are distributed by that particular Contributor. A Contribution -'originates' from a Contributor if it was added to the Program by such -Contributor itself or anyone acting on such Contributor's behalf. -Contributions do not include additions to the Program which: (i) are -separate modules of software distributed in conjunction with the Program -under their own license agreement, and (ii) are not derivative works of -the Program. - -"Contributor" means any person or entity that distributes the Program. - -"Licensed Patents" mean patent claims licensable by a Contributor which -are necessarily infringed by the use or sale of its Contribution alone -or when combined with the Program. - -"Program" means the Contributions distributed in accordance with this -Agreement. - -"Recipient" means anyone who receives the Program under this Agreement, -including all Contributors. - -*2. GRANT OF RIGHTS* - -a) Subject to the terms of this Agreement, each Contributor hereby -grants Recipient a non-exclusive, worldwide, royalty-free copyright -license to reproduce, prepare derivative works of, publicly display, -publicly perform, distribute and sublicense the Contribution of such -Contributor, if any, and such derivative works, in source code and -object code form. - -b) Subject to the terms of this Agreement, each Contributor hereby -grants Recipient a non-exclusive, worldwide, royalty-free patent license -under Licensed Patents to make, use, sell, offer to sell, import and -otherwise transfer the Contribution of such Contributor, if any, in -source code and object code form. This patent license shall apply to the -combination of the Contribution and the Program if, at the time the -Contribution is added by the Contributor, such addition of the -Contribution causes such combination to be covered by the Licensed -Patents. The patent license shall not apply to any other combinations -which include the Contribution. No hardware per se is licensed hereunder. - -c) Recipient understands that although each Contributor grants the -licenses to its Contributions set forth herein, no assurances are -provided by any Contributor that the Program does not infringe the -patent or other intellectual property rights of any other entity. Each -Contributor disclaims any liability to Recipient for claims brought by -any other entity based on infringement of intellectual property rights -or otherwise. As a condition to exercising the rights and licenses -granted hereunder, each Recipient hereby assumes sole responsibility to -secure any other intellectual property rights needed, if any. For -example, if a third party patent license is required to allow Recipient -to distribute the Program, it is Recipient's responsibility to acquire -that license before distributing the Program. - -d) Each Contributor represents that to its knowledge it has sufficient -copyright rights in its Contribution, if any, to grant the copyright -license set forth in this Agreement. - -*3. REQUIREMENTS* - -A Contributor may choose to distribute the Program in object code form -under its own license agreement, provided that: - -a) it complies with the terms and conditions of this Agreement; and - -b) its license agreement: - -i) effectively disclaims on behalf of all Contributors all warranties -and conditions, express and implied, including warranties or conditions -of title and non-infringement, and implied warranties or conditions of -merchantability and fitness for a particular purpose; - -ii) effectively excludes on behalf of all Contributors all liability for -damages, including direct, indirect, special, incidental and -consequential damages, such as lost profits; - -iii) states that any provisions which differ from this Agreement are -offered by that Contributor alone and not by any other party; and - -iv) states that source code for the Program is available from such -Contributor, and informs licensees how to obtain it in a reasonable -manner on or through a medium customarily used for software exchange. - -When the Program is made available in source code form: - -a) it must be made available under this Agreement; and - -b) a copy of this Agreement must be included with each copy of the Program. - -Contributors may not remove or alter any copyright notices contained -within the Program. - -Each Contributor must identify itself as the originator of its -Contribution, if any, in a manner that reasonably allows subsequent -Recipients to identify the originator of the Contribution. - -*4. COMMERCIAL DISTRIBUTION* - -Commercial distributors of software may accept certain responsibilities -with respect to end users, business partners and the like. While this -license is intended to facilitate the commercial use of the Program, the -Contributor who includes the Program in a commercial product offering -should do so in a manner which does not create potential liability for -other Contributors. Therefore, if a Contributor includes the Program in -a commercial product offering, such Contributor ("Commercial -Contributor") hereby agrees to defend and indemnify every other -Contributor ("Indemnified Contributor") against any losses, damages and -costs (collectively "Losses") arising from claims, lawsuits and other -legal actions brought by a third party against the Indemnified -Contributor to the extent caused by the acts or omissions of such -Commercial Contributor in connection with its distribution of the -Program in a commercial product offering. The obligations in this -section do not apply to any claims or Losses relating to any actual or -alleged intellectual property infringement. In order to qualify, an -Indemnified Contributor must: a) promptly notify the Commercial -Contributor in writing of such claim, and b) allow the Commercial -Contributor to control, and cooperate with the Commercial Contributor -in, the defense and any related settlement negotiations. The Indemnified -Contributor may participate in any such claim at its own expense. - -For example, a Contributor might include the Program in a commercial -product offering, Product X. That Contributor is then a Commercial -Contributor. If that Commercial Contributor then makes performance -claims, or offers warranties related to Product X, those performance -claims and warranties are such Commercial Contributor's responsibility -alone. Under this section, the Commercial Contributor would have to -defend claims against the other Contributors related to those -performance claims and warranties, and if a court requires any other -Contributor to pay any damages as a result, the Commercial Contributor -must pay those damages. - -*5. NO WARRANTY* - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED -ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, -EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES -OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR -A PARTICULAR PURPOSE. Each Recipient is solely responsible for -determining the appropriateness of using and distributing the Program -and assumes all risks associated with its exercise of rights under this -Agreement , including but not limited to the risks and costs of program -errors, compliance with applicable laws, damage to or loss of data, -programs or equipment, and unavailability or interruption of operations. - -*6. DISCLAIMER OF LIABILITY* - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR -ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, -INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING -WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF -LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING -NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR -DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED -HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - -*7. GENERAL* - -If any provision of this Agreement is invalid or unenforceable under -applicable law, it shall not affect the validity or enforceability of -the remainder of the terms of this Agreement, and without further action -by the parties hereto, such provision shall be reformed to the minimum -extent necessary to make such provision valid and enforceable. - -If Recipient institutes patent litigation against any entity (including -a cross-claim or counterclaim in a lawsuit) alleging that the Program -itself (excluding combinations of the Program with other software or -hardware) infringes such Recipient's patent(s), then such Recipient's -rights granted under Section 2(b) shall terminate as of the date such -litigation is filed. - -All Recipient's rights under this Agreement shall terminate if it fails -to comply with any of the material terms or conditions of this Agreement -and does not cure such failure in a reasonable period of time after -becoming aware of such noncompliance. If all Recipient's rights under -this Agreement terminate, Recipient agrees to cease use and distribution -of the Program as soon as reasonably practicable. However, Recipient's -obligations under this Agreement and any licenses granted by Recipient -relating to the Program shall continue and survive. - -Everyone is permitted to copy and distribute copies of this Agreement, -but in order to avoid inconsistency the Agreement is copyrighted and may -only be modified in the following manner. The Agreement Steward reserves -the right to publish new versions (including revisions) of this -Agreement from time to time. No one other than the Agreement Steward has -the right to modify this Agreement. The Eclipse Foundation is the -initial Agreement Steward. The Eclipse Foundation may assign the -responsibility to serve as the Agreement Steward to a suitable separate -entity. Each new version of the Agreement will be given a distinguishing -version number. The Program (including Contributions) may always be -distributed subject to the version of the Agreement under which it was -received. In addition, after a new version of the Agreement is -published, Contributor may elect to distribute the Program (including -its Contributions) under the new version. Except as expressly stated in -Sections 2(a) and 2(b) above, Recipient receives no rights or licenses -to the intellectual property of any Contributor under this Agreement, -whether expressly, by implication, estoppel or otherwise. All rights in -the Program not expressly granted under this Agreement are reserved. - -This Agreement is governed by the laws of the State of New York and the -intellectual property laws of the United States of America. No party to -this Agreement will bring a legal action under this Agreement more than -one year after the cause of action arose. Each party waives its rights -to a jury trial in any resulting litigation. - diff --git a/sources b/sources deleted file mode 100644 index 6f32cec..0000000 --- a/sources +++ /dev/null @@ -1,2 +0,0 @@ -20fecd796edf139657cd631684485325 aspectjweaver-1.8.9-sources.jar -8494656dd83d45bc9880a38c99da0ee0 aspectjweaver-1.8.9.pom https://src.fedoraproject.org/rpms/aspectjweaver/c/f61564ef66104ade170fb6...

4 years, 7 months

Re: Need help on kickstarting my Open Source Contribution

by Charalampos Stratakis

----- Original Message ----- > From: "Rajeshkumar Pothiappan" <rajeshkumargp(a)fedoraproject.org> > To: python-devel(a)lists.fedoraproject.org > Sent: Saturday, January 26, 2019 6:01:35 PM > Subject: Need help on kickstarting my Open Source Contribution > > Hi Fedora Python Team, I am a developer, I can code in Python. I am > interested in contributing to Fedora as a Developer. I have read few > guides/wiki. Still I need someone to guide atleast till I make my first > contribution. > Can some one please guide me.. ,With minimal guidance on > 1. what to do > 2. where to refer > 3. Is any specific procedure to do that task, > > and many more. > > I need some mentor/guide to get started. > Thanks in advance. > by > Rajeshkumar P > _______________________________________________ > python-devel mailing list -- python-devel(a)lists.fedoraproject.org > To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/python-devel@lists.fedorapr... > Hello Rajeshkumar and thank you for your interest to contribute. As the previous poster said, it really depends on your interests. Fedora's python-sig group is usually focused on packaging python software, so basically working with SPEC files and the various intricacies around python software in order to produce rpm's for users to install. Fedora however has many of its infrastructure pieces written in python, and contributions to it are always welcome. Many other core components of the operating system are written in python as well, like dnf, abrt, the anaconda installer etc. You can check this page as well: https://whatcanidoforfedora.org/en In general, it is up to you to decide where you would like to focus your energy and skills on and after that we can guide you further. Do not hesitate to ask if you have any more questions. -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat

5 years, 3 months

Search results for query "contribute to wiki"