Primer commit

This commit is contained in:
Iván Ruvalcaba 2024-04-12 21:40:50 -06:00
commit e811205e82
11 changed files with 609 additions and 0 deletions

34
.editorconfig Normal file
View File

@ -0,0 +1,34 @@
# editorconfig.org
# https://github.com/jokeyrhyme/standard-editorconfig
# top-most EditorConfig file
root = true
# defaults
[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true
# Markdown
[*.md]
eclint_indent_style = unset
indent_size = 4
indent_style = space
# double whitespace at end of line
# denotes a line break in Markdown
trim_trailing_whitespace = false
# TOML
# https://github.com/toml-lang/toml/tree/master/examples
[*.toml]
indent_size = 2
indent_style = space
# YAML
# http://yaml.org/spec/1.2/2009-07-21/spec.html#id2576668
[*.{yaml,yml}]
indent_size = 2
indent_style = space

82
.gitattributes vendored Normal file
View File

@ -0,0 +1,82 @@
# Common settings that generally should always be used with your language specific settings
# Auto detect text files and perform LF normalization
# https://www.davidlaing.com/2012/09/19/customise-your-gitattributes-to-become-a-git-ninja/
* text=auto
#
# The above will handle all files NOT found below
#
# Documents
*.bibtex text diff=bibtex
*.doc diff=astextplain
*.DOC diff=astextplain
*.docx diff=astextplain
*.DOCX diff=astextplain
*.dot diff=astextplain
*.DOT diff=astextplain
*.pdf diff=astextplain
*.PDF diff=astextplain
*.rtf diff=astextplain
*.RTF diff=astextplain
*.md text
*.tex text diff=tex
*.adoc text
*.textile text
*.mustache text
*.csv text
*.tab text
*.tsv text
*.txt text
*.sql text
# Graphics
*.png binary
*.jpg binary
*.jpeg binary
*.gif binary
*.tif binary
*.tiff binary
*.ico binary
# SVG treated as an asset (binary) by default.
*.svg text
# If you want to treat it as binary,
# use the following line instead.
# *.svg binary
*.eps binary
# Scripts
*.bash text eol=lf
*.fish text eol=lf
*.sh text eol=lf
# These are explicitly windows files and should use crlf
*.bat text eol=crlf
*.cmd text eol=crlf
*.ps1 text eol=crlf
# Serialisation
*.json text
*.toml text
*.xml text
*.yaml text
*.yml text
# Archives
*.7z binary
*.gz binary
*.tar binary
*.tgz binary
*.zip binary
# Text files where line endings should be preserved
*.patch -text
#
# Exclude files from exporting
#
.gitattributes export-ignore
.gitignore export-ignore
.gitkeep export-ignore

191
.gitignore vendored Normal file
View File

@ -0,0 +1,191 @@
# Created by https://www.toptal.com/developers/gitignore/api/windows,linux,macos,emacs,vim,sublimetext,notepadpp
# Edit at https://www.toptal.com/developers/gitignore?templates=windows,linux,macos,emacs,vim,sublimetext,notepadpp
### Emacs ###
# -*- mode: gitignore; -*-
*~
\#*\#
/.emacs.desktop
/.emacs.desktop.lock
*.elc
auto-save-list
tramp
.\#*
# Org-mode
.org-id-locations
*_archive
# flymake-mode
*_flymake.*
# eshell files
/eshell/history
/eshell/lastdir
# elpa packages
/elpa/
# reftex files
*.rel
# AUCTeX auto folder
/auto/
# cask packages
.cask/
dist/
# Flycheck
flycheck_*.el
# server auth directory
/server/
# projectiles files
.projectile
# directory configuration
.dir-locals.el
# network security
/network-security.data
### Linux ###
# temporary files which can be created if a process still has a handle open of a deleted file
.fuse_hidden*
# KDE directory preferences
.directory
# Linux trash folder which might appear on any partition or disk
.Trash-*
# .nfs files are created when an open file is removed but is still being accessed
.nfs*
### macOS ###
# General
.DS_Store
.AppleDouble
.LSOverride
# Icon must end with two \r
Icon
# Thumbnails
._*
# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent
# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk
### NotepadPP ###
# Notepad++ backups #
*.bak
### SublimeText ###
# Cache files for Sublime Text
*.tmlanguage.cache
*.tmPreferences.cache
*.stTheme.cache
# Workspace files are user-specific
*.sublime-workspace
# Project files should be checked into the repository, unless a significant
# proportion of contributors will probably not be using Sublime Text
# *.sublime-project
# SFTP configuration file
sftp-config.json
sftp-config-alt*.json
# Package control specific files
Package Control.last-run
Package Control.ca-list
Package Control.ca-bundle
Package Control.system-ca-bundle
Package Control.cache/
Package Control.ca-certs/
Package Control.merged-ca-bundle
Package Control.user-ca-bundle
oscrypto-ca-bundle.crt
bh_unicode_properties.cache
# Sublime-github package stores a github token in this file
# https://packagecontrol.io/packages/sublime-github
GitHub.sublime-settings
### Vim ###
# Swap
[._]*.s[a-v][a-z]
!*.svg # comment out if you don't need vector files
[._]*.sw[a-p]
[._]s[a-rt-v][a-z]
[._]ss[a-gi-z]
[._]sw[a-p]
# Session
Session.vim
Sessionx.vim
# Temporary
.netrwhist
# Auto-generated tag files
tags
# Persistent undo
[._]*.un~
### Windows ###
# Windows thumbnail cache files
Thumbs.db
Thumbs.db:encryptable
ehthumbs.db
ehthumbs_vista.db
# Dump file
*.stackdump
# Folder config file
[Dd]esktop.ini
# Recycle Bin used on file shares
$RECYCLE.BIN/
# Windows Installer files
*.cab
*.msi
*.msix
*.msm
*.msp
# Windows shortcuts
*.lnk
# End of https://www.toptal.com/developers/gitignore/api/windows,linux,macos,emacs,vim,sublimetext,notepadpp
### Vim ###
# scratch.vim
.scratch.vim
### mdBook ###
book/
### ghostwriter ###
*.backup

View File

@ -0,0 +1,23 @@
---
title: Inventario de actividades pendientes
date: 2024-04-07
last_update:
table: |
| Detalles | Tarea o actividad | Estimación |
|:---------|:------------------|:-----------|
| | | |
| | | |
| | | |
comment: En el inventario de actividades se enumeran todas las tareas que debes llevar a cabo, que habrás identificado durante la planificación, una fase necesaria para determinar cómo puedes lograr tus objetivos (por ejemplo, al principio de un proyecto) y gestionar las interrupciones.
---
# Inventario de actividades pendientes
**Nombre:** Iván Ruvalcaba.
## Actividades pendientes
| Detalles | Tarea o actividad | Estimación |
| :------- | :---------------- | :---------- |
| | | |
| | | |
| | | |

138
LICENSE Normal file
View File

@ -0,0 +1,138 @@
Copyright (C) 2020, 2021, 2022, 2023, 2024 Iván Ruvalcaba <ivanruvalcaba[at]disroot[dot]org>
- El código que hace funcionar este blog se encuentra bajo una licencia
FSF All Permissive:
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without any warranty.
<https://spdx.org/licenses/FSFAP.html>.
- A no ser que se indique explícitamente lo contrario, el contenido del
sitio se encuentra bajo una licencia Creative Commons Zero v1.0 Universal (CC0-1.0).
Creative Commons Legal Code
CC0 1.0 Universal
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator
and subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for
the purpose of contributing to a commons of creative, cultural and
scientific works ("Commons") that the public can reliably and without fear
of later claims of infringement build upon, modify, incorporate in other
works, reuse and redistribute as freely as possible in any form whatsoever
and for any purposes, including without limitation commercial purposes.
These owners may contribute to the Commons to promote the ideal of a free
culture and the further production of creative, cultural and scientific
works, or to gain reputation or greater distribution for their Work in
part through the use and efforts of others.
For these and/or other purposes and motivations, and without any
expectation of additional consideration or compensation, the person
associating CC0 with a Work (the "Affirmer"), to the extent that he or she
is an owner of Copyright and Related Rights in the Work, voluntarily
elects to apply CC0 to the Work and publicly distribute the Work under its
terms, with knowledge of his or her Copyright and Related Rights in the
Work and the meaning and intended legal effect of CC0 on those rights.
1. Copyright and Related Rights. A Work made available under CC0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not
limited to, the following:
i. the right to reproduce, adapt, distribute, perform, display,
communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or
likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work,
subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data
in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the
European Parliament and of the Council of 11 March 1996 on the legal
protection of databases, and under any national implementation
thereof, including any amended or successor version of such
directive); and
vii. other similar, equivalent or corresponding rights throughout the
world based on applicable law or treaty, and any national
implementations thereof.
2. Waiver. To the greatest extent permitted by, but not in contravention
of, applicable law, Affirmer hereby overtly, fully, permanently,
irrevocably and unconditionally waives, abandons, and surrenders all of
Affirmer's Copyright and Related Rights and associated claims and causes
of action, whether now known or unknown (including existing as well as
future claims and causes of action), in the Work (i) in all territories
worldwide, (ii) for the maximum duration provided by applicable law or
treaty (including future time extensions), (iii) in any current or future
medium and for any number of copies, and (iv) for any purpose whatsoever,
including without limitation commercial, advertising or promotional
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
member of the public at large and to the detriment of Affirmer's heirs and
successors, fully intending that such Waiver shall not be subject to
revocation, rescission, cancellation, termination, or any other legal or
equitable action to disrupt the quiet enjoyment of the Work by the public
as contemplated by Affirmer's express Statement of Purpose.
3. Public License Fallback. Should any part of the Waiver for any reason
be judged legally invalid or ineffective under applicable law, then the
Waiver shall be preserved to the maximum extent permitted taking into
account Affirmer's express Statement of Purpose. In addition, to the
extent the Waiver is so judged Affirmer hereby grants to each affected
person a royalty-free, non transferable, non sublicensable, non exclusive,
irrevocable and unconditional license to exercise Affirmer's Copyright and
Related Rights in the Work (i) in all territories worldwide, (ii) for the
maximum duration provided by applicable law or treaty (including future
time extensions), (iii) in any current or future medium and for any number
of copies, and (iv) for any purpose whatsoever, including without
limitation commercial, advertising or promotional purposes (the
"License"). The License shall be deemed effective as of the date CC0 was
applied by Affirmer to the Work. Should any part of the License for any
reason be judged legally invalid or ineffective under applicable law, such
partial invalidity or ineffectiveness shall not invalidate the remainder
of the License, and in such case Affirmer hereby affirms that he or she
will not (i) exercise any of his or her remaining Copyright and Related
Rights in the Work or (ii) assert any associated claims and causes of
action with respect to the Work, in either case contrary to Affirmer's
express Statement of Purpose.
4. Limitations and Disclaimers.
a. No trademark or patent rights held by Affirmer are waived, abandoned,
surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or
warranties of any kind concerning the Work, express, implied,
statutory or otherwise, including without limitation warranties of
title, merchantability, fitness for a particular purpose, non
infringement, or the absence of latent or other defects, accuracy, or
the present or absence of errors, whether or not discoverable, all to
the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons
that may apply to the Work or any use thereof, including without
limitation any person's Copyright and Related Rights in the Work.
Further, Affirmer disclaims responsibility for obtaining any necessary
consents, permissions or other rights required for any use of the
Work.
d. Affirmer understands and acknowledges that Creative Commons is not a
party to this document and has no duty or obligation with respect to
this CC0 or use of the Work.
<https://creativecommons.org/publicdomain/zero/1.0/legalcode>.

View File

@ -0,0 +1,38 @@
---
title: Lista de tareas
date: 2024-04-07
last_update: 2024-04-07
table: |
| Descripción | Tarea o actividad | Progreso |
|:------------|:------------------|:---------|
| | | |
| | | |
| | | |
comment: Al principio de cada jornada, decide qué tareas del «inventario de actividades» quieres abordar, ordénalas por prioridad y anótalas en la lista de tareas para hoy.
---
# Lista de tareas para hoy
**Nombre:** Iván Ruvalcaba.
**Lugar y fecha:** Naucalpan de Juárez, a 7 de abril, del 2024.
| Descripción | Tarea o actividad | Progreso |
| :----------- | :---------------- | :------- |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
## Imprevisto y urgente
| Descripción | Tarea o actividad | Progreso |
| :----------- | :---------------- | :------- |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |

View File

@ -0,0 +1,21 @@
---
title: Registro de actividades completadas
date: 2024-04-07
last_update:
table: |
| Fecha | Hora | Tipo de actividad | Descripción | Pomodoros completados | Observaciones | Mejoras |
|:----- |:---- |:----------------- |:----------- |:---------------------:|:------------- |:------- |
| | | | | | | |
| | | | | | | |
| | | | | | | |
comment: El objetivo inicial del seguimiento y del registro posterior podría ser, sencillamente, generar un informe con la cantidad de pomodoros completados para cada tarea. En otras palabras, quizá quieras reflejar el esfuerzo que has invertido en completar cada actividad.
---
# Registro de actividades completadas
## Actividades completadas
| Fecha | Hora | Tipo de actividad | Descripción | Pomodoros completados | Observaciones | Mejoras |
| :---- | :--- | :---------------- | :----------- | :-------------------: | :------------ | :------ |
| | | | | | | |
| | | | | | | |
| | | | | | | |

