Re: Intent to start ARC investigation git-forge replacement
Hello folks, It has been a couple of weeks since Tomas announced the requirements gathering phase and till now we have received about nine of those - all from Maxwell G (by the way, thanks for your inputs) in the Fedora ARC issue ticket[1]. I want to bump this up to folks' attention and ensure we account for as many usecase requirements as possible. Please take some time and let us know about it as comments under the ticket - multiple comments are totally fine. If you agree with the usecase requirements mentioned in someone else's comment, please use the reactions to let us know of the importance of the same. Please take until 29th May 2024 to communicate your requirements with us. As always, this thread can be responded to if you have any questions or concerns. Index [1] - https://pagure.io/fedora-infra/arc/issue/164 Regards, Akashdeep Dhar (he/him), Red Hat Community Platform Engineering Elected Representative, Fedora Council t0xic0...@fedoraproject.org akashd...@redhat.com TZ = Asia/Kolkata (UTC+05:30) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
MDAPI Rewrite - Out Now in Production
Hello everyone, I hope you are doing well. I wanted to let you know that the rewritten MDAPI is out now in production. You can find the production deployment here[1]. The announcement of the testing deployment made on the staging environment was made previously[2][3]. Please reach out to the project repository[4] for more information, filing issue tickets and contributing. Index 1. https://mdapi.fedoraproject.org/ 2. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KAZOUBVPGV62UKESGNKOTWW554QDEX4Q/ 3. https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/message/KAZOUBVPGV62UKESGNKOTWW554QDEX4Q/ 4. https://github.com/fedora-infra/mdapi Regards, Akashdeep Dhar (he/him), Objective Representative, Fedora Council Red Hat Community Platform Engineering t0xic0...@fedoraproject.org akashd...@redhat.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Testing of the New Staging Deployment of MDAPI
Hi folks, I hope you are doing well. I write this to let you know that I have been working on the MDAPI project under Pierre-Yves Chibon's guidance for some time now for 1. Refactoring the code 2. Implementing code quality standards 3. Adding more comprehensive tests 4. Implementing a CLI wrapper And other major changes The codebase functionality remains the same in this rewrite for users, but I have made attempts to ensure that it becomes relatively easier for the community members to be able to contribute to the project with the addition of documentation, enhancements in code readability and other miscellaneous changes that help improve the contributor quality of life. Once the changes were completed, I moved the repository from my personal GitHub namespace (now archived)[1] over to Fedora Infra's GitHub namespace[2] and deployed it on the Fedora's staging environment[3], with David Kirwan's assistance. Please take it for a spin and test it out so that we can fix as many issues as we can before we deploy it on the production environment. Happy holidays! :) Index 1. https://github.com/t0xic0der/mdapi 2. https://github.com/fedora-infra/mdapi 3. https://mdapi.stg.fedoraproject.org/ Regards, Akashdeep Dhar (he/him), Objective Representative, Fedora Council Red Hat Community Platform Engineering t0xic0...@fedoraproject.org akashd...@redhat.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
CPE Weekly Update for Week 39 of 2022
Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-39-2022/. If you want to receive weekly reports by email in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
CPE Weekly Update – Week 25 2022
Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 20th - 24th June 2022 If you wish to read this in form of a blog post, check the post on the Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-25-2022/ Highlights of the week Infrastructure & Release Engineering Goal of this Initiative The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update Fedora Infra - Most apps have moved over to the OpenShift4 cluster. Hopefully, the transition should be finishing up this week. - Wiki: All upgraded in production and working (thanks Ryan!) - Resultsdb: All moved over to OpenShift 4 in prod and working (thanks Leo!) - Business proceeding as usual CentOS Infra including CentOS CI - Kerberos settings switch for git.centos.org (kcm on el8 vs keyring on el7) for lookaside upload CGI <https://pagure.io/centos-infra/issue/811> [1] - Issue on iad2 hosted reference mirror <https://pagure.io/centos-infra/issue/812>[2] (epel.next and mirrormanager), all fixed now - Duffy CI ongoing tasks and deployments (all announced) - Equinix nodes migration <https://pagure.io/centos-infra/issue/816>[3] (on their request) - Business proceeding as usual Release Engineering - Compose-tracker updated to f36 in staging, production happening tomorrow - Python 3.11 merged to rawhide - MBS randomly fails to process builds - Rawhide compose failures recently (syslinux retirement, then python 3.11 merge) all fixed now - Business proceeding as usual CentOS Stream Goal of this Initiative This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates - CentOS Stream 8: Manually keeping regular RPMs and module RPMs updated on the koji.stream server as current updates are composed and released. CentOS Duffy CI Goal of this Initiative Duffy is a system within CentOS CI infrastructure allowing tenants to provision and access machines (physical and/or virtual, of different architectures and configurations) for the purposes of CI testing. Development of Duffy is largely finished, we're currently planning and testing deployment scenarios. Updates - Release version 3.2.1 - Docs, docs, docs and a Dojo Package Automation (Packit Service) Goal of this initiative Automate RPM packaging of infra apps/packages Updates - Mostly business as usual - Thanks again to all who are reviewing our PRs - Most of our GitHub critical apps are enabled now or close to being enabled Flask-oidc: oauth2client replacement Goal of this initiative Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: - POC working using authlib, tidying up code to prepare to submit a PR back to upstream EPEL Goal of this initiative Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high-quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including a build system, Bugzilla instance, updates manager, mirror manager and more. Updates - This week we have 6442 (+127) packages, from 2882 (+76) source packages - Containerd and puppet retired from EPEL7 because of upstream EOL and multiple CVEs. - Caddy was updated, fixing 4 CVEs in EPEL9 *Index* [1] https://pagure.io/centos-infra/issue/811 [2] https://pagure.io/centos-infra/issue/812 [3] https://pagure.io/centos-infra/issue/816 Thanks and Regards, Akashdeep Dhar (he/him), Objective Representative, Fedora Council Red Hat Community Platform Engineering t0xic0...@fedoraproject.org akashd...@redhat.com ___ devel mailing list -- devel@lists.fedoraproject.o
CPE Weekly Update – Week of October 25th – 29th
Hello, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read in a well-formatted blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-october-25th-29th/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative --- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Updates --- ### Fedora Infra * Freeze breaks: added regions to aws fedimg uploads and fixed a caching issue with upgrade json * Rebooted: proxy34 and bvmhost-x86-07 * Tried to fix move of wiki talk pages, ended up creating PR to disable all talk pages. * At 66 tickets, but many should be closable after freeze ### CentOS Infra including CentOS CI * Kicked some migration for tenants on legacy cluster (nfs-ganesha) * Rebased cico-workspace container to 8-stream (staging) (Ref https://quay.io/repository/centosci/cico-workspace/build/b197513b-0105-4774-a651-89cc4fe8e19d ) * Pushed some new ciphers in prod through ansible role to get A+ cert on Qualys (Ref https://www.ssllabs.com/ssltest/analyze.html?d=git.centos.org=on ) * Mirrormanager tuning with Adrian for 9-stream inside CI infra (Ref https://admin.fedoraproject.org/mirrormanager/host/2751) * Added/announced aarch64 as covered architecture for CI infra tenants ### Release Engineering * F35 RC-1.2 is out and can be found at https://dl.fedoraproject.org/pub/alt/stage/35_RC-1.2/ * Business as usual ## CentOS Stream Goal of this Initiative --- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates --- * Basic Stream/RHEL Buildroot reporting is in place, thanks James! * Open discussion on pruning older packages from what we publish to the mirrors * Open discussion on the impact of consolidating the Stream 8 and Stream 9 workflows for maintainers * Business as usual ## CentOS Duffy CI Goal of this Initiative --- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates --- * Set up a boilerplate with a skeleton application * Set up the CI in the repository with tests and coverage * Created a CLI for configuring parameters * Discussed workflows and methods for implementing models ## FCOS OpenShift migration Goal of this Initiative --- Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly deployed fedora infra OCP4 cluster. Updates --- * Obtaining access on the cluster * Creating playbook to create OpenShift resources * Got the cluster updated and ready Thanks and regards, Akashdeep Dhar t0xic0...@fedoraproject.org akashd...@redhat.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
CPE Weekly Update - Week of October 04th 2021
Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on `#redhat-cpe` channel on libera.chat. - If you wish to read this in rendered markdown, check the post on discussion link https://discussion.fedoraproject.org/t/cpe-weekly-update-week-of-october-04th-2021/33558 . - *As October is the new quarter, we are about to overtake new projects, there are no new updates on non-rolling initiatives[0].* - *CentOS Stream team is continuing with their work:* - The work on the Mirror Manager has been completed - The work on the Automated Signing has been completed - Automatic Signing was broken on Monday night - Working on batch resigning packages still - Completed our October planning - aiming to work on - Content Resolver Docs - Compose Reporting - content changes between RHEL9/Stream 9 - Forming a plan of record for the work needed to align Stream 8 and Stream 9 workflows in the future - Technical debt movement - Jenkins updates, old image cleanups, etc. - *Infra and releng continues to take care of day to day business as initiatives team members are working with them to handover SOPs and maintenance tasks:* - *Fedora Infra* - 23 issue tickets were closed this week - Unfroze after beta and then froze again for F35 final - Merged a ton of pull requests that were pending - We have a possible fix to the sssd auth issues, many thanks sgallagh! - Updated all the proxies, including for the latest httpd CVE - Tracked down openQA worker instability to a kernel bug - We now have backups locally on netapp for Weblate content - *CentOS Infra* - Collaboration with Artwork SIG for new CentOS Stream 9 theme that will be pushed at release day. Preview at https://www.dev.centos.org and https://lists.dev.centos.org - CentOS Plus repo being worked on as a SIG (same process) through Core SIG (new GPG public key) and so building for Stream 8 (and eventually later Stream 9) on cbs.centos.org - Business as usual: - Sponsors leaving (decommissioning nodes in infra) - Relocate some services - Progress on the blocker for Stream 9 tests in CI - *Release Engineering* - Staging Bodhi deployment 5.7.1 - F35 final freeze - Removal of bot form `#releng` channel will happen after the freeze [0] With the rolling initiative, we mean the initiatives that will take longer than one quarter and they are not affected by the quarter cycle. That’s all of this week :) Kindest regards & on behalf of the CPE team, Thanks and regards, Akashdeep Dhar t0xic0...@fedoraproject.org akashd...@redhat.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Join us at our Fedora Websites and Apps Meet-up - 1330hrs UTC Every Friday
Hello everyone, I write this mail to let you know about the very recent developments that took place which led to the revamp of the previous Fedora Websites, as the new Fedora Websites and Apps team as well as to invite you to our weekly meetings that helps shape our objective. You can find more about the discussions that led this to happen over at https://pagure.io/mentored-projects/issue/85 and https://discussion.fedoraproject.org/c/project/websites/66. Support from the infrastructure team and from all over the Fedora is valuable for us to realize the objectives stated in our https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Community_Revamp draft so please feel free to join us over at #fedora-websites:matrix.org. We have a weekly meet to discuss progress and plans every Friday, 13:30UTC at https://meet.jit.si/fedora-websites-apps-meeting and everyone is welcome! Thanks and regards, Akashdeep Dhar t0xic0...@fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Ars claims: Fedora 32 is sluggish
Hey Matthew, Could you please try switching to a much stronger CPU governor like `performance` and see if it helps? You could use this tool https://github.com/t0xic0der/switcheroo and run `sudo ./switcheroo -setn performance` to do so. Regards, Akashdeep Dhar ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Ars claims: Fedora 32 is sluggish
This was once discussed here in Ask Fedora https://ask.fedoraproject.org/t/how-to-increasing-performance-by-changing-cpu-governor-and-reducing-swappiness/10006 and there's an ongoing investigation regarding the same here https://pagure.io/fedora-workstation/issue/212. You would want to check both to stay posted about the updates regarding this issue. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Proposing Container Performance Monitoring Toolkit for Podman - Need Review
Hey folks, I write this to let you know that there has been this decoupled container performance monitoring toolkit that I have written for Docker, which you can find here https://github.com/t0xic0der/supervisor-driver-service (the API service) and here https://github.com/t0xic0der/supervisor-frontend-service (the web frontend). I am proposing a Podman counterpart of it with improvements and bug fixes to it as a project to be developed to complement Podman by providing a monitoring tool with easier learning curve and effective usage. You can find the links to the screenshots here https://github.com/t0xic0der/supervisor-driver-service/wiki/Screenshots (the API service) and here https://github.com/t0xic0der/supervisor-frontend-service/wiki/Screenshots (the web frontend) if you're all packed but you are requested to kindly review this idea on the basis of its need, efficacy and implementation. You can find the proposition ticket here https://pagure.io/mentored-projects/issue/95 if you wish to directly comment there. Thanks in advance! Looking forward to your responses. Regards, Akashdeep Dhar t0xic0der ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Requesting Review for Fedora Easyfix Modernization PR + Active Tagging of Issues With Easyfix
Hello folks, I write this to request review of the most recent PR https://pagure.io/fedora-gather-easyfix/pull-request/9 made to modernize the overall experience and functioning of the site. The changelog is listed in the PR body includes rewrite of the template in Bootstrap 5, in-page active searching using Javascript, adding placeholders to template logic, removal of obsolete JQuery and Bootstrap assets and much more. The logo design is requested at https://pagure.io/design/issue/714 and the design is put to review at https://pagure.io/design/issue/715 too. With that, I also wish to note that being Easyfix an entrypoint to the community to a lot of new contributors - who feel like they can get started quickly by solving self-contained and well-documented issues - there should be an added attention to tag issues with Easyfix whenever they come under the above classification. It is understandable that there are multiple projects with tasks that could use a greater involvement but there can also be some issues, if you look closely, that you can pass on to someone who is relatively new to the project. Feel free to discuss about the same in the thread. Thanks and regards, Akashdeep Dhar t0xic0der ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Syngrafias - AsciiDocs Collaboration Tool for Fedora Documentation Maintainers, Available for testing
Hello, The suggestions made here https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/message/CXXZ6YIL22Y34SIFT6XWK3DL3FD5VCLF/ and https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/message/ZWSKCQ2BQD4UZJAKEDNREF3FX6RVCDAR/ are taken into account in the most recently made PR https://github.com/t0xic0der/syngrafias/pull/94. Feel free to take a look at it. Regards, Akashdeep Dhar t0xic0der ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Syngrafias - AsciiDocs Collaboration Tool for Fedora Documentation Maintainers, Available for testing
Hey Matthew! > This is super, super cool! We are so glad to know that you liked the idea. :) > One suggestion I have is to start in the simpler "Unity" mode rather than > the "Cellular" one by default. Also, in the Cellular one, provide a button > or something to add a new cell rather than requiring the menu item -- it > took me an embarrassingly long time to figure out how to start typing. Noted. We would make the "Unity Mode (ADOC)" as the default and give users the choice to move on to a much more sophisticated "Cellular Mode". Also, in order to add cells we are working on "Tabs UI" that we would love for you to take a look. You can find the preview of it here at https://github.com/t0xic0der/syngrafias/pull/87#issuecomment-752829071 and this makes adding cells and working on them a breeze. > As an end-state goal, I'd love to so anyone clicking "edit" on a page on > the > docs site got this editor! Sounds like an awesome plan to me. What do you say @nasirhm? Thank you for taking the time out to review the public preview and suggesting the changes. Wish you a very happy 2021! :D Regards, Akashdeep Dhar t0xic0der ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Syngrafias - AsciiDocs Collaboration Tool for Fedora Documentation Maintainers, Available for testing
Hey Benson, Thank you so much for taking some time out to check the public preview. > Nice. Consider using a > temporary domain name for this. For example from > Freenom. We are considering a domain name for it and would surely keep you posted, should we obtain one. > Are there any similar tools in other languages (Go, Rust, Crystal)? > Python runtime includes heavy batteries, so not great for underpowered > instances, though useful for rapid development. There are libraries for websockets in Go but with much divisive community support for each. When it comes to Python, we are using the excellent websockets library created by @aaugustin. (But yes, we are keeping our eyes on a Go rewrite down-the-line for speedup and efficiency should the Python implementation feel heavy) > A link to an Asciidoc cheatsheet maybe a good > tip to have. Examples include: > https://powerman.name/doc/asciidoc > https://www.writethedocs.org/guide/writing/asciidoc/ > One could also create one, but the tips and documentation section seems > not to be currently available at > https://github.com/t0xic0der/syngrafias We do have general usability documentation as a part of the help and support topics which was introduced as of https://github.com/t0xic0der/syngrafias/pull/88 but adding an Asciidoc cheatsheet sound like an awesome idea. I have filed a feature request ticket here at https://github.com/t0xic0der/syngrafias/issues/91 which you can track for your reference and this would be prioritized. Thank you for taking your time out to review the public preview and suggesting the changes. Wish you a very happy 2021! :D Regards, Akashdeep Dhar t0xic0der ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Proposed Project for GSoC - Unintrusive Synchronized Authorship Web Application
Hi folks, Akashdeep/t0xic0der here. I would love to hear what you think about a project that I am proposing for Fedora's representation in this year's Google Summer of Code. Take a look at the following excerpt which was taken from the proposition I wrote (Check issue https://pagure.io/mentored-projects/issue/85 of mentored-projects for the entire content and the conversation regarding it). - There has been this web application I have been building a functional prototype for, which allows for synchronized authorship of documents in an unintrusive manner. The project is called Syngrafias. - To explain this in a better way, people who have used Google Docs for editing documents collaboratively know how the changes made to the document are actively synchronized to all the collaborators during the time of editing. Syngrafias does that but with a much more distributive approach to it - as here the changes made in the document in the absence of the other user would not be synchronized, thereby seamlessly creating (say) a fork of the same document. ([See the attached image collabnt.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/master/pictures/collabnt.png)) - The unintrusiveness in the document editing can be better explained if I draw parallelism with Jupyterlab. Just like in Jupyterlab, we have distinctive cells here for editing text. It is a simple mechanism but with much greater functionality as it allows you to selectively share the parts of the document you want collaborators to edit and rearrange the parts of the document by simply using a drag-n-drop operation. I have added in Summernote for WYSIWYG editing for each cell. ([See the attached image opendocs.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/master/pictures/opendocs.png)) - Of course, there is activity tracking so any change in the document title, cell title or cell content gets logged and activities like cell creation and removal are synchronized across all connected clients. The way I see it, this project can bring about radical positive changes to the way Fedora's project documentation are worked upon collaboratively. Also, if I simply replace Summernote with CodeMirror - this can even be used for collaboratively editing code snippets on-the-go. ([See the attached image activlog.png](https://raw.githubusercontent.com/t0xic0der/syngrafias/master/pictures/activlog.png)) - With 57 commits as of the time of writing the idea description, the project is only getting started and only the bare functionalities of the project are complete. You can find the repository [here](https://github.com/t0xic0der/syngrafias), the usage instructions [here](https://github.com/t0xic0der/syngrafias/wiki/Usage) and the screenshots [here](https://github.com/t0xic0der/syngrafias/wiki/Screenshots). There are tons that we can expand upon if this ends up becoming a project for GSoC. I would very much love for you folks to try out the project, let know what you think about it and your valuable suggestions for it to become a GSoC project - if it can. I would be obliged. The reason why I wish to propose this (outside) project for Fedora's GSoC representation is because it has the potential to be a project assisting the distro/community (e.g. Bodhi and Mote) by making the process of documentation creation much more efficient and conveniently collaborative (as compared to the Pagure and Antora-bound method that we use right now). Do note that the project (I believe) aims to complement the tried-and-tested systems in place as of now with the features it has (and plans to have). The way I see it - the project I am proposing here can complement to Antora's functioning by cutting down on the mandated build times to generate a preview (as we have a WYSIWYG feature) and deferred collaboration (highly subjective though as active synchronization would mostly benefit only those who are living at the same timezone and decide to work together for the same time). I cannot emphasize enough how beneficial it can be to try out the project prototype to understand how capable the project can be. You can find the [project page](https://github.com/t0xic0der/syngrafias) and the [project wiki](https://github.com/t0xic0der/syngrafias/wiki) links here. (or drop a response expressing willingness for a demonstration and maybe, we can schedule a video meet ;-)) As the proposed project marks a departure from the kinds of project that were used to be proposed for GSoC, it would be vital for me to know what you think about the proposed idea and the likeliness of adoption of the ideas stated in the project. How effective do you think it can be (if it can be selected as a GSoC project) and what can be done to make it better? Thanks in advance. Looking forward to your responses. Yours faithfully, Akashdeep Dhar ___ devel mailing list -- devel@lists.fedoraproject.org
