first commit : english version of project thesis

.gitignore

+*.out
+*.aux
+*.log
+*.abs

Copyright-logo.txt

+CEUR-WS Restricted Use Logo License
+Copyright (c) 2020 CEUR-WS.org Team
+
+1. The CEUR-WS logo is reserved for use at CEUR-WS.org. Please do not use the CEUR-WS logo on your website.
+2. The CEUR-WS logo can be used in the official template for publishing articles on CEUR-WS.
+3. We reserve the right to revoke a license for the CEUR-WS logo.

Copyright.lppl.txt

+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but 
+it is written in such a way that you can use it even if your work is 
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+    
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification' 
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+    
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter' 
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.    
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the 
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption 
+to a component of the Work. 
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+     
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+  
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work; 
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+     
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+      
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the 
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+     
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+     
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.  
+    
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+     
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be distributed and/or modified under the
+  % conditions of the LaTeX Project Public License, either version 1.3
+  % of this license or (at your option) any later version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  % 
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.  
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+   
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
+

Copyright.txt

+Latex files are licensed under the LaTeX Project Public License (Copyright.lppl)
+CEUR-WS logo is licensed under the CEUR-WS Restricted Use Logo License (Copyright.logo)

README.md

+# LaTeX user template and guide
+
+To compile user guide:
+
+1. `pdflatex sample-1col`
+2. `bibtex sample-1col`
+3. `pdflatex sample-1col`
+4. `pdflatex sample-1col`
+
+and
+
+1. `pdflatex sample-2col`
+2. `bibtex sample-2col`
+3. `pdflatex sample-2col`
+4. `pdflatex sample-2col`
+
+or
+
+use the makefile:
+
+`make`
+

obs-en.bib

