Ticket #565 (new roadmap)

Opened 6 years ago

Last modified 5 years ago

remove optional features from default config, refactor config probes

Reported by: coke Owned by:
Priority: normal Milestone: 3.0
Component: configure Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Change History

in reply to: ↑ description ; follow-up: ↓ 2   Changed 6 years ago by jkeenan

Replying to coke:

From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.

1. That link no longer links to a page with relevant data.

2. The ticket is too vague and general to be actionable at the present time. Every 'optional' feature in our configuration system was added because, at some point in our past, some committer felt that the 'default' features were insufficient. In fact, lacking an overall PDD for configuration, we have no definitive guide as to what Parrot's configuration process must discover about a host machine, what it would be nice to learn about a host machine, etc.

3. Assuming that we do add specificity to this ticket, we should discuss where it stands in relation to TT #619, subsequently filed by Allison.

in reply to: ↑ 1 ; follow-up: ↓ 3   Changed 6 years ago by coke

Replying to jkeenan:

Replying to coke:

From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.

1. That link no longer links to a page with relevant data.

I copied all the relevant information (to wit: the summary) from the note on that page here. I was merely moving the placeholder task into a ticket so the wiki page could eventually be replaced with a query against our ticketing system. You'll find several such empty tasks with little or no details in the system which need to be fleshed out by whoever got them added to the roadmap in the first place.

in reply to: ↑ 2   Changed 6 years ago by jkeenan

Replying to coke:

I was merely moving the placeholder task into a ticket so the wiki page could eventually be replaced with a query against our ticketing system.

... which I appreciate. I have queries set up for Trac tickets that I run more times each day than I care to admit, but I rarely go to the 'pure' wiki pages at our site.

Over the past 3 years, I have found wikis useful for preparing for events like hackathons because they enable me to list what we'd like to accomplish and then list what actually got accomplished. But they're not as queryable as a ticketing system and a cage cleaner, as a de facto assistant project manager, needs to be able to query the state of the project at any time.

Thank you very much.
kid51

  Changed 6 years ago by allison

  • priority changed from normal to critical
  • milestone changed from 1.2 to 1.3

  Changed 6 years ago by allison

  • priority changed from critical to normal

  Changed 5 years ago by allison

  • milestone changed from 1.3 to 3.0

I'm moving this ticket to the 3.0 milestone, as it's really a part of TT #619.

  Changed 5 years ago by jkeenan

  • component changed from none to configure
Note: See TracTickets for help on using tickets.