I will state what my personal goals are for the project if it gives perspective:
Building a Debian package (1st priority!)
Cutting out cruft (OS support for OSs that have no chance of ever being 
revived, and have no active maintainers, honestly if we could've found active 
maintainers for the OSs I removed I would not have removed them. etc.) While 
maintaining an intact CDE toolset
Fixing warnings and other issues
Keeping things within standards (POSIX, FHS, etc.)
Adding modern functionality without the resource requirements of the modern day.

Basically, having an "up to date", 90s desktop. I've always hated new UI 
decisions, and would like a desktop that is from the 90s but is still up to 
date.

Every other desktop has its own tools, I see no reason we should remove them, 
as they are somewhat historical, and should be maintained (unless they are 
absolutely useless like that one daemon that Doug mentioned...) lest become a 
copy of gnome.

​Thank you for your time,

-Chase​

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On June 20, 2018 7:46 PM, <d...@blackshard.net> wrote:

> ​​
> 
> > As for dtudc*, why? Who needs it?
> 
> > If you really want it, there is no reason it could not just be
> > 
> > maintained outside of CDE as a separate project -- just requiring a
> > 
> > X11/Motif/CDE dev environment to build.
> 
> Is there some strong reason we need to kill it? I understand why there
> 
> might not be priority for others to fix it, but if I were willing to
> 
> repair it, can it stay? I don't know anything about this component
> 
> personally, but I'd like to see the traditional CDE toolkit and
> 
> application base stay intact where at all possible.
> 
> Separate maintainership is one possiblity, but I have reservations
> 
> regarding splitting up the CDE codebase...
> 
> > TBH, I'd like to get rid of dtmail as well, unless someone wants to
> > 
> > drag it into the 21st century.
> 
> Okay, definitely I want dtmail to stay. Yes, it needs some help.
> 
> Completing the IMAP support would go a long ways. It's on my list of
> 
> items to attend to; I can try to bump it up in priority.
> 
> > Besides, there are far better font editors out there, if that's your thing.
> 
> Some people would undoubtedly argue that there are far better (more
> 
> capable, modern, etc) desktop environemnts out there. Obviously, some
> 
> of us still care about this one, undoubtedly for a variety of reasons.
> 
> So I guess this is a reasonable time to ask, what is your vision for the
> 
> CDE project? Do you want to maintain this legacy product as-is, keeping
> 
> it alive? Do you want to modernize it somehow? Do you want it mainly
> 
> to serve the purposes of the developer base here, and people who don't
> 
> want to let go of their old familiar environment? Do you want to stage
> 
> a coup and overthrow Gnome/KDE/Unity? =)
> 
> I know those are broad questions, I'm just wondering what you're
> 
> thinking in general; if there's a master plan, or what. This type of
> 
> question is important, I think, when considering things like platform
> 
> support, and which programs we want to maintain.
> 
> -mrt



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to