Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sensitive HW project topics (ethics, safety, ...) #147

Open
Tracked by #146
hoijui opened this issue Oct 17, 2024 · 0 comments
Open
Tracked by #146

Sensitive HW project topics (ethics, safety, ...) #147

hoijui opened this issue Oct 17, 2024 · 0 comments
Labels
enhancement New feature or request workable Ready to be worked on

Comments

@hoijui
Copy link
Collaborator

hoijui commented Oct 17, 2024

(This came in as a question by Katarzyna Puchała from the NGI Search ethics evaluation)

Think of HW projects allowing to build weapons, otherwise dangerous objects, contraception apparatus, medical tools, containing religious imagery, and so on.
While we do not deem it our responsibility nor mandate to decide what is appropriate and what not, as authors of software infrastructure, it certainly would be diligent to allow users of our software to make such decisions. More specifically, I would se it as optimal if anyone running an indexer would be able to choose which kinds of potentially sensitive topics to exclude. To achieve that, each project needs to be annotated with tags representing touched topics. Though one could also argue that it would be more diligent to additionally also supply the negative of this list: untouched such topics, as it allows for more topics to be added later on, without the project falsely stipulating that it does not touch these topics, even if it does not get updated after the new categories are added.

In short:
If there are no objections. I will regard this issue as a request for implementing two fields in the ontology that may list touched and respectively untouched sensitive topics, out of a predefined list of such topics (i.e. tags).

This can then be used by anyone down the line, be it indexers, front-ends or end-users, to filter as desired.
The project maintainers have the duty to fill-in these fields.

NOTE: Front-ends/Indexers might want to implement additional mechanisms fro flagging projects as inappropriate, independent of this mechanism.

@hoijui hoijui added enhancement New feature or request workable Ready to be worked on labels Oct 17, 2024
@hoijui hoijui mentioned this issue Oct 17, 2024
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request workable Ready to be worked on
Projects
None yet
Development

No branches or pull requests

1 participant