100 lines
No EOL
3.1 KiB
JSON
100 lines
No EOL
3.1 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "92168b2b-6e46-4548-a7b0-824c862126e3"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T09:00:02+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Who is your BDFL?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-01-11T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:02+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/01\/11\/bdfl",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Most open source projects have a BDFL (Benevolent dictator for life) who makes the ultimate decisions for the project.<\/p>\n\n<p>The ones who spring to mind are Dries, Fabien and Taylor for Drupal, Symfony and Laravel respectively.<\/p>\n\n<p>But what about your codebase?<\/p>\n\n<p>Who is the BDFL for your application?<\/p>\n\n<p>Who decides how features should be implemented or what standards to follow?<\/p>\n\n<p>Who ensures the codebase is consistent regardless of the feature being delivered or the file being read?<\/p>\n\n<p>If you don't have one, you should.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Most open source projects have a BDFL (Benevolent dictator for life) who makes the ultimate decisions for the project.<\/p>\n\n<p>The ones who spring to mind are Dries, Fabien and Taylor for Drupal, Symfony and Laravel respectively.<\/p>\n\n<p>But what about your codebase?<\/p>\n\n<p>Who is the BDFL for your application?<\/p>\n\n<p>Who decides how features should be implemented or what standards to follow?<\/p>\n\n<p>Who ensures the codebase is consistent regardless of the feature being delivered or the file being read?<\/p>\n\n<p>If you don't have one, you should.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-05-11T09:00:02+00:00",
|
|
"guid": null,
|
|
"hash": "222b248251326ba2fe44041d0e2f159a",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |