Add new project from OKF network

[okf-network-site]

Dear human,

Here's a new entry for your approval. 🎉

Merge the pull request to accept it, or close it to send it away.

❤️ Your friend Staticman 💪

---

Field	Content
name	CnkwebB
description	# Glossary of Fields

Google Issue Tracker provides a set of default fields that are available in all
issues. Additional
custom fields may be available on a per-component
basis.

The following table shows the default fields provided by Issue Tracker:

Field	Description
Archived	Indicates whether the issue has been archived.
Assignee	User to which this issue is assigned.
Blocked By	IDs of issues that block this issue.
Blocking	IDs of issues that this issue blocks.
CC	List of users or groups who are interested in the issue, but are not assignees, reporters or verifiers.
Collaborators	List of users that are actively working on an issue.
Component	Component that contains the issue.
Created	Date and time at which the issue was created.
Description	A detailed description of the issue including steps to reproduce it (if applicable). This field might already be partially populated for you if description text is provided by the default or the selected template. You can also check the Markdown option to write the description as Markdown text.
Status Update	The "current state" of an issue. On high traffic issues, teams can use this to provide a canonical "answer" about what is going on. Learn More
Dupe Count	Number of duplicates reported for the issue.
Duplicate Of	ID of the issue that this issue duplicates.
Found In	Version of the software where the issue was found.
ID	Unique numerical issue ID.
In Prod	Indicates whether the issue occurs in production.
Last Modified	Date and time at which the issue was last modified.
Priority	Priority of the issue.
Reporter	User who reported the issue.
Severity	Severity of the issue.
Staffing	Users or future roles (placeholders) who are planning to contribute to the issue.
Status	Status of the issue (for example, New , Assigned , or Fixed).
Targeted To	Version of the software where the issue should be resolved.
Type	Type of issue (for example, Bug , Feature Request or Process).
Verified In	Version of the software where the issue was verified as resolved.
Verifier	User who verified the resolution of the issue.
Resolved	Date and time at which the issue was resolved.
Verified	Date and time at which the issue was verified.
Vote count	Number of times users have voted for the issue (e.g. by starring it).
Estimated Effort	Estimated Effort in story points, dev days, or t-shirt sizes (configured by component administrators)
Start Date	Planned start date.
End Date	Planned end date.
Risk	Risk to meeting the planned End Date.
Commitment Level	Planned level of work completion.
organisation_email	bartascnk@gmail.com
organisation_website	Cnkweb
country	PL
languages	Poland
link	https://docs.x.com/llms.txt
date	1776805047