The Common Lispers list aims to be factual and accurate.
Please report any factual errors and other inaccuracies and they will be promptly fixed.
An attempt has been made to lay out the tenets according to pleasant groupings and orderings, but this is not intended to be semantically significant.
The Common Lispers list aims to be factual and accurate.
The Common Lispers list aims to unify the Common Lisp community.
To accomplish this, it is necessary for the list to remain as apolitical as possible.1
The Common Lispers list aims to include as many Common Lisp open-source contributors as possible, regardless of their characteristics.
The Common Lispers list aims to make it easy to discover any and all Common Lisp open-source contributors.
Besides documenting their existence, we shall make it easy to find their Common Lisp open-source contributions.
The Common Lispers list aims to enhance the status of all Common Lisp open-source contributors.
Nobody should have to toil in obscurity and then have their worthwhile contributions be overlooked.
The Common Lispers list expresses gratitude by featuring each contributor's best contributions.
The Common Lispers list aims to be as useful and usable as possible for its stated purposes.
The Common Lispers list aims to avoid undue burdens that would impede the achievement of its stated purposes.
The Common Lispers list aims to include everyone regardless of their political leanings and affiliations.
The Common Lispers list aims to remain upright, resolute, whole and undivided regardless of political pressures.
The Common Lispers list aims to create a fair environment in which everyone is treated equally.
This is accomplished by formulating these public policies and then rigorously applying them.
When the policies are unclear, consistency with the list's historical precedents shall be considered.
The Common Lispers list aims to be a trusted resource that can be depended on.
The Common Lispers list aims to be predictable and stable in its developments.
Developments include technical enhancements and changes to list membership.
The Common Lispers list aims to be transparent in its developments.
Developments include technical enhancements and changes to list membership.
The Common Lispers list aims to be a portal linking to Common Lispers and their contributions.
The Common Lispers list aims to link to publicly accessible resources that anyone can immediately review.
The Common Lispers list aims to be easy for anyone to independently audit.
All content featured in the list is assembled from publicly available sources.
The Common Lispers list aims to be fully accessible to anyone at any time.
Useful and accurate information will generally not be removed from the list.
The Common Lispers list aims to evolve and adapt to best serve the needs of the Common Lisp community.
The Common Lispers list aims to clearly identify who is ultimately responsible for the proper functioning of the list.
The Common Lispers list aims to allow derivative works to serve this or other communities in similar or different ways.
The above tenets already substantially reflect current practices and policies, but have not yet been fully integrated into the rest of this policies page. Thank you for your patience.
Only persons will be added to the list. This excludes teams, companies, organizations, etc. Of course, individual members of such groups may be eligible.
To be eligible for inclusion in the list, the candidate must have contributed something (anything) to the open-source Common Lisp ecosystem and have some kind of Common Lisp related web presence that they personally control.3
Proprietary contributions have no weight, since they cannot easily be reviewed by everyone.
Please open an issue if any eligible persons have not yet been added to the list, whether that is you or someone else.
Please note that nobody has received, nor will receive, any type of notification as a direct result of them getting added to the list, as that could certainly be seen as "spamming" or otherwise undesirable.4
To help ensure that the list is as comprehensive as possible, and to avoid politicizing the list, and to avoid dividing the community, and to avoid contentious discussions about who should or should not be included, nobody will be excluded from the list on the basis of alleged or actual reprehensible behavior.
This implies that inclusion in the list merely documents existence, and does not in any way imply affiliation or endorsement. One may simply block people they don't want to see.
Additionally, nobody will be excluded from the list on the basis of: age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.5
Addenda aside, all information presented on the Common Lispers list must be strongly related to open-source Common Lisp.
Addenda don't have to have anything to do with Common Lisp, or Lisp, or even programming.
For now, social media account information does not have to have anything to do with open-source Common Lisp. See below for details.
The list is composed of entries. Each entry describes one person, and is composed of the following fields, which must all be composed of links only (for ensuring a minimum of concreteness and verifiability):
The Full name field is the person's full name as it is publicly disclosed by the person themselves to the Common Lisp community, and as is generally known to the Common Lisp community. This does not usually include any middle name, unless that person very consistently uses their middle name everywhere or unless an ambiguity would otherwise arise. If the full name is not publicly known, then just a nickname is fine.
The Nickname field is the person's informal name as generally known within the Common Lisp community.
When a person is first added to the list, they may or may not be auto-assigned a nickname or linkable nickname, depending on the level of certainty or lack thereof about their preferred nickname in a Common Lisp context. Generally, a linkable nickname will be auto-assigned if at least 2 of their accounts have the same nickname, or substantially the same nickname when accounting for avoidance of nickname collisions among other users on the same service.
Linkable nicknames are auto-assigned only when certainty is high, as changing a linkable nickname breaks all links referring to that nickname. Unlinkable nicknames are much less prejudicious if incorrect, since changing them breaks no links.
List members with no nickname or an unlinkable nickname are encouraged to open an issue stating their preferred nickname, and they will then be assigned that linkable nickname. So as to avoid confusion and preserve the list's integrity, they must have a history of using that nickname in a Common Lisp context.
The Website or Blog field is the most general entry point to that person's website or blog that is specifically about open-source Common Lisp.
The label for this field must be
Blog. The name of the website or blog itself is never used as label, due to fairness concerns. This way, websites or blogs with better or longer names don't get an advantage, and we avoid bloating up the list and getting a lot of variation in Website or Blog label length.
If the blog supports a tag filtering option and a tag
common-lisp, then the link must point to that tag. Else, if the
lisptag is supported, then that tag must be used. This applies even if most or all of the blog's posts use these tags anyway. This is to ensure that the link remains focused on Common Lisp even if multiple posts unrelated to Common Lisp are added in the future. If the link points to one of these tags rather than the blog itself, then this is reflected in the label with a mention such as (lisp tag).
On occasion, a common-lisp or lisp tag may be ignored if it is believed that the tag is broken in some way, such as if posts are not consistently appropriately tagged.
The Highlights field highlights up to 2 of that person's most notable open-source Common Lisp related accomplishments.
This field is limited to 2 items. This confers several benefits:
We avoid devolving into a laundry list of accomplishments that would bloat up the list.
For many people, only one or two of their contributions really stand out compared to their other ones anyway, so listing any further would confer diminishing returns, thereby lowering the overall quality of the list.
It is up to the individual list members to properly organize their Common Lisp web presence (that the list conveniently points to) to properly feature their further contributions.
We avoid thorny questions about the relative notability of accomplishments, and also avoid large variations in the number of items, whether fair or unfair. Furthermore, list members for which the best contributions were incorrectly identified are less penalized than otherwise, relative to list members for which the best contributions were perfectly well identified.
We create a more welcoming environment for beginners, who might otherwise be intimidated with the prospect of being included in a list where many people have a long list of several notable accomplishments when they themselves have only one or two contributions to offer. We also avoid digging up several barely usable contributions from less experienced contributors.
We incite more casual users of the list to review the contributions of more persons overall, since there are less contributions to review per person.
The list is more stable, which means those who track its changes (such as by "watching" the repo on GitHub) experience a better signal to noise ratio.
Books for which the full text is not freely legally available online (without any access restrictions such as a "loginwall") are not eligible, since their contents cannot be readily reviewed by everyone.
List members who believe their best contributions have not been correctly identified are encouraged to open an issue to rectify the situation.
Due to various factors, some list members may have been auto-assigned less than 2 highlights, in which case they are encouraged to submit further contributions to better take advantage of the 2 slots they are entitled to. For instance, if one particular contribution is believed to completely dwarf that list member's other contributions, then only that contribution may be auto-assigned, but said list member is then encouraged to submit another contribution that they wish to promote.
Rarely, some list members may not be auto-assigned any highlights if the editor is particularly confused about which of their contributions are the most notable. This might arise for example if the contributions are vastly outside the fields of expertise or interest of the editor, or if many of said contributions are in a foreign language. So-afflicted list members are greatly encouraged to submit their best contributions to rectify the situation.
The Addenda fields link to more general information about the person, and don't even have to have anything to do with programming.
The Portal field is the most general entrypoint to the person's web presence. This field is omitted if it would point to the exact same location as the Website or Blog field, as the user should not have to waste their time browsing duplicate links.
The Keybase field points to the person's keybase account, which is generally a good repository of verified general information about that person.
Keybase accounts that don't link to at least one of the social media accounts featured in the list are not eligible.
The BDFL of this list is Jean-Philippe Paradis.
Updates to the list will be driven by the policies, which are themselves driven by the BDFL's vision, which is itself driven by (what is believed to be) the needs of the open-source Common Lisp community, as notably reflected in community feedback.
For the foreseeable future, so as to ensure consistency and accountability, the BDFL will be the only editor of the list.
Only list members who no longer meet the minimum requirements for inclusion will be removed from the list.
Per the tenets of Unity, Diversity, Discoverability, Dignity, Usability, Practicality, Apoliticality, Integrity, Consistency, Reliability, Predictability and Availability, the BDFL cannot simply remove from the list6 any eligible persons who object to be included.
Those who cannot bear to see themselves being included in the Common Lispers list can solve the problem on their end by blocking themselves.7
Simply removing objectors would violate the tenet of Unity.
There would be a division between those who accept to be included in the list and those who do not.
While it is clear that many divisions will remain within the Common Lisp community,
representing them front and center in the list would greatly impede its stated purposes.
Simply removing objectors would violate the tenet of Diversity.
Some eligible persons would be absent from the list due to their characteristic of not wanting to be in it.
Simply removing objectors would violate the tenet of Discoverability.
Objectors and their best contributions and other information would be harder to find than otherwise.
Simply removing objectors would violate the tenet of Dignity.
It would be especially sad if some people were deprived of the benefits of being included
due to having requested to be removed from the list entirely due to political pressure.
Anyone who thinks that aggregating their willingly publicly disclosed information
constitutes affront or prejudice to their dignity may want to reconsider their life choices.
Simply removing objectors would violate the tenet of Usability.
Removing many objectors would make the list much less useful for everyone.
Simply removing objectors would violate the tenet of Practicality.
Removing many objectors would constitute an existential threat to the stated purposes of the list.
Simply removing objectors would violate the tenet of Apoliticality.
It is hard to imagine that anyone would want to be removed from the list for apolitical reasons.
Simply removing objectors would violate the tenet of Integrity.
Dividing the list by giving in to political pressures is antithetical to the stated purposes of the list.
It would also be unwise to give list members undue political leverage to compromise the list
by allowing them to threaten to demand to be taken off the list if certain demands are not met.
Simply removing objectors would violate the tenet of Consistency.
Removing objectors would engender many inconsistencies in who's included or absent.
Removing certain people from the list for political reasons would be inequitable.
Removing objectors would engender many discrepancies between
the stated purposes of the list and the actual state of the list.
Simply removing objectors would violate the tenet of Reliability.
Allowing the state of the list to fluctuate according to politics would make it much less dependable.
Simply removing objectors would violate the tenet of Predictability.
It would obviously be harder to predict who is going to be included in the list or absent.
This would be especially annoying when trying to find specific people using the search feature.
Simply removing objectors would violate the tenet of Availability.
Removing useful and accurate information from the list makes it harder to find.
There is not much point in the list remaining available if it is stripped of much valuable information.
Note that due to the Forkability, simply removing objectors would potentially cripple this instance of the list and thus incite a potentially much less scrupulous person to upload a (probably much less trustworthy) version of the list that restores all the information. Nothing good would come of this.
1. especially given the current political status of the BDFL within the community
2. This further incentivises the BDFL to be responsive, and provides a safeguard should he become unavailable in some way.
3. Deceased persons are not eligible for inclusion, since they cannot have
some kind of Common Lisp related web presence that they personally control.
4. Of course, those who requested themselves to be added to the list will receive a notification...
5. List copy-pasted from Contributor Covenant 1.4.
6. nor omit to include in the list