I'd be happy to contribute what I could, not sure what I would do. Maybe a few GUIs, make a few PETs, testing, etc...
Just thought I'd post my 2 cents while everything is still up the in the air... For the next Puppy, here's a few things I was thinking about:
- Firstly, I do not want us to jump the gun. Let Lucid lie for a while, other developments will come along with Wary, Quirky, etc, that we will want to have a look at.
- I do not want too many confusing, concurrent project names, like luci, lucid, lupu, saluki, etc
- I do not want two concurrent version numbers for each build (or any fork of) that gets made (6.0 already referred to as 5.3, above)...
- I want to see us start with 6.0 alpha1, then 6.0 alpha2, alpha 3.. then 6.0 beta1, beta2, beta3... then 6.0 RC1, RC2, RC3... Then Puppy 6.0! Then 6.1 alpha1, 6.1 alpha2, 6.1 beta1, 6.1 RC1, etc, then finally Puppy 6.1.... It's easy. for everyone this way, right?
- I do not want ANY menu entries for apps that work with only 1 specific WM! A JWM settings app in the menu, when we use XFCE, for example..
- If you put any items into the menu that require a specific WM, better make sure they are removed or hidden, if the WM is not in use.
The above 'issues' make following development harder for those with less knowledge and/or time.
Size:
- locales and stuff in separate SFS, easy installer of extra lcoales, linked with firstrun or something
- I want the vesa only Xorg (idea from Quirky) as standard - if it works nicely.
- I want under 100mb, or under 110mb or so, if possible. But with the zdrv_cutr and OTF SFS loading, we should really be talking about a starting size... Puppy should be VERY easy to grow or shrink as required!!
- I want conservative lib versions, where we can get away with it - to increase backward compatibility
- I want a zdrv, so I can reduce the modules needed later. Ttuuxxx posted on the BK blog some good ideas about going further than the 'zdrc_cutr'.
- I want technosaurus and goingnuts to look at making thigns less resource intensive as small and lightweight as possible.
- Ttuuxx and Barry K should be listened to about keeping compiled packages smaller - we should compile our apps whenever possible, not steal from ubuntu.
Features and Apps:
- RDP! working out of the box
_ also prefer xarchiver to xarchve
- I want a CLI package manager!
- I want OTF SFS loading
- I want a simple "dir2pet" type thing, that automatically separates and builds the pkg, and its DEV and NLS pets. Igu has done something abotu this already , I think...
- Knowing the exact names of the deps to include when building a PET is not easy. I want to have a tool that gives me a list, or choice, or helps me in some way!
- About security, MU posted a BASH script to generate random MAC addresess, this could be combined with my MAC-Changer GUI to give random MAC addresses at boot.. If anyone wanted it
- I want ALL of the PETswe make to install not only themselves but their deps as well - this is usually not the case (see above)
- I want my default-apps-chooser thing to be included (or similar).
- I want shinobars internationalisation and localisation work to be included as much as possible.
- I want only 1 menu entry to 'Set Wallpaper' or 'Edit Taskbar' (etc), NOT specific to a particular WM - load up some Puppy scripts that detect the WM and run the relevant wallpaper changer, or menu config, etc
- I want bigbass to look at the package management, see if we can make it more 'standard', and remove 'built ins' very easily.
- I want maybe an optional HUGE devx, including nearly everything we got, to make compiling stuff on Puppy as easy as on other distros. At least put src2pkg in the devx.
I know I don't know as much about any of this as most people, but thought I'd share my thoughts... As I contributed literally nothing to Lupu, except the Advert Blocker thing...