Data objects for login.
Changes for 0.03 - 2024-03-22T14:37:07+01:00
- API CHANGE: Add 'valid_from' and 'valid_to' parameters to Data::Login.
- API CHANGE: Add 'valid_from' and 'valid_to' parameters to Data::Login::Role. 'active' parameter will be removed in future. And 'valid_from' will be required in future.
- Add DESCRIPTION section to Data::Login doc.
Perl.social Code of Conduct
I've posted this on reddit and wanted a discussion here too for those not on reddit for whatever reason:
reddit.com/r/perl/comments/1bl…
The gist though is that I've gotten another request for a proper CoC/ToS that would be acceptable to the community since i've been negligent in doing so. I've decided that a slightly modified version from the mastodon CoC might be a good starting point and I'll post that content in a reply to this so that it doesn't flood everyone's feeds with a giant wall of text immediately.
BrowseEntry like widget without button
Changes for 0.02
- added -command option updated and corrected documentation
Utilities related to mineral supplements
Changes for 0.012 - 2024-03-22
- Add mg-mg-malate, mg-mg-malate-trihydrate.
General purpose command option wrapper
Changes for v0.99.1 - 2024-03-22T09:31:18Z
- Make tabstop configurable in -Mutil::filter module.
Implementation of various techniques used in data compression.
Changes for 0.03 - 2024-03-22
- ADDITIONS
- CHANGES
Asynchronous HTTP Request and Promise
Changes for v0.5.1 - 2024-03-27T16:53:48Z
- Minor correction of undefined variable in HTTP::Promise
- Correcting minor bug in _read_body() in HTTP::Promise
Fork Based Promise with Asynchronous Execution, Async, Await and Shared Data
Changes for v0.4.10 - 2024-03-22T16:50:25Z
A real Try Catch Block Implementation Using Perl Filter
Changes for v1.3.6 - 2024-03-22T15:05:39Z
- Corrected Makefile to require experimental module for testing.
Generic Module to inherit from
Changes for v0.35.2 - 2024-03-22T14:13:24Z
- Minor corrections to unit tests
find, build and install the hmmer3 tools
Changes for 0.02 - 2024-03-21T23:16:26-06:00
- fixed documentation errors
Fork Based Promise with Asynchronous Execution, Async, Await and Shared Data
Changes for v0.4.9 - 2024-03-22T14:04:36Z
- Minor correction of untrapped condition
A SQL Database object abstraction class
Changes for v1.2.1 - 2024-03-22T13:52:05Z
- Correction of unit test to better handle non-existing DBD modules
A SQL Database object abstraction class
Changes for v1.2.0 - 2024-03-22T12:12:11Z
- Improvement to DB::Object::Query, DB::Object::Postgres::Query and DB::Object::Query::Element
find, build and install the hmmer3 tools
Changes for 0.01 - 2024-03-21T21:25:40-06:00
- initial commit
Actually Portable Perl
Changes for v0.5.0 - 2023-12-01
- Revert `full` and `small` targets with cosmo 3.0.2 Base `full` and `small` (with vista) targets off of perl 5.36.3
Tab expand and unexpand with ANSI sequence
Changes for 1.04 - 2024-03-22T01:32:12Z
- make configure method can set tabstop
Build hash based classes.
Changes for 0.013 - 2024-03-21T17:41:14-07:00
- Documentation Fixes
Plugin to use when building Sah-SchemaBundle-* distribution
Changes for 0.034 - 2024-02-13
- Rename module/dist Dist-Zilla-Plugin-Sah-Schema{s,Bundle}.
Build hash based classes.
Changes for 0.012 - 2024-03-21T13:55:43-07:00
- Do not taint $@, $!, $? or $^E when checking for Class::XSAccessor.
- Ignore __DIE__ handlers when checking for Class::XSAccessor.
A utility class for building table layouts in a PDF::Builder (or PDF::API2) object.
A utility class for building table layouts in a PDF::Builder (or PDF::API2) object.
type definitions for Coordinates
Changes for 0.12 - 2024-03-21T16:23:34-04:00
- BUGFIX
Easily format content into PDF/PS/DVI with LaTeX templates.
Changes for 0.03 - 2024-03-21
- Fixed LaTeX program paths detection where e.g. xelatex was not tested to actually exist on disk and being an executable with right permissions.
Dispatch by HTTP Methods
Changes for 0.104 - 2024-03-21
- Support for HTTP::Request::Common < 6.21
weave together a Pod document from an outline
Changes for 4.020 - 2024-03-21T13:58:33-04:00
- do not allow Moose::Util::TypeConstraints to turn warnings back on after they were turned off by experimental.pm! (thanks, Karen Etheridge)
Check at build/release time if modules are out of date
Changes for 0.060 - 2024-03-21T17:39:03Z
- fix experimental warnings on earlier perls
Plack search application.
Changes for 0.04 - 2024-03-21T14:13:15+01:00
- Add missing 'image_height' parameter description in doc.
- Add 'image_radius' parameter.
- Add 'name' attribute to search field.
Implementation of various techniques used in data compression.
Changes for 0.02 - 2024-03-21
- ADDITIONS
- CHANGES
ANSI sequence aware column command
Changes for 1.4101 - 2024-03-21T07:50:10Z
- make man page accurate
data pack for Business::ISBN
Changes for 20240321.001 - 2024-03-21T07:16:25Z
- Data update for 2024-03-21
SPVM Language
Changes for 0.989091 - 2023-03-21
- Incompatible Changes
- New Features
- New Features
Provides United States of America holidays
Changes for 0.0201 - 2024-03-20T21:16:45Z
- Drop circular dependents.
translation support module for greple
Changes for 0.3101 - 2024-03-21T03:43:52Z
- fix bug in xlate.el
- include sdif output in README
Adapter for USA holidays
Changes for 0.0101 - 2024-03-20T20:35:19Z
- Remove the accidental circular dependency from the dist.ini file.
Implementation of various techniques used in data compression.
Changes for 0.01 - 2024-03-21
- Initial release.
Use Data::Dump::SkipObjects to stringify some objects
Changes for 0.001 - 2020-06-19
- First release.
Ryan Voots
in reply to Ryan Voots • •COC/TOS
Borrowing many things from the Mastodon CoC as a astarting point (github.com/mastodon/mastodon/b…).
I am removing a few things from it, not because I don't think they're good ideas or anything but also because I want to limit the scope
of the initial discussion and the amount of work for myself as I'm still currently the only moderator but once the community there gets larger
or it changes that I'm not the only one maintaining things, we will hold another discussion about everything.
I've changed a few things also, specifically to add stronger language that any moderators
MUST document why an action was taken. This doesn't necessarily mean that I believe
that those reasons must be immediately given to an affected user, but that they must
be available when requested. Specifically I'm thinking of not informing in the context
of bots, spam, illegal or otherwise legally actionable content (i.e. something that's going to get me a subpeona or court case).
Other proposed ideas:
1) Some kind of regular discussion, maybe annually? on ToS/CoC type things
1a) The idea being that we require a regular discussion of anything that's
happened over the last time period to avoid it being possible for something
happening being "swept under the rug" or "falling through the cracks" because
it didn't get the proper time given to it previously. How this should be done
I have no good recommendations for, likely creating a group on perl.social to
host the conversation each time?
2) ?
Contributor Covenant Code of Conduct
Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
Privacy
I reserve the right to collect email or other identifiable contact information,
and it will never be shared to an outside party without consent except in the case
of it being required by some legal process. If at any time perl.social becomes
a larger organization and there is a desire to change this, I will require the
removal of all such information until explicit consent is given again with such
a new policy. I don't know if there's a way I can make this legally enforcable
but I see it as something I do not own and therefore cannot ethically give it to
another party in that kind of scenario.
Both perl.social and I are located in the USA, and therefore I believe are not
directly subject to the GDPR, but as there are similar laws in other jurisdictions
even within the USA, and I basically agree with the ideas involved, I will do
whatever is reasonable feasible to follow them.
Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
and learning from the experience
community
Examples of unacceptable behavior include:
and sexual attention or advances of any kind. Consenting adults in private
should be acceptable.
without their explicit permission
professional setting
Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders 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, and MUST communicate reasons for moderation
decisions.
Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[hello@joinmastodon.org](mailto:hello@joinmastodon.org).
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
1. Correction
Community Impact: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.
2. Warning
Community Impact: A violation through a single incident or series of
actions.
Consequence: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.
3. Temporary Ban
Community Impact: A serious violation of community standards, including
sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the
community.
Attribution
This Code of Conduct is adapted from the Contributor Covenant,
version 2.1, available at
contributor-covenant.org/versi…contributor-covenant.org/versi….
And from the Mastodon code of conduct available at github.com/mastodon/mastodon/b…
Community Impact Guidelines were inspired by
Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at
contributor-covenant.org/faqcontributor-covenant.org/faq. Translations are available at
contributor-covenant.org/trans…contributor-covenant.org/trans….