+
+@book{jeanne_guien_consumerisme_2021,
+	title = {Le consumérisme à travers ses objets},
+	url = {https://www.editionsdivergences.com/livre/le-consumerisme-a-travers-ses-objets},
+	abstract = {Qu’est ce que le consumérisme ? Comment s’habitue-t-on à surconsommer, au point d’en oublier comment faire sans, comment on faisait avant, comment on fera après ? Pour répondre à ces questions, Jeanne Guien se tourne vers des objets du quotidien : gobelets, vitrines, mouchoirs, déodorants, smartphones. Cinq objets auxquels nos gestes et nos sens ont été éduqués, cinq objets banals mais opaques, utilitaires mais surchargés de valeurs, sublimés mais bientôt jetés. En retraçant leur histoire, ce livre entend montrer comment naît le goût pour tout ce qui est neuf, rapide, personnalisé et payant. Car les industries qui fabriquent notre monde ne se contentent pas de créer des objets, elles créent aussi des comportements. Ainsi le consumérisme n’est-il pas tant le vice moral de sociétés « gâtées » qu’une affaire de production et de conception. Comprendre comment nos gestes sont déterminés par des produits apparemment anodins, c’est questionner la possibilité de les libérer.{\textless}/p{\textgreater}
+{\textless}p{\textgreater}\ {\textless}/p{\textgreater}
+{\textless}p class="p1"{\textgreater}JEANNE GUIEN, ancienne élève de l’École normale supérieure, est docteure en philosophie et agrégée. En 2019, elle a soutenu une thèse à l’université Paris 1 Panthéon-Sorbonne consacrée à la notion d’obsolescence, étudiant l’histoire des débats autour de la durée de vie des moyens de production et des biens de consommation. Membre du CETCOPRA et du LISRA, co-organisatrice du séminaire Deuxième vie des objets (Mines, EHESS), elle conduit également des expériences de recherche-action concernant les biffins (récupérateurs de rue en Ile-de-France), le freeganisme (récupération alimentaire), la collecte municipale des déchets et l’antipub. Elle anime également une émission radio et un blog sur médiapart afin de médiatiser certains enjeux sociaux et politiques liés au déchet : condition de travail des éboueurs et des biffins, politiques d’ « économie circulaire », injustices environnementales en France, répartition inégale de l’étiquette « écologiste » dans les luttes et les mouvements sociaux.},
+	language = {fr},
+	urldate = {2022-07-20},
+	publisher = {Editions Divergences},
+	author = {Jeanne Guien},
+	year = {2021},
+	file = {Snapshot:/home/eda/Zotero/storage/KPZVKFNR/le-consumerisme-a-travers-ses-objets.html:text/html},
+}
+
+@book{emmanuel_bonnet_heritage_2021,
+	title = {Héritage et fermeture},
+	url = {https://www.editionsdivergences.com/livre/heritage-et-fermeture},
+	abstract = {{\textless}p{\textgreater}Nous dépendons pour notre subsistance d’un «monde organisé», tramé par l’industrie et le management. Ce monde menace aujourd’hui de s’effondrer. Alors que les mouvements progressistes rêvent de monde commun, nous héritons contre notre gré de communs moins bucoliques, «négatifs», à l’image des fleuves et sols contaminés, des industries polluantes, des chaînes logistiques ou encore des technologies numériques. Que faire de ce lourd héritage dont dépendent à court terme des milliards de personnes, alors qu’il les condamne à moyen terme? Nous n’avons pas d’autre choix que d’apprendre, en urgence, à destaurer, fermer et réaffecter ce patrimoine. Et ce, sans liquider les enjeux de justice et de démocratie. Contre le front de modernisation et son anthropologie du projet, de l’ouverture et de l’innovation, il reste à inventer un art de la fermeture et du démantèlement: une (anti)écologie qui met «les mains dans le cambouis».{\textless}/p{\textgreater}},
+	language = {fr},
+	urldate = {2022-07-20},
+	publisher = {Editions Divergences},
+	author = {Emmanuel Bonnet and Diego Landivar and Alexandre Monnin},
+	year = {2021},
+}
+
+@article{jeanne_guien_travailler_2017,
+	title = {Travailler à consommer. {Expérimentation} et émancipation dans les pratiques de consommation alternative},
+	volume = {31},
+	issn = {1627-9506},
+	shorttitle = {Travailler à consommer},
+	url = {https://www.cairn.info/revue-terrains-et-travaux-2017-2-page-45.htm},
+	doi = {10.3917/tt.031.0045},
+	abstract = {L’évitement des circuits marchands et des modèles de production dominants ouvre à un répertoire d’activités et de techniques variées : récupérer, revendre, recycler, réparer, faire soi-même, réduire ses besoins... Contrairement aux discours qui classent ces pratiques de consommation alternative selon les motivations et le niveau de vie des acteurs (sommairement catégorisés comme « précaires » ou « bobos »), pour distinguer voire opposer ceux-ci, cet article d’ethnographie comparative est fondé sur l’analyse des pratiques et représentations des acteurs. Les terrains comparés montrent qu’un certain nombre de gestes, valeurs et représentations sont communs aux différents acteurs, suggérant l’invention d’une culture matérielle partagée, où faire avec peu signifie expérimenter en faisant par soi-même, et où l’évitement des circuits économiques dominants conduit à les contester, dans une démarche de consommation à la fois laborieuse et émancipatrice.},
+	language = {fr},
+	number = {2},
+	urldate = {2022-07-20},
+	journal = {Terrains \& travaux},
+	author = {Jeanne Guien and Violeta Ramirez},
+	year = {2017},
+	note = {Place: Cachan
+Publisher: ENS Paris-Saclay},
+	keywords = {alternative, culture matérielle, environnement, expérimentation, récupération},
+	pages = {45--62},
+	file = {Snapshot:/home/eda/Zotero/storage/VL857QVQ/revue-terrains-et-travaux-2017-2-page-45.html:text/html},
+}
+
+@misc{vasseur_quest-ce_2015,
+	title = {Qu’est-ce que l’obsolescence logicielle ?},
+	url = {https://www.halteobsolescence.org/quest-ce-que-lobsolescence-logicielle/},
+	abstract = {Le raccourcissement intentionnel de la durée de vie n’est pas réservé aux biens matériels. Les logiciels en font aussi les frais. Les mécanismes utilisés sont les mêmes que pour les...},
+	language = {fr-FR},
+	urldate = {2022-07-20},
+	journal = {HOP},
+	author = {Vasseur, Laetitia},
+	month = aug,
+	year = {2015},
+}
+
+@incollection{bartels_software_2012,
+	title = {Software {Obsolescence}},
+	isbn = {978-1-118-27547-4},
+	url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/9781118275474.ch6},
+	abstract = {The three general causes of software obsolescence are categorized as technological, functional, and logistical, and are referred to as obsolescence modes. The purchase obsolescence mechanism includes obsolescence root causes that pertain primarily to purchasing issues. The support mechanism has to do with obsolescence root causes that arise when the technical support of software ends or when update or patches are no longer created for a software application. The compatibility mechanism deals with problems that develop when changes in either software or hardware result in an incompatibility between the two, eventually limiting or terminating the functionality of the system. The infrastructure mechanism includes problems that arise when the tools needed to build, test, and integrate the software with other software applications become unavailable. The distribution mechanism encompasses problems that arise when the access to the software is limited or terminated. Controlled Vocabulary Terms computer software},
+	language = {en},
+	urldate = {2022-07-20},
+	booktitle = {Strategies to the {Prediction}, {Mitigation} and {Management} of {Product} {Obsolescence}},
+	publisher = {John Wiley \& Sons, Ltd},
+	author = {Bartels and Ermel and Sandborn and Pecht},
+	year = {2012},
+	doi = {10.1002/9781118275474.ch6},
+	keywords = {software compatibility obsolescence mechanism, software distribution obsolescence mechanism, software infrastructure obsolescence mechanism, software purchasing obsolescence, software support},
+	pages = {143--155},
+	file = {Snapshot:/home/eda/Zotero/storage/IG9V7S55/9781118275474.html:text/html},
+}
+
+@article{tamar_makov_is_2021,
+	title = {Is repairability enough? big data insights into smartphone obsolescence and consumer interest in repair},
+	volume = {313},
+	url = {https://www.sciencedirect.com/science/article/pii/S0959652621017790},
+	abstract = {A dominant narrative surrounding smartphone lifespans suggests that their objective functional capabilities deteriorate rapidly and that if only devices were more repairable consumers would use them longer thereby reducing demand for new production and e-waste generation. Here we use a big-data approach to help unpack this narrative and examine two related yet distinct aspects: smartphone performance and obsolescence, and consumers interest in repair. Examining over 3.5 million iPhone benchmarking test scores, we reveal that the objective performance of devices remains very stable over time and does not rapidly deteriorate as common wisdom might suggest. In contrast, testing frequency varies substantially. This discrepancy suggests that factors other than objective performance meaningfully influence consumers' perceptions of smartphone functionality and obsolescence. Relatedly, our analysis of 22 million visits to a website offering free repair manuals revels that interest in repair declines exponentially over time and that repairability does not necessarily prolong consumer's interest in repair. Taken together, our findings indicate that non-technical aspects, such as mental depreciation and perceived obsolescence play a critical role in determining smartphone lifespans, and suggest that focus on the technical aspects of repairability as currently discussed by policy makers is unlikely to yield the desired extension in smartphone lifespan. We propose that sustainability advocates try to avoid narratives of planned obsolescence which might have counterproductive impacts on perceived obsolescence and consumer's’ interest in repair, and instead highlight how well devices perform over time. More broadly, this work demonstrates the potential of using novel datasets to directly observe consumer behavior in natural settings, and improve our general understanding of issues such as planned obsolescence and repair.},
+	urldate = {2022-07-20},
+	journal = {Journal of Cleaner Production},
+	author = {Tamar Makov and Colin Fitzpatrick},
+	month = sep,
+	year = {2021},
+}
+
+
+@techreport{castellazzi_obsolescence_2021,
+	title = {Obsolescence logicielle},
+	url = {https://www.vie-publique.fr/rapport/280293-obsolescence-logicielle},
+	abstract = {{\textbar} 75 \%, c’est la part des impacts environnementaux du secteur numérique uniquement lié à la fabrication d’appareils numériques. L’une des causes : leur renouvellement trop rapide. L’obsolescence logicielle correspond à la diminution des possibilités d’usage d’un appareil numérique (smartphone, tablette, ordinateur, etc.) en raison de l’indisponibilité ou du dysfonctionnement d’un logiciel. Confié au Conseil général de l’environnement et du développement durable (CGEDD) et au Conseil général de l’économie (CGE), le rapport formule plusieurs propositions visant à lutter contre l’obsolescence logicielle et à allonger la durée de vie des appareils numériques et agissant sur trois axes : Améliorer l’accès du consommateur aux mises à jour et aux logiciels. Cette première préconisation est de permettre au consommateur de dissocier les mises à jour nécessaires et non nécessaires. Le grand public doit avoir accès à l’information la plus transparente possible sur l’impact des mises à jour sur ses biens, tout en limitant la taille des mises à jour indispensables. Objectif, éviter les cas d’"obésiciels" où une mise à jour logicielle est trop lourde pour que l’équipement le supporte. Une dissociation qui rend possible la proposition phare du rapport : imposer aux fabricants de fournir gratuitement les mises à jour nécessaires au maintien de la conformité du bien. Celles-ci devront être disponibles pendant une période correspondant à la durée d’usage attendue, par exemple 5 ans pour un smartphone. Faciliter la réparation des appareils. Pour faciliter la réparation des appareils numériques, le rapport propose d’imposer aux fabricants de mettre à disposition les logiciels et leurs mises à jour, pendant la durée d’usage définie et dès la fin de la commercialisation du bien. Le but est de rendre possible leur réinstallation en cas de dysfonctionnement. Le rapport préconise également de lever les obstacles précis en matière de réparation, tels que les difficultés de remplacement de la batterie pour les téléphones portables. Il recommande de réaliser une étude destinée à identifier les bons leviers pour interdire les pratiques logicielles qui bloquent le fonctionnement d’un appareil. Des pratiques qui le rendent souvent irréparable. Mieux informer le consommateur. Le rapport insiste sur l’importance de l’information donnée aux consommateurs. Ceux-ci pointent tout particulièrement l’importance d’intégrer les critères relatifs à la pérennité des logiciels d’un bien, dans le futur indice de réparabilité européen. Enfin, le rapport recommande largement l’adoption au niveau européen de la majorité des propositions. Une adoption qui pourrait se faire dans le cadre du Pacte Vert pour l’Europe et des travaux de révision de la directive éco-conception.},
+	language = {fr},
+	urldate = {2022-07-21},
+	author = {Castellazzi and Moatti and Flury-Hérard and Schwob},
+	month = feb,
+	year = {2021},
+	file = {Snapshot:/home/eda/Zotero/storage/VBN3HKUX/280293-obsolescence-logicielle.html:text/html},
+}
+
+@phdthesis{jeanne_guien_obsolescences_nodate,
+	title = {Obsolescences : {Philosophie} des techniques et histoire économique à l'épreuve de la réduction de la durée de vie des objets},
+	author = {Jeanne Guien},
+}
+
+@book{laurence_allard_ecologies_2022,
+	title = {Ecologies du smartphone – {Le} {Bord} de l'{Eau}},
+	url = {https://www.editionsbdl.com/produit/ecologies-du-smartphone/},
+	urldate = {2022-07-21},
+	publisher = {Le bord de l'eau},
+	author = {Laurence Allard and Alexandre Monnin and Nicolas Nova},
+	year = {2022},
+	file = {Ecologies du smartphone – Le Bord de l'Eau:/home/eda/Zotero/storage/D2BH3ZWM/ecologies-du-smartphone.html:text/html},
+}
+
+@inproceedings{valk_pluriverse_2021,
+	title = {A pluriverse of local worlds: {A} review of {Computing} within {Limits} related terminology and practices},
+	shorttitle = {A pluriverse of local worlds},
+	url = {https://limits.pubpub.org/pub/jkrofglk/release/1},
+	doi = {10.21428/bf6fb269.1e37d8be},
+	abstract = {Green capitalism is shaping public discourse on how to best deal with the climate crisis, yet doesn’t challenge the ‘business as usual’ of free market capitalism that caused the crisis in the first place. Small scale practices challenging ’business as usual’ aren’t part of public discourse because they are small scale, less visible, often hard to access, easily appropriated by and seemingly unable to compete with the powerful lobby of large corporations. With Big Tech having an increasingly negative impact on the environment, and simultaneously shaping the discourse on how to best tackle the climate crisis, it is important to give voice and visibility to these alternatives. There is a rich diversity of practices and views on how network infrastructures’ impact could be lowered. This study aims to make them visible through a mapping of the different terms currently in circulation used by communities of practice, with the aim of teasing out the diverse thinking informing the infrastructures that are developed, maintained and repaired. The mapping will be based on a reviewof relevant literature and the results from a survey conducted on Mastodon, an open source decentralized social network with a user base that includes many developers and activists working on sustainability and social justice in relation to computing. The mapping aims to celebrate differences and also show what common ground this pluriverse of small scale community practices share.},
+	language = {en},
+	urldate = {2022-07-21},
+	booktitle = {Computing within {Limits}},
+	publisher = {LIMITS},
+	author = {Valk, Marloes de},
+	month = jun,
+	year = {2021},
+	file = {Full Text PDF:/home/eda/Zotero/storage/FPK9REN8/Valk - 2021 - A pluriverse of local worlds A review of Computin.pdf:application/pdf},
+}
+
+
+@article{guien_heuristique_2019-1,
+	title = {Une heuristique de la panne ?},
+	copyright = {All rights reserved},
+	issn = {0248-6016},
+	url = {https://journals.openedition.org/tc/12557},
+	abstract = {Durant les années 2010, se développe en France un débat public sur l’« obsolescence programmée », une expression fortement contestée. Au gré des campagnes associatives, publications médiatiques et initiatives politiques, se multiplient les injonctions à définir, exemplifier, prouver l’obsolescence programmée. En guise de réponse, les enquêtes autour de pannes d’appareils, leurs causes et leur réparation se multiplient. Étudiant ces discours et les topoi qu’ils mettent en circulation, on montrera qu’ils développent ce que l’on propose d’appeler une heuristique de la panne, dont on exposera aussi les limites. En effet, à la faveur de cette focalisation sur la panne des appareils, beaucoup d’objets sont évacués du débat et de la réflexion sur la durabilité. De plus, dans la mesure où l’obsolescence programmée est comprise comme une « arnaque », un vice caché révélé par l’enquête, les initiatives politiques favorisent la promotion d’une meilleure « information du consommateur », laissant aveuglément au marché le soin de rétablir l’équilibre entre offres jetable et durable.},
+	language = {fr},
+	urldate = {2022-07-21},
+	journal = {Techniques \& Culture. Revue semestrielle d’anthropologie des techniques},
+	author = {Guien, Jeanne},
+	month = dec,
+	year = {2019},
+	note = {Publisher: Les Éditions de l'EHESS},
+	keywords = {consommation, débat public, durabilité des produits, médias, obsolescence programmée, réparation},
+	file = {Full Text PDF:/home/eda/Zotero/storage/VN6D5ZYU/Guien - 2019 - Une heuristique de la panne .pdf:application/pdf},
+}
+
+@article{sandborn_software_2008,
+	title = {Software {Obsolescence}: {Complicating} the {Part} and {Technology} {Obsolescence} {Management} {Problem}},
+	volume = {30},
+	url = {http://escml.umd.edu/Papers/IEEE_SoftwareObs.pdf},
+	doi = {10.1109/TCAPT.2007.910918},
+	abstract = {Not Available},
+	journal = {Components and Packaging Technologies, IEEE Transactions on},
+	author = {Sandborn, Peter},
+	month = jan,
+	year = {2008},
+	pages = {886--888},
+	file = {Full Text PDF:/home/eda/Zotero/storage/3JXDQUDJ/Sandborn - 2008 - Editorial Software Obsolescence—Complicating the P.pdf:application/pdf},
+}
+
+@book{xu_lizhi_machine_2015,
+	title = {La machine est ton seigneur et ton maître},
+	url = {https://agone.org/livres/la-machine-est-ton-seigneur-et-ton-maitre},
+	urldate = {2022-07-21},
+	publisher = {Agone},
+	author = {{Xu Lizhi} and {Jenny Chan} and {Yang}},
+	year = {2015},
+}
+
+@book{antonio_a_casilli_en_2019,
+	title = {En attendant les robots - {Enquête} sur le travail du clic},
+	url = {https://www.seuil.com/ouvrage/en-attendant-les-robots-antonio-a-casilli/9782021401882},
+	urldate = {2022-07-21},
+	publisher = {Editions Seuil},
+	author = {Antonio A. Casilli},
+	year = {2019},
+	file = {En attendant les robots , Antonio A. C... | Editions Seuil:/home/eda/Zotero/storage/PHDQI42R/9782021401882.html:text/html},
+}

obs-en.tex

+%% twocolumn : Two column layout.
+%% hf: enable header and footer.
+\documentclass[
+% twocolumn,
+% hf,
+]{ceurart}
+
+%% One can fix some overfulls
+\sloppy
+
+%%
+%% Minted listings support 
+%% Need pygment <http://pygments.org/> <http://pypi.python.org/pypi/Pygments>
+\usepackage{listings}
+%% auto break lines
+\lstset{breaklines=true}
+
+%%
+%% end of the preamble, start of the body of the document source.
+\begin{document}
+
+%%
+%% Rights management information.
+%% CC-BY is default license.
+\copyrightyear{2023}
+\copyrightclause{Use permitted under Creative Commons License Attribution Share Alike 4.0
+  International (CC BY SA 4.0).}
+
+%%
+%% This command is for the conference information
+\conference{ICT4S: Symposium on the irreproducible science,
+  June 07--11, 2022, Woodstock, NY}
+
+%%
+%% The "title" command
+\title{Software obsolescence}
+
+\tnotemark[1]
+\tnotetext[1]{You can use this document as the template for preparing your  publication. We recommend using the latest version of the ceurart style.}
+
+%%
+%% The "author" command and its associated commands are used to define
+%% the authors and their affiliations.
+\author[1]{Edlira Nano}[%
+orcid=0000-0002-0877-7063,
+email=eda@mutu.net,
+url=https://eda.mutu.net,
+]
+\cormark[1]
+\fnmark[1]
+\address[1]{Equipe limites numeriques, Université Lyon 1}
+
+%% Footnotes
+\cortext[1]{Corresponding author.}
+\fntext[1]{These authors contributed equally.}
+%%
+%% The abstract is a short summary of the work to be presented in the
+%% article.
+\begin{abstract}
+Within the framework of a reflection on the reduction of the
+ecological impact of digital technology, this thesis project aims at
+understanding, analyzing and dissecting the mechanisms of software
+obsolescence, as well as its impact and its intertwining with the
+obsolescence of digital tools in general. The study will first focus
+on the classical editors dominating the software market. Then, in a
+second step, it will focus on alternative editors, communities or
+initiatives that aim directly or indirectly to divert, minimize,
+reduce or counter this software obsolescence.
+
+We will focus on two use cases: systems and software for smartphones
+and online digital services.
+
+Finally, our digital heritage will be a problematic that this thesis
+will take into account and will try to treat all along.
+  
+\end{abstract}
+
+%%
+%% Keywords. The author(s) should pick words that accurately describe
+%% the work being presented. Separate the keywords with commas.
+\begin{keywords}
+  LaTeX class \sep
+  paper template \sep
+  paper formatting \sep
+  CEUR-WS
+\end{keywords}
+
+%%
+%% This command processes the author and affiliation and title
+%% information and builds the first part of the formatted document.
+\maketitle
+
+\section{Study framework}
+The 2021 parliamentary report on the subject,
+\cite{Castellazzi_obsolescence_2021}, defines software obsolescence as
+a special case of technical obsolescence, which is the loss of use
+value resulting from a technical evolution, characterized by the
+unavailability or the malfunctioning of a software. This report
+advocates longer update guarantees and assured backward compatibility
+on the part of software suppliers. Software obsolescence has also been
+defined in the Anglo-Saxon literature from the point of view of
+managing the obsolescence of information systems in an industrial and
+professional context (see \cite{sandborn_software_2008} or
+\cite{bartels_software_2012}).
+
+However, we believe that few studies focus on the mechanisms at play
+upstream of the technical observations of obsolescence, those relating
+to the socio-economic, political and technical history of the
+evolution of digital tools, their influence in the design and
+democratization of these tools, in our dominant uses, their societal
+place today, and their future in the context of an ecological crisis
+that society as a whole must now manage. These mechanisms shape at the
+same time the design of the software, the design of the terminals that
+these software will put in our hands, the design of the
+infrastructures and industries necessary for this use, but also and
+especially the place that they occupy and will occupy in our future
+lives and living environment. 
+
+This last point presents a paradox in our opinion: in a world where
+man's environmental footprint has become an urgent climatic problem to
+manage, with an important and proven impact of the digital sector, we
+note however that digital services and tools take an increasingly
+important place in our daily uses (smart-phones, computers,
+teleworking, connected objects), in our cities (smart-citys and
+connected territories). But also digital technology is systematically
+presented as one of the first means to implement to manage complex
+problems (in each institution, public service or company a solution
+based on big data, AI or other algorithm is now presented to us as a
+priority). In an increasingly digitalized world, how will we be able
+to change our uses, reduce the material and immaterial impact of this
+digital technology, but also manage the legacy of these
+infrastructures, industries and wastes that cannot change, evolve or
+disappear overnight? How are we going to manage the obsolescence of a
+digital technology implemented in every corner of our living
+environment?
+
+It is in this framework of reflection that this thesis project will
+try to fit. We will aim at understanding, analyzing and dissecting
+some of the mechanisms at stake in software obsolescence, software
+being the algorithmic base of our digital tools, and the impact of
+this algorithmic obsolescence on the general obsolescence (material,
+industrial, infra-structural, social, human) of these digital tools.
+
+To circumscribe the work, we think it would be relevant to focus on
+the following two use cases: smart-phones and online digital services.
+
+\subsection{Smartphone operational systems and applications}
+
+Smartphones have become one of the most preponderant objects in our
+digital usage. During this study we will focus on the two dominant
+software ecosystems of smartphones: Google Android, composed of the
+Android operating system and applications from the Google Play Store,
+and Apple iOS (system and applications). We may have to look at some
+applications in particular, to reflect more precisely some
+preponderant uses (messaging applications, social networking
+applications, games ...).
+
+Unlike the personal computer that dominated digital uses before their
+arrival, smart-phones present a rapid hardware and software
+development that has left no room for standardization and
+normalization of practices between manufacturers, designers and
+developers. The world of smartphones consequently presents a strong
+technical obsolescence, and an imbrication of the software
+obsolescence with the hardware one, which is important and
+enlightening to study in the framework of this thesis. 
+
+Moreover, the object of the smartphone and its uses over time present
+a strong implication of technical, social, economic and political
+factors (such as marketing, advertising, changes in signal
+transmission technologies, the rapid evolution of the economic offer,
+social pressures linked to the uses of the object), which influence
+its uses and its obsolescence
+
+\subsection{Online digital application services}
+
+Online digital application services, also called "in the cloud", have
+invaded our daily personal and professional uses during the last 10
+years, and in particular in these last years of Covid
+pandemic. Telecommuting, online office and entertainment services
+(Google drive and similar, Youtube, Netflix), social networks,
+connected objects (including smart-phones, but also home automation
+objects), public services more and more dematerialized, all are
+becoming ubiquitous in our daily uses. 
+
+The same is true in our cities and living areas, where we are seeing
+an increasing number of smart-city and connected territory projects,
+connected seaports, connected buildings, filled with sensors, video
+surveillance systems, biometric algorithms (object recognition,
+(recognition of objects, cars, human behavior), intelligent sensors
+for managing public spaces (garbage cans, streetlights, connected
+parking lots), intelligent counting systems (pedestrian flows, cyclist
+flows, air quality sensors, weather sensors).
+
+These services, which have this common feature of being "in the cloud"
+and need to be connected to the Internet to function, have another
+common feature: they all produce what we will call mass data
+obsolescence. Streaming services offer us video or audio streams that
+are downloaded locally from a server, to be consumed and discarded
+immediately. Video surveillance networks produce video streams that
+are recorded continuously and of which only a small part are or will
+be used for police purposes, they will mostly be unconsumed and
+destroyed within a legal timeframe of a few days or weeks (in France
+it is maximum one month). All social networks and their continuous
+data flow are not intended to produce durable data, their effective
+life span must be counted in hours. The data produced by smart-city
+systems (sensors, metrics) are permanently captured, for a much rarer
+and debatable effective use, and are only used in the long term for
+statistics from time to time, or to feed new algorithms based on
+artificial intelligence, needing a lot of data, algorithms that will
+be proposed again for use in public or private space, and will in turn
+generate a new form of obsolescence.
+
+The particularity of these services is therefore the continuous
+production of data that they generate, and the ephemeral quality,
+almost disposable in the short term, of these data. These services all
+have a physical reality: they need an infrastructure to exist,
+datacenters for the servers that will offer them, cable networks and
+antennas to carry the information and data collected, and the final
+form, the terminals, which capture or return the data (cameras,
+smart-phones, connected street lamps, augmented garbage cans
+etc.). All these material objects are subject to obsolescence in their
+turn. And once again, the interweaving of software obsolescence, that
+of the algorithms under the hood of these objects and services, and
+hardware obsolescence, seems to us to be closely linked here.
+
+There is another case that seems interesting to study, but that it
+would surely be too ambitious to study in the framework of this
+thesis. It is the case of video games, on personal computers, on
+smart-phones or via consoles, online or offline. We think that this
+use of digital technology, which is becoming more and more important,
+with very high rates of hardware and software renewal, can be
+enlightening from the point of view of the interaction between
+software obsolescence and hardware obsolescence.
+
+\section{A historical study of software obsolescence}
+
+In the first part of the thesis, we want to look at the parallel
+history of computing and software obsolescence. We want to start this
+study from the birth of computing, from the theories that allowed the
+development of the first machines (Turing machine) and the first
+theoretical software (Lovelace-Babbage's analytical machine), through
+the birth of the first physical computers in the form of calculators,
+and then through the birth of the personal computer, which marked the
+beginning of the democratization of digital technology, accompanied by
+the birth of the first operating systems and software. Then, with the
+arrival of the Internet, we wish to study the birth of the current
+digital infrastructures (datacenters, cable networks, antennas,
+satellites) constituting a new use of the digital today, the online
+one, the one that inserts itself in each object and usual corner of
+our environment, which makes it much less visible, and yet omnipresent.
+
+This dive into the history of computing and the software that
+accompanies it, will be done under the prism of software obsolescence,
+and hardware when the two seem closely linked. In the manner of Jeanne
+Guien and her works around obsolescence in general, and obsolescence
+linked to the smart-phone in particular (see her thesis
+\cite{jeanne_guien_obsolescences_nodate} or the book from her thesis
+\cite{jeanne_guien_consumerisme_2021}, and her article on the
+heuristic of failure \cite{guien_heuristique_2019-1}), we will try to
+see the influence of economic, social and political factors on
+software obsolescence. In particular the place of advertising and
+marketing, of growth policies without consideration of natural limits,
+of the development of cognitive algorithms and commercial practices
+influencing our social behaviors and unconscious uses, of the
+preponderant place of technological solutionism in societal problems,
+until the arrival of the works highlighting the negative impact of
+digital technology in the current ecological crisis.
+
+Another social aspect of our historical study will consider the links
+between software obsolescence and the new digital workers: the work in
+the factories that manufacture smartphones (for example, Foxconn in
+China), the work of subcontracted developers, as well as the so-called
+"click workers" (see \cite{antonio_a_casilli_en_2019}). These new
+forms of work are part of obsolescence due to the accelerated renewal
+of hardware, the non-management of digital waste, the increased need
+or injunction to develop applications, the need to moderate the flow
+of content or data constantly produced. But they are also an indicator
+of obsolescence above all human and social, because they violate
+fundamental human rights and seriously deteriorate their living and
+working conditions.
+
+\section{Quantitative and qualitative study of smartphone usage}
+
+The quantitative usage study will be based on both Google Android and
+Apple iOS ecosystems. It will use data from the two respective
+application stores. We may have to look at other indicative data, like
+the article \cite{tamar_makov_is_2021} which also scans the statistics
+of known smartphone repair sites (iFixIt in this case).
+
+The quantitative study will be done through participative workshops,
+questionnaires and case studies of uses in families or in
+companies. We will try to understand the mechanisms of digital usage,
+and in particular of services or software, which lead to a material
+renewal, to a feeling of obsolescence, induced or forced, or to a
+change of behavior or perception towards the considered tool.
+
+We would like to carry out this same study on alternative practices
+that aim directly or indirectly at reducing this software
+obsolescence. We are thinking in particular of the communities of free
+smartphone systems: LineageOs, MicroG, /e/solutions, the free
+application store F-Droid, alternative decentralized and peer-to-peer
+online digital services such as Mastodon, Peertube, the peer-to-peer
+protocol IPFS, the decentralized and federated protocol
+ActivityPub. By investigating both the designers and users of these
+alternative systems, we hope to see why and how these practices aim to
+escape the dominant system, and how they attempt to minimize or solve
+the problem of software and digital obsolescence. We hope to draw from
+this study a panorama of these attempts and uses at the level of
+obsolescence precisely (in the line of the article
+\cite{valk_pluriverse_2021} by Maroes de Valk which looks at
+alternative practices of a digital that takes into account the limits,
+or \cite{laurence_allard_ecologies_2022} which looks at the study
+of self-managed citizen networks of wifi Mesh in Detroit (chapter
+7)).
+
+These alternative solutions range from minimizing the effects leading
+to obsolescence, to repairing the damage caused by it, but also to the
+total escape or the fight in different forms against it. We believe
+that these alternative uses, in addition to the dominant uses studied,
+can shed light on some of the technical, social and political levers
+at play in the currently possible solutions towards a less obsolete
+digital world, or a world with less digital impact.
+
+\section{The legacy of digital obsolescence}
+Finally, we would like to keep in mind the cultural and material
+heritage of the digital world throughout this study. For in any case,
+from the perspective of reducing our ecological digital impact, or
+from the much more pessimistic perspective of a digital world that
+continues to spread without significant limits, we will continue to
+have to manage waste, obsolete infrastructures, industries,
+territories and workers undergoing ecological, cultural, social and
+economic change. This legacy, which the authors call "negative
+commons" in the book "Héritage et fermeture: une écologie du
+démantèlement" (Héritage and closure: an ecology of dismantling)
+(\cite{emmanuel_bonnet_heritage_2021}), is something we must learn
+to identify, analyze and manage collectively as we make future changes
+in a world in the midst of an ecological crisis. 
+
+As far as possible, the software and digital obsolescence studied in
+this thesis, will try to take into account also its impact and its
+links with this legacy and these negative commons. 
+
+
+\section{Acknowledgments}
+
+Identification of funding sources and other support, and thanks to
+individuals and groups that assisted in the research and the
+preparation of the work should be included in an acknowledgment
+section, which is placed just before the reference section in your
+document.
+
+This section has a special environment:
+\begin{lstlisting}
+\begin{acknowledgments}
+  These are different acknowledgments.
+\end{acknowledgments}
+\end{lstlisting}
+so that the information contained therein can be more easily collected
+during the article metadata extraction phase, and to ensure
+consistency in the spelling of the section heading.
+
+Authors should not prepare this section as a numbered or unnumbered
+\verb|\section|; please use the ``\verb|acknowledgments|'' environment.
+
+\section{Appendices}
+
+Start the appendix with the ``\verb|\appendix|'' command:
+\begin{lstlisting}
+\appendix
+\end{lstlisting}
+and note that in the appendix, sections are lettered, not
+numbered. 
+
+%%
+%% The acknowledgments section is defined using the "acknowledgments" environment
+%% (and NOT an unnumbered section). This ensures the proper
+%% identification of the section in the article metadata, and the
+%% consistent spelling of the heading.
+\begin{acknowledgments}
+  Thanks to the developers of ACM consolidated LaTeX styles
+  \url{https://github.com/borisveytsman/acmart} and to the developers
+  of Elsevier updated \LaTeX{} templates
+  \url{https://www.ctan.org/tex-archive/macros/latex/contrib/els-cas-templates}.  
+\end{acknowledgments}
+
+%%
+%% Define the bibliography file to be used
+\bibliography{obs-en}
+
+%%
+%% If your work has an appendix, this is the place to put it.
+\appendix
+
+\section{Online Resources}
+
+The sources for the ceur-art style are available via
+\begin{itemize}
+\item \href{https://github.com/yamadharma/ceurart}{GitHub},
+% \item \href{https://www.overleaf.com/project/5e76702c4acae70001d3bc87}{Overleaf},
+\item
+  \href{https://www.overleaf.com/latex/templates/template-for-submissions-to-ceur-workshop-proceedings-ceur-ws-dot-org/pkfscdkgkhcq}{Overleaf
+    template}.
+\end{itemize}
+
+\end{document}
+
+%%
+%% End of file