Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expanding project stages #1

Open
stuartpb opened this issue Jan 14, 2018 · 2 comments
Open

Expanding project stages #1

stuartpb opened this issue Jan 14, 2018 · 2 comments
Labels
model / schema Shortcomings of the project definition structure

Comments

@stuartpb
Copy link
Member

Right now, the stages of a project, as described in the README, are:

0, "Seed": The project is just an idea. It may not even have a name.

1, "Incubating": The project has a name and resources (such as a domain name) secured. It may have some development, but not enough to be usable.

2, "Viable": The project is, at least in part, usable, but is not fully developed or polished.

3, "Polished": The project looks and works as it should.

The final stage being "Polished" on my Trello board is because I'm hesitant to ever describe a project as "Done", under the philosophy that there's always something to clean up, improve, or update; however, going forward, I might want to distinguish between "this project is good, but could still be improved" and "this project was completed, has served its purpose, and no longer needs any work" (essentially like "Forgotten", but for projects abandoned after completion).

I'm not sure if there really is a way to make such a distinction, which is why I'm not making one right now, but this is something to consider going forward, and worth tracking thoughts on for posterity.

@stuartpb
Copy link
Member Author

As mentioned in the README, the nature of "change" makes project changes like this something of a case-by-case question, which is why I started with this as the collective issue for future discussions on the subject.

@stuartpb
Copy link
Member Author

For one thing, not all project changes are different "stages", so this issue title's probably a little off-base from the outset: I'm going to post some more hypothetical issues that touch on project changes that would probably make them essentially devoid of stage entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model / schema Shortcomings of the project definition structure
Projects
None yet
Development

No branches or pull requests

1 participant