All Projects → piccalil-li → Cube Css Issue Tracker

piccalil-li / Cube Css Issue Tracker

This is the issue and discussion tracker for CUBE CSS.

Projects that are alternatives of or similar to Cube Css Issue Tracker

Mysapadventures
A quick methodology on testing / hacking SAP Applications for n00bz and bug bounty hunters
Stars: ✭ 164 (+429.03%)
Mutual labels:  methodology
adage
Data and code related to the paper "ADAGE-Based Integration of Publicly Available Pseudomonas aeruginosa..." Jie Tan, et al · mSystems · 2016
Stars: ✭ 61 (+96.77%)
Mutual labels:  methodology
Innersourcepatterns
Proven approaches that can guide you through applying open source best practices within your organization
Stars: ✭ 473 (+1425.81%)
Mutual labels:  methodology
Kb
A minimalist command line knowledge base manager
Stars: ✭ 2,789 (+8896.77%)
Mutual labels:  methodology
shared-latent-space
Shared Latent Space VAE's
Stars: ✭ 15 (-51.61%)
Mutual labels:  methodology
tenet
A practical starting point for designing and building large-scale web frontends.
Stars: ✭ 14 (-54.84%)
Mutual labels:  methodology
Devopsfactors
The DevOps Factors
Stars: ✭ 134 (+332.26%)
Mutual labels:  methodology
Assessment Mindset
Security Mindmap that could be useful for the infosec community when doing pentest, bug bounty or red-team assessments.
Stars: ✭ 608 (+1861.29%)
Mutual labels:  methodology
stats
📈 Useful notes and personal collections on statistics.
Stars: ✭ 16 (-48.39%)
Mutual labels:  methodology
Guide
Aiming to be a fully transparent company. All information about source{d} and what it's like to work here.
Stars: ✭ 268 (+764.52%)
Mutual labels:  methodology
UpCss
Методология для модульной организации CSS.
Stars: ✭ 18 (-41.94%)
Mutual labels:  methodology
bug-bounty
My personal bug bounty toolkit.
Stars: ✭ 127 (+309.68%)
Mutual labels:  methodology
snorkeling
Extracting biomedical relationships from literature with Snorkel 🏊
Stars: ✭ 56 (+80.65%)
Mutual labels:  methodology
Aboutsecurity
A list of payload and bypass lists for penetration testing and red team infrastructure build.
Stars: ✭ 166 (+435.48%)
Mutual labels:  methodology
Dostoevsky Pentest Notes
Notes for taking the OSCP in 2097. Read in book form on GitBook
Stars: ✭ 495 (+1496.77%)
Mutual labels:  methodology
Osvvm
OSVVM Utility Library: AlertLogPkg, CoveragePkg, RandomPkg, ScoreboardGenericPkg, MemoryPkg, TbUtilPkg, TranscriptPkg, ...
Stars: ✭ 140 (+351.61%)
Mutual labels:  methodology
documentation
🍰 Architectural design methodology for Frontend projects
Stars: ✭ 359 (+1058.06%)
Mutual labels:  methodology
Designcourse
Course materials for "Research Design in Political Science"
Stars: ✭ 12 (-61.29%)
Mutual labels:  methodology
Payloadsallthethings
A list of useful payloads and bypass for Web Application Security and Pentest/CTF
Stars: ✭ 32,909 (+106058.06%)
Mutual labels:  methodology
lean-bem
A leaner, cleaner & prettier adaptation of BEM
Stars: ✭ 12 (-61.29%)
Mutual labels:  methodology

CUBE CSS

CUBE CSS logo

This is the issue and discussion tracker for CUBE CSS.

The content isn’t open source, but the discourse certainly should be, so please, feel free to open up an issue to start a discussion. Please, first search for your issue to make sure we don’t have duplicate conversations though 🙏

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, 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 [email protected]. 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, version 1.4, available at http://contributor-covenant.org/version/1/4

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].