Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
community:development:devuan_ascii_roadmap [2017/10/03 21:06]
msi ↷ Page moved from community:devuan_ascii_roadmap to community:development:devuan_ascii_roadmap
community:development:devuan_ascii_roadmap [2017/10/06 17:39] (current)
blinkdog Sync parazyd's latest updates to the roadmap
Line 1: Line 1:
-====== Parazyd'​s ASCII release proposal ​======+====== Parazyd'​s ​New Proposed ​ASCII roadmap ​====== 
 +Due to the streamlining from experimental->​unstable->​testing->​stable not yet being ready, to catch up with Debian we should probably release Ascii the same way we did with Jessie. With Jessie we haven'​t made a patch release (e.g. 1.0.1 or 1.1.0) since the initial 1.0.0 release. IMHO we can leave it like that, but with Ascii we can do these if necessary. What I find more important is the streamlining work so we can be on track with Debian and keep going on with testing and development on Ceres and Beowulf - rather than losing time and nerves with Jessie and Ascii.
  
-Due to the streamlining from experimental->​unstable->​testing->​stable ​not +The Ascii roadmap I wrote after the release of Jessie hasn't received much love and not much progress has been made on itso with this email I will render it obsolete and try getting ​the points below finishedThese should be about enough to make 2.0.0 release, ​and later on, if really needed, ​we can make 2.1.0 and others.
-yet being readyto catch up with Debian we should probably release +
-Ascii the same way we did with JessieWith Jessie we haven'​t made a +
-patch release (e.g. 1.0.1 or 1.1.0) since the initial 1.0.0 release+
-IMHO we can leave it like thatbut with Ascii we can do these if +
-necessaryWhat I find more important is the streamlining work so we can +
-be on track with Debian ​and keep going on with testing and development +
-on Ceres and Beowulf - rather than losing time and nerves with Jessie +
-and Ascii.+
  
-The Ascii roadmap (see below) I wrote after the release of Jessie hasn't received 
-much love and not much progress has been made on it, so with this email 
-I will render it obsolete and try getting the points below finished. 
-These should be about enough to make a 2.0.0 release, and later on, if 
-really needed, we can make 2.1.0 and others. 
  
 ===== General status ===== ===== General status =====
- 
   * outdated packages in Ascii: http://​sprunge.us/​AIeF   * outdated packages in Ascii: http://​sprunge.us/​AIeF
-       * These packages might and might not need updates, but we should figure out if there is some necessary releases to be done regarding security.+    ​* These packages might and might not need updates, but we should figure out if there is some necessary releases to be done regarding security.
  
-  *libsystemd packages in Ascii: http://​sprunge.us/​cfAW +  * libsystemd packages in Ascii: http://​sprunge.us/​cfAW 
-        * These packages shouldn'​t have to be forked at this point, since the library doesn'​t do anything if systemd is not there.+    * These packages shouldn'​t have to be forked at this point, since the library doesn'​t do anything if systemd is not there.
  
-   * banned packages in Ascii: http://​sprunge.us/​ALPE +  ​* banned packages in Ascii: http://​sprunge.us/​ALPE 
-         These packages look fine, and should not need touching.+    * These packages look fine, and should not need touching.
  
-==== init ====+  * files.devuan.org currently doesn'​t have enough space to host both jessie and ascii
  
-sysvinit is still working fine in Ascii. I would propose keeping it this +==== init (DONE!) ==== 
-way, and looking at OpenRC for Ceres first, and then Beowulf.+<del>sysvinit is still working fine in Ascii. I would propose keeping it this way, and looking at OpenRC for Ceres first, and then Beowulf.</​del>​ 
 + 
 +We're keeping sysvinit.
  
 ==== udev ==== ==== udev ====
 +We should try and push eudev as the default hotplugging daemon. It has been working perfectly stable for a while now. Currently it's still in the experimental repos.
  
-We should try and push eudev as the default hotplugging daemon. It has +==== syslog (IN PROGRESS) ==== 
-been working perfectly stable ​for a while nowCurrently it's still in +  ​rsyslog still isn't being built properly ​for AsciiThis breaks default 
-the experimental repos.+  ​debootstrap and locks the Jessie version if a dist-upgrade is being 
 +  doneShould we try fixing the rsyslog package or forcing a different 
 +  daemon like syslog-ng?
  
-==== syslog ====+rsyslog is being fixed by parazyd for ascii
  
-rsyslog still isn't being built properly for Ascii. This breaks default +setup new jenkins build slaves: 
-debootstrap and locks the Jessie version if a dist-upgrade is being +  * one dedicated armhf board 
-done. Should ​we try fixing ​the rsyslog package ​or forcing a different +  * one dedicated armel board 
-daemon like syslog-ng?+  * one dedicated amd64 computer 
 +  * one dedicated arm64 board (by end of the week) 
 + 
 +we can't include them in the CI since nextime'​s VPN doesn'​t quite seem to work and/or we're failing to setup openvpn clients. who can help with this
  
 ==== Xorg ==== ==== Xorg ====
 +Xorg still seems to work if we use the "​xserver-xorg-legacy"​ package. It requires a hack being put in Xwrapper.config that makes it mandatorily run as root if no login manager is present. If a login manager like slim or lightdm are present, it should work just fine.
  
-Xorg still seems to work if we use the "​xserver-xorg-legacy"​ package. It +==== Amprolla (DONE!) ==== 
-requires a hack being put in Xwrapper.config that makes it mandatorily +<​del>​We need to finish ​the new Amprolla setup and force it as the new main package mirror. Amprolla3 is merging ascii-updates and ascii-security,​ which should need no tweaking and should keep working as-is. It has been tested and proven working multiple timeseven before deploying ​it on the Devuan infrastructure. This action point implies fixing and pushing an update to devuan-keyring as well.</​del>​
-run as root if no login manager ​is presentIf a login manager like slim +
-or lightdm are present, it should work just fine.+
  
-==== amprolla ​==== +==== Antofox'​s MATE repos ==== 
- +Can we include Antofox'​s MATE repos in Ascii? Parazyd ​is currently hosting 
-We need to finish the new Amprolla setup and force it as the new main +them on his serverAntofox could benefit a lot from using our CI infra.
-package mirror. Amprolla3 ​is merging ascii-updates and ascii-security,​ +
-which should need no tweaking and should keep working as-is. It has been +
-tested and proven working multiple times, even before deploying it on +
-the Devuan infrastructureThis action point implies fixing and pushing +
-an update to devuan-keyring as well.+
  
 ===== Conclusion ===== ===== Conclusion =====
 +Unfortunately,​ due to the timespan, I feel like these are the only points we should address for this 2.0.0 Ascii release. Again, the reason for this (somewhat radical) approach is to catch up with Debian and not be two years behind. This allows us to keep being a competitor and gives newcomers expected behavior and not two-year-old packages.
  
-Unfortunately,​ due to the timespan, I feel like these are the only +Please, let me know your thoughts and criticisms and let's discuss this in a polite way.
-points we should address for this 2.0.0 Ascii release. Again, the reason +
-for this (somewhat radical) approach is to catch up with Debian and not +
-be two years behind. This allows us to keep being a competitor and gives +
-newcomers expected behavior and not two-year-old packages. +
- +
-Please, let me know your thoughts and criticisms and let's discuss this +
-in a polite way.+
  
-Source: ​[[https://​lists.dyne.org/​lurker/​message/​20170924.110504.106070c4.en.html]]+Source: https://​lists.dyne.org/​lurker/​message/​20170924.110504.106070c4.en.html
 ---- ----
 ---- ----