23
book.toml Normal file
View File

@ -0,0 +1,23 @@
[book]
title = "Iván Ruvalcaba's Work Flow"
description = "Anotaciones personales y otras recopilaciones sobre mi flujo de trabajo."
authors = ["Iván Ruvalcaba"]
language = "es"
multilingual = false
src = "src"
[output.html]
git-repository-icon = "fa-code-fork"
git-repository-url = "https://git.disroot.org/ivanruvalcaba/golang_notes"
edit-url-template = "https://git.disroot.org/ivanruvalcaba/golang_notes/_edit/main/{path}"
[output.html.print]
page-break = true
[output.html.search]
limit-results = 15
# Requires mdBook-yml-header
#
# https://github.com/dvogt23/mdbook-yml-header
[preprocessor.yml-header]

18
src/Introduccion.md Normal file
View File

@ -0,0 +1,18 @@
---
title: foo bar…
description: bar
date: 2024-04-05
---
# Introducción
Aquí pretendo documentar mi flujo de trabajo empleado en la utilización de herramientas de software para la redacción de textos. Tales herramientas se listan a continuación:
[foo]: #
- [mdBook][]: Es una herramienta de línea de comandos para la creación de libros «online» a partir de archivos en formato [Markdown][], empleando la especificación [CommonMark][].
- mdfmt
- zola
[mdBook]: https://rust-lang.github.io/mdBook/
[Markdown]: https://rust-lang.github.io/mdBook/format/markdown.html
[CommonMark]: https://commonmark.org/

15
src/SUMMARY.md Normal file
View File

@ -0,0 +1,15 @@
# Índice
[Introducción](./Introduccion.md)
# Herramientas de edición
- [mdBook]()
- [Archivo SUMMARY.md](./mdBook/SUMMARY.md.md)
- [mdfmt]()
- [zola]()
- [git]()
# Markdown
- [CommonMark]()

26
src/mdBook/SUMMARY.md.md Normal file
View File

@ -0,0 +1,26 @@
# Archivo SUMMARY.md
*mdBook* utiliza el archivo **SUMMARY** para determinar qué capítulos incluir, el orden en que deben mostrarse, su jerarquía y dónde se localizan los archivos fuente. Sin este archivo no es posible la creación del libro.
Este archivo Markdown debe tener por nombre `SUMMARY.md`. Su formato es muy riguroso, por lo que se debe seguir la estructura que se describe a continuación, esto es con la finalidad de permitir ser analizando sintácticamente con facilidad. Es probable que cualquier elemento no especificado, ya sea que se trate de un elemento de formato o textual, podría llegar, en el mejor de los casos, a causar un error al intentar crear el libro.
## Estructura
1. **Título**: aunque es opcional, resulta ser una práctica común comenzar con un título, generalmente `# Summary`. Sin embargo, el *parser*[^nota1] ignora esto y el título es omitido.
```md
# Summary
```
[Prefix Chapter -> traducido cómo «Título del capítulo»]: #
2. **Títulos de capítulos**: antes de los capítulos principales del libro, los cuales comunmente irán numerados, se pueden añadir títulos de capítulos sin numeración. Esto es útil para prólogos, introducciones, etc. Sin embargo, existen algunas limitaciones. Los capítulos con prefijo no pueden ser anidados; todos deberían estar en el nivel raíz. Y no puedes agregar prefije los capítulos una vez que haya agregado capítulos numerados.
```md
[A Prefix Chapter](relative/path/to/markdown.md)
- [First Chapter](relative/path/to/markdown2.md)
```
Prefix Chapter - Before the main numbered chapters, prefix chapters can be added that will not be numbered. This is useful for forewords, introductions, etc. There are, however, some constraints. Prefix chapters cannot be nested; they should all be on the root level. And you cannot add prefix chapters once you have added numbered chapters.
[^nota1]: *parser*: analizador sintáctico, analizador de sintaxis.