DOCSLIB.ORG

Where's My Monitoring At?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Where's My Monitoring At? André Klapper <[email protected]> GUADEC 2007, Birmingham Where's my monitoring at? Some random figures about a software project called GNOME (and a pr etty untechy talk, compared to the rest here) Monitoring ● Measurement & numbers for decision making support & a more optimal use of resources ● continuous process on various levels, can end up in defining and better documenting of processes and assigning of responsibilities What is this about, dude? ● GNOME = not a company, but nevertheless professional? ● identifying problems with the help of some automatization – some examples what we have, and what we don't have ● end up in better overall quality and happier end customers by clearer internal processes? „Where are we, where do we wanna be?“ GNOME: Structure Here: ● Release Team ● Docs ● GTP/I18N ● Bugsquad ● („Hacking“ only w.r.t maintainers) Source: https://twiki.softwarelivre.org/bin/viewfile/Main/ Vice nteAguiar?rev=1;filename=OrganogramaGNOME2.4_.png by Vicente Aguiar Release Team (RT) ● Aim: Test & publish perfect(TM) releases [partially helped by GARNOME and the BuildBrigade (-> Thursday 19th, 16:00)] ● Tasks: Release Engineering, Schedule Planning, Nagging, module inclusion final decisions, assigning Release Notes ● Resources: 8 persons, see http://live.gnome.org/ReleasePlanning/Membership ● Stats: no, what for? :-) ● Problems: response times, manpower/slacking. RT: Break request amounts and response times ● Rules: http://live.gnome.org/ReleasePlanning/ RequestingFreezeBreaks ● ABI/API UI String Hardcode 2.13 Amount 2 2 24 21 ø Resp.Time >1 >1, >3 18× >1, (in days) 3× >2 2.17 Amount 1 1 5 10 ø Resp.Time >1 >1 2× >1, 2× >2, >1 (in days) 1× >4, 1× >9 RT: Wrong/missing announcements of maintainers ● miss of informing any of release-team, desktop- devel-list, gnome-i18n and gnome-doc-list (http://live.gnome.org/MaintainersCorner) ● total correct missed... r-t i18n d-d-ldoc all 2005/09/05 – 2006/03/12 (2.13) 41 23 12 1 3 6 0 2006/03/13 – 2006/09/03 (2.15) 46 20 19 2 12 11 0 2006/09/04 – 2007/03/11 (2.17) 54 26 19 2 16 8 1 ● Some modules do not have strings, therefore no announcements were sent to gnome-i18n@. Table results by searching for „branch“ in subject of the four mail ing lists) Maintainers' quick guide de g sk r no t el g m op ea no e -d se m -d e -t e o ve e -i1 c-l l-l Code- am 8 is is Time @ n@ t@ t@ Action base http://live.gnome.org/Schedule Branching % always inform inform inform inform String Change trunk Announcement Period inform inform trunk Freeze period request (accidentially forgotten stable to mark) inform inform stable ...else: inform request UI Change trunk Announcement Period inform trunk Freeze period request request stable always request request Code Change trunk Hardcode Freeze request RT: Release notes ● Resources: pure luck? ● Problems: last cycles: always new writers; different lenghts & styles => no consistency ● 2.18 release notes written in the last days, no volunteers ● 2.20: volunteers available, better planning and embedded into the schedule (timeframe: august 6th – September 10th) => looks good ;-) User Documentation ● http://live.gnome.org/DocumentationProject ● Aim: Provide documentation for applications ● Tasks: Write and update documentation ● Resources, Stats: ? ● Problems: not always up-to-date (only a few weeks between freeze and release) => manpower (?); no way of tracking actuality Documentation: How up to date? ● Outdated if UI changes a lot => developers have to inform the doc writers ● Docs that haven't been updated for a long time: svn log - -limi t 1 h ttp:/ /akla pper@ svn.g nome. or g/ svn/ $modu le/tr unk/{d oc,he lp,do cs}/C /$mod ule.x ml (excluded build fixes, migration to g-d-u) ● => oldest docs: bug-buddy; gnome-keyring-manager (2005-03-25), fast-user-switch-applet, zenity, gnome- applets\battstat (2005-12-11) ● http://l10n.gnome.org/module/: add „last change“ info? I18N/GTP ● Aim: Translate UI and Documentation to other languages ● Resources: 2 GTP spokepersons (http://live.gnome.org/TranslationProject/SpokesPersons), >100 language teams (http://developer.gnome.org/projects/gtp/ teams.html), each one with one coordinator and an unknown number of translators I18N/GTP ● Stats: damned-lies at http://l10n.gnome.org per language, module, team, and release set. Powerful. ● Tasks of GTP: String Freeze Break Approvals, Language Team Maintainership changes, new languages approval: gnome-18n@ for entry at l10n.gnome.org, bugzilla team for creation of L10N component, and later on accounts-team for svn permissions (only 3 1/2 people on accounts team) I18N Teams: Maintenance ● http://l10n.gnome.org/languages/ lists 133 langs ● Strings: 2.14 2.18 UI ~35000 36916 Docs ~18100 24094 ● (note: partially buggy stats due to http://bugzilla.gnome.org/416009) I18N Teams: UI Translation changes within the last 12 months Positive (>10%) Negative (>-7%) Lang 2.14 2.18 diff Lang 2.14 2.18 diff Bengali Indian 9 80 71 Nepali 97 77 -20 Malayalam 19 76 57 Albanian 98 84 -14 Slovenian 40 89 49 Indonesian 96 84 -12 Oriya 18 61 43 Czech 98 87 -11 Marathi 9 52 43 Croatian 65 54 -11 Malagasy 8 50 42 Romanian 93 83 -10 Arabic 57 99 42 Norwegian Nynorsk 80 70 -10 Tamil 67 85 18 Serbian Latvian 98 89 -9 Serbian 98 89 -9 Welsh 97 88 -9 Canadian English 96 87 -9 Latvian 97 89 -8 GNOME 2.18: 63 langs Georgian 66 58 -8 with UI translation >50% Slovak 61 54 -7 Source: Stats as per http://l10n.gnome.org/releases/gnome-2-1* on 2007-07-10, 02:00 UTC I18N Teams: Docu Translation changes within the last 12 months Docs with >10% status Comparison Lang 2.14 2.18 diff Lang UI Docs Spanish 71 88 17 Arabic 99 0 French 34 85 51 Dzongkha 99 0 Swedish 24 70 46 Macedonian 99 0 Italian 41 44 3 Hungarian 99 2 Russian 14 40 26 Catalan 99 2 British English 0 34 34 Finnish 99 2 Ukrainian 33 32 -1 Lithuanian 99 0 Brazilian Portugu2e5se 27 2 Danish 99 0 Punjabi 5 18 13 Japanese 99 1 Portuguese 0 16 16 Vietnamese 99 0 Korean 0 14 14 German 0 12 12 Bulgarian 11 12 1 63 langs with UI >50%, but 13 langs with Docs >10%? Source: Stats as per http://l10n.gnome.org/releases/gnome-2-1* on 2007-07-10, 02:00 UTC I18N Teams: Maintainer changes and other non-“freeze requests“ ● data taken from gnome-18n@ mailinglist Maintainership change or drop actively by Complaint about Granting for SVN maintainer himself, or unresponsiveness, Access; webpage or after a complaint with and NO response by email address change, positive reaction of the team leader => or wrong maintainer in maintainer to change maintainership change b.g.o 2.13 9 1 8 2.15 12 6 7 2.17 9 0 6 ● response times? I18N Teams: Maintainer changes etc: Response times of GTP ● Number of „Trackable“ Median [in Average Version requests requests days] [in days] 2.13 17 16 1 7,06 2.15 23 20 2,5 7,75 2.17 13 8 0 2,38 ● some requests perhaps answered off-list, or really unanswered... GTP: Announcement amounts ● 2.14 (6 weeks) 2.18 (8 weeks) Total 163 69 Top 3 evolution (58) gedit (8) gnome-utils (13) eog (6) gnome-panel (12) evolution (6) ● not significant Bugsquad ● Aim: Quality Assurance (http://live.gnome.org/Bugsquad) ● Tasks: Keeping track of bugs, make major bugs not go unnoticed, user help and feedback. ● Resources: Technical bugmasters and varying number of triagers (2-8 „hardcore“ triagers, plus maintainers and some „normal“ triagers) ● Existing stats: b.g.o/weekly-bug-summary.cgi, b.g.o/duplicates.cgi, Patches: b.g.o/reports/patch-diligence-report.cgi, b.g.o/reports/patch-report.cgi (general) Bugsquad: Workload 2005 2006 2007 Amount of Days: 365 365 193 Current open reports, excludes enhance. req.: 18888 26942 30691 Opened in that period: 37845 67543 64952 +78% +81% Closed: 34196 59006 62413 #Bugs closed by top All-time: bug closer 3211 8371 6788 15842 Sources: <http://developer.gnome.org/projects/bugsquad/statistics/2005/> and /2006/>, <http://bugzilla.gnome.org/reports/weekly-bug- summary.cgi?days=194&products=0>, <http://mail.gnome.org/archives/desktop- devel-list/2006-January/msg00004.html>, Olav Top 10 Bug closers in 2007 Bugs without a response Open bugs Bugs without Product (incl. enhanc.)response Evolution 4259 1045 24,54% nautilus 2057 665 32,33% gtk+ 2015 406 20,15% doxygen 650 344 52,92% rhythmbox 818 100 12,22% gnome-vfs 456 120 26,32% epiphany 612 23 3,76% GnuCash 514 38 7,39% gnome-panel 436 69 15,83% gnome-applets 377 124 32,89% gimmie 296 233 78,72% Gnumeric 486 55 11,32% Evolution Exchange 288 117 40,63% GtkHtml 319 65 20,38% Gstreamer 446 56 12,56% Source: top 15 modules of the last 365 days (http://bugzilla.gnome.org/reports/weekly-bug- summary.cgi?days=365&products=30) as per 2007/07/13 UTC 02:45 Graphical Reports? Source: http://bugzilla.ximian.com/reports.cgi?product=Evolution& output=show_chart&datasets=NEW %3A&banner=1&quip=0 Bugsquad ● Problems: Amount of untriaged bugs, response rate and time; understaffed products (bugzilla mail ignored by maintainers and only up to triagers), quality of stacktraces and installing debug packages, hacked up Auto-reject feature, manpower, Patch nagging (-> Patchsquad BoF on Saturday 21st, 10:30) ● 2.20: Breakpad Support (see Fernando Herrera's „Managing bugs and crashes in GNOME“, Sa 21st July, 14:00) ● => Major aim: reduce w orkloud Bugsquad: Flood me, baby! Bugsquad: Auto-reject ● http://live.gnome.org/Bugsquad/AutoReject ● Bugsquad: Auto-reject Date 2007/05/08 2007/06/10 2007/07/10 Nautilus 8925 9347 9603 Evolution 10604 11190 11524 TOTAL 26236 27571 28619 Dead modules in SVN ● Problems: Identify dead modules (bit rott) => translators waste time; or new maintainership needed? ● "svn log --limit 5" to find modules without
Load more

