Version 15.0.0 (#17)

* fix(#7): apply 670e4e1

Note that commit hash refers to old repository used before amssive migration and hystory cleanup

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* fix(#7): apply c4dc0b6

Note that commit hash refers to old repository used before massive migration and history cleanup

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* Prepare for v15.0.0

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* feat(#15): add dry-run / doctor script

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* [#10] Better management of GNU/Linux and macOS on same scripts

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: checksums display

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: support of both GNU/Linux and macOS and config

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: URL check

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* fix: polluting symbols in outputs

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: remove useless code

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: remove polluting symbols in find primitive outputs

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: force output in JSON for feed shell scripts

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: better management of GNU/Linux and macOS primitives for hash feature

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: remove typo

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* refactor: web pages details

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: update headers for SPDX templates

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc(#14): add double license

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* chore(#1): image in README

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: add CITATION file

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: add CODE files

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: add DCO

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* doc: add SECURITY file

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

* Prepare version 15.0.0

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

---------

Signed-off-by: Pierre-Yves Lapersonne <dev@pylapersonne.info>

CHANGELOG.md

@@ -1,5 +1,21 @@
 # CHANGELOG
 
+## v15.0.0
+
+### Bugs
+
+- [#7](https://github.com/pylapp/Tips-tools/issues/7) Pick hard-coded fixes and improve versions
+
+### Changes
+
+- [#15](https://github.com/pylapp/Tips-tools/issues/15) Add dry-run script 
+- [#10](https://github.com/pylapp/Tips-tools/issues/10) Deal with GNU/Linux and macOS primitives
+- [#14](https://github.com/pylapp/Tips-tools/issues/14) Add CC-BY license for generated and ODS file
+- Improve check of URL in CSV files
+- Update sources headers
+- Refactor file tree
+- Add DCO, codes of conduct and conflict, security and citation files
+
 ## v14.3.3
 
 _This version is dedicated to macOS users, and is based on v14.3.2_

CITATION.cff

@@ -0,0 +1,44 @@
+cff-version: 1.2.0
+title: >-
+  tips'n'tools: Project to compile references of publications, devices, SoC and tools for technical watch.
+  Provides CLI tool, web page, Ruby server and kind of PWA to read data and search inside corpora.
+message: >-
+  If you use this software, please cite it using the
+  metadata from this file.
+type: software
+authors:
+  - affiliation: pylapersonne.info
+    given-names: Pierre-Yves
+    family-names: Lapersonne
+repository-code: 'https://github.com/pylapp/Tips-tools'
+url: 'https://github.com/pylapp/Tips-tools'
+abstract: >-
+  Tips'n'tools is a project which has the aim of making searches faster and improving technical watch.
+  Indeed, sometimes you need to share usefull web links and cool libraries to your colleagues, 
+  but which platform to use?
+
+  Your company's inner social network? Lost time if you move from your job. 
+  A public social media? Lost time if this medium is closed.
+  Fill your web browser's bookmarks? Yeah, got stolen or reinitialized your computer and you are done.
+
+  Tips'n'tools allows you to fill a spreadsheet (.ods file) and then export its sheets to CSV files. Then you can:
+  use the main Shell script to make queries so as to find a thing you have listed, 
+  build a little Progressive Web App which allows you to make queries with a more user-friendly UI, 
+  update a global web page if you cannot use the web app, run the server-side feed script, written in Ruby, so as to expose an HTTP API to make the queries from everywhere.
+
+  This tool has been developed so as to help people to store and get useful data for their jobs.
+
+  The project is under permissive non-copyleft open source MIT license for sources, and CC-BY or generated content.
+keywords:
+  - watch
+  - data
+  - tools
+  - publications
+  - devices
+  - SoC
+  - Shell
+  - Ruby
+  - PWA
+license: MIT
+version: 15.0.0
+date-released: '2023-09-25'

CODEOWNERS

@@ -1,4 +1,5 @@
 # Just to help to find people able to deal with pull requests
 
-/utils/core/ @pylapp
-/utils/web/ @pylapp
+project @pylapp
+project/utils/core/ @pylapp
+project/utils/web/ @pylapp

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at opensource.contact@orange.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+

CODE_OF_CONFLICT.md

@@ -0,0 +1,21 @@
+Code of Conflict
+----------------
+
+The tips'n'tools development effort is a kind of personal process just 
+like open source (or not) software projects. Your code and ideas
+behind it will be carefully reviewed, maybe resulting in critique and
+criticism. The review will sometimes require improvements to the
+code before it can be included in the project. Know that this happens
+because everyone involved wants to see cool and useful features for
+the project.
+
+If however, anyone feels personally abused, threatened, or otherwise
+uncomfortable due to this process, that is not acceptable. If so,
+please contact core maintainer at
+<dev@pylapersonne.info>, or the individual members,
+or create an issue, 
+and they will work to resolve the issue to the best of their ability. 
+
+As a reviewer of code, please strive to keep things civil and focused on
+the technical issues involved. We are all humans, and frustrations can
+be high on both sides of the process.

DCO.txt

@@ -0,0 +1,37 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.