# wiki Published articles for wiki. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Documentation as a Repository: Publishing a Wiki.js Site from Reviewed Markdown DevFeed: [Documentation as a Repository: Publishing a Wiki.js Site from Reviewed Markdown]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-01T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [Documentation](), [Markdown](), [pull-requests](), [Git](), [Wiki](), [Open Source]() Tags: [architecture](), [ci-cd](), [documentation](), [git](), [markdown](), [open-source](), [pull-request](), [testing](), [wiki]() ### AI overview The article argues that keeping documentation as reviewed Markdown in a repository makes changes visible, reviewable, and enforceable alongside code changes. It presents OpenTaberna's Wiki.js documentation workflow as an example. ### Source excerpt Wiki.js Git storage for docs as code: publish reviewed Markdown and fail a pull request when src/ changes without docs/, checked with git diff. ## Software Engineering Rules Explained Through Stories, Trade-offs, and Decision Records DevFeed: [Software Engineering Rules Explained Through Stories, Trade-offs, and Decision Records]() Original publisher: [Read original article]() Author: Davide Angelocola Published: 2026-07-04T00:00:00Z Content type: article Language: en Sources: [Davide Angelocola]() Topics: [Software Engineering](), [engineering-culture](), [Refactoring](), [Wiki](), [trust]() Tags: [agent](), [architecture](), [engineering](), [markdown](), [repo](), [software-engineering](), [wiki]() ### AI overview The author revisits a list of software engineering rules, retaining principles grounded in personal experience and explaining the reasoning behind them. The article emphasizes documenting trade-offs through mechanisms such as code comments, project wikis, and Architecture Decision Records, including in repositories used by AI-assisted development workflows. ### Source excerpt Once in a while, someone shares an "X rules of software engineering" list and I find myself agreeing with about a third of it. This is my pass through one such list -- keeping what I've actually had to write down somewhere, dropping what I haven't, and rewriting the rest in my own language. Each rule opens with an extract from the story where it was earned. ## GNU Hurd Q2 2026 development updates DevFeed: [GNU Hurd Q2 2026 development updates]() Original publisher: [Read original article]() Published: 2026-07-03T20:32:51Z Content type: news Language: en Sources: [GNU Hurd]() Topics: [Code](), [POSIX](), [SVG](), [GitHub](), [virtio](), [Kernel](), [Wiki]() Tags: [2026](), [code](), [crash](), [cross-compilation](), [posix](), [servers](), [svg](), [virtio](), [wiki]() ### AI overview A quarterly GNU Hurd development update covering a public 9pfs repository with basic file browsing and reading support, additional write support, POSIX-related validation, bug fixes, cross-compilation work, Rust translator development, and planned dynamic device population. ### Source excerpt Hello and welcome to another Qoth! Here's what's been happening in Q2 of 2026! Joshua Branson added a pretty cool svg logo for our ethernet multiplexor. He built that image with Inkscape whilst using a Hurd laptop (Thinkpad 420) running on real iron! The Hurd wiki could certainly use more artwork. Perhaps you have a favorite Hurd translator that you believes needs some artwork! Sergey Bugaev announced his WIP 9pfs (source code), and it has a wiki page! He writes: Some years ago, I experimented with implementing a 9P translator for the Hurd. Hopefully there is no need to tell this list what 9P is :) Besides just browsing files on the few existing servers out there, a potential use case is virtio-9p, to enable shared directory trees between VMs and the host. But that would need someone to implement virtio support in the Hurd. I wanted to complete 9pfs before publishing, but that ultimately didn't happen, so now it's time to turn it over to the community. I now went and made the repository public on GitHub: https://github.com/bugaevc/9pfs What's implemented is basic browsing (readdir, stat), path resolution (dir_lookup), and reading files (io_read). And below that, the whole tracking for nodes, peropens, protids, fids, tags, and 9p RPCs. Improvements are welcome, send patches to this list with [PATCH 9pfs] in the subject. A good starting point would be to continue porting things that I had implemented in the old netfs-based version (see netfs.c) but didn't yet port to the new one. He then got a little more motivated, and he added some write support! Etienne Brateau added validation to msync, so that the Hurd better follows POSIX. Diego Nieto Cid worked on allowing privileged users to set their task priority (nice value). His patches landed in glibc and GNU Mach. He also fixed a tiny bug in our test suite. He fixed an adjtime bug, which is helpful to the OpenNTPD port, and he fixed two more bugs. Paulo Duarte sent a RFC patch series trying to commit Sergey's previous AA ## A wiki from a single Go binary: LeoMoon Wiki-Go DevFeed: [A wiki from a single Go binary: LeoMoon Wiki-Go]() Original publisher: [Read original article]() Author: Jan-Piet Mens Published: 2026-05-04T22:00:00Z Content type: article Language: en Sources: [Jan-Piet Mens]() Topics: [Wiki](), [Go Language](), [Filesystems](), [Markdown](), [Docker](), [REST API](), [Kanban](), [YAML](), [Open Source]() Tags: [docker](), [file-system](), [go](), [jan-piet-mens](), [jpm](), [jpmens](), [kanban](), [markdown](), [open-source](), [rest-api](), [wiki](), [yaml]() ### AI overview This article reviews LeoMoon Wiki-Go, an open-source wiki platform delivered as a single Go binary or Docker image. It stores wiki pages, Kanban boards, and link-management pages as Markdown files in a flat-file directory, with a REST API, web-based settings, user roles, and YAML configuration. ### Source excerpt LeoMoon Wiki-Go calls itself a modern, feature-rich, databaseless, flat-file wiki platform built with Go, and it is all that. Wiki-Go is a single-binary Go program, but there is a docker image for those who want it. I download the binary for my platform and launch it; this creates a data/ directory and its configuration file. If need be I configure a port number for it plus a timezone and the odd other setting and relaunch the binary. The program has all the features I need and more, and what I most appreciate is that I can simply drop Markdown files, images, videos, etc. into a directory to have Wiki-Go serve them. I can also move documents to other pages, so for instance, when I've finished working on the Cascade page, I'll move it into DNS/. The program also boasts an interactive Markdown editor which certainly fulfills all I expect of one, including being able to format text, add links, insert images, etc. In addition to wiki pages, the program supports the creation of Kanban boards and Link management pages, all of which are stored in *.md Markdown files. There is a REST API with examples, which might be interesting to programmatically add comments, say, but if I have access to the server, I copy files into their directories. There's a web-based settings dialog where I can add users and configure roles, but I can also add these to the YAML configuration file manually: users: - username: admin password: $2a$14$V0SkqSKvFPmJMICFqrW6qO9ufQh0befHwHE7uuJZdudK1DcGgPlY. role: admin - username: jp password: $2a$10$KdlXhhVpMiP1QPkggskUQOp4LBZ2JaSADm2ccfyl8JalN10dqmR7W role: viewer groups: - dns - tech This is really a lovely piece of work, and it is open source, and IMO its major features: Markdown in flat files on the file system, which makes it easy for me to synchronize the data directory onto my laptop and use a separate instance of Wiki-Go on that. ## Fibery vs. Notion 2025: not Better, Different DevFeed: [Fibery vs. Notion 2025: not Better, Different]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2025-04-11T07:52:12Z Content type: comparison Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Notion](), [knowledge-management](), [Product Management](), [Wiki](), [Low-Code / Internal Tools]() Tags: [2025](), [automation](), [notion](), [permissions](), [processes](), [product-management](), [productivity](), [saas-tools](), [tools-for-thought](), [visualization](), [vs](), [wiki]() ### AI overview A founder-authored comparison explains that Fibery and Notion serve different use cases rather than one being universally better. It presents Notion as well suited to personal knowledge management, company wikis, knowledge bases, and simple processes, while describing Fibery as better suited to complex processes with deeper hierarchies, relations, permissions, formulas, automations, and advanced visualizations. ### Source excerpt Disclaimer: This post is written by Fibery Founder, so it is inevitably biased (but I tried to be as objective as I can). You came here to find out how 🐉 Fibery is better than 🐼 Notion. Well, it is not. Fibery is different. Notion is a great tool and it works exceptionally well for some use cases, but it fails for others. Let me just quickly answer your main question and then feel free to dig into details later. 🐼 What Notion is great for? Personal knowledge management (PKM) Company wiki and knowledge base Simple (not complex) processes: basic project management, basic CRM, basic candidates tracking, etc. "I've been using Notion for the past few years. It's undoubtedly the most flexible note-taking app on the market. Offering both simplicity and complexity, it caters to a variety of users. Its recent integration with AI and automation further elevates the note-taking experience. Imagine having your own personal Wikipedia, comprehensive databases, calendar, tasks, calculator, and more, all within a single app. This truly makes Notion the best of the best." -- Notion user🐉 What Fibery is great for? Company wiki and knowledge base Complex processes: product management, feedback management, portfolio management, OKR, HR, Vacation tracking, etc. "We use Fibery to manage all our startup processes, from customer discovery over HR until CRM, Project management and documentation. We could replace 27 of our 36 internal tools: Fibery is a rocket for managing all sorts of processes and lets us the freedom to create our own templates and spaces aka processes, if needed." -- Fibery user It can be illustrated like this: Notion and Fibery areas of best applicability Fibery will help you when Notion is just not enough. When you need deep hierarchies and relations, advanced access and permissions control, formulas and automations across these hierarchies, visualization of information in hierarchical timelines and table views, complex charts. In general, Fibery is harder to "get" and ma ## FOSDEM 2025 + Hackathon DevFeed: [FOSDEM 2025 + Hackathon]() Original publisher: [Read original article]() Published: 2025-02-10T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [FOSDEM](), [Hackathon](), [foss](), [Linux](), [Mobile](), [AdventureX 2025](), [Kernel](), [Sailfish OS](), [ui](), [Wiki]() Tags: [2025](), [blog-post](), [fosdem](), [foss](), [hackathon](), [kernel](), [linux](), [mobile](), [os](), [podcast](), [postmarketos](), [ui](), [wiki]() ### AI overview A postmarketOS community report on FOSDEM 2025 describes its Linux mobile stand, related talks, device-support discussions, recordings, a podcast episode, and a post-conference hackathon. ### Source excerpt When so many people involved with postmarketOS and Linux Mobile come together in one place, magic happens. Without even trying to solve problems, we end up finding important solutions to long-term issues as we discuss running mainline Linux on all sorts of devices while walking around in ULB or elsewhere in Brussels, going by public transport or while eating in restaurants. Thanks to everybody who came by, it was amazing! FOSDEM 2025 We had a separate postmarketOS stand with our Linux on Mobile friends (Mobian, Sailfish OS, AsteroidOS, LINMOB.net, MNT) on one side and our friends from CalyxOS on the other. Usually we team up with the rest of the Linux on Mobile crowd, but given that in 2024 we almost ran into serious space issues, we figured it would be safer to request our own stand for 2025. And it was a blast, thanks to everybody who came by and asked us questions and tried out our (sometimes quite crazy) setups. It was especially nice seeing true tiling WM lovers experiencing Sxmo for the first time and feeling right at home! Federico had printed out 150 copies of the leaflet (which were all taken by visitors -- except for the last two which people apparently didn't want to take since these were the last ones). He also printed the entire devices wiki page in DIN A3 format, which proved to be very useful: people ask us if we support a specific device all the time, so every few minutes we could whip out the entire print out and look for that specific device together with the visitor to see if it is in there or not. Regardless, we always got the same reaction: sooo many devices! On Saturday afternoon the FOSS on Mobile Devices devroom took place, with many postmarketOS related talks such as Kernel support for Mobile Linux: The missing 20% by Luca, Sxmo: A mobile UI for hackers by Maarten, postmarketOS: what is it and what's new? by Oliver and many more! For most of them, the video recordings are already up by now. Anjan also gave a talk called Introduction to pmboot ## Nix Weekly Recap: 2024-04-07 DevFeed: [Nix Weekly Recap: 2024-04-07]() Original publisher: [Read original article]() Published: 2024-04-07T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Virtual Private Network](), [Wiki](), [Neovim](), [configuration](), [ssh](), [Garry's Mod](), [GitHub]() Tags: [announcements](), [community](), [github](), [pull-request](), [recap](), [ssh](), [vpn](), [weekly](), [wiki]() ### AI overview A weekly recap of Nix community announcements and activity, covering the official NixOS wiki, sponsorship policy discussions, the Clan toolkit for VPN-connected NixOS machines, Neovim and SSH-related projects, Catppuccin-nix, a Garry's Mod Nix flake, and new packages. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## Default-to-Open: A Principle for High-Performance Organizations DevFeed: [Default-to-Open: A Principle for High-Performance Organizations]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-04-22T06:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [context](), [permission](), [Slack](), [Wiki]() Tags: [culture-employee-happiness-practices-engineering-excellence-organizational-design](), [organization](), [permission](), [slack](), [wiki]() ### AI overview The article presents "default-to-open" as a company principle: communication and information should be openly accessible by default when there is no reason to keep them private. It describes benefits such as easier knowledge discovery, participation in decisions, faster problem surfacing, and reduced risk of decisions happening behind closed doors, while preserving confidentiality for personal or sensitive conversations. ### Source excerpt Default-to-Open: A Principle for High-Performance Organizations Sharing, communicating, and persisting knowledge, information, and decisions is a challenge that most companies have. This challenge may become even bigger in remote-first companies. ## Maximizing Productivity with Obsidian: My Second Brain for Organizing Work Notes DevFeed: [Maximizing Productivity with Obsidian: My Second Brain for Organizing Work Notes]() Original publisher: [Read original article]() Published: 2023-02-24T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Obsidian](), [data](), [Notion](), [Wiki]() Tags: [brain](), [documentation](), [notes](), [obsidian](), [productivity](), [ux](), [wiki](), [work]() ### AI overview The article explains brain dumping and the second-brain method for organizing information, tasks, and notes. It describes using Notion for personal notes and Obsidian for work notes, while noting that the available text ends during the discussion of Obsidian. ### Source excerpt 🧠 Introduction to Second Brains & Brain Dumping As I'm working with data all the time, I'm aware of the importance of keeping it in a safe... ## This month in Mobian: May 2022 DevFeed: [This month in Mobian: May 2022]() Original publisher: [Read original article]() Author: Mobian team Published: 2022-05-31T23:59:59Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Development](), [GitLab](), [ci](), [Debian](), [Kernel](), [systemd](), [Wiki]() Tags: [blog-posts](), [bugs](), [ci](), [configs](), [debian](), [gitlab](), [kernel](), [kernels](), [repositories](), [systemd](), [update](), [wiki]() ### AI overview A May 2022 Mobian development update covers monthly developer meetings, planned repository and developer-wiki moves toward Debian infrastructure, kernel and audio fixes, universal images for PinePhone devices, tow-boot limitations on PineTab, and a PinePhone Keyboard driver change. ### Source excerpt This is the first in a (hopefully) series of short blog posts summarizing what has happened in Mobianland. Given that Mobian integrates much of the ecosystem not developed by us, this report could reiterate many of the things being said somewhere else. Monthly dev meeting Despite being located all over the world (really!), we manage to meet in person once a month. Well, ok, "meet in person" means we conduct a jitsi video call. It is fun seeing all these sleepy faces where half of the people would like to go to bed already, while others wished they could have remained in bed longer. The TL;DR: we will attempt to move over more repositories from gitlab to salsa.debian.org (given gitlabs changes to the CI allowance we get, and in an attempt to align ourselves closer to Debian). In a similar move, the developer's wiki (NOT the user wiki) moves over to the Debian wiki. pondering if systemd-repart and systemd-growfs can maybe replace "growroot" We really should be opening a user-contrib section or something where contributed ports and kernels can live, e.g. for the Nexus 5. Planning stage. OnePlus 6 / Pocophone F1 Audio was broken due to a missing config option on 5.17 kernels, and was fixed by a subsequent update. Thanks to everyone who reported this issue and provided the information allowing us to fix it. Universal Images We have a universal mobian image that boots on the original Pinephone and the Pinephone Pro, however, there are still some bugs to iron out and kernel configs to be adapted. But overall, this looks promising. However, this will require some tool that can adapt configuration settings at runtime, based on the device it is currently running on. Tow-boot We were one of the earliest distributions to move over to tow-boot, and that worked out nearly well. However, there is a little catch: There is no tow-boot for the PineTab yet. So all images post-March 27, will not be able to install a U-boot if you have non installed yet. Help to port tow-boot to the Pin ## January Update: Happy New Gear! DevFeed: [January Update: Happy New Gear!]() Original publisher: [Read original article]() Published: 2021-01-15T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Linux](), [OpenGL](), [USB](), [GPU](), [IRC](), [Website](), [Wiki]() Tags: [community-edition](), [community-update](), [gpu](), [irc](), [linux](), [opengl](), [pinebook-pro](), [pinecil](), [pinecube](), [pinephone](), [pinetime](), [update](), [usb](), [website](), [wiki]() ### AI overview PINE64's January community update covers the final PinePhone community edition, Quartz64 single-board computers, PineTab and Pinebook Pro production, software builds, graphics support, community infrastructure, and PineTime firmware developments. ### Source excerpt Happy New Year everyone! Let us all hope that the difficulties brought about by the COVID-19 virus are now waning and that more aspects of our lives will return to normal soon. We start this year with announcing the last community edition of the PinePhone, an update on the Quartz64 single board computers, and with some good news regarding PineTab and Pinebook Pro production. You can watch a synopsis of this month's community update on Youtube (embedded below) but also on LBRY and Peertube. Stay up-to-date with PINE64 news and make sure to subscribe to this blog (bottom of the webpage), follow PINE64 Telegram News channel as well as our Twitter and Mastodon. I'd like to acknowledge JF, Marek (gamiee), Alex (clover), 33YN2 and PizzaLovingNerd for their contributions to this community update. Thank you. Let's get to it. Note: This image preview protects your privacy. Click to load the video from the Google servers. Link to the video & January Community Update Video Synopsis by PizzaLovingNerd TL:DR New website it up! Chats have been reworked and IRC bridged back up; more work on chat infrastructure soon Thank you to those who've been making documentation for Wiki PinePhone KDE CE slightly delayed but shipping soon; issues shipping to the UK PineTalk podcast starts next month! Hosted by Ezra from Elatronion and Peter from LINMOBnet Pinebook Pro and PineTab LCD panel availability looking better; production to resume after CNY Pinebook Pro OpenMandriva and AOSC Linux builds are now available Pinebook Pro FreeBSD 13 build brinds a lot of functionality to the platform Pinebook Pro alt DP display mode available in Manjaro & coming to other distros. Enables DockingDeck and other USB-C dongles Pinebook Pro to get Panfrost GPU driver with OpenGL 3.0 Quartz64 is the name of our next SBC line Quartz64 model-A detailed spec and availability roadmap PineTime important work done on the bootloader and release of InfiniTime 0.10.0 PineTime InfiniTime fork brings colourful icons, multi ## ROCKPro64 Cluster Move June 5-10 DevFeed: [ROCKPro64 Cluster Move June 5-10]() Original publisher: [Read original article]() Published: 2020-06-05T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Server](), [maintenance](), [IRC](), [Wiki](), [Website]() Tags: [cluster](), [community](), [forum](), [infrastructure](), [irc](), [maintenance](), [pine64](), [rockpro64](), [server](), [website](), [wiki]() ### AI overview PINE64 announces a June 5-10 move of end-user services to the ROCKPro64 cluster. The forum, Wiki, chat bridge, IRC, parts of the support system, installer mirrors, and website may experience downtime, while the store, ticket filing system, and support emails are expected to remain operational. An update reports that the key community infrastructure was moved successfully by June 11, 2020. ### Source excerpt The process of moving our end-user services to the ROCKPro64 cluster will be taking place in the coming days (5-10 June). I am not going to pretend like this is the best time for the move to be taking place, since it is not. Many users are relying on our infrastructure for information and community support, particular now that people are receiving their devices and many more are waiting for their units to ship. But things are what they are, and we have a strict deadline we need to adhere to. In practice, this means that at different times during this move key parts of the infrastructure will be down. This includes: the forum, the Wiki, the chats bridge and IRC, portions of the support system, PINE Installer mirrors as well as this website. It is not possible for me to say with certainty when exactly each of these community-facing services will be moved nor how long it will be down for. Obviously we'll aim to complete the process as quickly and painlessly as possible but unpredictable things can, and likely will, happen. I'll do my best to give you a heads-up when portions of the system are scheduled to go down for maintenance on Twitter and Mastodon. I'll also issue notices in the news section of the forums. Lastly, I'd like to note that the PINE store and ticket filing system, as well as our info and support emails will remain operational though the entire server move. Thank you in advance for your patience. [edit June 11, 2020] All key community based infrastructure has now been moved to the cluster. Moreover, the move went went surprisingly well and without any major hiccup. In the coming weeks and months we'll be adding more services to the cluster. I have already spoken to FireTwoOneNine about writing a short blog post about the cluster, its present utilization and future applications in the project. Lastly, I'd like to thank all those who offered advise and were directly involved in this project. ## Announcing Stack Overflow for Teams DevFeed: [Announcing Stack Overflow for Teams]() Original publisher: [Read original article]() Author: Joel Spolsky Published: 2018-05-03T12:58:25Z Content type: release Language: en Sources: [Joel Spolsky]() Topics: [Stack Overflow](), [Development](), [Wiki](), [IRC]() Tags: [company](), [development](), [documentation](), [irc](), [news](), [product](), [stack-overflow](), [teams](), [wiki]() ### AI overview The article announces Stack Overflow for Teams, a paid private Q&A service for teams, companies, and organizations. It is presented as a way to capture searchable institutional knowledge through questions and answers. ### Source excerpt New product: Stack Overflow for Teams lets you direct questions to members of your own team, company, or organization. Read more "Announcing Stack Overflow for Teams" ## PostgreSQL Index bloat under a microscope DevFeed: [PostgreSQL Index bloat under a microscope]() Original publisher: [Read original article]() Author: Peter Geoghegan (noreply@blogger.com) Published: 2017-07-19T05:43:00Z Content type: article Language: en Sources: [Peter Geoghegan's blog]() Topics: [PostgreSQL](), [Database]() Tags: [index](), [indexes](), [internals](), [nbtree](), [pageinspect](), [postgresql](), [query](), [wiki]() ### AI overview This technical article presents a PostgreSQL query that summarizes the keyspace of a target B-Tree index. Using pageinspect and a pgbench database, it examines index levels, page utilization, indexed value ranges, and block pointers, then interprets the resulting structure and relationships between the index and table. ### Source excerpt I've posted a snippet query to the PostgreSQL Wiki that "summarizes the keyspace" of a target B-Tree index. This means that it displays which range of indexed values belong on each page, starting from the root. It requires pageinspect. The query recursively performs a breadth-first search. Along the way, it also displays information about the space utilization of each page, and the number of distinct key values that actually exist on the page, allowing you to get a sense of how densely filled each page is relative to what might be expected. The query is available from: https://wiki.postgresql.org/wiki/Index_Maintenance#Summarize_keyspace_of_a_B-Tree_index If I use the query against the largest index that results from initializing a pgbench database at scale factor 10 (pgbench_accounts_pkey), the query takes about 3 seconds to execute on my laptop, and returns the following: level | l_item | blkno | btpo_flags | type | live_items | dead_items | avg_item_size | page_size | free_size | distinct_real_item_keys | highkey | distinct_block_pointers -------+--------+-------+------------+------+------------+------------+---------------+-----------+-----------+-------------------------+---------+------------------------- 2 | 1 | 290 | 2 | r | 10 | 0 | 15 | 8192 | 7956 | 10 | | 10 1 | 1 | 3 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 103945 | 284 1 | 2 | 289 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 207889 | 284 1 | 3 | 575 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 311833 | 284 1 | 4 | 860 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 415777 | 284 1 | 5 | 1145 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 519721 | 284 1 | 6 | 1430 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 623665 | 284 1 | 7 | 1715 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 727609 | 284 1 | 8 | 2000 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 831553 | 284 1 | 9 | 2285 | 0 | i | 285 | 0 | 15 | 8192 | 2456 | 284 | 935497 | 284 1 | 10 | 2570 | 0 | i | 177 | 0 | 15 | 8192 | 4616 | 177 | | 177 0 | 1 | 1 | ## The First Ever ReactOS Hackfest! DevFeed: [The First Ever ReactOS Hackfest!]() Original publisher: [Read original article]() Published: 2015-06-20T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Code](), [Wiki]() Tags: [code](), [free](), [germany](), [open-source](), [os](), [react](), [reactos](), [wiki](), [win32](), [winapi]() ### AI overview An announcement for the first ReactOS Hackfest, scheduled for August 7-12, 2015, in Aachen, Germany. It encourages participants to plan their travel and collaborate on coding projects. ### Source excerpt Join us for the very first ReactOS Hackfest from Friday, 7th August to Wednesday, 12th August 2015, in the German city of Aachen. Discover Germany's most-Western city in the direct neighborhood of Belgium and the Netherlands. Within the historical city center, Aachen offers a scientific environment and a high density of pubs. Let's catch this atmosphere to code the week away and achieve great results as a team! It is now time to plan your trip! ## April 2013 Meeting Minutes DevFeed: [April 2013 Meeting Minutes]() Original publisher: [Read original article]() Published: 2013-04-30T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [jira](), [Wiki]() Tags: [changelog](), [dev](), [development](), [free](), [jira](), [open-source](), [os](), [react](), [reactos](), [release](), [wiki](), [win32](), [winapi]() ### AI overview ReactOS developers discussed intellectual property guidelines, the 0.3.15 release, contract-related funding delays, and planning for the 0.4 release. The team considered using resolved JIRA issues for changelogs and creating a more accurate roadmap. ### Source excerpt 2013-04-25 19:00 UTC dev.reactos.org, #meeting Proceedings Meeting started at 19:20 by Aleksey Bragin. Point 1: Legal Whitepaper Point 2: 0.3.15 Point 3: Contracts Point 4: 0.4 Point 1 Ziliang Guo reported that the intellectual property guidelines had been agreed upon with other developers and would be published the coming weekend. Point 2 Ziliang stated that he wanted the release to be out the coming weekend regardless of whether the changelog was complete or not. ## March 2013 Meeting Minutes DevFeed: [March 2013 Meeting Minutes]() Original publisher: [Read original article]() Published: 2013-04-10T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [Google](), [Wiki]() Tags: [bugs](), [development](), [free](), [funding](), [google](), [google-summer-of-code](), [open-source](), [os](), [react](), [reactos](), [release](), [wiki](), [win32](), [winapi]() ### AI overview Meeting minutes from a March 28, 2013 ReactOS development meeting cover Google Summer of Code proposals, a convention report, LinuxTag preparation, foundation funding issues, and debate over the next release version. ### Source excerpt 2013-03-28 19:00 UTC dev.reactos.org, #meeting ProceedingsMeeting started at 19:26 by Aleksey Bragin. Point 1: GSoC StatusPoint 2: CLT ReportPoint 3: LinuxTag BerlinPoint 4: Foundation FundingPoint 5: Release PlansPoint 1Amine Khaldi reported that the Google Summer of Code application had been completed and a preliminary list of project proposals set up on the wiki, with a link to the main GSoC page put on the front page. Feedback from Google indicated that there was nothing wrong per se with the application last year and the project was encouraged to try again this year. ## Notes on index-only scans DevFeed: [Notes on index-only scans]() Original publisher: [Read original article]() Author: Peter Geoghegan (noreply@blogger.com) Published: 2012-11-16T12:31:00Z Content type: article Language: en Sources: [Peter Geoghegan's blog]() Topics: [PostgreSQL]() Tags: [article](), [performance](), [postgres](), [postgresql](), [wiki]() ### AI overview The article discusses index-only scans in Postgres 9.2, which allow certain queries to avoid retrieving table data and potentially reduce I/O. It also notes that the feature has important implementation limitations. ### Source excerpt One of the most important performance features in Postgres 9.2 is index-only scans: the ability for certain types of queries to be performed without retrieving data from tables, potentially greatly reducing the amount of I/O needed. I recently completely overhauled the Index-only scans PostgreSQL wiki page, so that the page is now targeted at experienced PostgreSQL users that hope to get the most out of the feature. My apologies to the authors of the feature, Robert Haas, Ibrar Ahmed, Heikki Linnakangas and Tom Lane, if my handling of the topic seems to focus on the negatives. Any reasonable article about any given index-only scan implementation would have to extensively discuss that implementation's limitations. Any discussion of Postgres index-only scans that focussed on the positives would be much shorter, and would essentially just say: "Index-only scans can make some of your queries go much faster!". ## Website Design Contest DevFeed: [Website Design Contest]() Original publisher: [Read original article]() Published: 2009-08-04T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Website](), [User interface design](), [Web Development](), [ReactOS]() Tags: [browser](), [color](), [design](), [free](), [html](), [javascript](), [layout](), [open-source](), [os](), [react](), [reactos](), [render](), [usability](), [website](), [website-design](), [wiki](), [win32](), [winapi]() ### AI overview ReactOS announces a website design contest seeking original mockups for a new homepage and menu layout. Proposals should align with the ReactOS branding, integrate visually with the forum, wiki, and Bugzilla, and render consistently across several older browsers without requiring JavaScript or browser plugins. ### Source excerpt The task is to create a mockup for a new homepage and menu layout. We want a fresh layout, as the current one is starting to show its age. color scheme should be compatible with the ReactOS logo and the logo included into the design. it should contain a diagram for a simplified frontpage it should also integrate stylistically with the forum, wiki & bugzilla it should render consistently across IE7+, FF2+, Opera 9+, Safari 3+ and without javascript or other browser plugins, though javascript and DOM may be used for optional effects whose absence will not adversely degrade the usability of the site there is no guarantee that your proposal will not be modified if selected any submission must be of an original work by the submitter/submitters (you are free to use the ReactOS logo for the proposal) submitters grants the ReactOS Foundation a royalty-free license to use and/or modify their respective designs, though all submitters retain the rights to their work The best submission will be selected by a jury of five (Aleksey Bragin, Colin Finck, Danny Götte, Ged Murphy and Ziliang Guo). ## Update on ReactOS internals DevFeed: [Update on ReactOS internals]() Original publisher: [Read original article]() Published: 2007-06-07T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [version]() Tags: [bugfixes](), [free](), [improvements](), [open-source](), [os](), [react](), [reactos](), [release](), [repository](), [team](), [update](), [version](), [wiki](), [win32](), [winapi]() ### AI overview ReactOS 0.3.2 will be skipped because of four blocker bugs, with ReactOS 0.3.3 planned for July. The update also reports team changes, repository access grants, Wiki upgrades, and a scheduled RosBE release. ### Source excerpt Update on ReactOS internals 0.3.2 Release ReactOS 0.3.2 is officially going to be skipped (due to 4 blocker bugs), and ReactOS 0.3.3 will be the next in the cycle which, according to the 2 months release schedule, will be released in July. Trunk already has many improvements and bugfixes for 0.3.3, however we are still working on fixing those 4 major issues. Team Alex Ionescu left the ReactOS team to follow an exciting career opportunity working with David Solomon as an official replacement to Mark Russinovich Our best wishes to him at his new position, and a big thanks for all the great work he has done for ReactOS.