Recommended publications
  • Ubuntu Kung Fu
    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
    [Show full text]
  • Ausgabe 06/2016 Als
    freiesMagazin Juni 2016 Themen dieser Ausgabe sind u. a. Ubuntu unter Windows ausprobiert Seite 3 Microsoft hat auf der Entwicklerkonferenz Build 2016 einigermaßen überraschend verraten, dass in zukünftigen Windows-Versionen die Bash sowie eine ganze Sammlung von Linux-Tools auf der Basis von Ubuntu 14.04 integriert werden soll. Der Artikel gibt einen ersten Eindruck des „Windows-Subsystems für Linux“, das Microsoft bereitstellt, um Ubuntu ohne Virtualisierung unter Windows laufen zu lassen. (weiterlesen) Linux-Distributionen im Vergleich – eine etwas andere Auswahl Seite 8 In dem Artikel werden eine Reihe von Linux-Distributionen vorgestellt, die nicht so bekannt sind wie die klassischen „großen“ Distributionen oder nicht so häufig verwendet werden, weil sie entweder für spezielle Anwendungen oder für einen besonderen Benutzerkreis konzipiert sind. Ziel ist es, diese Distributionen ein bisschen näher kennenzulernen, damit man weiß, was zur Verfügung steht, wenn man einmal etwas ganz bestimmtes braucht. (weiterlesen) Audacity 2.1 – Teil I Seite 21 Aus verschiedenen Gründen ist Audacity der beliebteste freie Audio-Editor. Im Internetzeitalter hat man sich daran gewöhnt, dass viele Programme kostenlos verfügbar sind, aber dennoch eine hohe Professionalität aufweisen. In die Riege der besten Open-Source-Werkzeuge reiht sich auch Audacity ein. Ob man nun die Schallplatten- oder Kassettensammlung digitalisieren, Videos nachvertonen oder das eigene Gitarrenspiel oder den Bandauftritt aufnehmen und bearbeiten möchte – all das ist mit Audacity möglich. (weiterlesen) © freiesMagazin CC-BY-SA 4.0 Ausgabe 06/2016 ISSN 1867-7991 MAGAZIN Editorial Veränderungen unter der Haube Viewport-Meta-Tag auf den meisten Seiten Stan- Inhalt Technisch betrachtet ist freiesMagazin stabil. Ver- dard ist, gilt er eher als eine Krücke, die in Zukunft Linux allgemein änderungen erfolgen daher naturgemäß in klei- wohl durch eine CSS basierte Lösung ersetzt wer- Ubuntu unter Windows ausprobiert S.
    [Show full text]
  • A Brief History of GNOME
    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
    [Show full text]
  • Ubuntu Kung Fu.Pdf
    Prepared exclusively for J.S. Ash Beta Book Agile publishing for agile developers The book you’re reading is still under development. As part of our Beta book program, we’re releasing this copy well before we normally would. That way you’ll be able to get this content a couple of months before it’s available in finished form, and we’ll get feedback to make the book even better. The idea is that everyone wins! Be warned. The book has not had a full technical edit, so it will con- tain errors. It has not been copyedited, so it will be full of typos and other weirdness. And there’s been no effort spent doing layout, so you’ll find bad page breaks, over-long lines with little black rectan- gles, incorrect hyphenations, and all the other ugly things that you wouldn’t expect to see in a finished book. We can’t be held liable if you use this book to try to create a spiffy application and you somehow end up with a strangely shaped farm implement instead. Despite all this, we think you’ll enjoy it! Throughout this process you’ll be able to download updated PDFs from your account on http://pragprog.com. When the book is finally ready, you’ll get the final version (and subsequent updates) from the same address. In the meantime, we’d appreciate you sending us your feedback on this book at http://books.pragprog.com/titles/ktuk/errata, or by using the links at the bottom of each page.
    [Show full text]
  • Indicators for Missing Maintainership in Collaborative Open Source Projects
    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
    [Show full text]
  • GNOME Annual Report 2014
    GNOME Annual Report 2014 GNOME Annual Report 2013 Letter from the GNOME Foundation 3 Hackfests 4 Conferences 6 Internship programs 8 Finances 10 Accessibility 11 Privacy campaign 12 Bugzilla statistics 13 GNOME releases 14 Advisory Board 17 Friends of GNOME 18 Credits 20 1 Letter from the GNOME Foundation It is bittersweet to be introducing the 2013 GNOME annual report. This financial year was my last year as GNOME's Executive Director, as I left the position in March of 2014. However, I'm thrilled to have recently been elected to GNOME's Board of Directors and am happy to continue to contribute to GNOME's future. GNOME is such an important, vibrant project, and I feel lucky to be able to play a part in it. As you will see when you read this annual report, there have been a lot of great things that have happened for the GNOME Foundation during this period. Two new companies joined our advisory board, the Linux Foundation and Private Internet Access. The work funded by our accessibility campaign was completed and we ran a successful campaign for privacy. During this period, there was a fantastic Board of Directors, a dedicated Engagement team (who worked so hard to put this report together), and the conference teams (GNOME.Asia, GUADEC and the Montreal Summit) knocked it out of the park. Most importantly, we’ve had an influx of contributors, more so than I’ve seen in some time. I hope that I have helped us to get in touch with our values during my time as Executive Director and I think that GNOME is more aware of its guiding mission than ever before.
    [Show full text]
  • Awoken Icon Theme - Installation & Customizing Instructions 1
    Awoken Icon Theme - Installation & Customizing Instructions 1 AWOKEN ICON THEME Installation & Customizing Instructions Alessandro Roncone mail: [email protected] homepage: http://alecive.deviantart.com/ Awoken homepage (GNOME Version): link kAwoken homepage (KDE Version): link Contents 1 Iconset Credits 3 2 Copyright 3 3 Installation 3 3.1 GNOME........................................................3 3.2 KDE..........................................................4 4 Customizing Instructions 4 4.1 GNOME........................................................4 4.2 KDE..........................................................5 5 Overview of the customization script6 5.1 How to customize a single iconset..........................................7 6 Customization options 8 6.1 Folder types......................................................8 6.2 Color-NoColor.................................................... 11 6.3 Distributor Logos................................................... 11 6.4 Trash types...................................................... 11 6.5 Other Options.................................................... 11 6.5.1 Gedit icon................................................... 11 6.5.2 Computer icon................................................ 11 6.5.3 Home icon................................................... 11 6.6 Deprecated...................................................... 12 7 How to colorize the iconset 13 8 Icons that don't want to change (but I've drawed) 14 9 Conclusions 15 9.1 Changelog......................................................
    [Show full text]
  • Debian and Ubuntu
    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
    [Show full text]
  • Demande-Subvention-Mairie-Toulouse
    IINNFFOORRMMAATTIIOONNSS PPRRAATTIIQQUUEESS Cette partie constitue un guide pratique pour les associations souhaitant faire une demande de subvention. La Ville de Toulouse peut apporter un concours financier à une association lorsque son activité présente un intérêt communal. Une subvention n’est jamais attribuée spontanément ; il appartient donc à l’association et à elle seule d’en formuler la demande. Toute subvention égale ou supérieure à 23 000 € doit faire l’objet d’une convention entre la Ville et l’association. Cette convention définit l’objet, le montant et les conditions d’utilisation de la subvention attribuée. Cette convention peut être annuelle ou pluriannuelle. L’association qui demande une subvention au titre de la politique de la ville n’est pas concernée par l’obligation de remplir le présent formulaire, sauf si elle demande une subvention hors du champ de la politique de la ville. Le dossier commun de demande de subvention comprend un formulaire et des pièces à joindre impérativement (voir liste ci-après). Il concerne les demandes de financement du fonctionnement de l’association, d’action(s) spécifique(s) ou d’investissement. Le dossier complet doit être composé de : 1 – Formulaire de demande à renseigner Pour toutes les demandes, les fiches 1, 2 et 7 doivent être obligatoirement renseignées. - Fiche 1 (pages 4 à 7) : présentation de l’association, éléments d’identification, activités habituelles, mode de fonctionnement… - Fiche 2 (page 8) : budget prévisionnel établi dans le respect de la nomenclature du plan comptable associatif. - Fiche 7 (page 19) : attestation sur l’honneur permettant au représentant légal de l’association ou à son mandataire, de signer la demande de subvention et d’en indiquer le montant.
    [Show full text]
  • 080216 Commissioners Court
    THE COMMISSIONERS COURT * McLENNAN COUNTY THE STATE OF TEXAS TO ALL PERSONS INTERESTED: NOTICE IS HEREBY GIVEN that, in accordance with the Government Code, Chapter 551, ( known as the Open Meetings Act), as amended, a regular meeting of Commissioners' Court, the governing body of McLennan County, will be held on Tuesday, the 2° 1 day of August, 2016 at 9: 00 a. m. in the Commissioners' Courtroom, I° Floor, West Wing, McLennan County Courthouse, City of Waco, Texas, at which time, the subjects below will be considered. In addition, notice is hereby given that this August 2, 2016 meeting may be recessed and reconvened on Wednesday, the rd day of August, 2016 at 1: 30 p.m. at the same location, to complete discussion and action on the agenda items set forth below, including the Budget Work Session, unless the meeting on August 2, 2016 is adjourned by decision of the Commissioners Court. AGENDA I. PROOF OF POSTING OF NOTICE in accordance with the provisions of Chapter 551. 041, Government Code, as amended, known as the Open Meetings Act. II. A MOMENT OF SILENCE/ INVOCATION; PLEDGES OF ALLEGIANCE III. CONSIDERATION OF, AND/ OR ACTION ON, THE FOLLOWING: A. APPROVAL/ RATIFICATION OF PROCLAMATION/ RESOLUTIONS B. HEARING FROM MEMBERS OF THE PUBLIC ON COUNTY BUSINESS MATTERS C. ITEMS PREVIOUSLY DEFERRED 1. Regarding Contracts/ Lease Agreements/! nterlocal Agreements: a. Authorization of Service Agreement: Sterling Infosystems, Inc.( re: Background Screening Services) b. Authorization of(nterlocal Cooperation Agreement for Animal Shelter Services: City of Waco c. Authorization of Spay/ Neuter Services Contract: Animal Birth Control Clinic, Inc.
    [Show full text]
  • 1 Simon Schampijer
    Sugar: using the GNOME platform to build a learning platform 1 Simon Schampijer - GUADEC 2012, A Coruña Talk outline - Introduction to Sugar - The Sugar platform - Using the GNOME platform - GNOME technologies Sugar is using - Adapt to new technologies - Sugar and Touch - Future Roadmap - How to contribute, where do we need help? 2 Simon Schampijer - GUADEC 2012, A Coruña Sugar ...is a learning environment designed for children ...was originally designed for the XO-1 laptop of the One Laptop per Child project (OLPC) ...runs on most netbooks and PCs today ...is for example used by learners in Uruguay, Ruanda and Nepal ...is available in more than 25 languages 3 Simon Schampijer - GUADEC 2012, A Coruña Main features - especially made for the audience - clarity in design - work-flow based on Activities (tasks) - Journal 5 Simon Schampijer - GUADEC 2012, A Coruña Main features - collaboration centric - low floor, no ceiling - every user can be a contributor of content and code 6 Simon Schampijer - GUADEC 2012, A Coruña Collaboration Centric 7 Simon Schampijer - GUADEC 2012, A Coruña The Sugar platform - a platform for Activity authors - a platform for deployments - a platform for the learner 8 Simon Schampijer - GUADEC 2012, A Coruña Using the GNOME platform - Sugar is the GNOME platform + a target audience oriented UI - Sugar does use the GNOME building blocks (libraries) - we share the platform/application model - Sugar does mimic the GNOME schedule 9 Simon Schampijer - GUADEC 2012, A Coruña GNOME technologies Sugar is using - GTK+ - Metacity
    [Show full text]
  • Easy File Sharing with Nitroshare Xfce Power User Tips, Tricks
    Easy File Sharing with NitroShare Xfce Power User Tips, Tricks & Tweaks: File Utilities (Part Two) Running Multiple Commands From The Command Line Or A Bash Script Undo Gmail's Latest "Enhancements" Game Zone: Steel Storm: Burning Retribution PCLinuxOS Recipe Corner Testimonials From Veteran PCLinuxOS Users ms_meme's nook GIMP Tutorial: Masks Explained LibreOffice Tips & Tricks, Part 2 And Much More! PCLinuxOS Magazine Page 1 Table of Contents 3 Welcome From The Chief Editor Disclaimer 4 Easy File Sharing with NitroShare 1. All the contents of The PCLinuxOS Magazine are only for general information and/or use. Such contents do not constitute advice and should not be relied upon in making (or refraining from 5 Screenshot Showcase making) any decision. Any specific advice or replies to queries in any part of the magazine is/are the person opinion of such experts/consultants/persons and are not subscribed to by The 6 Xfce Power User Tips, Tricks & Tweaks: File Utilities (Part Two) PCLinuxOS Magazine. 12 Screenshot Showcase 2. The information in The PCLinuxOS Magazine is provided on an "AS IS" basis, and all warranties, expressed or implied of any kind, regarding any matter pertaining to any information, advice 13 PCLinuxOS Puzzled Partitions or replies are disclaimed and excluded. 16 Undo Gmail's Latest "Enhancements" 3. The PCLinuxOS Magazine and its associates shall not be liable, at any time, for damages (including, but not limited to, without limitation, damages of any kind) arising in contract, rot or 17 Game Zone: Steel Storm: Burning
    [Show full text]