In regard to: Re: [oi-dev] component TODO list for perl components?,...:
I've updated TODO list http://docs.openindiana.org/dev/existing-tasks/
some time ago. There are mostly tasks which I'm interested in.
Now I'm looking at removing binary blobs from DDU. Later I'll likely
look at switching it to Python 3.5.
If you can propose any tasks which you can take (or pehaps, someone
else), feel free to update this page. I just don't want it to become a
list of never-done tasks.
Thanks Alexander, and I understand completely about a list of never-done
tasks.
I'll open a pull request with some proposed updates, and you and others
can comment on whether they're a good idea or not.
Tim
________________________________________
От: Tim Mooney <[email protected]>
Отправлено: 24 июня 2019 г. 5:24:33
Кому: [email protected]
Тема: [oi-dev] component TODO list for perl components?
I've been considering packaging the latest stable perl5, 5.30.0, as
perl-530 and then packaging (and in some cases, updating) the perl
modules that are part of hipster, but I want to make certain I'm not
working at cross-purposes to any planned updates for OI and that this
type of update is actually useful.
There's a checklist of small/easy changes to make when updating a
component,
https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/current-tasks.md
but is there a list of the bigger packaging tasks, perhaps prioritized by
need? Obviously people volunteering their time are going to work on
things that interest them, benefit them, and are within their ability,
but at times it would be helpful to know what the most pressing packaging
needs are.
I'm happy to continue choosing components kind of at random to update, but
if I have a list of easy (but perhaps tedious) packaging tasks that are
priorities for update in OI, I would probably attempt some of them as I
have time, especially if it frees up more time for core contributors to
work on the more difficult tasks.
Does a list like that exist? Those types of things tend to go stale fast,
so I understand if there isn't one.
Tim
--
Tim Mooney [email protected]
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
--
Tim Mooney [email protected]
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
